Domain controler rename failed

Hello PLZ help

i fuc*ed up i think :-(

i wanted to rename a new server 2012R2(srv2012) to the name of the old server 2003(srv2003) server
the server 2003 rename wendt perfect(srv2003-O).

But when i tryed to rename server 2012 r2 it said that the name was already used
so i rebooted, when the server was online again the server name was changed on the server but NOT in AD
So now the AD cant connect to the FSMO roles on srv2012 , and i cant change the name back :-(
i did the rename from control panel -> system

in AD under domain controlers the servern is still listed as srv2012 but the servername is srv2003

what to do ??
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Salah Eddine ELMRABETTechnical Lead Manager (Owner)Commented:

I had the same issue, the solution is to manually rename all related values using LDAP.

Launch the ADSI editor (adsiedit.msc) and change all values with the old name srv2012 to your new name srv2003, then start the Netlogon service (it should be stopped and you should have error in the events).

Here is a screen shot of the ADSI Console


nova-cAuthor Commented:
Hello Salah

I think that is i a bit much, i think there is 4000 Places in adsi that name is

is it all Places ?? configuration and default naming context ??

and what server to do it on ??

Will SzymkowskiSenior Solution ArchitectCommented:
What are the error messages you are getting when you login to this DC after you changed the name? Was this DC the FSMO role holder? If it was your best bet would be to Seize the FSMO roles to another DC (transfer them gracefully if possible) and then decommission the server.

If you seize the FSMO roles from this DC you need to completely rebuild the OS and promote it as a new DC into the environment.

If you are not completely confident with modifying AD using ADSIEdit.msc you could really create more issues in your environment.


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
nova-cAuthor Commented:
ok here is what i did

1. disconnected the networkcard on new server
2. seize fsmo roles on old server- this guide
3. run Dcpromo /forceremoval on new server
3. renamed the new server 2 times and ended up with the servername i wanted on the domain :-)
4. cleaned up on old server - this guide
5. connected new server to network again and ran dcpromo

so far it is working :-)

thx alot
Salah Eddine ELMRABETTechnical Lead Manager (Owner)Commented:
Happy to know about your problem solved!
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
Windows Server 2012

From novice to tech pro — start learning today.