WSUS 2016 not showing connected computers

I am in the process of replacing my aging Windows Server 2008 servers with new Windows Server 2016 servers. My first and top priority is replacing the WSUS. I have created a new VM on my new 2016 server called (for now) DOMCON02 and created the role for WSUS.

I then put two computers in an OU on the 2008 DC as a test and setup a group policy to have them get their updates from the new DOMCON02. I did a Gpupdate on everything and then did a GPresult to confirm my test computer is looking at the new DOMCON02 as its WSUS server.

However, no matter what I seem to do, the WSUS 2016 server doesn't seem to see any computers. I keep getting the message: Your WSUS server currently shows that no computers are registered to receive updates.

The new WSUS server itself seems to be functioning normally. It was able to sync to Windows Update without an issue. It just doesn't see these test computers.

I feel like I'm missing something easy. Why isn't WSUS seeing the two new computers? Is there a delay? Does it take a few hours for it to register the change? I've tried rebooting but it still doesn't see anything. Could it be because the Group Policy and Domain Controller are all still on Windows Server 2008 R2 and the Update service is running 2016?

If screenshots or more information is required, just ask.

Thanks
TarkisalAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

McKnifeCommented:
WSUS is passive, clients are active. The server only visualizes what the clients report. So look at the client side, not the server side.
Use wuinstall on the command line at the client to test: https://web.archive.org/web/20151227002916/http://www.hs2n.at/component/docman/doc_download/11-wuinstall-11-32-bit
Syntax: wuinstall /install
0
DonNetwork AdministratorCommented:
Try the following command on them

wuauclt.exe /resetauthorization /detectnow

https://support.microsoft.com/en-us/help/555974
0
TarkisalAuthor Commented:
It's giving me a message back saying it can't find the server. What does that tell me? Is something blocking the path back?
2017-12-13_16-30-42.png
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

McKnifeCommented:
By default, wsus uses port 8530. Your client is set to contact port 80, that seems wrong, adjust that.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
TarkisalAuthor Commented:
Sorry for the delayed response. This appears to have been the problem. When I added the port in the GP my test computers were able to connect and the WSUS server showed them. Thanks!
0
McKnifeCommented:
You are welcome.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2016

From novice to tech pro — start learning today.