Recovery Manager for AD Disaster Recovery Edition 10.2.2 latest build (Full Hotfix Release) (4368856)

Recovery Manager for AD Disaster Recovery Edition 10.2.2 latest build (Full Hotfix Release)

This solution contains the latest full build of RMADDRE 10.2.2 (currently 10.2.2.38943)

This Full Maintenance Release is HERE  and addresses the issues described in the attached Release Notes. Please review the problem descriptions included to ensure your issue criteria is met prior to installing this Full Maintenance Release.
This build addresses the issues noted in the attached Release Notes which were found since the release of 10.2.2.36571 and can be installed directly on top of that build or older builds including 10.0, 10.0.1, 10.1, 10.1.1, 10.2, 10.2.1 and 10.2.2 as per the included documentation.
Please download the RMADDRE 10.2.2.38943 Full Maintenance Release by Clicking Here  and installing according to the "...\Documentation\RecoveryManagerForAD_DisasterRecoveryEdition_ReleaseNotes_en-us.pdf"
The latest full build of RMADDRE 10.2.2 (10.2.0.38943) includes the following:

IMPORTANT NOTIFICATION: Recovery Manager for Active Directory has deprecated support for a group managed service account (gMSA) to be specified as the account to connect to the backup agent for manually triggered backups. Managed service accounts will continue to be supported for scheduled backup tasks. In accordance with Microsoft®, it is recommended to not use a group managed service account (gMSA) for interactively initiated network connections such as Recovery Manager for Active Directory manually triggered backups. To enforce this recommendation and to address the vulnerability CVE-2023-21524 (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-21524), Microsoft has limited the usages of managed service accounts with a Windows Update.
By removing support for a gMSA to connect to the backup agent, this ensures an attacker does not exploit the RMAD backup agent to perform actions or access resources over the network. To utilize the benefits and security provided by a group managed service account (gMSA), we highly recommend that a gMSA account is used for the scheduled backup task.

When upgrading to Recovery Manager for Active Directory 10.2.2 Hotfix 3, if a gMSA is currently configured in computer collection properties as an account to connect to the backup agent (see Agent tab), it will automatically be removed to ensure security of the backup agent and your installation of RMAD. You can then configure a standard domain account in the computer collection properties as the account to connect to the backup agent. If not configured, the scheduled backup task account or the logged on user account will be used instead.
For information about managed service accounts and their usage in Recovery Manager for Active Directory see the section [Using Managed Service Accounts] in the Recovery Manager for Active Directory User Guide.

You can also configure Recovery Manager for Active Directory (RMAD) to back up data in an Active Directory® domain under a least-privileged user account and create a group named RMAD Backup Operators that will automatically grant the necessary permissions to back up data. See [Using a least-privileged user account to backup data] in the User Guide.

10.2.2 Hotfix 3 Resolved Issues:

• RMAD fails to perform backups when using GMSA account after Microsoft Patch applied KB5022289\KB5022286 - 406231

10.2.2 Hotfix 2 Enhancements:

• Support for OAuth2 authentication method for email notifications. Required due to deprecation of basic authentication for Exchange Online - 384541
• Option for pre-installed online recovery agent - 358029
• Support for agent based restore with LSA protection for Windows 2022 - 318168

10.2.2 Enhancements:

• Improve message the error while creating remote DCOM object failed because "Access is denied" - 263396
• Cannot restore a user from a backup that requires credentials for accessing it - 267022
• Support GMSA account type to run PS custom script (Agent side only) - 317648
• Installation option for hybrid service in the main product setup - 346507
• New hybrid configuration Powershell API - 346513
• Installer check updated for .NET 4.8 - 349988
• Full support for GMSA accounts for RMAD DRE/FE/Standard - 352707
• Support for Windows 2022 with exceptions. See User Guide - 363862
• Allow UI to configure different criteria for BMR backups vs system state backups - 318213
• As a RMAD DRE user I have an option to add and remove an AWS S3 storage location under the storage node - 329448
• As a RMAD PowerShell user I can use a PowerShell cmdlet to add/remove/edit AWS S3 storage - 329452
• Ability to pause recovery in DSRM mode - 333756
• Secure Storage: support secure storage server maintenance without unhardening - 353018
• Forest level option to pause recovery in DSRM mode - 358283

10.2.1 Enhancements:

