A supplement dated May 29, 2009 to the List of Known Issues for Recovery Manager for Active Direc (4306057)

This article is a supplement to the List of Known Issues provided in the Recovery Manager for Active Directory 7.9.0 Release Notes. For each issue, the article includes an ID (TF number), a brief description of the problem, and a workaround.

TF00046306
You may observe the following problem after you select a session in the console tree to view its details in the right pane: The Domain column in the right pane is empty, although it should provide information about the domains that include the computers on which you ran the backup operation.
WORKAROUND
To view information about the domains, refresh the session details:
- Right-click the session in the console tree, and then click Refresh on the shortcut menu.

TF00055433
When attempting to view a Recovery Manager report by using the Start-RMReportViewer cmdlet, you may encounter the following problem: The report fails to open and an uninformative error message displays. This problem occurs if all of the following conditions are true:
- Recovery Manager is configured to use SQL Server Reporting Services (SSRS) to display reports.
- The SQL Server that hosts SSRS (this is the SQL Server you specified when installing Recovery Manager) is unavailable.
WORKAROUND
Make sure the SQL Server that hosts SSRS is up and running.

TF00057137
Your attempt to back up a domain controller may fail with the following error message being displayed: "Unable to execute request (109). Unable to connect to LDAP server. Target server: <Name>. Port: <Number>. Unable to connect to LDAP server. Server Down." This problem occurs if all of the following conditions are true:
- The domain controller you attempt to back up has AD LDS (ADAM) installed on it.
- AD LDS (ADAM) installed on the domain controller is disabled or damaged.
WORKAROUND
WORKAROUND 1
Remove AD LDS (ADAM), and then retry the backup operation.
WORKAROUND 2
1. If necessary, repair AD LDS (ADAM).
2. Activate AD LDS (ADAM), and then retry the backup operation.

TF00057273
When using the Online Restore Wizard, in a situation where you choose the agent-based restore method, and then specify invalid credentials to access the target domain controller, you may encounter the following error message that incorrectly describes the problem: "Unable to install Online Restore Agent. Error description: Failed to create a remote object. Access is denied."
In fact, the error message should read that you have specified invalid credentials to access the target domain controller.
WORKAROUND
Disregard the error message in question. Rather, specify valid credentials to access the domain controller:
1. Click the Back button until you are on the "Domain Access Options" page.
2. Click the Change button, and then specify valid credentials to access the domain controller. When finished, click OK.
3. Step through the wizard to complete the restore operation.

TF00058108
When using the Recovery Manager Management Shell, you may encounter any of the following problems:
- Some cmdlets or cmdlet parameters may not work as expected or fail to work at all.
- Cmdlet Help mentions the following nonexistent cmdlet parameter: "-DayOfWeek". The cmdlet parameter that exists is named "-DaysOfWeek".
- Cmdlet Help erroneously mentions the following value for the "-Week" cmdlet parameter: None. In fact, this value is not supported.
- Cmdlet Help fails to provide the values that the "-BackupComponents" parameter can take.
- Some cmdlet usage examples provided in Cmdlet Help for the Add-RMBackup, Compare-RMActiveDirectoryObject, and Get-RMBackupContent cmdlets may be incorrect.
WORKAROUND
Use the Recovery Manager console to perform the tasks you cannot complete in the Management Shell due to these problems.

TF00058213
When using the Recovery Manager Management Shell, you may encounter any of the following problems:
- Some cmdlets or cmdlet parameters may not work as expected or fail to work at all.
- Cmdlet Help mentions the following nonexistent cmdlet parameter: "-DayOfWeek". The cmdlet parameter that exists is named "-DaysOfWeek".
- Cmdlet Help erroneously mentions the following value for the "-Week" cmdlet parameter: None. In fact, this value is not supported.
- Cmdlet Help fails to provide the values that the "-BackupComponents" parameter can take.
- Some cmdlet usage examples provided in Cmdlet Help for the Add-RMBackup, Compare-RMActiveDirectoryObject, and Get-RMBackupContent cmdlets may be incorrect.
WORKAROUND
Use the Recovery Manager console to perform the tasks you cannot complete in the Management Shell due to these problems.

