Windows Forum

Ask something
Discussion Locked

DCPROMO error promoting mem server to DC

0 helpful
7 replies

by whatme?

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Or DC crashed at site 1.It had the major roles on it. I seized the roles on another DC at site 2.I also had another member server already on the domain. I wanted to bring the member server online at site 1.

After I type in dcpromo I specify additional domain controller for an existing domain, from there I type in madmin username/password I click next 4 times, then type in the password twice as the administrator account password to use. I press next, then it seems as though everything is going ok, (actually trying to update the active directory) then I get an error stating
the operation failed: because failed to modify the necessary properties for the machine account LUSDC2$ (which is the new computer name) access denied. ($ sign is attached by the error code)
Tried everything I can think of to promote it. What's wrong???
even took mem serv to site 2..side by side..same thing

help

7 replies

by cdue

One assumption: you have only One Domain and two sites.

There are as said in reply #2 a need to remove the DC1 if didnt already do that. After you seize roles make sure the original server is never brought back online.
You need to clean up a little:
Under sites & services you need to delete the server covering site 1 (if thats your crashed one. Also make shure you have subnets correctly set up, so that your subnets are covered by the correct DC: In this situation you will have to make all subnets controlled by DC2 (the live one)

In DNS: Remove all (frwd+reverse) entries for the crashed one: Then make sure you have reverse lookup zones for all your subnets (this is especially important if you are actually using sites)
Was the crashed DC the only DNS here?
(If so, just install DNS on DC2 and make it AD integrated before you make any more changes)

In the DC you are trying to promote: Do the following. Verify its configured to run in a subnet that is actually covered by bothSites & services and DNS (frwd and reverse)
Make sure the DNS are pointing to the live DC
(I assume its running DNS), Rejoin the domain (do not use the same DC name as the crashed one)and then run dcpromo again.

For your own piece of mind: Take a complete backup of you DC2 before changing anything: use NTbackup on the server itselves, point to another machine to store the backupfile

good luck

This discussion is closed to new replies.