Recovery Manager for Active Directory Disaster Recovery Edition 10.0.1 - What is new and resolved (4223923)

New Features:

• Continuous recovery (Change Auditor integration) - Recovery Manager for Active Directory restores a deleted object and the last change (if any) that was made to the object properties after the backup creation using data from the Change Auditor database.
• Support for restore of Group Policy Objects in non-trusted domains  - Domain access credentials can be explicitly specified in Group Policy Restore Wizard.
• Support for Azure Files as a backup storage - Recovery Manager for Active Directory Forest Edition can work with backups stored in the Azure Files share.
• Separate accounts to access the backup storage and the Backup agent - Now a user can access backup storage share under specified account, which is not the same as an account used to access the backup agent.
• Install AD recovery method supports RODC - Now the Install Active Directory recovery method supports promoting read-only domain controllers (RODC).
• Independent DC verification workflow - Now verification of DC1 does not wait for verification of DC2.
• New verification step "Check if promoting paths are valid" for the 'Install Active Directory' and 'Install from Media' recovery methods - On this step Recovery Manager for Active Directory Forest Edition checks whether the specified 'DIT database path", "Log files path" and "SYSVOL path" are available.
• Configure as Global Catalog option for the Install from Media recovery method - Now the Install from Media recovery method has the "Configure as Global Catalog" option.
• Checking the System State backup password - Now the Verify Settings operation checks the System State backup password for the "second stage" scenario.
• NAT Settings for Bare Metal Recovery - The "NAT settings" option lets you access recovered domain controllers that are located outside the network where Recovery Manager for Active Directory Disaster Recovery Edition is installed.
• Custom port for Forest Recovery Agent in Windows Recovery Environment - Now you can connect to the FR agent in Windows Recovery Environment using a custom port.
• BMR project verification in a live environment - BMR project settings can be verified in a live environment, without additional blank hosts.
• UEFI boot mode on SCVMM - Active Directory Virtual Lab: Support for source machines with the UEFI boot mode on System Center Virtual Machine Manager (SCVMM).

Resolved Issues:

