> George Schneider wrote:
>> I've been trying to get WSUS setyup in my enviroment for months now and
>> kleep running into the same road blocks. I eventual got so frustrated
>> I uninstalled WSUS and reinstalled. I thought that resolved by problem
>> forst because some updtaes were actual installed ot the two test computer
>> group I set up. As of right now I have 75 updates that have been
>> but haven't been installed on the test computer. I have the setting set
>> to download dail at 8:00 PM.
Okay.. first misunderstanding to correct... the client does not download at
8pm daily. It detects/downloads every 22 hours (by default).
It /installs/ at 8pm daily, if it has successfully detected/downloaded an
update (or more) before 8pm.
>> Whats really starnds is the WSUS console is
>> reporting that the computer has reported to the server since 2/25.
This is actually good. It allows us to immediately rule out the =network= as
a possible cause.
>> I ran
>> wuauclt /detectnow and ensure the GPO detection frequrcy is set to one
>> hours. What am i missng so I can get WSUS to actual work in my
>> I've approved all updates
Well, a number of possible things:
 Even though the client has =registered= with the WSUS Server, that does
not necessarily mean that it has:
[a] Downloaded and successfully installed the latest version of the
Windows Update Agent, or
[b] Actually executed a detection scan against the WSUS Server, or
[c] Determined there are any update(s) to install, or
[d] Successfully downloaded those update(s)
It's unfortunate that you've spend so much time and frustration, but now
that you're here, we'll get you going in short order.
Next step is to download and run the "Client DIagnostic Tool" and post the
results. The results of this tool will help us verify that:
[a] Your Windows Update Agent has been properly updated and is
[b] Your policy is actually applied correctly, and
[c] Your WUA can make a valid connection to the WSUS Server.
Once we verify those three things, the next step is to inspect the
WindowsUpdate.log to determine /what/ and /why/ the updates are not getting
installed. There are dozens of reasons why this might be happening.
When you post the output of the Client Diagostic Tool, also post the last
250 lines of the WindowsUpdate.log -- which should be sufficient to get a
preliminary analysis and focus our diagnostic efforts -- if not actually
identify the specific cause(s) of the failures.
>> I also notice in the windows update log on the test machine (XP) that it
>> states the scheduled install time to 20080-03-04 16:00:00 even though the
>> download and install time is set to 11:00 am as of today.
GMT vs Local Time. You're in GMT+5... Eastern Time.
Oh.. btw... your installation time isn't 8pm, either (anymore) :-)
Any possibilities some other options in your GPO were also changed?
Or... perhaps... what you have set to occur at 8pm is the server
=synchronization= with microsoft.com?
Lawrence Garvin, M.S., MCBMSP, MCTS, MCP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin