rebuilding the primary dc

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I tried to ghost one drive to another to get a larger drive. apparently this
destroyed active directory for some reason. i had no bkup for it. so I
reinstalled server and active directory (off the network) named it what it
was. During that time I forced another domain controller to be primary. now i
put it back on the network but how do I get active directory computers and
users etc. to the new controlloer and make it the primary again.
 
The problem here is that you've gone and created a new domain - a separate
one to the original. Your clients are not members of this domain, nor are
the users.

If this was the only DC, you will have to disjoin the client computers from
the domain they currently reside on (add each one to a workgroup) and then
join them to the new domain (the current one).

If you had multiple DCs and you seized the OM roles to another DC, what
you'll have to do with the broken DC is demote it (offline) and promote it
online and use the option "new DC in an existing domain". Replication will
then take care of all the user, computer, etc. objects.

One thing you need to note, is that you should follow these instructions
before doing this:
-- http://support.microsoft.com/?id=216498


Then you can promote the machine back into the original domain.

--

Paul Williams

http://www.msresource.net
http://forums.msresource.net


I tried to ghost one drive to another to get a larger drive. apparently this
destroyed active directory for some reason. i had no bkup for it. so I
reinstalled server and active directory (off the network) named it what it
was. During that time I forced another domain controller to be primary. now
i
put it back on the network but how do I get active directory computers and
users etc. to the new controlloer and make it the primary again.
 
Shaun here is a description of what I went through to save my AD (hope it
helps).
What you need to have/keep is a "System State" backup of your DC. This is
where/when the AD info is saved.


Synopsis of my past problem:

Due to some bad advice one of our DCs got royally messed up. So I shut
down the machine and remove it from the system.
(MS Doc #216498 & #260378 & # 255504) And I manage to stabilize the network
so people can work.

The consultant declares that we have to Rebuild Everything and give him
lots of money to do it.

I grab an old workstation and install fresh server software. I go
through the restore
process and bring it back to a system state of just before the problem. Set
it up on it's own Network, can not let it talk to the production network
yet. Seize the FMSO roles, use the metabase Cleanup and MS doc 216498, then
setup DNS so I can get it
to work by itself. So now I have a DC with a my AD as it was before the
problem.
Then on my messed up/rebuilt server I do a Dcpromo and join it to my
restored
AD so that it is once more a DC. I transfer the FMSO Roles and DNS to the
messed up/rebuilt server.

On the production Network I take one DC at a time and do a Dcpromo. Move it
to the restored network and do Dcpromo to make it a AD DC on my restored
network with my original AD setup info. Then before I remove the last DC
from the production network I disjoin the workstation /server from the
restored network transfer and balance out the FSMO roles, as well as DNS &
DHCP. And make sure all is well. Then that night, I shut down the
production network, rearrange some plug in the server room patch panel.
Reboot the whole system. And we have our AD as it was before the troubles.


Ok a few services and problems to sort out. Have to edit the logon scripts
and I have messed up my Certificate & Terminal License servers with the
changes.
 
Back
Top