Number of clients are not reporting to WSUS

We are having problems windows 10 clients reporting to WSUS.A very high percentage of clients are not reporting. Some of them are reporting fine with no problem. All clients are with same configuration and connecting to the same network. I have attached logs of both clients one was connected and one wasn't .I really need help of some WSUS experts who can look in to the log and give me some suggestions please  . I have made some changes in logs and changed server name but they are obviouslyWindowsUpdate-B25122-Failed---Copy.txt exactly the same.
Who is Participating?

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

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.

Mal OsborneAlpha GeekCommented:
Were these client machines imaged in some way?

Sometimes imaging can be problematic. Each machine reports back to the WSUS server with a GUID, kinda like a serial number. The name is displayed, but not used to identify which machine is which. Thus, if you have several machines with identical GUIDs, they, WSUS will assume they are all the same machine. The name displayed will be that of the most recent machine to report.

Here is a procedure to fix that:

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
wajhiuddinAuthor Commented:
Thanks for your response We do clear susid running  our script after when they get cloned . and before reporting to WSUS
By they way I ran this bat file what you send in a link on one of the client and it did reported afterward. which is strange.  I just don't know if susid is the problem then why WSUS server is assigning similar ID to different clients. ?
Hello ThereSystem AdministratorCommented:
We had the same issue... We had to delete all superseded updates. After that and running my custom script I resolved the issue.
For Win 10 you need to use UsoClient.exe command.

net stop wuauserv
net stop bits
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
RD /s /q %windir%\SoftwareDistribution
net start wuauserv
net start bits
wuauclt /resetauthorization /detectnow

Open in new window

Also see the best answer here:
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

From novice to tech pro — start learning today.