Can someone point me to tips where the WSUS server is not seeing new computers on the network?
Who is Participating?
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.

Justin OwensITIL Problem ManagerCommented:
The machines on your network need to be pointing to the WSUS server.

MS Documentation on WSUS can be found here:

If you have access to GPO, then a GPO would be an easy way to point your machines to the new server:

If you have any specific questions, please let us know.
I  used AD GP to create groups and applied a group policy with the WSUS template to configure the WSUS settings. From there, placed the computers in the group, and then few minutes later they show up in WSUS
You may need to either reboot the workstations that don't show up or run "wuauclt /detectnow". Also check the windowsupdate.log file in the WINNT or WINDOWS folder to see if they're attempting to connect to the WSUS server. That may give you more info to work on.
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

ikeeponAuthor Commented:
I will try all said utilities.  The issue is that the WSUS saw most computers on the network but when a computer was upgraded by switching it out with a newer model WSUS has not seen most (maybe 2%).  The computers are also ghosted so I think that may come into the mix.
Did you sysprep (or use a utility to change SIDs) on the ghosted computers?
ikeeponAuthor Commented:
No, that wasn't done and has consequently caused a problem other programs as well.
WSUS: Script to delete duplicate SID created by Disk Imaging / Disk Cloning
WSUS Clients do not report on WSUS Server. This script will delete AccountDomainSid, PingID, SusClientId registry keys if exists. Automatic Updates with WSUS doesn’t work if the workstation is installed via Disk Imaging or Disk Cloning.
Back to the top Back to the top
WSUS: Script to delete duplicate SID created by Disk Imaging / Disk Cloning
When you ghost an image and when that machine is a WSUS Client, it may not appear in the Windows Server Update Services (WSUS) console or sometime, it may not communicate with WSUS Server as it will have the duplicate registry values. More information on

Automatic Updates with WSUS doesn’t work if workstation is installed via Disk Imaging / Disk Cloning;

If you have multiple computers with this behavior, then you can add a logon script which can do the task automatically. Note this has to be done only once.
@echo off
Echo Save the batch file "AU_Clean_SID.cmd". This batch file will do the following:
Echo 1. Stop the wuauserv service
Echo 2. Delete the AccountDomainSid registry key (if it exists)
Echo 3. Delete the PingID registry key (if it exists)
Echo 4. Delete the SusClientId registry key (if it exists)
Echo 5. Restart the wuauserv service
Echo 6. Resets the Authorization Cookie
@echo on
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
net start wuauserv
wuauclt /resetauthorization /detectnow
These registry entries will be re-created at the next detection cycle.

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
ikeepon here is your solution>>  this answer from our own EE snewo was accepted as a solution to this problem.
Title: WSUS Client Computer not showing up
How WSUS Works with Microsoft Update

If you are using WSUS, you configure synchronization options—for example, products, update classifications, and languages—through the WSUS console, and do not go directly to Microsoft Update. WSUS connects directly to Microsoft Update to get both the update metadata and the update files as specified by the content storage options you configure through the WSUS console.

You manage all synchronized updates on the WSUS console. The Update News section on the Windows Server Update Services pageon TechNet provides links to a list of Windows and non-Windows updates to make it easier for you to see recently published new, revised, or rereleased updates. This can help you determine what updates to include in your WSUS update synchronizations.

ikeeponAuthor Commented:
I have not had a chance yet to implement suggested solutions.
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
Operating Systems

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.