• Usability improvements to the Computer Collections Properties dialog including removal of Logging tab and introduction of new tab for Secondary Storage - 283362
• Creation of Management Shell Guide which lists all available PowerShell® cmdlets, with examples. Appendix removed from User Guide - 275100
• Automatically enable File and Printer Sharing on the clean OS machine when installing FR agent - RMADFE-2778, 242106
• RMAD Console and Forest Recovery Agent cannot read AD configuration with more than 1000 sites - 274279
• Support console local storage as a primary storage for copying to Secure Storage server - 280129
• Smart instance type selection for Azure virtual machine creation with Restore to Clean OS feature - 281406
• In the Secure Storage node provide ability to sort/filter/group backups in the RMAD console - 278538
• As a part of server hardening check server and do not allow a domain joined server. Secure Storage agent will not be installed - 258979
• Ability to configure volume for backups on Secure Storage server. Default to copy backups to non system drives - 276487
• Option to specify static IPs for Azure virtual machine creation - 315595
• Improvement for template selection in Restore to Clean OS - 297078
• Support verify for 'Restore to Clean OS' on live DCs, show warning when live DC is contacted - RMADFE-2933, 218376
• Show free disk space and warning when space is low for volumes on Secure Storage server - 227980

10.2 Enhancements:

• Rename system state backups to Active Directory® backups - RMADFE-3009, 218405
• Hide the "Components" tab in computer collection settings - RMADFE-3042, 218415
• SCOM 2019 support - 219783
• Pass through Synchronize across time zones from windows task scheduler to RMAD - RMADFE-952, 220703
• Create Logs Daily to be on by default - 223980
• Display operating system version for all backups - 228741
• Forest Recovery simulation mode available - RMADFE-920, 218277
• The 'View Recovery Report' action should be available as one of the post recovery dialog actions - RMADFE-3034, 218413
• Encrypt credentials in Forest Recovery project using AESCryptoServiceProvider instead of TripleDESCryptoServiceProvider - RMADFE-2199, 220948
• Allow RMAD backup to continue if forest recovery agent cannot be installed - 221433
• Set default global catalog handling option to "Keep GC Intact" - 223871
• Show 'object's tombstone is expired' detailed warning in the Online Restore Wizard - RMADFE-1613, 223987
• Default recovery method to the Repromotion phase should be "Install AD", not "ReinstallAD" - 234195
• Tool to update backup creation date in simulation projects - 234197
• Keep previous recovery methods when changing recovery mode like Forest Recovery --> Repromotion --> Forest Recovery - 234201
• Every DC in simulation project should have a backup created for this domain controller so all recovery methods are available - 234203
• The current image file is not recreated if the file is not older than X days and the version of the Forest Recovery agent and network settings are not changed - 218323
• Document how to pre-configure clean external DNS server which is used for BMR or Clean OS recovery - RMADFE-3110, 218435
• Show computer collection type (system state/BMR) in the RMAD console collections grid - RMADFE-3228, 218917
• In "Restore to Clean OS" we need to disable Windows Updates before promoting machine to DC - 229862
• Recreate ISO when third-party drivers added or removed - 230402
• Log the recovery event with source disk configuration information - 230457
• Validate source and target disks layout match - 230963

10.2.2 Hotfix 2 Resolved Issues:

• Include product name and version to the self-extracted installation package - 367930
• Remove Autorun from build, CD package - 380288
• Email notifications to O365 email is not supported when Basic Authentication disabled on tenant - 386176
• RMAD Console crashes when recovering SYSVOL from a backup using Repair Wizard - 388796
• SCOM: computer collection and RMAD instances are in not monitored health state - 393392
• Option to "Repair" an installation is greyed out - 383571
• Online restore wizard does not work on Windows 2016 with LSA protection and Secure Boot enabled - 226670
• Online restore wizard does not work on Windows 2022 with agent based restore and with LSA protection enabled - 367163
• Forest recovery step Configure DNS server slow - 355113
• Forest recovery failed at Apply group policy step - 384999
• Loopback address is duplicated in DNS client settings - 364187
• Apply Group Policy step should not restart DC if not required - 381177
• Skip removing deletion protection from domain controller objects when doing metadata cleanup - 395989
• Clean OS recovery can take too long on Configure DNS Server step - 386993

10.2.2 Hotfix 1 Resolved Issues:

