将AD同步移动到新服务器时，m-DS-ConsistencyGuid/ObjectGUID [英] m-DS-ConsistencyGuid / ObjectGUID when moving AD sync to new server

问题描述

我在现有域中安装了新的AD同步服务器.旧服务器正在使用ADFS和m-DS-ConsistencyGuid源锚.

I installed a new AD sync server in existing domain. Old server is using ADFS and the m-DS-ConsistencyGuid source anchor.

我看到新服务器正在使用ObjectGUID-服务器已启用登台模式.

尝试将源锚定在新服务器上时，我得到:

您的源锚配置无法更改，因为m-DS-ConsistencyGuid已在使用中...

Your source anchor configuration cannot be changed because m-DS-ConsistencyGuid is already in use ...

我不介意使用ObjectGUID-我只想确保已同步到O365的用户保持完整?而且它们没有被删除/不被认可吗?用户正在使用Exchange Online ..真的不想重新创建邮箱等..

I dont mind using ObjectGUID - I just want to make sure my users already synced to O365 stays intact? And that they are not removed/addeed? Users are using Exchange Online .. Really dont want to re-create mailboxes etc ..

谢谢.

BR

卡斯滕

推荐答案

由于您以前已经使用SourceAnchor作为ObjectGUID运行了Azure AD Connect，并且metaverse仍然保留在服务器中-因此您将无法选择ms-DS-Consistency GUID作为源锚点.

Since you had already run the Azure AD Connect previously with the SourceAnchor as ObjectGUID, and the metaverse still remains in the server - hence you are unable to select the ms-DS-Consistency GUID as the sourceanchor.

您需要从本地清除服务器的Azure AD Connect，然后重新运行AADConnect向导，这次选择ms-DA-ConsistencyGUID.

You would need to clean uninstall the Azure AD Connect from the server on-premise and then re-run the AADConnect Wizard and this time choose ms-DA-ConsistencyGUID.

参考:U

这篇关于将AD同步移动到新服务器时，m-DS-ConsistencyGuid/ObjectGUID的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！