Domain originated on SBS but was migrated to Std AD and now has a GUID mismatch

LJ 1 Reputation point
2021-09-20T17:11:24.237+00:00

We are in the process of migrating to some online services and encountered an error when we flipped the switch to only allow X from domain computers. All our computers lost their ability to connect. We found that the GUID being reported by the domain computers is different from the GUID being reported by the DCs. Our domain originated on an SBS server way back in SBS 2008 I believe and was migrated to standard AD some time after and has been updated through various windows server versions. The GUID in ADSIedit is the same as the DCs are reporting but the GUID in DNS is different and the endpoints are using that GUID.

After some research, we came upon https://social.technet.microsoft.com/Forums/lync/en-US/6427a110-1565-4b5e-8913-15361d9fab69/domain-guid-dns-registration-conflict?forum=winserverDS

Is this still the recommended solution for this issue?

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,822 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. LJ 1 Reputation point
    2021-09-20T17:38:04.523+00:00

    We enable OneDrive to sync only to computers joined to the domain. After we did that, none of our domain joined computers could connect to Onedrive.

    0 comments
  2. Limitless Technology 39,336 Reputation points
    2021-09-21T10:37:06.35+00:00

    Hi there,

    Yes, the forum you posted seems to be ended with a Good note, converging on the Issue and you can try out it. Meanwhile, I also came across this when you said that you have issues with one driver sync connectivity

    https://learn.microsoft.com/en-us/exchange/troubleshoot/administration/validation-errors-for-mailbox-archive-guid

    Hope this answers all your queries, if not please do repost back.
    If an Answer is helpful, please click "Accept Answer" and upvote it : )

    0 comments