-- Main.ctucker - 31 Oct 2005
Procedure for Rebuilding a Domain Controller in the CSCF Active Directory Using Domain Synchronization
During the Summer of 2005, the domain controller
intacta in the CS-GENERAL domain died.
This left the CS-GENERAL domain relying strictly on one domain
controller (
serverus) for authentication. The recovery procedure that follows can be applied to
any circumstance where one domain controller is lost but another domain controller within that domain is
still healthy.
Since both
serverus and
intacta retain essentially the same information it
was possible to quickly wipe
intacta clean and place a new Windows 2003
image on the server. Once this re-created
intacta was promoted to domain controller
status again,
serverus proceded to update
intacta automatically. The procedure that follows can
be applied to any similar circumstance where a domain controller fails but the domain is still operational.
- If the failing domain controller (intacta) is an operational master, then
transfer (if possible) all operational master roles to an alternate
domain controller: serverus. This is done using the Active Directory
Users and Computers programme in the Administators tools.
- Shutdown intacta.
- Delete intacta's computer entry from the domain.
- Pull out intacta's mirror drive for safe keeping.
- Reapply CSCF Windows 2003 OS image onto intacta (following README
instructions).
- A copy of this OS image can be found on the core share of the CSCF app server cs-appserv.cscf.
- Boot intacta, follow through with driver install process.
- Specify elisa and eponina as primary and secondary DNS servers respectively.
- Enable DNS registration.
- Disable unused network adaptor.
- Patch the server using Windows Update in Internet Explorer.
- Convert intacta to a domain controller using dcpromo.exe command.
Follow the wizard to make intacta a domain controller in CS-GENERAL.
A server reboot will have to take place when this is complete.
- Wait for domain controllers in CS-GENERAL to synchronize (about 90 minutes).
- In Directory Service logs on intacta check for any remaining issues.
- Seize any remaining operational master roles to serverus using the
NTDSUTIL.EXE commmand. There is a nice Microsoft Knowledge Base article
KB-255504
which outlines how to perform this task.
- Reboot intacta.
- Reassign operational master roles back to intacta.
- Once statisfied that intacta is work properly, replace the server's mirror drive
and re-establish mirroring.