TF00058414
When using the Recovery Manager Management Shell, you may encounter any of the following problems:
- Some cmdlets or cmdlet parameters may not work as expected or fail to work at all.
- Cmdlet Help mentions the following nonexistent cmdlet parameter: "-DayOfWeek". The cmdlet parameter that exists is named "-DaysOfWeek".
- Cmdlet Help erroneously mentions the following value for the "-Week" cmdlet parameter: None. In fact, this value is not supported.
- Cmdlet Help fails to provide the values that the "-BackupComponents" parameter can take.
- Some cmdlet usage examples provided in Cmdlet Help for the Add-RMBackup, Compare-RMActiveDirectoryObject, and Get-RMBackupContent cmdlets may be incorrect.
WORKAROUND
Use the Recovery Manager console to perform the tasks you cannot complete in the Management Shell due to these problems.

TF00058450
When using the Recovery Manager Management Shell, you may encounter any of the following problems:
- Some cmdlets or cmdlet parameters may not work as expected or fail to work at all.
- Cmdlet Help mentions the following nonexistent cmdlet parameter: "-DayOfWeek". The cmdlet parameter that exists is named "-DaysOfWeek".
- Cmdlet Help erroneously mentions the following value for the "-Week" cmdlet parameter: None. In fact, this value is not supported.
- Cmdlet Help fails to provide the values that the "-BackupComponents" parameter can take.
- Some cmdlet usage examples provided in Cmdlet Help for the Add-RMBackup, Compare-RMActiveDirectoryObject, and Get-RMBackupContent cmdlets may be incorrect.
WORKAROUND
Use the Recovery Manager console to perform the tasks you cannot complete in the Management Shell due to these problems.

TF00058491
When using the Recovery Manager Management Shell, you may encounter any of the following problems:
- Some cmdlets or cmdlet parameters may not work as expected or fail to work at all.
- Cmdlet Help mentions the following nonexistent cmdlet parameter: "-DayOfWeek". The cmdlet parameter that exists is named "-DaysOfWeek".
- Cmdlet Help erroneously mentions the following value for the "-Week" cmdlet parameter: None. In fact, this value is not supported.
- Cmdlet Help fails to provide the values that the "-BackupComponents" parameter can take.
- Some cmdlet usage examples provided in Cmdlet Help for the Add-RMBackup, Compare-RMActiveDirectoryObject, and Get-RMBackupContent cmdlets may be incorrect.
WORKAROUND
Use the Recovery Manager console to perform the tasks you cannot complete in the Management Shell due to these problems.

TF00058532
When using the Recovery Manager Management Shell, you may encounter any of the following problems:
- Some cmdlets or cmdlet parameters may not work as expected or fail to work at all.
- Cmdlet Help mentions the following nonexistent cmdlet parameter: "-DayOfWeek". The cmdlet parameter that exists is named "-DaysOfWeek".
- Cmdlet Help erroneously mentions the following value for the "-Week" cmdlet parameter: None. In fact, this value is not supported.
- Cmdlet Help fails to provide the values that the "-BackupComponents" parameter can take.
- Some cmdlet usage examples provided in Cmdlet Help for the Add-RMBackup, Compare-RMActiveDirectoryObject, and Get-RMBackupContent cmdlets may be incorrect.
WORKAROUND
Use the Recovery Manager console to perform the tasks you cannot complete in the Management Shell due to these problems.

TF00058587
When using the Recovery Manager Management Shell, you may encounter any of the following problems:
- Some cmdlets or cmdlet parameters may not work as expected or fail to work at all.
- Cmdlet Help mentions the following nonexistent cmdlet parameter: "-DayOfWeek". The cmdlet parameter that exists is named "-DaysOfWeek".
- Cmdlet Help erroneously mentions the following value for the "-Week" cmdlet parameter: None. In fact, this value is not supported.
- Cmdlet Help fails to provide the values that the "-BackupComponents" parameter can take.
- Some cmdlet usage examples provided in Cmdlet Help for the Add-RMBackup, Compare-RMActiveDirectoryObject, and Get-RMBackupContent cmdlets may be incorrect.
WORKAROUND
Use the Recovery Manager console to perform the tasks you cannot complete in the Management Shell due to these problems.

