WSUS client on ghosted images

I am implementing WSUS on my network. I already have the WSUS server up and
running, and I am planning on using ghost to deploy my images in the labs I
maintain. I found an article ID 555351 that says WSUS client computers may
have trouble communicating with the WSUS server if workstation is installed
using disk imaging / disk cloning.

I use the Ghost 8 Ghostcast server to deploy my images, and after the image
is finished and the computer reboots, sysprep kicks in. Is this enough of a
change to the registry on the ghosted image that WSUS will work properly?

If that is not the case and I delete the registry entries prior to ghosting,
do I need to run: "wuauclt.exe /reauthorization /detectnow" after the
computer has been ghosted? Thanks for any suggestions.

Perhaps try the WSUS Newsgroup

news://msnews.microsoft.com/microsof...pdate_services
(OE client)
or
http://www.microsoft.com/communities...pdate_services
(web client)



"zeb2100" wrote:

> I am implementing WSUS on my network. I already have the WSUS server up and
> running, and I am planning on using ghost to deploy my images in the labs I
> maintain. I found an article ID 555351 that says WSUS client computers may
> have trouble communicating with the WSUS server if workstation is installed
> using disk imaging / disk cloning.
>
> I use the Ghost 8 Ghostcast server to deploy my images, and after the image
> is finished and the computer reboots, sysprep kicks in. Is this enough of a
> change to the registry on the ghosted image that WSUS will work properly?
>
> If that is not the case and I delete the registry entries prior to ghosting,
> do I need to run: "wuauclt.exe /reauthorization /detectnow" after the
> computer has been ghosted? Thanks for any suggestions.