Upgrade azure ad connect to v2 - swing migration

[Irino Houndekon (irinohdk)]

Hello ,

we are migrating AAD Connect from one server to another and we are stuck on the final step and need some advice on how to proceed. we currently have ADconnect with v1.2.69.0 running on Win2012R2 and, since we didn't think upgrading the OS under AAD Connect was a good idea, we decided to make a new instance of AADConnect on Win2019 . We then installed v2.1.15.0 ( the last one ) on the new Win2019 server. After that, I exported the configuration from the original and imported it to the new instance ( we have some custom rules) ... then there is no issues so far. We then ran AADConnectSyncDocumenter and compared the two instances. Re-running AADConnectSyncDocumenter leaves me with somes mismatches I'm not sure how to address. Some Import flows rules have been changed drastically while in the Export flows rules there are no changes detected between the two instances

First the sourceanchor .. maybe it comes with the new version of ADConnect?

Then a lot of modification in the new feature " end to end attribute flow summary " but only in import flows

Have you ever encountered these types of problems during version upgrades?

Do you think that these cases are normal and will not cause any trouble during the switchover?

All other configurations are identical with the production so far except for these ones.
Thanks