Mark Minasi's Reader Forum
Mark Minasi's Reader Forum
Home | Profile | Register | Active Topics | Active Polls | Members | Search | FAQ | Minasi Forum RSS Feed
Username:
 Password:
Save Password
Forgot your Password?

 All Forums
 OTHER HALP! Linux, Hardware, and Anything Else
 SUS / WSUS, HFNetChk
 Clients not reporting		  New Topic  Reply to Topic
 Printer Friendly
Author  Topic Next Topic  

Michael
Old Timer

USA
608 Posts
Status: offline
Posted - 08/20/2012 :  10:21:04 AM  Show Profile  Reply with Quote
This is my first WSUS server, I have followed the setup I found on this site and everything seemed to go correct. I get email reports and the test client worked correct at my shop. Now that the server is on-site in operation with 30 pc connected I have some problems. So far all the pc do show up and about 4 (win xp) did all the updates just like the should. But the others (xp and 7) have the statement Have not Reported. From my searching this seems to be a common problem, but the fixes have not corrected it. I did try a MS fix late Friday on one of the XP box and it said that it Fixed the problem, I will see when I get on-site today. Any ideas are welcome.

Next, I have a few pc on the network that are not in the domain, so they do not get the policy to force them to the WSUS. Can I make the same entries in each local pc that I did on the server policy and have them see the WSUS that way?

Thanks,
Michael

Endaar
Old Timer

USA
567 Posts
Status: offline
Posted - 08/24/2012 :  11:53:13 AM  Show Profile  Reply with Quote
For the machines not reporting, try running the below as a batch file on each of them:

reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v AccountDomainSid /f
reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v PingID /f
reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientId /f

net stop wuauserv
net start wuauserv
wuauclt /resetauthorization /detectnow


I've occasionally run into this problem with imaged machines and the above should resolve it.

For non-domain PCs, export the following reg keys from a domained machine and import them to the off-domain systems:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU

That should take care of it.

Endaar
Go to Top of Page

Michael
Old Timer

USA
608 Posts
Status: offline
Posted - 09/06/2012 :  12:01:52 AM  Show Profile  Reply with Quote
Thanks for the reply Endaar.
I had tried a MS Fix that did what or close to what you recommend to in a batch file, it may not have been the same but I did see it reported that it reset the windows update files, but did not correct my issue. I am not saying yours would not have worked.
I ended up getting Microsoft Support involved as I was on a time limit to get this working correct. We did some dll entires and other steps, that got all pc reporting and updating.
As for the non domain boxes, I did the policy edit manual on each (only about 6 total) with the same setting I had done on the DC Policy. They are all working correct too. But it sounds like your idea of reg key import would have worked also.
I do not have the documentation of each step we did but will get it added to the post in hopes it will help others in the future.

Thanks
Michael
Go to Top of Page

Endaar
Old Timer

USA
567 Posts
Status: offline
Posted - 09/06/2012 :  09:23:44 AM  Show Profile  Reply with Quote
Glad you got it fixed. Would certainly love to see the PSS steps as I do have some machines that have issues with BITS that perhaps might be related.

James
Go to Top of Page
   Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
Mark Minasi's Reader Forum © 2002-2011 Mark Minasi Go To Top Of Page
This page was generated in 0.12 seconds. Snitz Forums 2000