• Restore-RMADDeletedObject cmdlet crashes when it's used without explicitly specified credentials -  382646
• Domains that are not synced with Azure AD should be present in the list of discovered domains but should not cause error (require credentials) while saving the configuration - 380628
• Cannot save ODR integration settings in RMAD due to an old forest/dc listed in discovered domains - 380625
• Offline Restore Wizard fails with Access Denied to install Offline Restore Agent - 375451
• Setup folder does not include .NET 4.8 after changing product requirement - 373180
• Full replication between two consoles is failing with 'The given key was not present in the dictionary' error - 322095
• Check Forest Health uses the local credentials to create a test user - 374940
• Manage Domain Controller Tools allow to manage agents for "Do not recover" domain controllers using "invisible" credentials - 372411
• Forest Recovery projects are not loaded automatically after upgrade if they were created by the prior version - 322930
• Azure VM cleanup before/after creation fails if source DC has one disk - 379041
• Share User Name cannot be empty on cloud upload - 371060
• Secure Storage: Upgrade or Clean install of Secure Storage Agent fails - 370364
• Secure Storage: UI text bug only - Security Status incorrect after unhardening/hardening SS server after agent upgrade - 369651
• Cloud Storage: Azure Container drop-down poor performance - 369471
• Secure Storage: Running Get-RMADStorageServerException throws PowerShell error - 369467

10.2.2 Resolved Issues:

• RMAD replication doesn't work with Group Managed Service Account (gMSA) configured for console connection - RMADFE-2594, 242195
• gMSA cannot be used when setting up replication - RMADFE-2519, 242560
• Use a gMSA account from one domain as the agent account for backing up DCs in a different domain does not work - 265197
• RMAD not finding backups requested by ODR in different timezones - 316404
• BackupAgent does not respect global logging setting "Create a new set of log files: Never" - 322747
• Update DisksInfoProvider to be more current and ignore unnecessary drive types - 323924
• ERDiskAD.mdb does not get imported, gets overwritten by blank rmad.db3 when installing the new version - 352421
• A v10.2.1 pre-installed backup agent fails when backup is requested by a v10.1.1 console - 353765
• Updating backup agent fails if custom port is configured - 354851
• Global settings dialog has a slightly broken layout on several tabs - 358457
• RMAD Console - Replication: Backup information is not being cleaned out of the console when it no longer exists on source - 359553
• RMAD Console: Diagnostic Logging drop-down reverts to Global Settings when enabled within Advanced settings of Computer Collection - 363140
• Installer log messages are truncated – 364258
• Installing Forest Recovery agent hangs if SMB shares are disabled - 285225
• Antivirus scanning failed with 'Path too long' error - 324610
• FRConsole broken due to undocumented new System Requirements for FR Console - 325287
• FR Console Crashes after recovery cancellation – 363341
• Online restore with agent failed with the error code "The operation completed successfully" - 231815
• Replication health check hangs if some replication neighbors cannot be contacted - RMADFE-2841, 242201
• The "Ensure that domain controller isolation is disabled" Clean OS operation might stuck - 273396
• Unisolate step hangs indefinitely during Clean OS recovery if FW turned on by GPO - 320773
• Azure VM creation fails on generating service principal with "cannot call method on a null-valued expression" - 333691
• Windows Server Backup (BMR) Verify doesn't work on non-English windows - 355867
• Unable to install Secure Storage Agent on non-English server - 361135
• Clean OS recovery. Ensure Sysvol replication engine is initialized completely before proceeding to backup recovery - 363117
• Mapping of same share takes a long time in sequential order if it has already been mapped under another user - 364473
• Azure VM creation: Unable to configure VPN connection if target network has multiple subnets - 364504
• Automatic boot of VMWare VM may fail on uploading ISO file to the datastore - 364508

10.2.1 Hotfix 2 Resolved Issues:

• RMAD Console Replication error (XML error) during replication when backup runs on master console - 351462
• Cleanup of metadata during restore of an unprotection object failed from accidental deletion - 354567
• RMAD Console: Diagnostic Logging drop-down reverts to Global Settings when enabled within Advanced settings of Computer Collection - 363140
• RMAD build 10.2.1.36279 will not install and triggers MS Defender notification – 366313
• Install AD/IFM operation may fail unable to bind replicationPartner parameter – 356459
• Restore to clean OS may fail with "More data is available" error - 323968
• Verification fails with 80+ AD DCs in parallel - 346048

10.2.1 Hotfix 1 Resolved Issues:

