Re: Odd WSUS Client Check In Behavior

"Mitch" <> wrote in message
news:dd47c215-a4e1-4c42-87a4-...
> I've run out of ideas on what might be causing this behavior so I
> figured it was time to ask the question in a broader forum.
>
> I've got a WSUS 3 SP1 server, newly installed, and I'm using Client-
> side Targetting to sort the client machines into specific groups.
> Most of the client machines are behaving as expected but one batch
> does not appear in the console group as the others. There are about
> 40 machines but only one device will appear at a time.

This is classic behavior caused by duplicate SusClientIDs, which is
generally caused by machines cloned from a master image which already has a
SusClientID.

> If I refresh the container a different machine is displayed.

Could be coincidental. Usually the different machine occurs because another
of the 40 machines has executed a detection/reporting event. By default,
statistically speaking, a group of 40 machines would have one machine
detecting/reporting every 33 minutes.

To isolate this -- pick one machine, navigate to this key in the registry:
HKLM\Software\Microsoft\Windows\CurrentVersion\Win dowsUpdate
and delete the SusClientID and SusClientValidationID values.

Restart the Automatic Updates service (net stop/start wuauserv).

Force a new detection (wuauclt /resetauthorization /detectnow),
wait 5 minutes and force a reporting event (wuauclt /reportnow).

Observe the WSUS console -- if you now have *two* machines, one being the
machine you just 'fixed', then you've identified the problem, and you merely
need to repeat this procedure on 39 other systems. (You'll also want to
build a new master image without the SusClientID.)

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin