WSUS Clients Not Registering with Server
-
@ajstringham
Read the guide. It is pretty short. You can force it, but once you change a GP or assign it to a User or Group, you'll need to refresh Group Policy unless you wish to wait. -
@DenisKelley said:
@ajstringham
Read the guide. It is pretty short. You can force it, but once you change a GP or assign it to a User or Group, you'll need to refresh Group Policy unless you wish to wait.I ran a gpupdate /force on the key machines. Am I missing something?
-
@ajstringham said:
Here is my GPO.
Imgur
I didn't have client-side targeting turned on or setup. It was still in the default "Not configured". I added a group to WSUS called "Computers" and set that as the group to add it to. I logged out and back in on the key machines but it hasn't registered in WSUS yet. I'll give it 24 hours to see if it registers tonight. Not sure if I'm missing something else. I'm new to WSUS, never setup it up before. Thanks for all the help!You could always remove that policy and create a new policy and reboot.
Also setting that up at the top level like that can be an issue. All your servers and DCs will be in the same Target group as client PCs. You probably dont want every update you apply to client PCs applied to your servers.
-
@ajstringham Why do you have so many unnecessary settings? There is no reason for users to receive update notifications since updates are automatically schedule to happen at 3am
-
also your intranet Microsoft Update Service Location is incorrect.
Look at the example and look how mine is setup with http:// (nevermind mine is blacked out)
-
@IRJ said:
@ajstringham said:
Here is my GPO.
Imgur
I didn't have client-side targeting turned on or setup. It was still in the default "Not configured". I added a group to WSUS called "Computers" and set that as the group to add it to. I logged out and back in on the key machines but it hasn't registered in WSUS yet. I'll give it 24 hours to see if it registers tonight. Not sure if I'm missing something else. I'm new to WSUS, never setup it up before. Thanks for all the help!You could always remove that policy and create a new policy and reboot.
Also setting that up at the top level like that can be an issue. All your servers and DCs will be in the same Target group as client PCs. You probably dont want every update you apply to client PCs applied to your servers.
For the sake of the lab, I want all updates going to all endpoints. I know in a prod environment it would be different.
-
@IRJ said:
@ajstringham Why do you have so many unnecessary settings? There is no reason for users to receive update notifications since updates are automatically schedule to happen at 3am
I was just playing with the available settings. I had other documentation I was following.
-
@IRJ said:
also your intranet Microsoft Update Service Location is incorrect.
Look at the example and look how mine is setup with http:// (nevermind mine is blacked out)
Didn't realize I needed the http:// I went ahead and added that.
-
There are some troubleshooting tools you can run that will help you narrow the problem down:
http://technet.microsoft.com/en-us/windowsserver/bb466192.aspx
Grab the client diagnostics tool and the server diagnostics tool.
-
You should check out the following regarding GPO settings:
http://community.spiceworks.com/how_to/show/1390-wsus-gpo-settings-for-the-real-worldWith regards to why your computers aren't checking in...well, I have a how-to for that as well!
http://community.spiceworks.com/how_to/show/91430-wsus-computers-are-not-showing-up-in-the-console-what-s-wrong -
@Rob-Dunn said:
You should check out the following regarding GPO settings:
http://community.spiceworks.com/how_to/show/1390-wsus-gpo-settings-for-the-real-worldWith regards to why your computers aren't checking in...well, I have a how-to for that as well!
http://community.spiceworks.com/how_to/show/91430-wsus-computers-are-not-showing-up-in-the-console-what-s-wrongThanks Rob. I'll check those out tomorrow!