TF00058668
When using the Recovery Manager Management Shell, you may encounter any of the following problems:
- Some cmdlets or cmdlet parameters may not work as expected or fail to work at all.
- Cmdlet Help mentions the following nonexistent cmdlet parameter: "-DayOfWeek". The cmdlet parameter that exists is named "-DaysOfWeek".
- Cmdlet Help erroneously mentions the following value for the "-Week" cmdlet parameter: None. In fact, this value is not supported.
- Cmdlet Help fails to provide the values that the "-BackupComponents" parameter can take.
- Some cmdlet usage examples provided in Cmdlet Help for the Add-RMBackup, Compare-RMActiveDirectoryObject, and Get-RMBackupContent cmdlets may be incorrect.
WORKAROUND
Use the Recovery Manager console to perform the tasks you cannot complete in the Management Shell due to these problems.

TF00058751
When using the Recovery Manager Management Shell, you may encounter any of the following problems:
- Some cmdlets or cmdlet parameters may not work as expected or fail to work at all.
- Cmdlet Help mentions the following nonexistent cmdlet parameter: "-DayOfWeek". The cmdlet parameter that exists is named "-DaysOfWeek".
- Cmdlet Help erroneously mentions the following value for the "-Week" cmdlet parameter: None. In fact, this value is not supported.
- Cmdlet Help fails to provide the values that the "-BackupComponents" parameter can take.
- Some cmdlet usage examples provided in Cmdlet Help for the Add-RMBackup, Compare-RMActiveDirectoryObject, and Get-RMBackupContent cmdlets may be incorrect.
WORKAROUND
Use the Recovery Manager console to perform the tasks you cannot complete in the Management Shell due to these problems.

TF00058857
When using the Recovery Manager Management Shell, you may encounter any of the following problems:
- Some cmdlets or cmdlet parameters may not work as expected or fail to work at all.
- Cmdlet Help mentions the following nonexistent cmdlet parameter: "-DayOfWeek". The cmdlet parameter that exists is named "-DaysOfWeek".
- Cmdlet Help erroneously mentions the following value for the "-Week" cmdlet parameter: None. In fact, this value is not supported.
- Cmdlet Help fails to provide the values that the "-BackupComponents" parameter can take.
- Some cmdlet usage examples provided in Cmdlet Help for the Add-RMBackup, Compare-RMActiveDirectoryObject, and Get-RMBackupContent cmdlets may be incorrect.
WORKAROUND
Use the Recovery Manager console to perform the tasks you cannot complete in the Management Shell due to these problems.

TF00058863
When using the Recovery Manager Management Shell, you may encounter any of the following problems:
- Some cmdlets or cmdlet parameters may not work as expected or fail to work at all.
- Cmdlet Help mentions the following nonexistent cmdlet parameter: "-DayOfWeek". The cmdlet parameter that exists is named "-DaysOfWeek".
- Cmdlet Help erroneously mentions the following value for the "-Week" cmdlet parameter: None. In fact, this value is not supported.
- Cmdlet Help fails to provide the values that the "-BackupComponents" parameter can take.
- Some cmdlet usage examples provided in Cmdlet Help for the Add-RMBackup, Compare-RMActiveDirectoryObject, and Get-RMBackupContent cmdlets may be incorrect.
WORKAROUND
Use the Recovery Manager console to perform the tasks you cannot complete in the Management Shell due to these problems.

TF00058977
When using the Recovery Manager Management Shell, you may encounter any of the following problems:
- Some cmdlets or cmdlet parameters may not work as expected or fail to work at all.
- Cmdlet Help mentions the following nonexistent cmdlet parameter: "-DayOfWeek". The cmdlet parameter that exists is named "-DaysOfWeek".
- Cmdlet Help erroneously mentions the following value for the "-Week" cmdlet parameter: None. In fact, this value is not supported.
- Cmdlet Help fails to provide the values that the "-BackupComponents" parameter can take.
- Some cmdlet usage examples provided in Cmdlet Help for the Add-RMBackup, Compare-RMActiveDirectoryObject, and Get-RMBackupContent cmdlets may be incorrect.
WORKAROUND
Use the Recovery Manager console to perform the tasks you cannot complete in the Management Shell due to these problems.

