WSUS 3.0 Clients are not showing in wsus admin console - different twist

[troy04]

Sponsored Links

Here's a twist to a similar thread with regards to client computers not showing in the wsus console.

We're using WSUS 3.0 SP1 and not all client computers are showing. BUT... all client computers are getting the updates that we roll out. Also, the listed client computers would randomly change (the count will not increase)

Any ideas?

Thank you.

The Windows Update NG deals with client issues, Troy.
Try the WSUS newsgroup:
http://www.microsoft.com/communities...pdate_services


MowGreen [MVP 2003-2009]
===============
*-343-* FDNY
Never Forgotten
===============


troy04 wrote:
> Here's a twist to a similar thread with regards to client computers not
> showing in the wsus console.
>
> We're using WSUS 3.0 SP1 and not all client computers are showing.
> BUT... all client computers are getting the updates that we roll out.
> Also, the listed client computers would randomly change (the count will
> not increase)
>
> Any ideas?
>
> Thank you.
>
>

[[ Right pew, wrong church. Forwarded to WSUS newsgroup
(microsoft.public.windows.server.update_services) 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
]]

troy04 wrote:
> Here's a twist to a similar thread with regards to client computers not
> showing in the wsus console.
>
> We're using WSUS 3.0 SP1 and not all client computers are showing.
> BUT... all client computers are getting the updates that we roll out.
> Also, the listed client computers would randomly change (the count will
> not increase)
>
> Any ideas?
>
> Thank you.

> troy04 wrote:
>> Here's a twist to a similar thread with regards to client computers not
>> showing in the wsus console.
>>
>> We're using WSUS 3.0 SP1 and not all client computers are showing.
>> BUT... all client computers are getting the updates that we roll out.
>> Also, the listed client computers would randomly change (the count will
>> not increase)

No twist. Read the solution provided in the 'similar thread'. It's the same
age-old problem with the same solution.

Duplicate SUSCLIENTID values caused by cloned systems. Delete 'em and allow
them to be regenerated.


--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin