WSUS not picking up PCs

[MK-2]

I just re-installed WSUS on to a server after the other server it was on died. Synchronized OK, set all the right approval and deployment stuff etc.

Went into GPOs and updated which server to look for.

But after 4 days, some suites are still only listing one machine in the WSUS computers tab.

One suite was ghosted last week so there shouldn't be any cr*p on them.

 

Any ideas, as I really don't fancy manual WU, especially on EMBC

 

 

Cheers

[Geoff]

Make sure your machines have been sysprepped after ghosting. Otherwise they'll have the same WSUS ID.

 

Also check your GPO settings and the WinHTTP proxy settings.

[Slartibartfast]

Were the machines in the suites imaged?

 

Delete the HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate key on the affected machines. Then run wsusadmin /resetauthorization /detectnow from the command prompt.

 

This problem can occur even if the machines have been sysprepped.

[thom]

I did the following from the clients and they were then picked up in WSUS

Visit the following from a client's Internet explorer

1 - Register with WSUS

http://wsusserver:port/iuident.cab

2 - Check WSUS for Updates

http://wsusserver:port/selfupdate/AU/x86/XP/EN/wuaucomp.cab

3 - Download latest client

http://update.microsoft.com/windowsupdate/v6/default.aspx?betathanksurl&ln=en-us

 

To check what settings the client has got run "gpresult" from the client's command line.

[MK-2]

thanks for the help guys. i'll give it a go later....its in use now (but not booked!!)

[tosca925]

I used to have this problem on a few machines in various OU's when first deployed WSUS. I used the script below in the various OU's that had the trouble. I put it in the Computer Configuration>Windows Settings> Scripts>log on of the OU in question and after they logged in they all started to appear over the next 12-24 hours.

 

Try the script and see how you get on.

 

'--------------------8<----------------------

Set oShell = CreateObject("WScript.Shell")

 

sRegKey = "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate"

 

' suppress error in case values does not exist

On Error Resume Next

 

' check for marker

sIDDeleted = oShell.RegRead( sRegKey & "\IDDeleted")

 

' to be sure values is only deleted once, test on marker

If sIDDeleted <> "yes" Then

' delete values

oShell.RegDelete sRegKey & "\AccountDomainSid"

oShell.RegDelete sRegKey & "\PingID"

oShell.RegDelete sRegKey & "\SusClientId"

 

' Stop and start the Automatic updates service

oShell.Run "%SystemRoot%\system32\net.exe stop wuauserv", 0, True

oShell.Run "%SystemRoot%\system32\net.exe start wuauserv", 0, True

 

' Run wuauclt.exe with resetauthorization

sCmd = "%SystemRoot%\system32\wuauclt.exe /resetauthorization /detectnow"

oShell.Run sCmd, 0, True

 

' create marker

oShell.RegWrite sRegKey & "\IDDeleted", "yes"

End If

'--------------------8<----------------------

[tosca925]

You will see in the script that it creates a marker in the regisitry so it does no keep runing everytime someone logs on. but after you see all machines showing in WSUS yu can remove the script from your OU.

[ChrisH]

Funnily enough Im having trouble like this as well. Will try that script tommorow but its looks very much like a batch script i have already tried.

[tosca925]

Let me know how you get on CHrisH, I must admit this script cleared up all the issues i had with my clients and WSUS.

 

But i guess i could have been just lucky....... ;-)

[Slartibartfast]

Fantastic script! Thanks!

[ChrisH]

I ahve sorted my problem I was just being dumb. I installed WSUS on the non standard port option because of what else was on the machine oops :oops: so a quick change of the GPO to add the port number and everybody is now reporting in . Im sure that script will come in handy at some point though.

[MK-2]

I ahve sorted my problem I was just being dumb. I installed WSUS on the non standard port option because of what else was on the machine oops :oops: so a quick change of the GPO to add the port number and everybody is now reporting in . Im sure that script will come in handy at some point though.

 

That's when you tell people you fixed the problem, Windows was playing up and you had to sort it yourself because Microsoft never works properly

[tosca925]

Glad you sorted it Chris ;-)

[ifs2010]

Should I save this as a batch file or vbs script? I don't script....

[sjatkn]

You will see in the script that it creates a marker in the regisitry so it does no keep runing everytime someone logs on. but after you see all machines showing in WSUS yu can remove the script from your OU.

 

I've just done the very same thing with a similar script. I discovered that sysprep is not removing the SusClientId registry entry so have no plans on removing the script from group policy. Because unless I remove the registry entry before sysprep then I am going have the problem keep coming back.

[ifs2010]

Well my question is should I save this as a .vbs file or .wsh? I am confused....

[elsiegee40]

Well my question is should I save this as a .vbs file or .wsh? I am confused....

vbs, I think