TF00059061
When using the Recovery Manager Management Shell, you may encounter any of the following problems:
- Some cmdlets or cmdlet parameters may not work as expected or fail to work at all.
- Cmdlet Help mentions the following nonexistent cmdlet parameter: "-DayOfWeek". The cmdlet parameter that exists is named "-DaysOfWeek".
- Cmdlet Help erroneously mentions the following value for the "-Week" cmdlet parameter: None. In fact, this value is not supported.
- Cmdlet Help fails to provide the values that the "-BackupComponents" parameter can take.
- Some cmdlet usage examples provided in Cmdlet Help for the Add-RMBackup, Compare-RMActiveDirectoryObject, and Get-RMBackupContent cmdlets may be incorrect.
WORKAROUND
Use the Recovery Manager console to perform the tasks you cannot complete in the Management Shell due to these problems.

TF00059427
When using the Recovery Manager Management Shell, you may encounter any of the following problems:
- Some cmdlets or cmdlet parameters may not work as expected or fail to work at all.
- Cmdlet Help mentions the following nonexistent cmdlet parameter: "-DayOfWeek". The cmdlet parameter that exists is named "-DaysOfWeek".
- Cmdlet Help erroneously mentions the following value for the "-Week" cmdlet parameter: None. In fact, this value is not supported.
- Cmdlet Help fails to provide the values that the "-BackupComponents" parameter can take.
- Some cmdlet usage examples provided in Cmdlet Help for the Add-RMBackup, Compare-RMActiveDirectoryObject, and Get-RMBackupContent cmdlets may be incorrect.
WORKAROUND
Use the Recovery Manager console to perform the tasks you cannot complete in the Management Shell due to these problems.

TF00059435
When using the Recovery Manager Management Shell, you may encounter any of the following problems:
- Some cmdlets or cmdlet parameters may not work as expected or fail to work at all.
- Cmdlet Help mentions the following nonexistent cmdlet parameter: "-DayOfWeek". The cmdlet parameter that exists is named "-DaysOfWeek".
- Cmdlet Help erroneously mentions the following value for the "-Week" cmdlet parameter: None. In fact, this value is not supported.
- Cmdlet Help fails to provide the values that the "-BackupComponents" parameter can take.
- Some cmdlet usage examples provided in Cmdlet Help for the Add-RMBackup, Compare-RMActiveDirectoryObject, and Get-RMBackupContent cmdlets may be incorrect.
WORKAROUND
Use the Recovery Manager console to perform the tasks you cannot complete in the Management Shell due to these problems.

TF00059795
When using the Recovery Manager Management Shell, you may encounter any of the following problems:
- Some cmdlets or cmdlet parameters may not work as expected or fail to work at all.
- Cmdlet Help mentions the following nonexistent cmdlet parameter: "-DayOfWeek". The cmdlet parameter that exists is named "-DaysOfWeek".
- Cmdlet Help erroneously mentions the following value for the "-Week" cmdlet parameter: None. In fact, this value is not supported.
- Cmdlet Help fails to provide the values that the "-BackupComponents" parameter can take.
- Some cmdlet usage examples provided in Cmdlet Help for the Add-RMBackup, Compare-RMActiveDirectoryObject, and Get-RMBackupContent cmdlets may be incorrect.
WORKAROUND
Use the Recovery Manager console to perform the tasks you cannot complete in the Management Shell due to these problems.

TF00060099
When using the Recovery Manager Management Shell, you may encounter any of the following problems:
- Some cmdlets or cmdlet parameters may not work as expected or fail to work at all.
- Cmdlet Help mentions the following nonexistent cmdlet parameter: "-DayOfWeek". The cmdlet parameter that exists is named "-DaysOfWeek".
- Cmdlet Help erroneously mentions the following value for the "-Week" cmdlet parameter: None. In fact, this value is not supported.
- Cmdlet Help fails to provide the values that the "-BackupComponents" parameter can take.
- Some cmdlet usage examples provided in Cmdlet Help for the Add-RMBackup, Compare-RMActiveDirectoryObject, and Get-RMBackupContent cmdlets may be incorrect.
WORKAROUND
Use the Recovery Manager console to perform the tasks you cannot complete in the Management Shell due to these problems.

