Two computers with the same name on domain

Two computers on our domain, both intermittently on the network, were having issues with 'lost trust relationship.' I discovered that they both had the same computer name on our domain. When I confirmed this, I removed Comp #1 from the domain, then rejoined. Next I renamed Comp #2, then unjoined and rejoined the domain. Problem: Comp #2 now appears in AD, but with the properties of Comp #1; and Comp #1 can no longer be found as a computer object in AD; it's as though they merged into one under the new name after it joined the domain.

How can this be resolved so they are both computer objects in AD with their individual names and properties?
sjcallenAsked:
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.

KwoofCommented:
Now they have 2 different names...1 item done.

Move both to a workgroup.

Check AD to make sure the computer names are gone...if not, delete them to make sure AD will not get confused again.

Re-add both computers to the domain.

(I am assuming the computers were NOT created from the same base image or sysprepped properly...computers with the same SID will confuse AD as well)
0

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
Will SzymkowskiSenior Solution ArchitectCommented:
When adding computers to the domain you should pre-stang them. Meaning create the computer objects first then adding the computers using the accounts created. This will resolve your issue.

Will.
0
sjcallenAuthor Commented:
Thank you - done - success!
0
SandeshdubeySenior Server EngineerCommented:
It seems that machines are created from and image that is NOT prepared with sysprep.If this is the case refer below links.Also ensure that only the domain DNS is configured on client/member server and None else like public IP address.

What Is Sysprep?  http://technet.microsoft.com/en-us/library/dd799240%28v=ws.10%29.aspx

How Sysprep Works  http://technet.microsoft.com/en-us/library/dd744512%28v=ws.10%29.aspx

How to Sysprep in Windows Server 2008 R2 and Windows 7  http://briandesmond.com/blog/how-to-build-a-sysprep-answer-file-for-imagin

It could be also that multiple DC are present and object are still not replicate force the replication and check.
0
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
Active Directory

From novice to tech pro — start learning today.