This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(240, 7.000000000000001%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
After Performing a new Azure Connect V2.2 install on a fresh 2019 Server DC, using an exported configuration from my original Connect V1.5 - everything appears to be normal except for one Delta-Sync reports a completed-sync-error for the local Domain in the Azure Service manger console. Monitoring and Health in the Entra Admin Center shows no alerts or errors. The new Sync service has been in production for 24 hours and no domain anomalies reported,,.so far. Event viewer on the on premise Server 2019 DC reports the following log entry:
The server encountered an unexpected error while performing a callback operation.
"ERR_: MMS(112): ..\ma.cpp(5142): Completing apply rules step has failed.
Azure AD Sync 2.2.8.0"
Hello @CowJazz , importing Entra Connect settings from a V1 installation to a V2 is not supported. The recommended approach is to do a Swing migration of your V1 installation.
Let us know if you need additional assistance. If the answer was helpful, please accept it and rate it so that others facing a similar issue can easily find a solution.
Swing was not possible as V 1.5 was no longer working (stop-server-error)
Thanks for sharing that. What solution was chosen?
Good day Alfredo,
I have not been able to find anywhere in MS documentation or the Knowledgebase where configuration export from AD Connect V1.5 to AD Connect V2.2 is not supported in that migration scenario. Can you send me a link? My solution after 4 days of a Severity A case and watching account after account lock out while waiting for support - was to bring up another brand new dedicated 2019 Server, join it to the domain and promoting it to a Domain controller as a global catalogue server. Verified AD health with DCDiag and that TLS 1.2 was available and working. Download AD Connect V 2.2 from the Azure Portal and installed it with the basic configuration using Password Hash Synchronization and Exchange Hybrid environment options and took the option to create new AD and AAD sync accounts and then password updates began syncing from the on-Premis AD to Azure and 365 as well as new AD accounts (which were working before... just not password sync)
I am currently working on a plan to move from our 365/Exchange-hybrid environment.