My first guess would be that a lot of your client have been deployed from an
image by Ghost or something similar. If the master image is not done correctly
(and a great number of posts here prove that many are not) then a registry key
called SUSClientID gets duplicated to each client and it MUST be different on
each client. The principal symptom you will notice is that PCs are displayed in
the WSUS console and then disappear and others turn up in their place.
see
http://support.microsoft.com/kb/903262
You will find many scripts to help fix this but I first recommend fixing it
manually to be sure this is the problem.
On Tue, 9 Dec 2008 10:58:56 -0500, "PA Bear [MS MVP]" <>
wrote:
>[[ Right pew, wrong church. Forwarded to WSUS newsgroup
>(microsoft.public.windows.server.update_service s) via crosspost as a
>convenience to OP.
>
>On the web:
>http://www.microsoft.com/communities...pdate_services
>
>In your newsreader:
>news://msnews.microsoft.com/microsof...pdate_services
>]]
>
>Gloria wrote:
>> I am new to WSUS, and having trouble with the reporting. The reports on
>> the
>> server show a total of approx 1300 pcs, but we actually have about twice
>> that. We are using Group Policy and I have verified that the devices are
>> in
>> the correct group. Some of the devices are definitely receiving the
>> udpates
>> so I know they are able to contact the server, they just aren't showing up
>> in the reports. I have run the client diagnostic tool, everything looks
>> ok.
>> The windowsupdate.log shows that the device is contacting the server. I
>> have tried resetting the client. I would appreciate any assistance or
>> hints.
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.