Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

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

73 views
Skip to first unread message

troy04

unread,
Jan 6, 2009, 2:12:19 PM1/6/09
to

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
------------------------------------------------------------------------
troy04's Profile: http://forums.techarena.in/members/troy04.htm
View this thread: http://forums.techarena.in/windows-update/1099065.htm

http://forums.techarena.in

MowGreen [MVP]

unread,
Jan 6, 2009, 2:58:08 PM1/6/09
to
The Windows Update NG deals with client issues, Troy.
Try the WSUS newsgroup:
http://www.microsoft.com/communities/newsgroups/list/en-us/default.aspx?dg=microsoft.public.windows.server.update_services


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

PA Bear [MS MVP]

unread,
Jan 6, 2009, 8:41:22 PM1/6/09
to
[[ 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/newsgroups/list/en-us/default.aspx?dg=microsoft.public.windows.server.update_services

In your newsreader:
news://msnews.microsoft.com/microsoft.public.windows.server.update_services
]]

Lawrence Garvin (MVP)

unread,
Jan 7, 2009, 12:15:55 AM1/7/09
to
> 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/profile/Lawrence.Garvin

Beklimes

unread,
Sep 24, 2009, 11:44:55 AM9/24/09
to

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


--
Beklimes
------------------------------------------------------------------------
Beklimes's Profile: http://forums.techarena.in/members/137617.htm
View this thread: http://forums.techarena.in/windows-update/1008581.htm

http://forums.techarena.in

MowGreen

unread,
Sep 24, 2009, 2:58:58 PM9/24/09
to

Try posting this issue to the WSUS newsgroup:
http://www.microsoft.com/communities/newsgroups/list/en-us/default.aspx?dg=microsoft.public.windows.server.update_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"

0 new messages