TF00060116
When using the Recovery Manager Management Shell, you may encounter any of the following problems:
- Some cmdlets or cmdlet parameters may not work as expected or fail to work at all.
- Cmdlet Help mentions the following nonexistent cmdlet parameter: "-DayOfWeek". The cmdlet parameter that exists is named "-DaysOfWeek".
- Cmdlet Help erroneously mentions the following value for the "-Week" cmdlet parameter: None. In fact, this value is not supported.
- Cmdlet Help fails to provide the values that the "-BackupComponents" parameter can take.
- Some cmdlet usage examples provided in Cmdlet Help for the Add-RMBackup, Compare-RMActiveDirectoryObject, and Get-RMBackupContent cmdlets may be incorrect.
WORKAROUND
Use the Recovery Manager console to perform the tasks you cannot complete in the Management Shell due to these problems.

TF00060171
When using the Recovery Manager Management Shell, you may encounter any of the following problems:
- Some cmdlets or cmdlet parameters may not work as expected or fail to work at all.
- Cmdlet Help mentions the following nonexistent cmdlet parameter: "-DayOfWeek". The cmdlet parameter that exists is named "-DaysOfWeek".
- Cmdlet Help erroneously mentions the following value for the "-Week" cmdlet parameter: None. In fact, this value is not supported.
- Cmdlet Help fails to provide the values that the "-BackupComponents" parameter can take.
- Some cmdlet usage examples provided in Cmdlet Help for the Add-RMBackup, Compare-RMActiveDirectoryObject, and Get-RMBackupContent cmdlets may be incorrect.
WORKAROUND
Use the Recovery Manager console to perform the tasks you cannot complete in the Management Shell due to these problems.

TF00060215
When using the Recovery Manager Management Shell, you may encounter any of the following problems:
- Some cmdlets or cmdlet parameters may not work as expected or fail to work at all.
- Cmdlet Help mentions the following nonexistent cmdlet parameter: "-DayOfWeek". The cmdlet parameter that exists is named "-DaysOfWeek".
- Cmdlet Help erroneously mentions the following value for the "-Week" cmdlet parameter: None. In fact, this value is not supported.
- Cmdlet Help fails to provide the values that the "-BackupComponents" parameter can take.
- Some cmdlet usage examples provided in Cmdlet Help for the Add-RMBackup, Compare-RMActiveDirectoryObject, and Get-RMBackupContent cmdlets may be incorrect.
WORKAROUND
Use the Recovery Manager console to perform the tasks you cannot complete in the Management Shell due to these problems.

TF00060279
When using the Recovery Manager Management Shell, you may encounter any of the following problems:
- Some cmdlets or cmdlet parameters may not work as expected or fail to work at all.
- Cmdlet Help mentions the following nonexistent cmdlet parameter: "-DayOfWeek". The cmdlet parameter that exists is named "-DaysOfWeek".
- Cmdlet Help erroneously mentions the following value for the "-Week" cmdlet parameter: None. In fact, this value is not supported.
- Cmdlet Help fails to provide the values that the "-BackupComponents" parameter can take.
- Some cmdlet usage examples provided in Cmdlet Help for the Add-RMBackup, Compare-RMActiveDirectoryObject, and Get-RMBackupContent cmdlets may be incorrect.
WORKAROUND
Use the Recovery Manager console to perform the tasks you cannot complete in the Management Shell due to these problems.

TF00061637
You may encounter the following problem when viewing the progress of a restore operation on the Restore Progress page in the Repair Wizard: The progress bar fails to show any progress, so you have no way of knowing when you can proceed with the wizard.
This problem shows up when you are restoring data from an encrypted backup.
WORKAROUND
To proceed with the wizard, wait until the Next button becomes available. Click the button, and proceed with the steps in the wizard.