• Now the "Windows Server Backup" feature is installed automatically during the backup process if the feature is missing - RMADFE-1874
• Now Backup Agent retries to connect to the LDAP server if it is not functional during start of the backup creation process - RMADFE-1954
• RMAD console may hang during startup on Windows Server 2016 with some updates - RMADFE-2006
• Now log information about backup creation sessions are written to the text file specified on the Alerts tab of the collection properties - RMADFE-2025
• Support for Windows Server 2019 for Recovery Manager Console hosts - RMADFE-2039
• Recovery Manager Console could show misleading "agent is up to date" message when the version of Backup agent did not match the console version - RMADFE-2054
• Recovery Manager for Active Directory can open a DIT database as Read/Write from backups made on other versions of operating system - RMADFE-2091
• Now we show the warning during the backup session if the agent is not up to date - RMADFE-2096
• Now Recovery Manager Console starts with no MMC errors - RMADFE-2097
• Now the error is shown if an AD component is copied incompletely from the VSS snapshot - RMADFE-2127
• MSA/gMSA accounts now can be used for scheduled backups on localized Windows operating systems - RMADFE-2145
• Support for RMAD backup and restore operations for Windows Server 2019 domain controllers - RMADFE-2168
• Unable to uncheck two options on the Components tab of the collection properties: "When backing up Global Catalog servers, collect group membership information from all domains within the Active directory forest" and "Collect Forest recovery metadata" - RMADFE-2183
• Support for RMAD backup and restore operations for Windows Server 2019 Core domain controllers - RMADFE-2211
• Now the firewall service is not enabled on the Forest Recovery Agent start - RMADFE-872
• Now you can configure Recovery Media and Drivers locations in Forest Recovery Console using the following command: Set-RMADFEGlobalOptions -RecoveryMediaPath "mediaDir" -CustomDriversPath "driverDir" –Save - RMADFE-1906
• In rare cases, the Verify settings could fail with the wrong error message "A conflict detected in the recovery project settings" - RMADFE-1898
• "Insufficient configuration information" warning appeared prior to the BMR recovery. This happened because the version of operating system was not read from the backup - RMADFE-1878
• Now the forest recovery step "Reset computer account password" is performed in parallel for all domain controllers - RMADFE-1926
• The password was asked two times during creation of the FR Project from backup and registration of encrypted backup - RMADFE-1983
• Forest recovery could fail with the exception "ThereIsAnotherWorkingSessionException" if a user abort the forest recovery procedure, reopen Forest Recovery Console and then start the recovery session again - RMADFE-1990
• Bare Metal Recovery Console could show the "Waiting for connection from the Forest Recovery Console" message being already connected - RMADFE-1978
• Agent operations may fail on canceling timeout expiration - RMADFE-2187
• "Disk already detached" error may occur when creating and registering the BMR backup - RMADFE-2007
• BMR backup could not be completed on Windows Server 2008 R2 because of insufficient size of VHD container - RMADFE-2008
• Could not apply the changed System State backup password - RMADFE-2010
• Wrong DNS server might be selected during the forest recovery process (Install from Media recovery method) - RMADFE-2019
• Could not create a backup on the restored machine in case of corrupted backup catalog - RMADFE-2026
• Now the "Restore DNS delegation" operation removes obsolete IP addresses - RMADFE-2027
• Now the Forest Health Check tool successfully performs "Active Directory replication" and "Domain trusts" checks - RMADFE-2040
• Now Recovery Manager for Active Directory Forest Edition cleans up duplicated DNS server IP addresses during the forest recovery - RMADFE-2048
• If a user changes some settings after the failed restore operation and then restarts the restore operation, new settings will be applied successfully - RMADFE-2056
• Now the project verification successfully updates the project file settings - RMADFE-2066
• You may get an error when retrying to reboot Windows Recovery Environment to DSRM mode -RMADFE-2073
• Forest Recovery Agent tried to configure network adapter only once after reboot from WinRE to DSRM mode - RMADFE-2074
• We add an option that lets you specify the target IP address and port to connect to Recovery Environment - RMADFE-2080
• If you need to schedule FR project verification, click the drop-down toggle next to Verify Settings on the tool bar and select Schedule Verify Settings - RMADFE-2084
• Now the email notification that is generated during the "Scheduled Verify Settings" procedure contains more detailed information - RMADFE-2085
• Now the Manage FSMO Roles tool correctly determines current role owner - RMADFE-2087
• Recovery report could contain obsolete IP addresses after the the Disaster recovery is completed - RMADFE-2109
• Bare Metal Recovery Console could show wrong IP address when it was manually changed - RMADFE-2110
• Now the backup criteria is automatically applied to BMR backups - RMADFE-2122
• Now Bare Metal Recovery Console shows correct subnet mask/gateway addresses for disconnected network adapters - RMADFE-2151
• Bare Metal Recovery Console could fail to configure the second network adapter with the "The object already exist" error in the log - RMADFE-2152
• Bare Metal Recovery Console could hang on quickly switching of network adapters - RMADFE-2159
• The BMR backup path field in the Forest Recovery Console contained some backup path in case of selection of multiple domain controllers. Now this field is empty - RMADFE-2166
• Support for Windows Server 2019 Domain Controllers - RMADFE-2169
• Invalid DNS server could be selected - RMADFE-2175
• Now the Manage FSMO Roles tool allows a user to seize or move FSMO roles to a running domain controller - RMADFE-2179
• Cancel of agent operation may hang on canceling timeout expiration - RMADFE-2187
• The "Reset computer account password" operation could report successful result even if some DC passwords were not reset - RMADFE-2206
• Now the "Configure DNS server" operation is waiting for the DNS server to become available - RMADFE-2208
• ADVL project could fail with the "Timeout expired" error - RMADFE-2125
• Now ADVL can work with VMWare agents deployed with self-signed certificates - RMADFE-2227