Unexpected behavior of the Forest Recovery Console when you update a recovery project created from a backup file: The "FSMO Roles" column in the right pane remains empty, although it should display information about FSMO roles of the DCs in the project.

WORKAROUND: Update the project: On the "Menu Bar", click Tools, and then click "Update Project with Changes in Active Directory".

Unexpected behavior in the Forest Recovery Console: When you group domain controllers by recovery method, some domain controllers may be included in the wrong group. This issue only occurs when you perform the following steps:

1. Group domain controllers in the Forest Recovery Console by recovery method.
2. Change recovery method for some of the domain controllers.

WORKAROUND: Change the grouping criteria for the domain controllers, and then again group the domain controllers by recovery method.

Unexpected behavior when you print out the Recovery Plan or Recovery Report: Your attempt to use the Portrait page orientation may have no effect, and the plan or report is printed out in the Landscape orientation.

WORKAROUND: This is a limitation in the Microsoft Report Viewer. Use the Landscape orientation since this is the orientation where everything fits.

Unexpected result of a forest recovery operation: Some member servers may erroneously appear as domain controllers in Active Directory. This issue may occur if the backups you used for the recovery were made before the computers in subject were demoted from domain controllers to member servers.

WORKAROUND 1: Run metadata cleanup to remove the unnecessary domain controllers from Active Directory.

WORKAROUND 2: Recover your forest by using more recent backups that correctly reflect the forest topology.

Your attempt to install the SCVMM agent on a source computer by using the Active Directory Virtual Lab console may fail with the error "<ComputerName> has an unsupported version of the Virtual Machine Manager agent installed." This behavior may occur if a virtual machine was previously created from the source computer by using some other Microsoft SCVMM server, and the SCVMM agent remained on the source computer after that.

WORKAROUND: Uninstall the SCVMM agent, and then install the agent by using the Active Directory Virtual Lab console.

1. Log on to the source computer and uninstall the agent manually from the list of installed programs (appwiz.cpl).
2. In the Active Directory Virtual Lab console, right-click the source computer, and then use the "Manage Agents | Install SCVMM agent" command to install the agent.

The Active Directory Virtual Lab console may erroneously state that the SCVMM agent is installed on a source computer added to the virtual test lab project, when in fact the agent is not installed. This behavior may occur if a virtual machine was previously created from the source computer by using some other Microsoft SCVMM server.

WORKAROUND: In the Active Directory Virtual Lab console, use the shortcut menu on the source computer to uninstall the SCVMM agent, and then install it back again.

The "Select preferred DNS server" recovery step may fail with the error "The process terminated unexpectedly." This issue only occurs on domain controllers that:

• Are being recovered with the "Restore from backup" method.
• Had a pending reboot when you started the recovery.

WORKAROUND: Retry last operation on the target domain controller.

Unexpected behavior: The Active Directory Virtual Lab may not automatically delete an unusable virtual machine whose creation has failed from the target virtual host.

WORKAROUND: Delete the virtual machine manually. To do so, you can use the native tools supplied with the third-party virtualization software with which you attempted to create the virtual machine.

When creating or opening a virtual lab project, you may encounter the error "Converter does not support agents of this version (<VersionNumber>)." This error shows up if any of the source computers in the virtual lab project have a VMware agent preinstalled and the agent version is earlier than the VMware vCenter Converter version you are using.

WORKAROUND: Update the VMware agent on the source computer to the latest version:

1. In the Active Directory Virtual Lab console, right-click the source computer in question.
2. From the context menu, select "Manage Agent | Install VMware agent".

The verify settings operation does not check whether the target virtual host supports the number of CPUs specified in the virtual lab project settings. As a result, if the number of CPUs is not supported, the virtual lab creation may fail with the error "The destination you selected does not support <Number> CPUs."

WORKAROUND: Before creating your virtual lab, ensure that the target virtual host supports the number of CPUs you have specified in the virtual lab project.

You may encounter the following unexpected behavior on the Backup Data Preparation step of the Online Restore Wizard: The wizard may not respond to any user action while it is processing a backup.

