This article provides a list of issues that were resolved in Recovery Manager for AD 7.5.0.
For each issue that was resolved in Recovery Manager 7.5.0, the following list includes the Change Request ID (CR) and a brief description of the problem.
Enhancement: In the Online Restore wizard or Group Policy Restore wizard, you can now specify a folder where you want the wizard to place the Active Directory database files being extracted from the backup. The earlier versions used a global setting for that folder, which could not be modified from within the wizard user interface.
Fixed: No information, such as a warning or error message, is provided to isolate a situation where a backup creation task fails due to insufficient rights of the user account the task is scheduled to run as.
Fixed: When restoring links to Group Policy objects on a container (site, domain or OU), the Group Policy Restore wizard does not restore the link order. The expected behavior is that the precedence order for the Group Policy objects linked to the container is reset to the state as of the time of the backup.
Fixed: Inconsistent information in the Properties dialog box for a backup creation session: The General tab erroneously reports that the session is running whereas the Progress tab reports that the session is successfully completed.
Fixed: The Repair wizard displays incorrect information about the size of the Active Directory database file (DIT Database) on the "Operation Start" page if the actual size of that file exceeds 4 GB.
Fixed: The Repair wizard may stop responding when you use an incorrect syntax to specify the user name of the Directory Service Restore Mode (DSRM) Administrator. The expected behavior is that the wizard prompts you to correct your input.
For example, when the wizard prompts you to specify the user name and password of the DSRM Administrator after restarting the target domain controller in Directory Service Restore Mode, you might enter an incorrect user name, such as \\Administrator (double slash at the beginning of the user name). Such an incorrect syntax of the user name causes the wizard to stop responding, with the operation progress status reading thus: "Parameter specified is incorrect"
Fixed: When creating an Active Directory backup, the Recovery Manager backup agent stops responding if it encounters a file in the SYSVOL folder with the file name more than 256 characters long. The backup is not created in this case.
Fixed: When restoring a deleted user object on a Windows Server 2003 R2 based domain controller using the agent method, the Online Restore wizard may display the following error message: "The naming context cannot be found." Despite the error message, the restore operation is completed successfully.
Fixed: When creating a backup of a domain controller with a very large size of the Registry, Recovery Manager may fail to include Registry data in the backup. As a result, the backup is created but it does not contain the Registry data.
Note that this fix only applies to Windows Server 2003 based domain controllers. You may still encounter this problem when creating a backup of a Windows 2000 based domain controller.
Fixed: When you use the Schedule tab in the Properties dialog box for a Computer Collection to set up a backup creation schedule and to specify the user account under which you want Task Scheduler to perform backup creation tasks, and then apply your changes, you may encounter the following error: "The server threw an exception."
Fixed: When you use the Online Restore wizard to compare two Active Directory backups, and click the "View Report" button on the "Operation Options" page, the Recovery Manager console may unexpectedly close.