Every client visible on WSUS 3.0 server, but no clients updating

Every client visible on WSUS 3.0 server, but no clients updating

Post by Z2xnY2F » Thu, 30 Oct 2008 06:55:01


have spent hours looking for a solution to my problem to no avail. I hope
someone here can help me!

I have a new install of WSUS 3.0 on Win2k3 server that I had to move because
the old server crashed. I changed the GPO for all my clients to the new
server and confirmed that all workstations and servers are visible on the
WSUS server. I have the proper permissions in IIS, proper ports, proper
registry settings and I'm getting "0 updates detected" in the
WindowsUpdate.log on the clients even though there are updates needed.

On the GPO I have the TargetGroup as "All Computers" though there is a
Server and Workstations group that I assign each computer to respectively
once it appears in WSUS. I'm wondering if the grouping is the problem?

Here's the last wuaclt.exe /detectnow that I ran (after restarting Automatic
Updates service) from the WindowsUpdate.log:

2008-10-28 14:40:20:169 1836 1438 Service *************
2008-10-28 14:40:20:169 1836 1438 Service ** START ** Service: Service
startup
2008-10-28 14:40:20:169 1836 1438 Service *********
2008-10-28 14:40:20:169 1836 1438 Agent * WU client version 7.1.6001.65
2008-10-28 14:40:20:169 1836 1438 Agent * Base directory:
C:\WINDOWS\SoftwareDistribution
2008-10-28 14:40:20:169 1836 1438 Agent * Access type: No proxy
2008-10-28 14:40:20:169 1836 1438 Agent * Network state: Connected
2008-10-28 14:41:05:653 1836 1438 Agent *********** Agent: Initializing
Windows Update Agent ***********
2008-10-28 14:41:05:653 1836 1438 Agent *********** Agent: Initializing
global settings cache ***********
2008-10-28 14:41:05:653 1836 1438 Agent * WSUS server: http://BES01a
2008-10-28 14:41:05:653 1836 1438 Agent * WSUS status server: http://BES01a
2008-10-28 14:41:05:653 1836 1438 Agent * Target group: Workstations
2008-10-28 14:41:05:653 1836 1438 Agent * Windows Update access disabled: No
2008-10-28 14:41:05:653 1836 1438 DnldMgr Download manager restoring 0
downloads
2008-10-28 14:41:05:653 1836 1438 AU ########### AU: Initializing Automatic
Updates ###########
2008-10-28 14:41:05:653 1836 1438 AU # WSUS server: http://BES01a
2008-10-28 14:41:05:653 1836 1438 AU # Detection frequency: 8
2008-10-28 14:41:05:653 1836 1438 AU # Target group: Workstations
2008-10-28 14:41:05:653 1836 1438 AU # Approval type: Scheduled (Policy)
2008-10-28 14:41:05:653 1836 1438 AU # Scheduled install day/time: Every
day at 3:00
2008-10-28 14:41:05:653 1836 1438 AU # Auto-install minor updates: Yes
(Policy)
2008-10-28 14:41:05:653 1836 1438 AU Setting AU scheduled install time to
2008-10-29 10:00:00
2008-10-28 14:41:05:919 1836 1438 Report *********** Report: Initializing
static reporting data ***********
2008-10-28 14:41:05:919 1836 1438 Report * OS Version = 5.1.2600.3.0.65792
2008-10-28 14:41:05:950 1836 1438 Report * Computer Brand = Dell Inc.

2008-10-28 14:41:05:950 1836 1438 Report * Computer Model = Precision
WorkStation 390
2008-10-28 14:41:05:950 1836 1438 Report * Bios Revision = 1.0.4
2008-10-28 14:41:05:950 1836 1438 Report * Bios Name = Phoenix ROM BIOS
PLUS Version 1.10 1.0.4
2008-10-28 14:41:05:950 1836 1438 Report * Bios Release Date =
2006-08-16T00:00:00
2008-10-28 14:41:05:950 1836 1438 Report * Locale ID = 1033
2008-10-28 14:41:05:966 1836 1438 AU AU finished delayed initialization
2008-10-28 14:41:05:981 1836 1438 AU #############
2008-10-28 14:41:
 
 
 

Every client visible on WSUS 3.0 server, but no clients updating

Post by MV » Thu, 30 Oct 2008 11:36:30


Yes. Lose the "All Computers" assignment. "All Computers" is a reserved name
used to rollup the individual groups. By placing a machine explicity in the
"All Computers" group, you make it *NOT* in any other group, and thus
they'll get exactly the "0 updates detected" that you are experiencing.


But the logfile you posted does not appear to be a machine involved in the
above scenario....



This machine is NOT in "All Computers"! This machine is assigned in
"Workstations".



This client performed a perfectly valid detection. The only logical
conclusion from this logfile is that there's nothing approved for
"Workstations" that is NEEDED by this client.

Specifically what update(s) do you feel should be detected by this client?

Specifically what update(s) are being reported as NEEDED by the
"Workstations" group, and is this particular machine (gge.gsamusic.com) one
of the machines listed with the update "Not Installed"?



--
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.yqcomputer.com/
My Websites: http://www.yqcomputer.com/ ;
http://www.yqcomputer.com/
My MVP Profile: http://www.yqcomputer.com/