In order to find this post, i would google for: windows client not visible wsus server

Let’s say you configured a GPO for servers or clients so they receive their updates from your local WSUS server, how do you speed up the process so they show up in the WSUS management page immediately?

1) Refreshing the GPO using “gpupdate /force” on the client

2) Check if the new policy is in use: “gpresult” (look for the applied machine policy’s)

3) Run “wuauclt.exe /detectnow” This command-line option instructs Automatic Updates to contact the WSUS server immediately.

If the client still doesn’t report to the wsus server try the following:
– Search the registry on the client to see what the WSUS location is
– Using a browser on a client, try to download: http://<WSUSSERVER>/
– Look in the IIS logs on the WSUS server: c:\windows\system32\logfiles\W3SVC1

Have fun patching!

4 Responses to “Force windows client to contact WSUS server”

  1. Mark Says:

    Thanks–I use WSUS 3.0 at work–this really helped speed up my deployment process. wuauclt.exe /detectnow is now part of my toolbox! Here’s a tip if you’re not aware . . . When using Sysprep be advised that WSUS doesn’t use the SID to ID a WSUS client. Therefore cloned systems will not show up in WSUS (although they will update–they just don’t show up as a client computer). Check out MS KB903262 for the work around.

  2. Steve Says:

    I have also found that the client system’s clock must be set correctly for it to recognize updates. We had one system that was mistakenly set several hours ahead of the WSUS server that refused to recognize any updates until we changed the time.

  3. quicken checks Says:

    Hi there,

    I guess the windows issue is becoming serious day by day


  4. Javis Says:

    Rant warning: Tried all the suggestions, machine refuses to update. gpudpate /force insists on resetting the machine after two reboots. I ended up running the update like a non domained workstation.

    Microsoft: you are an embarrassment

Post A Comment