WSUS 3.0 SP1 BUG - Computers with same configuration are overridden !

[techguru1]

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!

[qwdfwfwfw]

Hi,

There seems to be a way to spoof WSUS to accept computers with the same name. This isn't the most prettiest solution, but is working although :-)

REMARK: This only works when you have got different MAC addresses because the "SusClientIdValidation" regkey is generated using the MAC address.

It takes some small amount of time to manual editting the database:

1) Register the first computer to WSUS
2) Start Microsoft SQL Management Studio, and open the WSUS database (SUSDB)
3) Browse to SUSDB -> Tables -> dbo.tbComputerTarget, right-click on it and choose "Open Table"
4) In the column "FullDomainName", locate the computer, and change the hostname by clicking on it and modifying the name. Save and close the table
5) Open WSUS -> All computers and click on "Refresh"
6) Repeat the steps 1 to 5 for the other computers one by one.

Ok, please ignore the solution above.

When the computers are reporting again, the databse value is overwritten, which results in loosing computers within WSUS.

[ladykahu]

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