You can use Recovery Manager for Active Directory (RMAD) to manage the global catalog servers in your Active Directory® forest before or after the recovery. For example, you can view which domain controllers currently hold the global catalog server role and manually remove or assign the global catalog server role to the domain controllers you want.
| NOTE |
RMAD uses the domain controller access credentials to manage the Global Catalog servers. 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 manage the global catalog servers.
On the menu bar, select Tools | Manage | Global Catalog Servers.
Do one of the following:
To assign the global catalog server role to a domain controller, select the check box in the Global Catalog Server column next to that domain controller.
To remove the global catalog server role from a domain controller, clear the check box in the Global Catalog Server column next to that domain controller.
To sort or group the domain controllers in the list by the criteria you want, right-click anywhere in the list, and then select an appropriate command from the shortcut menu.
When you are finished, click the Apply button for your changes to take effect.
| TIP |
To avoid excessive replication traffic, it is recommended to assign one global catalog server role at a time. |
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. |
When you are finished, click Apply.
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 (RMAD), preventing you from backing up or restoring data. Before you start using RMAD, make sure your firewall does not block traffic on ports used by RMAD. For more information about these ports, see the Deployment Guide supplied with this release of RMAD.
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 RMAD 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 1a (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
PowerShell for the Rule 1a settings: New-NetFirewallRule -DisplayName "Rule 1a" -Group RMAD -Enabled True -Profile Any -Direction Inbound -Protocol TCP -Program "%SystemRoot%\System32\Svchost.exe" -Service WMI
Rule 2a (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
PowerShell for the Rule 2 settings: New-NetFirewallRule -DisplayName "Rule 2a" -Group RMAD -Enabled True -Profile Any -Direction Inbound -LocalPort 445 -Protocol TCP -Program System
Rule 3a (inbound)
- Rule type: Custom
- Program path: <Product installation folder>\FRRestoreService64.exe
The default product installation folder is %ProgramFiles%\Quest\Recovery Manager for Active Directory Forest Edition.
- 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
PowerShell for the Rule 3a settings: New-NetFirewallRule -DisplayName "Rule 3a" -Group RMAD -Enabled True -Profile Any -Direction Inbound -LocalPort RPC -Protocol TCP -Program "%ProgramFiles%\Quest\Recovery Manager for Active Directory Forest Edition\FRRestoreService64.exe"
Note: If the Online Restore Agent uses a specific TCP port then specify the TCP port in the LocalPort parameter. If the RPC dynamic port range is used then specify the RPC dynamic port range in the LocalPort parameter.
Rule 4a (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
PowerShell for the Rule 4a settings: New-NetFirewallRule -DisplayName "Rule 4a" -Group RMAD -Enabled True -Profile Any -Direction Inbound -LocalPort RPCEPMap -Protocol TCP -Program "%SystemRoot%\System32\Svchost.exe" -Service RpcSs
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
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center
