wuauclt /detectnow needs to be run on the client, in case this wasn't clear. There is no way you can do this from the WSUS server - this is a passive component just waiting for requests from clients.
Main Topics
Browse All TopicsI have a Windows 2008 Server running WSUS 3 SP2 and a GP in place. I have a few test systems that have received updates but I cannot figure out what determines the schedule for Clients systems to recieve updates from WSUS. Can someone tell me what determines this and also, is there a way to force aor push the updates.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Here's two real good guides
Configuring the WSUS Client by Group Policy
Beginners Admin FAQ for Windows Software Update Services
All,
Still confused..
in WSUS the client system i slisted and has 224 updates needed. This is a test system. I believe the GP is fine. I have manually run wuauclt.exe /detectnow and the test system does show up under the Test computer group in WSUS.
It has been about 8 hours and no updates have been applied. The schedule is set for every hour yet nothing. Very frustrating and I'd appreciate help here.
Post your clientdiag results from the client
http://download.micr
Check your permissions
What are the correct IIS and NTFS permissions for WSUS?
The test clients seem to be pulling the approved updates but not entirely. Does this mean I have to wait for the next scheduled cycle?
In the WSUS Console, under Updates, can you clarify the column header that reads: "Installed/Not Applicable Percentage"? Most are listed as 100% yet a few are at 60% or 80%. What does Install (1/3) represent??
Lastly, in GP, what is the difference in Enforcing the policy versus not?
Technically it should pull all required updates at once. Sometimes it doesn't hurt to be patient though, it may be a matter of time
100% is good (everything is installed or not required). If it's something else some clients are still missing the patches or have not reported back yet.
Install (1/3) means that you have several computer groups, and the update is only approved for one of the three groups. Only computers that are in the computer group the update is approved will install it.
Enforcing a GPO has nothing to do with WSUS directly. It would apply if you have several GPOs applied to the same computer with contradicting settings. The enforced one would win.
You've been fantastic and are getting me closer; I appreciate it. I am playing around with setting deadlines just to see how that works. In one case this test client failed on 2 updates; .net Framework 3.5 SP1 and a Security Update for .Net Framework 1.1 SP1.
I tried to pull them again and they didn't apply? any thoughts?? I have set each of them as another deadline for 15 minutes from now to see...
Deadlines will not force an update to install if there is a failure.
.Net is known to fail to update from time to time. Look here for resolution. http://blogs.msdn.com/joy/
Just so that you know, when you set a deadline on a update the system will reboot no matter who is signed in or even if the update didnt require a reboot in the first place.
Business Accounts
Answer for Membership
by: Wonko_the_SanePosted on 2009-09-08 at 13:57:55ID: 25286090
It is random (default is to do it once in a 10-hour timespan). You can use a GPO to determine how often your clients do it (e.g. at least once every x hours).
.log
To trigger it on a machine you can run "wuauclt /detectnow". Please note that this command will not return anything, wether it was successful or not. To see if it's actually doing anything you can check the log file, which should be
%SYSTEMROOT%\windowsupdate