I have a Server 2019 WSUS server. Everything appears to fine and currently synchronizing. I have a GPO configured and 2 systems listed in the WSUS OU. In the Update Services console I cannot get any computers to appear. Ran the following commands successfully. gpupdate /force, wuauclt /detectnow /reportnow, GPResult.exe /h c:\gpresult.htm. GPO is active on these 2 systems. Do I need more time for these top sync up? Any suggestion appreciated.
Thank you.
If they don't start popping back in within 72 hours, run the client side script on a couple and see if they pop in. They should.
First,
https://www.ajtek.ca/wsus/does-wuauclt-exe-detectnow-reportnow-work/
Second:
https://www.ajtek.ca/wsus/client-machines-not-reporting-to-wsus-properly/
Third - do any computers appear in Unassigned Computers? If so, you forgot to turn on client side targeting: https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-2-computer-groups-update-views/
Yes, you are quiet right.Do I need more time for these top sync up?
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi, I checked the registry and have the http path with port 8530 indicated. Sync completed last night but no system is listed. Ran windows update manually as suggested and took some time but now receive this error.
error: There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x8024401c)
RETRY
We’ll automatically download and install updates, except on metered connections (where changes may apply). In that case, we’ll automatically download only those updates required to keep Windows running smoothly.
Ran it a second time. Still working but I think I will get the same error. Should I switch to HTTPS path?
Continue to the troubleshooting part of clients not reporting to WSUS:
Hi Adam, when I go through the steps as per the link I get the following screen. 
That's correct - continue going through the troubleshooting - that one passed.
Still nothing. This is a fresh install of a server with WSUS role and SQL server. Everything seems to check out. I must be missing something simple.
What does the registry say for the clients?
What does this show from the client?
$(New-Object -ComObject "Microsoft.Update.ServiceManager").Services | Select-Object Name, IsDefaultAUService
9 people are following this question.
