nflynn85
asked on
WSUS Client Issue
I've set up a 2016 WSUS Server and have performed a successful synchronization. I've been testing with one server client (also 2016) just to make sure I can get it working correctly the way I want to before I go edit the Master GPO's on each domain and make this change permanent. The problem is I can't get this client to show in the WSUS Console
Firewalls are off on both server and each machine can ping each other. If I browse to http://WSUSservername I get hit with the IIS web page
When I open the local gpo on the client server, i've edited the correct windowsupdate policy object so that http://WSUSservername is the target WSUS server (I also see this http:// address in the registry)
What is it that i'm missing here? First time setting up WSUS in almost a decade so would appreciate some help! Thanks in advance
Firewalls are off on both server and each machine can ping each other. If I browse to http://WSUSservername I get hit with the IIS web page
When I open the local gpo on the client server, i've edited the correct windowsupdate policy object so that http://WSUSservername is the target WSUS server (I also see this http:// address in the registry)
What is it that i'm missing here? First time setting up WSUS in almost a decade so would appreciate some help! Thanks in advance
If your clients are running wsus 3 you could try updating to sp2
https://support.microsoft.com/en-us/help/2734608/an-update-for-windows-server-update-services-3-0-service-pack-2-is-ava
I seen an article where this resolved the issue in the past
That said look at the C:\windows\windowsupdate.l
https://support.microsoft.com/en-us/help/2734608/an-update-for-windows-server-update-services-3-0-service-pack-2-is-ava
I seen an article where this resolved the issue in the past
That said look at the C:\windows\windowsupdate.l
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Select any helpful answers to you. take care
ASKER
neither of your comments were helpful but I appreciate you guys trying to help, guess I just needed to write about it and go play with the options some more! thanks again
Hello nflynn85,
Good to know that you have figured out the solution yourself. However for the benefit of others facing the same issue, I would request you to share your findings and solution.
My experience has been that after Group Policies is set on clients, the WSUS server needs to be configured as well for computers to start showing up under the correct containers. For this, go to options on the wsus server console and Click on Computers. A new windows pops up, under General Tab choose “Use Group Policy or registry settings on computers“. Click Apply and OK. This should be done on all downstream and upstream wsus servers.
Thanks,
Sam
Good to know that you have figured out the solution yourself. However for the benefit of others facing the same issue, I would request you to share your findings and solution.
My experience has been that after Group Policies is set on clients, the WSUS server needs to be configured as well for computers to start showing up under the correct containers. For this, go to options on the wsus server console and Click on Computers. A new windows pops up, under General Tab choose “Use Group Policy or registry settings on computers“. Click Apply and OK. This should be done on all downstream and upstream wsus servers.
Thanks,
Sam
ASKER
No problem. As I mentioned in a previous comment, WSUS was set for server side targeting instead of client side targeting. This can be found via options -> computers in the WSUS console
ASKER
figured it out on my own
Here's a more detail video of how to do it, https://www.youtube.com/watch?v=luPy3lxbBKE the ws2016 is similar to 2012 just change the interface from win8.1 to the one w10.