Hello;

WSUS One of the common problems after installation is that Clients do not appear on WSUS . However, there are many reasons for this situation.. If we list them;

The 80 port or 8530 of the antivirus or firewall (firewall) we use on the server. You may have blocked your port.. As you know, an article appears on the installation screen asking how we can access WSUS.. If we have selected http://WSUSADI:8530 here, we must check our ports.

Active Directory < as Preferred DNS address on the client. We need to make sure that the strong>DNS address is set. If we define the wrong DNS here, the client will not appear again.

WSUS on clients that are not visible on the HKLMSoftware Microsoft WindowsCurrentVersionWindowsUpdate registry path
“PingID” , “AccountDomainSid” , “SusClientId” deleting.
Automatic Restart the Updates service. We wait around 30 minutes. Wait for it to get a new SusClientID. Run wuauclt.exe /resetauthorization /detectnow on WSUS . Is WSUS Server installed on 8530 port, 80 , or set to another port? You can look it up in IIS at WSUS Properties. If for example 8530 except port 80 , when entering WSUS in GPO, WUServer >and WUStatusServer , you need to define the port as http://WSUSServerName:8530. After a certain time (within about 30 minutes) you should see the client computers in the WSUS console.

WindowUpdate under WINDOWS directory on the client. You can also check the log. In this file, you can see if there is any problem in the client’s communication with WSUS .

WSUS 3.0 does not have a web interface. It has a structure that we have completely configured through the MMC console and you can review reports and statistics.. In GPO , you need to define the path address that you defined when clients receive WSUS updates as http://Wsusserveradi. If it is running from an external port, you must specify it as http://wsusserveradi:portnumber.