TF00061714
If you start the Recovery Manager Management Shell under an account that has no local administrator rights on the Recovery Manager computer, you may not be able to perform any operations in the Management Shell: Your attempt to perform an operation using a Recovery Manager cmdlet may end up with an error message.
WORKAROUND
- Start the Recovery Manager Management Shell under an account that has local administrator rights on the Recovery Manager computer.
-OR-
- Use the Recovery Manager console to perform your task.

TF00061824
You may encounter the following unexpected behavior while using the "Console Storage" tab in the Properties dialog box for a Computer Collection or the Defaults dialog box (default properties for Computer Collections): When you click the Browse button, and then specify a nonexistent location in the Folder box, no warning message appears to inform you that the location does not exist.
WORKAROUND
Make sure the location you specify in the Folder box exists.

TF00062518
The Group Policy Object Selection page in the Group Policy Restore Wizard may provide incorrect information about Group Policy objects: The "State in AD" column may display "Different" for the Group Policy objects that actually are identical.
WORKAROUND
To display correct information about Group Policy objects:
1. On the Group Policy Object Selection page, click "View Report" and wait until the report opens.
2. Close the report, and then click the "Compare All" button on the "Group Policy Object Selection" page.
Upon its refreshing, the page will display correct information about Group Policy objects.

TF00063291
The Start-RMBackup and Get-RMSession cmdlets fail to provide any means for you to get the details of an unsuccessful backup operation or session.
WORKAROUND
To view detailed information about a failed backup operation or session, use the Recovery Manager console.

TF00063350
After you select the "Deleted Objects" node in the Active Directory Users and Computers (ADUC) tool on the Recovery Manager computer, the column heading names in the right pane may appear truncated.
WORKAROUND
Manually adjust the width of the columns in the right pane of ADUC.

TF00063454
The deleted objects filter may unexpectedly become unavailable in the Active Directory Users and Computers (ADUC) tool: The check boxes through which you can access the filter may be missing from the column headings in the right pane of ADUC. This problem occurs if you close ADUC while it is displaying the "Getting deleted objects" status message, and then start the tool again.
WORKAROUND
Restart the Recovery Manager computer, and then start ADUC.

TF00065697
You may encounter the following unexpected behavior in the Online Restore Wizard: The wizard fails to display any warning message if you select a read-only domain controller (RODC) as a target for online restore operation. This is unexpected behavior, because Recovery Manager is not capable of restoring any objects on RODCs.
WORKAROUND
Do not select a RODC as a target for online restore operation.

TF00065874
Selecting a significant (500+) number of deleted objects in the Active Directory Users and Computers (ADUC) tool on the Recovery Manager computer may cause the system to become non-responsive for a certain period of time.
WORKAROUND
Select less than 100 deleted objects at a time.

TF00069480
The "Preparing for Working with AD and AD LDS (ADAM) Backups" section in the User Guide provides incorrect information about the Esent.dll file location on a Windows Server 2008-based computer.
WORKAROUND
Disregard the instructions provided in the table included in the "Preparing for Working with AD and AD LDS (ADAM) Backups" section for the scenario where the Recovery Manager computer is running Windows XP or Windows Server 2003, and the backed up computer is running Windows Server 2008.
Rather, copy the Esent.dll file from the backed up computer to the Recovery Manager installation folder (by default, this is %ProgramFiles%\Quest Software\Recovery Manager for Active Directory), depending on the Windows edition installed on the Recovery Manager computer and the backed up computer.
- If both the Recovery Manager computer and backed up computer are running a 32-bit or 64-bit edition of Windows, copy the Esent.dll file from %Windir%\System32.
- If the Recovery Manager computer is running a 64-bit edition of Windows, and the backed up computer is running a 32-bit edition of Windows, copy the Esent.dll file from %Windir%\System32.
- If the Recovery Manager computer is running a 32-bit edition of Windows, and the backed up computer is running a 64-bit edition of Windows, copy the Esent.dll file from %Windir%\Syswow64.

