You can use the Forest Recovery Console to view the current Flexible Single Master Operations (FSMO) role owners in your recovered Active Directory forest and manually change the FSMO role owners if necessary.
During the recovery, Recovery Manager for Active Directory uses an internal algorithm to automatically assign FSMO roles to the recovered domain controllers. After the recovery completes, you can view the current FSMO role owners and selectively reassign the FSMO roles if necessary.
NOTE |
Recovery Manager for Active Directory uses the domain controller access credentials to manage FSMO roles. For more details, refer Table 24 in the General tab section. |
In the Forest Recovery Console, open the recovery project in which you want to view the current FSMO roles.
On the menu bar, select Tools | Manage | FSMO Roles.
Use the dialog box that opens to view the current FSMO role owners and reassign FSMO roles as necessary.
You can use the following elements:
Elements you can use
Element | Description |
---|---|
Suggest Previous Owners | Allows you to automatically distribute FSMO roles to the domain controllers (owners) that held these roles before the recovery (that is, the owners stored in the recovery project). After you click this button, use the Assign Role To column to view or specify new role owners. If a FSMO role owner no longer exists, the most optimal existing owner will be selected for that role. |
Suggest Optimal Owners | Click this button to automatically distribute FSMO roles to the most optimal existing owners in the recovered Active Directory forest. |
Clear | Click this button to undo the changes you have made in the Assign Role To column. You can only use this button before you apply the changes you have made. |
FSMO Roles | Lists all FSMO roles in the recovered Active Directory forest. |
Current Owners | Lists the current owner of each FSMO role in the recovered Active Directory forest. |
Assign Role To | Use this column to manually select a new owner for the corresponding FSMO role. You can also use this column to view the automatically selected new owners after you click the Suggest Prerecovery Owners or Suggest Optimal Owners button. |
You can use the Forest Recovery Console to view or change DNS client settings for each domain controller in your recovery project. In the DNS client settings, you can define the DNS servers used by the domain controller. You can manage DNS client settings before or after recovery of your project.
NOTE |
Recovery Manager for Active Directory uses the domain controller access credentials to manage DNS client settings. |
In the Forest Recovery Console, open the recovery project in which you want to view or change the assigned DNS servers.
On the menu bar, select Tools | Manage | DNS Client Settings.
In the dialog box that opens, use the following elements:
Elements you can use
Element | Description |
---|---|
Suggest Previous Settings | Allows you to revert to the DNS client settings the domain controllers in your recovery project used before the recovery (that is, the settings stored in the recovery project). |
Edit | Allows you to change the DNS client settings for the domain controller selected in the list. |
Undo | Allows you to undo the changes you have made. |
Apply | Applies the changes you have made. |
A firewall enabled in your environment may block traffic on ports used by Recovery Manager for Active Directory, preventing you from backing up or restoring data. Before you start using Recovery Manager for Active Directory, make sure your firewall does not block traffic on ports used by Recovery Manager for Active Directory. For more information about these ports, see the Deployment Guide supplied with this release of Recovery Manager for Active Directory.
This section provides instructions on how to configure the built-in Windows Firewall enabled on Windows Server 2008 R2 or higher domain controllers in a domain or forest you want to recover, so that Recovery Manager for Active Directory could recover that domain or forest. To ensure a successful recovery, create the following Windows Firewall security rules on all Windows Server 2008 R2 or higher domain controllers in the domain or forest (leave the default values for settings not mentioned below):
Rule 1 (inbound)
Rule type: Custom
Program path: %SystemRoot%\System32\Svchost.exe
Service settings: Windows Management Instrumentation (Winmgmt)
Protocol: TCP
Local ports: Any
Remote ports: Any
Local IP addresses: Any
Remote IP addresses: Any
Action: Allow the connection
Rule profile: Domain, private, and public
Allowed users: Any
Allowed computers: Any
Rule 2 (inbound)
Rule type: Custom
Program path: System
Service settings: Apply to all programs and services
Protocol: TCP
Local ports: 445
Remote ports: Any
Local IP addresses: Any
Remote IP addresses: Any
Action: Allow the connection
Rule profile: Domain, private, and public
Allowed users: Any
Allowed computers: Any
Rule 3 (inbound)
Rule type: Custom
Program path: <Product installation folder>\FRRestoreService64.exe
The default product installation folder is %ProgramFiles%\Quest\Recovery Manager for Active Directory.
Service settings: Apply to all programs and services
Protocol: TCP
Local ports: RPC dynamic port range
Remote ports: Any
Local IP addresses: Any
Remote IP addresses: Any
Action: Allow the connection
Rule profile: Domain, private, and public
Allowed users: Any
Allowed computers: Any
Rule 4 (inbound)
Rule type: Custom
Program path: %SystemRoot%\System32\Svchost.exe
Service settings: Remote Procedure Call (RpcSs)
Protocol: TCP
Local ports: RPC dynamic port range
Remote ports: Any
Local IP addresses: Any
Remote IP addresses: Any
Action: Allow the connection
Rule profile: Domain, private, and public
Allowed users: Any
For more information about RPC dynamic port range, refer to the following Microsoft Support Knowledge Base articles at https://support.microsoft.com:
How to configure RPC to use certain ports and how to help secure those ports by using IPsec
How to configure RPC dynamic port allocation to work with firewall
The default dynamic port range for TCP/IP has changed in Windows Vista and in Windows Server 2008
When planning for Active Directory forest recovery, you should first have a detailed topology map of your forest. The map should list all the information about the domain controllers, such as their names, FSMO roles, backup status, and the trust relationships between them.
IMPORTANT |
Make sure that Forest Recovery Agents are installed and function properly on all domain controllers in the forest. |
Because of the complexity and critical nature of the forest recovery process, it is strongly recommended that Active Directory administrator observe the following rules to prevent the forest failure:
Use only reliable and tested hardware, such as hard disks and uninterruptible power supply.
Test any new configuration in a test lab before deploying it in your environment.
Ensure that each domain in the forest has at least two domain controllers.
Keep detailed logs about the health state of Active Directory on a daily basis, so that in case of a forest-wide failure the approximate time of failure can be identified.
Regularly back up all domain controllers in the forest with Recovery Manager for Active Directory.
Use the Forest Recovery Console to create a recovery project for your forest. Verify the settings of your forest recovery project on a regular basis, especially when there are membership changes to the Enterprise Admins or Domain Admins group. This helps ensure that the IT staff fully understands the forest recovery plan.
Recovery Manager for Active Directory allows you to restore a domain in the forest to its state at the time of the last trusted backup. Consequently, the restore operation will result in the loss of at least the following Active Directory data:
All objects (such as users and computers) that were added after the last trusted backup.
All updates made to existing objects since the last trusted backup.
All changes made to either the configuration partition or the schema partition in Active Directory (such as schema changes).
Additionally, any software applications that were running on the domain controllers will need to be reinstalled on the domain controllers after the forest is recovered.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center