RE: Using SMS 2003 to fix svchost/WindowsUpdate issue

So, you're NOT deleting the Windows\SoftwareDistribution folder and contents?

We found that, on some computers, we could NOT install the Client update,
until after we disabled both services, and rebooted (since you use ADS to
KEEP yours disabled, that's probably why it worked for you). Since there
were enough machines with this problem, I just decided to disable and reboot.

I think I'm going to have to end up with two tasks--one to disable and
reboot, and the second one to install the two programs (triggered on the
first task already happening).

Thanks.

"Mykhaylo" wrote:

Bill,

We've just done actually the same process. I created a bat-file with content
for Windows XPx86 machines:
WindowsXP-KB927891-v2-x86-ENU.exe /quiet /norestart /log:c:\wsus3.log
WindowsUpdateAgent30-x86.exe /wuforce /quiet
cscript wsusreporting.vbs
and located all needed files in one directory, created SMS package program
to run this bat-file after download source files and advertised it to
appropriate collection.

The last VB script, which is run after two updates is to report the results
to specific log repository.

We didnt use disable Automatic Updates service, since we had this service
disabled by AD Group Policy since that time we faced svchost.exe issue.

BTW, as far as i know WU Client 3.0 sets Automatic Updates service to
automatic mode by default.

We didnt let the systems reboot, since all our client systems systems log
off or restart within a few days anyway.

-Mykhaylo

"Bill Bradley" wrote:

I was going to use a batch to do the following on computers having the
svchost/WindowsUpdate issue:

1. Disable Automatic Updates and BITS Services, reboot.
2. RD c:\windows\softwaredistribution
3. Install WU Client 3.0 using /quiet /norestart /wuforce
4. Install Patch V3 using /quiet /norestart
5. Set Automatic Updates and BITS Services to Automatic, reboot.

# 1 is stumping me--how can I start this running, force a reboot, then pick
it back up? Do I need to use two batches, and link the programs, or, is
there a more elegant way.

If I link the programs, how long will it take the second to run, after the
first one does?

Thanks!



.

Relevant Pages

  • RE: Using SMS 2003 to fix svchost/WindowsUpdate issue
    ... you're gonna create two package programs then advertise one and the ... We found that, on some computers, we could NOT install the Client update, ... were enough machines with this problem, I just decided to disable and reboot. ... We didnt use disable Automatic Updates service, ...
    (microsoft.public.sms.swdist)
  • Re: Using SMS 2003 to fix svchost/WindowsUpdate issue
    ... you're gonna create two package programs then advertise one and the ... We found that, on some computers, we could NOT install the Client update, ... reboot, and the second one to install the two programs (triggered on the ... as far as i know WU Client 3.0 sets Automatic Updates service to ...
    (microsoft.public.sms.swdist)
  • Re: Data loss in Word after automatic reboot
    ... Don't allow Automatic Updates to run in full Auto mode. ... The reboot happened while I had left the computer for a few ...
    (microsoft.public.word.application.errors)
  • Computer Name.
    ... I was setting up three WIndows XP machines for a client. ... all updates and patches), we began to apply MS updates and Service Packs. ... the activation period was 22 days - which is correct. ... Now a reboot and VOILA back to "My Computer". ...
    (microsoft.public.windowsxp.general)
  • Re: WSUS doesnt see client
    ... Software Synchronization Windows Update Client failed to detect with error ... and the server has "Not yet reported" for the client. ... subject to the GPO (Automatic Updates options grayed out). ... Computer, properties), on the Automatic Updates tab, is everything ...
    (microsoft.public.windows.server.sbs)