No Clients connecting to WSUS

[Tricky_Dicky]

Hi all,
I'm hoping I've just missed something obvious here but for some reason no clients are connecting to the WSUS server.
It's WSUS 3.1.6001.65 on a server 2003R2 all clients are XP SP2+. I've attached a screen shot of the GPO that should be getting the clients to connect, I set this up a few weeks ago so I don't think it's a time thing.
Rich

[tosh74]

if you have a proxy server for your client machines. Just ensure that it's not intercepting your http requests to your wsus server

[Tricky_Dicky]

There is an exception in the proxy settings for anything in our subnet range, should that be enough or will it need something more specific?

[tosh74]

I would check your proxy access logs to be sure. I would also look at c:\windows\windowsupdate.log (on a client machine) to see if they're at least trying to contact your wsus server

[cookie_monster]

Is WSUS on the default website if not you'll need to add a port number to the URL e.g. http://servername:8530

Also do you mean no clients are checking in at all or are there a couple? This can happen when you have ghosted clients without seleting the susid.

[ZeroHour]

Also just to double check, your not running SCCM? its client by default takes control of updates and you have to disable that part to get it to go to a wsus server again.

[skell]

I've found that some of our machines don't get their proxy settings right in relation to WSUS. To correct this, we do the following.

Open a cmd prompt and type proxycfg -u

This command copies the proxy settings from Internet Explorer.

[Admiral208]

have you tried running the WSUS client diagnostic tool? that might throw up something useful.

Windows Server Update Services Tools and Utilities

James

[alan-d]

Also have a look at this thread PCs not seeing WSUS updates

[elsiegee40]

I have been having issues with some of my PCs not reporting to WSUS; ironically the ones that have been on the network longest in our ICT Suite, but not all of them.

In desperation, I ran Microsoft Update manually on half a dozen of them yesterday and today they are conversing with WSUS again. I cannot say which of the 18 updates sorted the problem, or why other networked PCs are not (so far) doing this... I have resigned myself to running Microsoft Update manually on the remaining 10 that are refusing to play nicely.

[ZeroHour]

This bat is from MS, try it on a client and see if it cures the issue.

Rem - Batch script to delete duplicate SusClientIDs
Rem - Implement this script as a "Startup" or "Logon"  script
Rem - Script creates an output file called %Systemdrive%\SUSClientID.log
Rem - If the %Systemdrive%\SUSClientID.log is already present, then the script simply exits
@Echo off
if exist %systemdrive%\SUSClientID.log goto end
net stop wuauserv
net stop bits
reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f  > %systemdrive%\SUSClientID.log 2>&1
reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f  >> %systemdrive%\SUSClientID.log 2>&1
reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f  >> %systemdrive%\SUSClientID.log 2>&1
net start wuauserv
wuauclt.exe /resetauthorization /detectnow         
:end
exit

[CyberNerd]

^^ above script (similar) works for us. Problem for us was that imaging machines copies the windowsupdate SUS client ID and it confuses the server. the script deletes and recreates the sus client ID.

[Tricky_Dicky]

Also just to double check, your not running SCCM? its client by default takes control of updates and you have to disable that part to get it to go to a wsus server again.

I don't currently have it running but I did install it on a seperate machine on the network for a play a little while ago. The fact that no machines at all are connecting is making me think it could be something like this.
How would I go about changing this back?
Rich

[elsiegee40]

I did try the above script on the other machines, but they still won't talk to WSUS... Microsoft Update, it'll have to be for me

[ZeroHour]

I don't currently have it running but I did install it on a seperate machine on the network for a play a little while ago. The fact that no machines at all are connecting is making me think it could be something like this.
How would I go about changing this back?
Rich

Hi
You dont have the client installed on any of your pc's? (remember its very easy to set it up to auto deploy without realising)
Is your test SCCM linked to your WSUS server or running its own instance?
Cant find the exact option right now in SCCM, hunting...