• Error with diagram explaining Change Auditor integration - 323348
• GMSA workflow in the documentation is reportedly missing steps - 325726
• Cannot retry a snapshot if certain errors occurred while creating a backup – 330733
• Forest Recovery Console takes a long time to apply backup selection criteria - 322570
• Online Restore Wizard cannot connect to Change Auditor database if the agent-based method is selected - 325775
• Verify Setting may fail at pre-recovery checking DSRM password - 328446
• Protect object from accidental deletion prevents Metadata Cleanup from removing DC computer object – 330979
• RMAD VSS backup might be corrupted, no errors is reported - RMADFE-2794, 242199
• BMR recovery may fail at ISO image creation with "Access to the share path is denied" error - 321726
• Regression on 220573: Should allow Console Storage unselection immediately - 324331
• Wrong disk free space calculation in Clean OS verify and recovery workflows - 324353
• Secure Storage Server - copying multiple backups at same time to new secure storage server folder can lead to error - 326044
• "EFI secure boot could be enabled only on EFI firmware" error when creating VMWare virtual machine - 329480
• Fix "Including additional volumes to a BMR backup" documentation - 348727

10.2.1 Resolved Issues:

• Allow to unselect Console storage immediately as alternative has been configured - 220573
• Large number of scheduled tasks can cause Console, Replication and PowerShell cmdlets to be extremely slow - RMADFE-1837, 242166
• Remove a BOM prefix from the script file - 257798
• Unpacking the backup and the retention policy may fail if the DC cannot be accessed via LDAP from the RMAD console machine - 279431
• RPC calls to Backup Agent are not retried on RPC_S_SERVER_TOO_BUSY error - 314812
• Misleading 'Unable to map the network share IPC$ on the computer' error message on attempt to map UNC share - 316902
• Installation fails with an invalid error message when using a local windows credential to connect to the remote SQL server - 317818
• Online Restore Wizard cannot undelete an object using a non-administrative account. Restoring an object in Online Restore Wizard using a non-administrative account may result in the following error for NT-Security-Descriptor attribute: "Cannot retrieve attribute value(s) from Active Directory. Possible reason: Insufficient access rights." To ignore this error, the NT-Security-Descriptor attribute can be excluded from the list of restored attributes – 293311
• Check Forest Health can get stuck on the second step - RMADFE-3041, 218559
• New recovery project, selecting a Backup display the adding time in the Backup Age column instead of backup age - 237971
• 'There is no PREFERRED_DNS value' error occurs, if no DNS server is found on installing Active Directory - RMADFE-2437, 242191
• Feature loss in Forest Edition: Cannot skip a backup for non-authoritative DCs in Sysvol recovery mode - 245551
• 'There is no PREFERRED_DNS value' error when a 'Select preferred DNS' agent operation did not return a result it causes product to halt and cannot be skipped or aborted - 253457
• Resume Forest Recovery show 'Password is incorrect' - 254788
• Installing Forest Recovery agent hangs if SMB shares are disabled – 285225
• Cache and reuse the extracted WinRE images - RMADFE-3206, 218577
• Health Check wizard should work after Restore to Clean OS - 226971
• Bare Metal Recovery backup does not work with SAN policy set to OfflineAll - RMADFE-1955, 242174
• Restore Clean OS failed if original DC has encrypted volumes - RMADFE-2857, 242202
• Recreate ISO when third-party drivers added or removed - RMADFE-2928, 242204
• Installing Active Directory may fail with access denied due to lack of permissions to write the objects into Computers OU. To workaround, user must set the JoinDomainBeforeInstallAD option to True in FRConsoleSettings.xml file. This will skip joining OU Computers during the promotion of the DC and join it directly to OU Domain Controllers - RMADFE-3101, 242598
• Incorrect filtering of backups on the secure storage server - 278874
• Password showing in clear text for event id 403, showing PowerShell script name, the user name, and password - 281399
• Project verification with Zero touch configured reboots the working servers to WinRE mode - 283230
• Unable to verify settings if Azure virtual machine exists or is shut down - 304177
• Forest Recovery with VMWare machine creation fails if source has BIOS firmware and more than one critical disk - 313724
• Console crashes if storage server refresh fails when secure storage backups node is selected - 315182
• Failed to establish DNS configuration after recovery with Azure virtual machine - 318396
• Failed to prepare infrastructure on Azure VM with 'QuestSoftware.RecoveryManager.AD.ForestRecovery.LocalizableException: Cannot find path because it does not exist' message - 318660
• Change the warning which explains that the recovery ISO should be dismounted - 318768
• Error message prompting the user failed because the host program or the command type does not support user interaction, after failing to create VM in Azure and Retry All operations for a specific DC - 319038
• Cannot validate argument on parameter 'VM'. The argument is null or empty - 319040
• Unable to access the backup on Azure file share during Clean OS Restore to Azure VMs - 304022
• For Azure VM creation, a cloned Infrastructure platform template is not automatically selected on the infrastructure tab after Service Principle generation - 259493
• Azure VM creation does not work with Az Powershell module 7.0.0. API changes in Service principal management cmdlets used by RMAD - 323193

