Main Domain Controller Died, but you have a backup domain controller

Let’s say your main domain controller died due to a BSOD and will not come back up. The main domain controller was also your DNS Server and your DHCP server. You will need another domain controller already in place that will replace the domain controller that died. This means seizing FSMO roles and replacing any services that are now gone.

1. Seize FSMO Roles using the ntdsutil command on another domain controller.

2. Enter netdom query fsmo in command prompt to check where the FSMO roles currently live.

3. Open a command prompt and enter ntdsutil.

4. Enter “roles”. Enter “connections”. Enter “connect to server <Name of server you’re on>”.

5. Enter quit.

6. Seize fsmo roles using commands “seize schema master”, “seize naming master”, “seize rid master”, “seize pdc”, “seize infrastructure master”.

7. Enter quit and then q.

8. Confirm the roles have been transferred by entering “netdom query fsmo” in the command prompt.

9. If your domain controller isn’t a DNS server. First point your DNS settings to 127.0.0.1.

10. Optionally, change your IP Address to the IP Address of the dead domain controller. This way, all other computers pointing to the dead domain controller will now point to the new domain controller.

11. Add roles of DNS Server and DHCP Server to the domain controller.

12. Configure the DHCP Server.

13. Configure DNS Server.