Hello,

We had the same problem and support told us that if you image a server the
susclientid id would be a duplicate and would cause this problem. We needed
to delete the key which is located at:
Local Machine | Software | Microsoft | Current Version | Windows | susclientid
After deleteing the registry entry run the following command to regenerate
the key:
C:\wuauclt /detectnow /resetauthorization
--
KM


"MowGreen [MVP]" wrote:

> Forwarded to the WSUS NG for OP's convenience:
>
> Web-based reader <for the kidz>
> http://www.microsoft.com/communities... date_services
>
> NNTP reader <for adults>
> news://msnews.microsoft.com/microsof...pdate_services
>
>
> ----------------------------------------------------------------------------------------------------
> Rock41 wrote:
>
> > Let me also add that I ran the Client Diagnostic utility and received the
> > message that useWUServer is disabled. The command prompt also states this
> > version is WSUS 2.0.
> >
> > "Rock41" wrote:
> >
> >
> >>My WSUS 3.0 clients are not showing in the wsus admin conosle. My
> >>configuration is by Active Directory (Group Policy Management Console). I
> >>have verfied that BITS are running. I tried the wuauclt.exe /detectnow
> >>command but I believe this only works if your using client-side targeting
> >>(using the local group policy). Also the automatic updates service is running
> >>on the local machine. I also waited for at least 24 hours to verify if the
> >>computers would show in the console. Any help would be appreciated. Thanks.
> -----------------------------------------------------------------------------------------------------
>
>
> MowGreen [MVP 2003-2008]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>