10.2 Hotfix 1 Resolved Issues:

• Installation of Quest personal certificates to the local certificate store failed. Receive error message to install Quest certificates later. This should not be required - 274643
• Computer Collection scheduled tasks removed after upgrade to 10.2 if gMSA used as the scheduled task account - 280854
• rmad.db3 file gets overwritten during an uninstall -> install of version 10.2 - 283069
• Cannot retain the uncheck "Global Catalog Servers" option in the Advanced tab of the Computer Collection properties window - 230397
• It will display 'Network access is denied' error in Win2016/2019 if specify account to restore GPO with "domain\username" format - 233623
• Cannot see some advanced objects in the object picker in Online Restore Wizard – 275027
• During upgrade a DBImport error occurs when antimalware status data exists. Caused by debug logging on by default - 274622
• GPO Comparison Report is not working – 278211
• Zero touch against Dell server not working. Forward slash in the ISO access credentials is required - 274417
• Integrity check may fail if the storage server is registered using an IP address - 274471
• Double backslash in the backup path on the storage server causes failure - 274472
• Cannot perform BMR restore in 10.2 if the source machine is BIOS with a SCSI boot volume - 277893
• "System.ArgumentException: An item with the same key has already been added" error during BMR recovery when multiple DCs configured to boot using iLO - 282728
• Dell and HP ZeroTouch settings are converted to templates on upgrade - 283208
• Template selection and configuration usability improvements and clarification with better text - 297078

10.2 Resolved Issues:

• Security Vulnerability - Sensitive comments embedded within client-side code sent to an end user machine - RMADFE-3244, 218142
• Security Vulnerability - Runtime hardening (SEP, ASLR and other) - RMADFE-3248, 218146
• Full replication fails when a DC is selected for the option 'Unpack each backup upon its creation' in the master console - RMADFE-1858, 218500
• Storage agent settings are not applied on install - 219910
• No progress/wait indication after clicking 'OK' on the 'Add Console…' dialog - 224321
• Backup fails if the Domain Controllers OU has a AzureADKerberos computer object in it as part of Azure AD FIDO deployment - 227903
• Improve documentation with information on number of scheduled computer collections for optimal performance - 232614
• Access Violation in the ProcessRequest function and crashes service - 232682
• Remove mutual exclusion mechanism between replication process and restore process - RMADFE-1575, 237972
• Display correct backup info and support restore for Collections with containers (not DCs) - 240580
• Retriable VSS error causes undefined behavior in Backup Agent on retry - 241825
• Modify the configuration to remove collision problems with SHA1, moved to SHA256 - 253913
• Retention policy ignores collection and consider backups of all collections – 259645
• Email notification template contains invalid text and status message - 252659
• Verification email contains incorrect backup data - 252866
• Creating ADVL fails when unable to access VConverter error - 253382
• Wrong replication partner is selected in IFM recovery on second phase. IFM failed - 253681
• IFM script does not automatically reboot DC after installed AD DS tools. IFM failed – 253778
• Install AD method on second phase may fail with "Unable to connect to the replication source" - 225791
• IPSec isolation policy was not removed successfully when previous forest recovery is aborted and left dirt data - 237004
• IPSec isolation policy was not removed successfully during restore - 237049
• The "Reset computer account" operation fails when some other recovery operation failed and retried earlier - RMADFE-2659, 242197
• After upgrade from 10.1 to 10.1.1, the Verify Settings in Forest Recovery console send emails with some kind of strange status messages – 242679
• An error "Index(zero based) must be greater than" during BMR recovery on the Restore disks step - 218575
• When processing Bare Metal Active Directory recovery for Korean Windows, it created error message in 'Run pre-recovery checks' step - 219702
• During BMR recovery restart domain controller in normal mode hanging - 227232
• "Collection diagnostic data" tool fails to collect data from target machine in Clean OS and BMR modes - 227427
• Cannot bind parameter 'DomainMode' to the target error - 232543
• DC restored with 'Restore to Clean OS' method from backup without DNS partition should not be selected as Primary DNS server - RMADFE-3100, 242133