jtidd Posted November 19, 2012 Posted November 19, 2012 As title above i have alot of machines that have not reported back to WSUS for 116 days, 122 days and so on What steps do i take Thanks in advance James
glennda Posted November 19, 2012 Posted November 19, 2012 Are you setting this via Group Policy for them to check in with the server? Have the machines been moved OU's and a Group Policy therefore not applying? Toby
Matt_Brfc Posted November 19, 2012 Posted November 19, 2012 I had a similar issue some time again when I initially deployed WSUS and if I recall the issue was down to permission within IIS. I recommend using group policy too, this way you can force your PC's to look at the WSUS server for the updates, once this has been applied and pushed out to the clients discovery will then stat to work and this will be reflected in the WSUS console.
jtidd Posted November 19, 2012 Author Posted November 19, 2012 ok so what is the solution where do i check the permissions of IIS? Do i need to check anything on the machines? sorry new to this
JonThompson Posted November 19, 2012 Posted November 19, 2012 Do you use ghosting software? (Symantec Ghost for example) It could be to do with duplicate security SIDS. There is a script online that you can run on PC's to clear this up.
jtidd Posted November 19, 2012 Author Posted November 19, 2012 no we started using KMS in the summer, so maybe this could be a problem, any ideas? we use WDS for imaging Thanks
CyberNerd Posted November 19, 2012 Posted November 19, 2012 try this on a client: net stop wuauserv reg.exe delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v PingID /f reg.exe delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v AccountDomainSid /f reg.exe delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientId /f reg.exe delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientIDValidation /f net start wuauserv wuauclt.exe /resetauthorization /detectnow
alan-d Posted November 19, 2012 Posted November 19, 2012 What OS are you using? There is a KB to fix this KB2720211 There have been problems with this KB though but can be fixed by editing the Server Registry as follows; HKLM\Software\Microsoft\Update Services\Server\Setup\ Find wYukonInstalled and change the value from 1 to 0 Reinstall the KB above Return to the above key and change the value back to 1.
jtidd Posted November 19, 2012 Author Posted November 19, 2012 CYBERNERD: i have run this on affected machine, how do i know if it has worked? ALAN-D : that KB is not installed on our WSUS server? Thanks
CyberNerd Posted November 19, 2012 Posted November 19, 2012 CYBERNERD: i have run this on affected machine, how do i know if it has worked? Does it appear/update in WSUS?
alan-d Posted November 19, 2012 Posted November 19, 2012 ALAN-D : that KB is not installed on our WSUS server? Thanks The KB is meant to fix your problem but some admins have a problem installing it hence my regedit.
jtidd Posted November 19, 2012 Author Posted November 19, 2012 no after running cmd's it still shows that the machine has not contacted WSUS for 116 days Thanks
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now