WORKAROUND: Wait until the backup processing is finished.

When you select the "Backup Agent Management" node in the Recovery Manager Console, you may observe the following issue: The Recovery Manager Console stops responding, showing the status "Discovering Backup Agent instances, please wait".

WORKAROUND: Wait until the Backup Agent discovery completes.

Unexpected behavior on the Reporting Options step in the Online Restore Wizard: When you select the "Include ChangeAuditor data in reports" check box, select a ChangeAuditor database, and click Next, you may encounter the error "Unable to connect to the ChangeAuditor database: <database>. Details: Login failed for user '<current user>'."

This error shows up if the current user account does not have sufficient permissions to access the ChangeAuditor database. The expected behavior in the described situation is that the Online Restore Wizard should prompt you for credentials to access the ChangeAuditor database.

WORKAROUND: Run the Online Restore Wizard under an account that has sufficient permissions to access the target ChangeAuditor database.

You may encounter the following unexpected behavior while using the "Backup Agent Management" view in the Recovery Manager Console to view a list of Backup Agents: The list of Backup Agents may be incomplete. The cause of this behavior is that when you apply a filter on one or more columns in the "Backup Agent Management" view, there is no indication that the filter is applied.

WORKAROUND: Check to see if a filter is applied on any columns in the "Backup Agent Management" view. Remove the filter if necessary.

A compare operation performed in the Online Restore Wizard may take a significant time to complete (30+ minutes). Also, the compare operation may consume a significant amount of RAM. This issue only occurs if the number of objects being compared is 100,000+.

WORKAROUND: Wait for the compare operation to complete.

The Online Restore Wizard cannot find an object if the object name contains 1-9 digits when searching by the full object name, but can find it by the common mask, for example: 'u01' object can be found by 'u' and cannot by 'u01'.

This issue may arise if the operating system version of a domain controller is greater or different from the RMAD Console machine operating system.

WORKAROUND: Copy the esent.dll file from the domain controller where the backup was created to the product installation folder on the Recovery Manager Console machine.

You may receive the "ASR Error: Fail to exclude disk#1" error when performing the Backup or Restore operation on Windows Server 2008/2008R2-based domain controller.

WORKAROUND: This error can be safely ignored because it does not affect the backup or restore process.

After the upgrade on the network isolated machine, the Recovery Manager Console is loaded too slowly.

WORKAROUND: Uncheck the Check for publisher's certificate revocation option on the Advanced tab in the Internet Option dialog in Microsoft Internet Explorer.

Pre-installed Backup Agent can be upgraded during the backup creation.

WORKAROUND: Do not upgrade Backup Agent if the backup operation is not finished.

Cannot disable replication schedule when there is no replication console (the replication console was deleted).

Unexpected behavior when you use the Recovery Manager Portal to delegate restore or undelete permissions to a user or group that is not assigned any role in the Recovery Manager Portal: The delegation operation completes successfully. The expected behavior in this situation is that the Recovery Manager Portal should not allow you to delegate permissions to a user or group that has not been assigned any role in the portal.

WORKAROUND: Before delegating restore or undelete permissions, ensure that the target user or group is assigned the appropriate role in the Recovery Manager Portal. For more information about assigning roles to portal users, see the "Using Recovery Manager Portal" chapter in the User Guide.

The Recovery Manager Portal fails to show the result of a restore or undelete operation if while the restore or undelete is still running you switch to some other tab, and then return to the Recovery tab.

WORKAROUND:

To ensure that all objects have been successfully restored or undeleted:

1. On the Recovery tab, click the button with the name of the operation you have just performed.
2. See the "Objects to restore" or "Objects to undelete" list. This list contains the objects whose restore has failed.

When selecting a backup the Recovery Manager Portal, you may encounter the error "No backup found for the last backup session." This issue occurs if the backup is located on the domain controller and in the Recovery Manager Console its storage location is specified using a UNC path.

WORKAROUND: Select a backup stored locally on the Recovery Manager for Active Directory computer.