This article provides a list of issues that were resolved in Recovery Manager for AD 7.5.2.
Resolved Issues and Enhancements
This section provides a list of issues that were resolved in this release of Quest Recovery Manager for Active Directory. For each issue resolved, the list includes the Change Request ID (CR), which uniquely identifies the issue, and a brief description of the problem. The list is divided by component so that the items related to each individual component of the product are grouped together.
Online Restore Wizard
CR0104233
Fixed: When restoring an organizational unit that was moved to a different location after the backup was created, you may encounter the following problem with the report on operation results: The reported number of the restored objects is incorrect.
CR0188611
Fixed: When using a comparison report created by the wizard, you may encounter the following problem: The Child Objects table on the Object Details page for containers cannot be sorted by the Type column.
CR0191608
Fixed: In the Online Restore Wizard, clicking Add on the Proceed to Objects to Be Processed page and then clicking Find may cause the Recovery Manager console to unexpectedly close.
CR0191617
Fixed: In the Online Restore Wizard for ADAM, clicking Add on the ADAM Instance Selection page and then selecting Register Offline ADAM Database causes the Recovery Manager console to unexpectedly close.
CR0192413
Fixed: In the Online Restore Wizard for ADAM, selecting Add | Find on the Objects to Be Processed page and then clicking Find Now causes the following error: "The key was not found."
Group Policy Restore Wizard
CR0173434
Fixed: When restoring Group Policy Objects, you may encounter the following problem: The order of GPO links is not restored.
CR0186132
Fixed: On the GPO Restore Options page, the wizard may erroneously display Policy settings in the selected GPO(s) have not changed since the backup was made instead of Security settings in the selected GPO(s) have not changed since the backup was made.
CR0192494
Fixed: When you use the wizard to restore Group Policy Objects on a Windows Server 2003 SP2 based domain controller, you may encounter the following problem: Clicking Next on the Target Domain Controller page causes the Recovery Manager console to unexpectedly close.
Repair Wizard
CR0193104
Fixed: After restoring the System State and Certificate Services Database components, you may encounter the following problem: Certificate Services fails to start, returning the error "The system cannot find the file specified. 0x2 (Win32: 2)."
Backing up Active Directory
CR0189422
Fixed: When backing up a domain controller that has the administrative share disabled, Recovery Manager returns the following error: "Failed to back up DIT Database. The system cannot find the file specified." As a result, backup creation fails.
CR0191600
Fixed: In the Backup wizard, selecting an ADAM host on the What to Back Up page and then clicking Next causes the Recovery Manager console to unexpectedly close.
CR0192219
Fixed: When backing up some files located in the SYSVOL folder, the Recovery Manager console may unexpectedly close.
CR0194907
Fixed: When creating a backup of the System State, you may encounter the following error: "Failed to install the agent: Cannot determine the type of the target computer processor. The network path was not found."
CR0195389
Fixed: When creating backups with the use of the pre-installed backup agent, you may encounter the following problem: Concurrent execution of backup jobs for different Computer Collections that include the same domain controller causes the backup agent to unexpectedly stop on all the domain controllers involved in the backup creation process.
CR0193262
Fixed: In some cases, Recovery Manager does not back up Cryptographic Keys.
CR0195526
Fixed: When backing up a target domain controller, you may encounter the following problem: if the network connection between the Recovery Manager console and domain controller is lost, the backup agent (ERDAgent.exe) unexpectedly closes generating a crash dump file.
CR0198604
Fixed: When you back up a domain controller that is running Windows Server 2003 SP1, the following event error message may be logged in the Directory Service event log for each writable domain or application partition that the domain controller hosts:
Event Type: Warning
Event Source: NTDS Replication
Event Category: Backup Event ID: 2089
Description: This directory partition has not been backed up since at least the following number of days.
This issue shows up because Recovery Manager does not update the DSA Signature attribute every time that a system state backup is made.
Using Recovery Manager Console
CR0186501
Fixed: When starting the Recovery Manager console, you may encounter the following error: "Failed to connect to the configuration database. Could not find file 'C:\Documents and Settings\All Users\Application Data\Quest Software\RMAD\ERDiskAD.mdb'." This error occurs if any of the two configuration-related files has been deleted: ERDiskAD.mdb; Backups.mdb.
CR0186696
Fixed: When starting the Recovery Manager console, you may encounter the following error: "Failed to initialize the application. Failed to open a log file." This error occurs if you have started a WMI script for comparing two backups prior to starting the Recovery Manager console.
CR0187455
Fixed: When upgrading Recovery Manager from an earlier version installed to a non-default folder, the Installation Wizard erroneously prompts you with the default path to the application files and backups. The expected behavior is that the wizard prompts you with the path to the folder where the earlier version is installed.
CR0189440
Fixed: When upgrading Recovery Manager from an earlier version, you may encounter the following message: "DllRegisterServer in ole32.dll succeeded." The expected behavior is that this message is not displayed.
CR0191603, CR0191600, CR0191809
Fixed: Clicking certain tabs in the Collection Properties or Collection Defaults dialog box may cause the Recovery Manager console to unexpectedly close.
CR0195584, CR0194904
Fixed: When using a scheduled backup job, you may encounter the following problem: The ERDisk.exe process unexpectedly closes without creating any crash dump file.