TF00069539
A Recovery Manager scheduled task may fail to start if Recovery Manager is installed on a computer running the Japanese-language version of Windows. This is because the command line in the task properties includes an unsupported double-byte character (a colon).
WORKAROUND
To ensure the task runs as expected:
Start the Task Scheduler tool, open the Recovery Manager task properties, and edit the command the task runs, so that the command only includes ASCII characters. You will need to substitute a simple ASCII colon for the double-byte colon that follows the -ID argument in the command.

TF00069721
The Recovery Manager Setup program may fail to install .NET Framework 3.5 SP1, returning an uninformative error message.
WORKAROUND
Manually install .NET Framework 3.5 SP1 before running Setup. You can do so by performing these steps:
1. Run the Autorun.exe file.
2. In the Autorun window, go to the Redistributables tab, and then click the ".NET Framework 3.5 SP1" hyperlink.

TF00069725
The Recovery Manager Setup program may fail to install Windows PowerShell 1.0, returning the following error message: "Component Windows PowerShell 1.0 has failed to install."
WORKAROUND
Manually install Windows PowerShell 1.0 before running Setup.

TF00070619
The Recovery Manager documentation fails to include any warning about the fact that upgrading to Recovery Manager version 7.9.x results in the change of the Recovery Manager reporting database structure and, as a result, loss of all comparison and restore reports created with an earlier version of Recovery Manager.
WORKAROUND
Before upgrading to Recovery Manager version 7.9.x, make sure you save the Recovery Manager reports you need.
For detailed instructions on how to save the reports, see Quest Knowledgebase article "How to prevent the reports generated with an earlier version of Recovery Manager from being erased during upgrade to version 7.9.x" (article ID: SOL48486) at http://support.quest.com.

TF00070917
Incorrect name of the product on page 8 in the Deployment Guide:
Forest Recovery System
WORKAROUND
Disregard this incorrect name.

TF00078885
Recovery Manager fails to integrate with recently released Quest ChangeAuditor versions 4.8 and 4.9.
WORKAROUND
Download and install a hotfix that is available at:
http://support.quest.com/SUPPORT/index?page=solution&id=SOL53425

TF00081418
When using Recovery Manager, you may observe these problems:
- After you click the "Test Settings" button on the E-mail tab in the Settings dialog box, you receive the following error message: "Failed to send the test message. The server threw an exception".
- Some or all backup creation sessions for Computer Collections finish with the Abandoned status.
WORKAROUND
Download and install a hotfix that resolves this issue. The hotfix is available at the following hyperlink:
http://support.quest.com/SUPPORT/index?page=solution&id=SOL53706

TF00088489
The Reporting feature may fail to work as expected. For example, your attempt to generate a report in the Recovery Manager console may permanently fail.
This problem results from the fact that the Setup program may fail to create the Recovery Manager reporting database during the installation of the product.
WORKAROUND
To work around this problem:
1. Uninstall Microsoft SQL Server Compact 3.5 SP1 from the Recovery Manager computer:
a. Click Start, click Run, type appwiz.cpl, and press ENTER.
b. In the list of currently installed programs, select the appropriate entry, and click Remove (under Windows XP or Windows Server 2003) or Uninstall (under Windows Vista or Windows Server 2008).
2. In the list of currently installed programs, select the item representing Recovery Manager, and,
- If you are using Windows XP or Windows Server 2003, click Change, and follow the steps in the Setup Wizard to repair the Recovery Manager installation.
-OR-
- If you are using Windows Vista or Windows Server 2008, click Repair, and wait for the repair operation to complete.

TF00090629
Unexpected behavior: You can run the backup creation operation for a Computer Collection even if no backup storage location is specified for that Collection. As a result, the backup creation session completes without any errors or warnings, but no backup files are created.
WORKAROUND
Make sure you specify a location for storing backups in the Properties dialog box for each created Computer Collection. You can specify such a location on the "Console Storage" and/or "DC Storage" tab.

TF00091883
The word "Windows" is misspelled as "Widows" in the check box name on the "Configure Windows Firewall" page in the Setup Wizard.
WORKAROUND
Try to remain serious. The check box name should actually read "Automatically configure Windows Firewall".