WSUS 3.0 Clients are not showing in wsus admin console

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.

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.

Forwarded to the WSUS NG for OP's convenience:

Web-based reader <for the kidz>
http://www.microsoft.com/communities...pdate_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
===============

See inline answers.
Also if you are having problems it is usually better to post the full output
from the Client Diag. There are people here who can tell a lot of detail from
that output that most miss completely.

On Thu, 24 Jul 2008 10:42:32 -0700, "MowGreen [MVP]" <>
wrote:

>Forwarded to the WSUS NG for OP's convenience:
>
>Web-based reader <for the kidz>
>http://www.microsoft.com/communities...pdate_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.
This need to be enabled int the GPO for the client to use WSUS

>>
>> "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
Incorrect, it is not related to client side targeting. It won't do anything
though if the above police does not enable WSUS on the client.

>>>(using the local group policy).
You would not use local policy if you have a GPO.

>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
>===============
--
Dave Mills
There are 10 type of people, those that understand binary and those that don't.

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...pdate_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
> ===============
>

Try posting this issue to the WSUS newsgroup:
http://www.microsoft.com/communities...pdate_services

This one, Windows Update, deals with client-side issues.


MowGreen
===============
*-343-* FDNY
Never Forgotten
===============

banthecheck.com
"Security updates should *never* have *non-security content* prechecked"



Beklimes wrote:

> Re: WSUS 3.0 client computers not populating WSUS console
>
>
>
> ---
> One key issue I haven't seen answered for an issue like this with
> GPOs:
>
> Where MUST the WSUS edits be done in the GPO?
> Must is be the Computer- Default Domain Polcy?
> Or can it be an =OU - sub GPO??
>
> Thanks, BK
>
>