WSUS 3.0 SP1 BUG - Computers with same configuration are overridden !
I am facing a bug while updating my system. I have a number of common systems on the network. Each of the client system on the network has a different SusClientID. Which is used by server to identify the clients. Now this system simply override each other in WSUS so that there is only a single pc is seen in console. But due to some issue everytime after a cookie refresh on the client system it overrides the other one. I had checked, there is only single computer in the database but the ComputerID keeps on changing when the client syncs. Now if any news changes are done like adding a hardware or software or by modifying the system name, it looks to be working. I am confused with the SusClientID. Why it is used here. If all client config is common then this must not be used. Hope you people will understand what I am trying to do here.
Re: WSUS 3.0 SP1 BUG - Computers with same configuration are overridden !
GUID is the main ID of a client system on your network. So when everytime the SUSID is modified there are multiple entries created. This might be some kind of additional feature of WSUS which is used to avoid duplication. I do not think it is a issue or a bug.
Re: WSUS 3.0 SP1 BUG - Computers with same configuration are overridden !
I am also a bit confused. I was reading for this kind of issue on WSUS and landed here. There is a question that I want to ask too. To some extent it is not fare to have a common computer name on the entire network. Common names can cause a tons of errors in DC which is not notified instantly unless you see in logs. I had seen a number of bugs on WSUS behind ISA where ample of systems are working on their own IP. If a system is restored through image on common hardware then there are chances of duplicate client name and IP on the network.
Re: WSUS 3.0 SP1 BUG - Computers with same configuration areoverridden !
That is common with me. All of my client on the network are installed from a image restore disc. So ample of them are having common configuration. I had modified the registry and removed WSUS Guid. And then I had created the image disc of system. So after restore a new ID should be generated on its own when then system boots up. For cookie refresh run wuauclt /resetauthorisation. Buy this the client will take the new ID. Now in a common workgroup things works a bit differently. There WSUS is not installed on the server. There are very less issue seen here as all of them communicate through netbois name.
Re: WSUS 3.0 SP1 BUG - Computers with same configuration are overridden !
It is much better if you rework on the WSUS configuration from scratch. That is the only way to get your settings back proper. The below link will provide you a bit of detailed information on the same.
Step-by-Step Guide to Getting Started with Microsoft Windows Server Update Services 3.0
Re: WSUS 3.0 SP1 BUG - Computers with same configuration are overridden!
What I know that FQDN is of no use here. It cannot help you much here. Also there is no chances of having a common FQDN. Client system uses a different identifiers to communicate with the server. WSUS server removes the old record when there are duplicate FQDN.
Re: WSUS 3.0 SP1 BUG - Computers with same configuration are overridden !
In my ways this is getting complicated. I had used WSUS based on the above suggestions. Every client connections with a system with anonymous connection. The value mentioned does not reflect a secure connectivity. Ample of them are auto-generated guid. If this is common then the SusClientID will also give duplicate result. If you can see those duplicates then remove the duplicate value of SusClientID and SusClientIDValidation. Run wuauclt /resetauthorization /detectnow.
Re: WSUS 3.0 SP1 BUG - Computers with same configuration are overridden !
What I know that you will have to configure a independent WSUS server on each of your clients location. That will quiet remove the issue of common names and domains.
Re: WSUS 3.0 SP1 BUG - Computers with same configuration are overridden!
Just want to confirm that does it works for two system which has a qualified dns name. The same can be found under System Properties.
Re: WSUS 3.0 SP1 BUG - Computers with same configuration are overridden !
Hi Harry,
Thanks for the reply. I had previously checked that setting; it was not an issue.
I assure you; I tested numerous scenarios and strongly believe that WSUS 3.0 is looking only at hostname.
Thanks!
Re: WSUS 3.0 SP1 BUG - Computers with same configuration are overridden !
I struck a similar issue at my last job. We used ghost to image machines.
It turned out that the last version of wsus (not current, no idea if current has same settings) was detecting the pc's sid
We ended up running newsid across all our desktops and then they started behaving in wsus
Natalie