Replacing A Primary Domain Controller (NT4)
Last Updated: 06 May 2004
*** PLEASE NOTE: Link(s), If Provided, May Be Wrapped ***
You should always have at least one BDC on your NT4-based
domain, so that if your PDC dies, you will still retain
your user accounts.
In the event that your PDC does meet with an untimely
death, here's what you have to do to get your network
back up to speed:
MYPDC = Current PDC
MYBDC = Current BDC
STEP 1: Promote your BDC (MYBDC) to the PDC
STEP 2: Fix or replace hardware and build new system as
a BDC (called MYPDC)
STEP 3: Once MYPDC is back up and running, promote it
back to PDC
Here are issues to avoid....
ACTIVE DIRECTORY ISSUES
The notion of Primary vs Secondary controllers is largely
done away with in Active Directory (2000/2003), even if
you consider the Flexible Single Master Operation (FSMO)
Roles in AD.
Building and rebuilding AD domain controllers is far more
straightforward than it was under NT4. Here are some
issues to consider with AD domain controllers.
WHITEPAPERS & TECH DOCUMENTS
• For Windows 2000 or 2003 with Active Directory, you can
rebuild your domain controller and then restore a recent
SystemState Backup, or build a clean DC, and seize or
transfer the appropriate FSMO roles.
• SystemState backups are very important for AD recovery.
• Use ADSIEdit to clean up any obsolete AD objects after
an emergency Domain Controller rebuild or replacement.