-
Title
Errors encountered when trying to restore an object that is synched between on-prem AD and Azure AD (hybrid object) -
Description
When trying to restore an object that is synched from the on-prem AD using Azure AD Connect with a version of 1.4.18.0 or later the following errors are shown in On Demand Recovery:"[Hybrid Module] Failed to build the attribute mapping: Failed to load attribute mapping: There was no endpoint listening at net.pipe://localhost/ADSyncManagement that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.; There was no endpoint listening at net.pipe://localhost/ADSyncManagement that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details"AND"[Hybrid Module] Failed to restore object . Cannot map object attributes" -
Resolution
An updated version of the RecoveryManagerPortal.msi installer has been released. Click Here to download the new version and run it to upgrade the RMAD Portal.
If the errors persist after upgrading the RMAD Portal, test to confirm that the account specified in the RMAD Portal On Demand Integration settings, has sufficient rights to create a remote Powershell session from the RMAD Portal server to the Azure AD Connect Host. The On Demand Integration Settings are found in the RMAD Portal under Configuration | Portal Settings | On Demand Integration. To confirm the account can create a Remote Powershell session, run the following script from the RMAD Portal server:
Import-Module "C:\Program Files (x86)\Quest\Recovery Manager Portal\Invoke-AADSync.psm1" -Force$creds = New-Object PSCredential('IntegrationAccount', (ConvertTo-SecureString 'IntegrationAccountPassword' -AsPlainText -Force))$session = New-AADSyncRemoteSession -AadConnectHost "AzureADConnectHostName" -Credential $creds#Get-AADSyncMapping -Session $session -Domain "DomainFQDN"Replace:- IntegrationAccount with the account name specified in the RMAD Portal On Demand Integration Settings
- IntegrationAccountPassword with the password for the account name specified in the RMAD Portal On Demand Integration Settings
- AzureADConnectHostName with the hostname for where you are running the Azure AD Connect software
- DomainFQDN with the FQDN of your domain
If you get errors such as Access Denied, test with a different account. Once you have the script running successfully, replace the credentials in the RMAD Portal On Demand Integration settings with the credentials used in the successful run of the script, and then test the On Demand Recovery again.
-
Defect ID
RMAZ-1260 -
Additional Information
Another symptom is configuring the On Demand Integration in the Recovery Manager Portal hangs and does not complete.