WSUS SusClientId problem

We have a network of 300 Windows XP SP2 machines. All have been deployed
using Sysprep (Reseal) and Ghost. All of the machines (as far as I can tell)
are receiving updates from the WSUS server, however only 200 are visible on
the WSUS console. I have checked 2 of the invisible computers, following the
leads in articles about SID problems on TechNet. I found that on the 2
offending machines, the AcountDomainSID's were UNIQUE, the PingID's were
UNIQUE but the SUSClientId's were the same. What does this mean in terms of
our image deployment? I was under the impression were using SysPrep
correctly (the machines are all domain members). Could this mean that the
image machine connected to the SUS/WSUS server before it was SysPrepped? Is
there a painless way of correcting this situation without visiting 100
machines or upsetting the 200 machines that are already registered? (I know
this sounds like the best of both worlds!) TIA

Hi,

Fyi:

Please post WSUS related issues to the newsgroup dedicated to WSUS:
microsoft.public.windows.server.update_services

WebNews link to the WSUS newsgroup:
http://www.microsoft.com/communities...pdate_services




--
torgeir, Microsoft MVP Scripting, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

Will do. Thanks for the link.

"Torgeir Bakken (MVP)" wrote:

> Hi,
>
> Fyi:
>
> Please post WSUS related issues to the newsgroup dedicated to WSUS:
> microsoft.public.windows.server.update_services
>
> WebNews link to the WSUS newsgroup:
> http://www.microsoft.com/communities...pdate_services
>
>
>
>
> --
> torgeir, Microsoft MVP Scripting, Porsgrunn Norway
> Administration scripting examples and an ONLINE version of
> the 1328 page Scripting Guide:
> http://www.microsoft.com/technet/scr...r/default.mspx
>