Asked by:
Wsus server more than 23 client computer not showing in WSUS console

Question
-
Wsus server more than 23 client computer not showing in WSUS consoleWednesday, July 3, 2019 6:10 AM
All replies
-
Hello Mohanrajlive,
1. Check if the firewall on client block traffic on port 8530, we may turn off the firewall to check if it could work;
2. Check if reset windows update component on clients could work:
How to reset windows update component:
https://support.microsoft.com/en-us/kb/971058
3. Try restart the computer and restart windows update service
4. Also run server cleanup wizard on WSUS server to check the result.
5.If it still doesn't work, you may post the detailed event log on client for further troubleshooting.
Also go through below link:
Best Regards,
Shumanyu Goel
Please remember to mark the replies as answers if they help.
- Proposed as answer by Hamid Sadeghpour SalehMVP Wednesday, July 3, 2019 7:06 AM
Wednesday, July 3, 2019 6:36 AM -
Hi,
First check if any client can access the WSUS server. Check the method You can use a browser on the client computer to access the address of the following structure:
- http://WSUSserverNAME:PortNUM/selfupdate/iuident.cab
(e.g http://WSUSserver001:8530/selfupdate/iuident.cab)
And make sure you can open/download the file. Otherwise check the connection between the client and the server.
Secondly, please confirm that the clients of these batches are built using a unified template? This may result in duplicate SusClientID values. For reference, the following script can also implement this feature, please execute in the elevated CMD on the client computers:
net stop bits net stop wuauserv reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientIDValidation /f rd /s /q "C:\WINDOWS\SoftwareDistribution" net start bits net start wuauserv
wuauclt /resetauthorization /detectnow % For Windows 7 % usoclient.exe startscan % For Windows 10 %
Then check if this part of the client computer can be detected in the WSUS console.
Regards,
Reply back with the results would be happy to help.
YicPlease remember to mark as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- Proposed as answer by Hamid Sadeghpour SalehMVP Wednesday, July 3, 2019 7:06 AM
Wednesday, July 3, 2019 6:45 AM - http://WSUSserverNAME:PortNUM/selfupdate/iuident.cab
-
our entire client connected with WSUS server even windows update also is going without any issue but where we are unable to see the client in WSUS Server console there are showing only any 23 computed only even computer name also change very often but also showing client count 23 only. i though which is console view count limitation or any restriction .Wednesday, July 3, 2019 12:00 PM
-
Am 03.07.2019 schrieb mohanrajlive:
our entire client connected with WSUS server even windows update also is going without any issue but where we are unable to see the client in WSUS Server console there are showing only any 23 computed only even computer name also change very often but also showing client count 23 only. i though which is console view count limitation or any restriction .
Your Clients are cloned, most of them have the same SUSClientID, this
is the reason for only 23 Clients.Winfried
WSUS Package Publisher:
https://github.com/DCourtel/Wsus_Package_Publisher
https://docs.microsoft.com/en-us/windows-server/administration/windows-server-update-services/get-started/windows-server-update-services-wsus
http://www.wsuswiki.com/Home
GP-PACK - PRIVACY AND TELEMETRIE: http://www.gp-pack.com/Wednesday, July 3, 2019 2:10 PM -
anyone can you help me ?Thursday, July 4, 2019 9:11 AM