BUG: 2016 server allows you to create machines with same name
I added a 2016DC to my 2012 and 2012r2 DCs a couple weeks ago.
Today I added a new PC into the network.
The problem is I used the same name as a PC already on the network (shouldn't be an issue Windows always catches this and doesn't allow it).
AD didn't catch this and actually updated the original PC in AD and did not add a second PC or warn that the name was already in use. If I look at the modified date of the original pc in AD it shows it was modified at the same time I supposedly added the new PC.
I then not totally believing this was happening renamed the pc and sure enough the original PC in AD changed to the new name of the new PC I just added.
Seems like a major bug.
Did you reset the computer account? this is one scenario I can think of it would happen
Jon Baker commented
So, I am curious if this updates the existing DNS entry or not. Have you been able to determine if there is any issue with DNS when the new PC is created?
David Hoffman commented
So Active Directory never had a mechanize to stop you from creating a PC with the same name?
This behavior is 17 years old. :)