Lawrence Garvin [MVP] replied to smiller
18-Nov-09 07:12 PM
[a] The client is properly configured to use the WSUS Server
[b] The client is critically MISconfigured to use this target group.
Computers should *NOT* be assigned to the "All Computers" group under any
circumstance.
[c] As a result because there is not actually an "All Computers" group that a
computer can be assigned to (it is a pseudo group populated from computers
that are members of *other* groups -- of which this computer belongs to
*zero* of the other groups, thus is not even populated into what can be
viewed in the console as members of "All Computers".), this computer is not
discovering any approved updates for the "group" it believes it is a member
of.
Note: Even though you may not have approved any updates, there are updates
approved on every WSUS Server. They may, or may not, be needed by any client
systems in your organization.
[d] Finally, you should rethink the use of underscores in your hostnames.
While Microsoft DNS is forgiving about the underscore, the DNS RFCs do not
permit the underscore as a valid character for use in DNS hostnames. The
valid character set includes a-z, 0-9, and the hyphen.
Aside from the target group configuration error, this client is functioning
perfectly, albeit with no updates to detect or install. I am not quite sure
what the point of posting the log segment was.
--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin