@VipulSparsh-MSFT : looks like there is an old version of AD Connect on on-prem DC (version 1.1.647), which does not have the EXPORT feature yet. Any advise?
I've found some guidance about how to preform custom installation and set up the same configuration as on the old one, including enabling/disabling staging mode etc. Doesn't look complicated...
Would you recommend to install the latest release of AZ AD Connect to the new server and configure it the same way as the old one.... and then just ENABLE staging on old one and disable on new server once all done? Or better to perform "in-place" upgrade of AD Connect on old server and then proceed with migration you mentioned above...
UPDATE:
I've already tried to install the most recent version of AZ AD Connect and noticed 3 things when going through the tasks that I would like to ask about:
- Connect to Azure AD - should I use "admin@mathieu.company .omnimicrosoft.com" as username? or "admin@mathieu.company .com" -that I've tried- would be OK as well, as this one is also marked as Global Administrator in AZ AD
- Azure AD sing-in task - I've seen "lan.company.com" UPN Suffix that was marked as "Not Added" only. It is the name of the domain in AD. However, the "lan.company.com" is not reigisterd in AZ AD, there is "company.com". I do not get "company.com" in UPN Suffix as an option. Can this cause any issue? ....I've marked "continue without matching all UPN suffixes to verified domains" during the installation.
- Identifying users - the recomended option was "Let Azure manage the source anchor" so I selected it. However, once installation finished, I saw that anchor was "objectGUID" with explanation that "ms-DS-ConsistencyGuid" attribute is already in use. I've tried to reinstall the AD Connect again and manually selected "ms-DS-ConsistencyGuid" to match the configuration on old server - woudl that be OK?
should I expect any issues when I move the new AD Connect to production (disable staging) with all the above? The environment is only a simple one AD forest environment... with no extra configuration...
UPDATE 2
Read your link once again and found info about how to get config file from AD Connect that does not support EXPORT feature. So following those instructions.... However, ended up on "Azure Active Directory credentials" when importing the configuration. By default, it chose "Azure Global Administrator", which is "admin@mathieu.company .omnimicrosoft.com"... Unfortunately, I do not have password for it as the guy who set it up before is not with us anymore. Would it work if I use another GLOBAL ADMIN? - e.g, "admin@mathieu.company .com" which I have the password for.... Or it may cause some mess...