Re: WSUS v2 client and high CPU fix

Tech-Archive recommends: Fix windows errors by optimizing your registry

I really only run Microsoft's BSA for verifying the security aspect. But
it's reassuring to confirm that programs are doing what they profess to do,
so its double check of needed updates (as well as running Shavlik - which I
prefer any day to wsus) is still of value.

David

"Les Connor [SBS MVP]" <les.connor@xxxxxxxxxxxx> wrote in message
news:D9FDDFA5-FAFF-47EE-8DAA-EF14E322B8EE@xxxxxxxxxxxxxxxx
Thanks. I don't use anything other than WSUS ;-). It either works -
completely - or it's of no use at all if another app has to check up on
it.

--
Les Connor [SBS MVP]


"David" <abc@xxxxxxxxx> wrote in message
news:e3LUThDkHHA.1240@xxxxxxxxxxxxxxxxxxxxxxx
Just a heads-up!

A side-effect of installing the v.3 client Update Agent, is that the
current v.2.01 Microsoft Baseline Security Analyser fails to scan
workstations for missing update patches.

David

"Les Connor [SBS MVP]" <les.connor@xxxxxxxxxxxx> wrote in message
news:68D4329C-2AC5-4B37-B006-52E970F5FC03@xxxxxxxxxxxxxxxx
Glad it worked as expected.

As an FYI, many of the SBS MVPs tested this client and provided direct
feedback to MS. SBS Dev has taken this issue (and others) seriously and
pushed the WSUS folks very hard on our behalf to get a resolution. If
you run into Paul Fitzgerald, a senior from the SBS Dev team, you can
personally thank him for his efforts on this, and other things he's
working on to specifically resolve issues on SBS that have shown up as a
direct result of recent changes to underlying parts.

--
Les Connor [SBS MVP]


"David" <abc@xxxxxxxxx> wrote in message
news:uWDOd8%23jHHA.4676@xxxxxxxxxxxxxxxxxxxxxxx
Took a chance and applied the v.3 client on PCs last night/today and
confirmed the findings. All of the PCs already had the
KB927891/KB916089 fix applied - so I don't know if that makes a
difference.

The new v.3 client appears to delay the initial firing off, so log-on
is not as problematic. On a Pentium-M 1.8MHz laptop, CPU usage for
that instance of svchost was 3-seconds at log-on after a restart with
peak memory usage of 29MB. When the wsus client fired off about
15-minutes later, it ran for 65-secs, peak memory of 135MB, usage of up
to 99%, but the laptop was still responsive. It fired off again about
an hour later for 103-secs, but once again didn't cause too much of a
problem.
Similar story with a Dual 1GHz P-III workstation. Delayed initial
fire-off, and then although it still fires off for 60 to 100-secs at
under hourly intervals, the system was not too unresponsive. Peak
memory 122MB, usage of over 50% (dual CPUs though).

All in all, confident enough to risk spoiling client's public holidays
to get them to turn on all their office PCs so I can deploy the patch.

Thanks for the help!
David

"Les Connor [SBS MVP]" <les.connor@xxxxxxxxxxxx> wrote in message
news:2919B98C-04D0-46C2-BD91-BA39ECEE0B31@xxxxxxxxxxxxxxxx
I never liked that name 'Celeron'. My every-day laptop is getting quite
crusty - Pentium M 1.3.

In today's computing environment it's only just tolerable. I'm sure
I'd quit if it was a Celeron.

--
Les Connor [SBS MVP]


"Owen Williams [SBS MVP]" <Owen@xxxxxxxxxxxxxxxxxx> wrote in message
news:MPG.20a71bd5507b762b989a30@xxxxxxxxxxxxxxxxxxxxx
In article <FCDA24EE-2FEE-4CBD-BBF5-429A755BBD0C@xxxxxxxxxxxxx>,
les.connor@xxxxxxxxxxxx says...

Yes, I've deployed the new WSUS client, and it performs as
advertised. The
high CPU is still there, but the machine remains responsive,
although it's
still affected during the 90 seconds or so the detection takes to
complete.

Just wanted to add to Les' response ... The "90 seconds" figure is
machine-dependent. On slower machines, especially Celerons, the time
may be much longer. I have one laptop where the CPU spikes for 8 to
16
_minutes_. The new client was a BIG help on that puppy, I can assure
you!

-- Owen Williams (SBS MVP)









.

Relevant Pages

  • Re: Warning: Beware of Office 2003 Service Pack 3
    ... Les Connor [SBS MVP] ... client has a bank that sends a credit-card account file to an internal ... Very annoying to my client. ...
    (microsoft.public.windows.server.sbs)
  • Re: Warning: Beware of Office 2003 Service Pack 3
    ... Les Connor [SBS MVP] ... Very annoying to my client. ... And she doesn't feel like telling Bank of ...
    (microsoft.public.windows.server.sbs)
  • Re: SVCHOST 100% CPU - Process hog wuaueng.dll
    ... Les Connor [SBS MVP] ... Find the PID for the particular svchost process that's using high CPU, ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS v2 client and high CPU fix
    ... A side-effect of installing the v.3 client Update Agent, ... v.2.01 Microsoft Baseline Security Analyser fails to scan workstations for ... Les Connor [SBS MVP] ... high CPU is still there, but the machine remains responsive, although ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS v2 client and high CPU fix
    ... many of the SBS MVPs tested this client and provided direct feedback to MS. SBS Dev has taken this issue seriously and pushed the WSUS folks very hard on our behalf to get a resolution. ... Les Connor [SBS MVP] ... CPU usage for that instance of svchost was 3-seconds at log-on after a restart with peak memory usage of 29MB. ...
    (microsoft.public.windows.server.sbs)