*Seizing Operations Masters for Quick Restoration of Functionality
*Possible Solutions for Restoring Domain Controllers.
Now here we have :
DC1 has Domaing Naming, Schema master Roles
DC2 has PDC emulator, RID master Role.
DC3 has Infrastructure master.
Here DC3 blows up, The good news is , you still have two other DC running so users can still log in. You need to get an Infrastructure Master back online as fast as you can first, and then decide how to get DC back.
Seizing Operations masters for Quick Restoration of Functionality
How to seize an Operations Master role when the Machine Doesn't Exist Anymore:
*The GUI :
- Try to move an Operations Masters from the GUI like you would normaly.
* NTDSUTIL:
- You can also use NTDSUTIL to seize an Operations Master rle with the following operation:
1) Go into NTDSUTIL like normal, and don't forget to type activate instance NTDS as your first command.
2) Type roles to move into the Roles context.
3) Type help to get a list of the commands.
- To seize the infrastructure Master, type seize infrastructure master.
How to transfer Roles through GUI ?
1) Open AD users and computers on DC2
2) Select Domain > Right click
3) Go to Operations Masters > Click on Infrastructure Master > Then you can see a message "The current operations master is offline. The role cannot be transferred".
4) Click on Change > Then you will be prompted are you sure you want to transfer this role to GC server > click Yes.
5) A message would be prompted saying that FSMO operation failed. Do you want to attempt a forced transfer > Click No.
Lets use through Command prompt.
1) Open cmd.
2) Type ntdsutil
3) type activate instance NTDS
4) type Roles
5) type help
6) type connections
7) type connect to domain globamantics.com
8) type quit
9) type seize infrastructure master
10) click yes on the prompt window.
Possible Solutions for Restoring DC it all depends:
*If the hardware and Server 2008 OS is Okay but AD has been trashed, you can just do a System state Restore from the last backup.
*If your Hardware is trashed, build a new server 2008, install Server backup, and do a recovery of the last full backup of DC3 (Require the Backup to be on a DVD or NAS)
*Last, if you don't have access to a set of backup files, since DC3 is more of an auxiliary machine, you can
- Delete the DC3 computer account from the DC OU.
-Build a brand new server 2008 machine, install AD DS and run DCPromo.
-Let replication do the job of restoring the AD database.
- Move the Infrastructure master back to the New DC3.
After this class, what you can do :
* Seize an Operations Master and thereby transfer the functionality to a live Domain Controller.
* Identify a methodology to restore a Domain Controller to functional Status.
*Possible Solutions for Restoring Domain Controllers.
Now here we have :
DC1 has Domaing Naming, Schema master Roles
DC2 has PDC emulator, RID master Role.
DC3 has Infrastructure master.
Here DC3 blows up, The good news is , you still have two other DC running so users can still log in. You need to get an Infrastructure Master back online as fast as you can first, and then decide how to get DC back.
Seizing Operations masters for Quick Restoration of Functionality
How to seize an Operations Master role when the Machine Doesn't Exist Anymore:
*The GUI :
- Try to move an Operations Masters from the GUI like you would normaly.
* NTDSUTIL:
- You can also use NTDSUTIL to seize an Operations Master rle with the following operation:
1) Go into NTDSUTIL like normal, and don't forget to type activate instance NTDS as your first command.
2) Type roles to move into the Roles context.
3) Type help to get a list of the commands.
- To seize the infrastructure Master, type seize infrastructure master.
How to transfer Roles through GUI ?
1) Open AD users and computers on DC2
2) Select Domain > Right click
3) Go to Operations Masters > Click on Infrastructure Master > Then you can see a message "The current operations master is offline. The role cannot be transferred".
4) Click on Change > Then you will be prompted are you sure you want to transfer this role to GC server > click Yes.
5) A message would be prompted saying that FSMO operation failed. Do you want to attempt a forced transfer > Click No.
Lets use through Command prompt.
1) Open cmd.
2) Type ntdsutil
3) type activate instance NTDS
4) type Roles
5) type help
6) type connections
7) type connect to domain globamantics.com
8) type quit
9) type seize infrastructure master
10) click yes on the prompt window.
Possible Solutions for Restoring DC it all depends:
*If the hardware and Server 2008 OS is Okay but AD has been trashed, you can just do a System state Restore from the last backup.
*If your Hardware is trashed, build a new server 2008, install Server backup, and do a recovery of the last full backup of DC3 (Require the Backup to be on a DVD or NAS)
*Last, if you don't have access to a set of backup files, since DC3 is more of an auxiliary machine, you can
- Delete the DC3 computer account from the DC OU.
-Build a brand new server 2008 machine, install AD DS and run DCPromo.
-Let replication do the job of restoring the AD database.
- Move the Infrastructure master back to the New DC3.
After this class, what you can do :
* Seize an Operations Master and thereby transfer the functionality to a live Domain Controller.
* Identify a methodology to restore a Domain Controller to functional Status.
No comments:
Post a Comment