Avatar of jskfan
jskfan
Flag for Cyprus asked on

How to Avoid the message "Object Already Exist in Active Directory"

How to Avoid the message "Object Already Exist in Active Directory"

We are in the process of re-imaging Windows computers Win 7 to Win 10. at the end when we rename computers and rejoin them to the domain manually, we get the message  "Object Already Exist in Active Directory".
we ll have to delete computer object in AD in order to rejoin it to the domain.

Is there a work around that enables us to rejoin computer to the domain without touching AD.

Thank you
Windows Server 2008Active Directory

Avatar of undefined
Last Comment
Shaun Vermaak

8/22/2022 - Mon
Jose Gabriel Ortega Castro

If you don't want to touch AD, then
  • Do the reimaging,
  • take original and remove it from the domain
  • Start the new imaged.
  • Take it out of the domain and re-join it

This way you make sure that the object is not on AD before adding it again.
jskfan

ASKER
i have been told that when you join a computer to the domain, if you specify the whole fqdn name in the domain field, then you will get the message that the object already exist in AD, if you you type just the first part of the domain then the message will not popup .. probably it will just use the existing one.

I haven not tested yet
Jose Gabriel Ortega Castro

hmm that doesn't have any sense my friend.

if your host is thishost
and your domain is : test.com and the
prewindows of your domain is test.

the object on ad will be
test\thishost
or
thishost.test.com

no matter what you do that's the unique identifier for your domain.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
jskfan

ASKER
you have seen sometimes you have to change the computer to Work Group before you join it to the domain if it was already joined before... there should be a work around that too..

example:

I have computer1.test.local
and there is a trust issue..

usually you will delete the computer object in AD and rejoin computer1 to the work group ,reboot, then rejoin it to the domain.
there should be work around that..
ASKER CERTIFIED SOLUTION
Jose Gabriel Ortega Castro

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
jskfan

ASKER
Thank you
Jose Gabriel Ortega Castro

glad to help you
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
Shaun Vermaak

Give your join account change permission on computer account (exclude sensitive computers) then you will not have this issue to begin with