Azure AD Connect/Sync no longer working after in place Server 2016 to 2022 upgrade

Anthony Rico 0 Reputation points
2023-08-10T14:00:46.8966667+00:00

I recently performed an in place upgrade from Server 2016 to Server 2022, and after the upgrade was completed, Azure AD Sync no longer seems to function. I am running the most recent version of Azure AD Connect (2.2.1.0) and I have already attempted uninstalling and reinstalling Azure AD Connect with no success. The installation goes fine and by everything I can see on the local server the sync is performed and is successful, however in the Azure Health Portal there are no completed syncs since the upgrade. There are also no sync errors shown other than the sync has not been completed in over 24 hours.

Any help is greatly appreciated.

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,903 questions
Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
21,308 questions
{count} votes

3 answers

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. James Hamil 24,136 Reputation points Microsoft Employee
    2023-08-16T20:12:54.1566667+00:00

    Hi @Anthony Rico , It's recommended not to perform an in-place upgrade of the OS for your Azure AD Connect server. Instead, you should prepare a new server with the desired operating system and perform a swing migration. Since you have already performed an in-place upgrade, you can try the following steps:

    1. Check if you have made any changes to the out-of-box synchronization rules. If so, these rules might be set back to the default configuration on upgrade.
    2. If you are using non-standard connectors, refresh the corresponding connector configuration in the Synchronization Service Manager after the in-place upgrade.

    If the issue persists, you may need to consider setting up a new server with the desired operating system and perform a swing migration as recommended in the documentation.

    We can also open a free support ticket for you to save you some pain. Please let me know and I can help you further.

    If this answer helps you please mark "Accept Answer" so other users can reference it.

    Thank you,

    James


  3. Andy David - MVP 147.5K Reputation points MVP
    2023-09-07T21:17:59.94+00:00

    I would note that in place upgrades of the Windows O/S are supported with AADConnect:

    https://learn.microsoft.com/en-us/azure/active-directory/hybrid/connect/how-to-upgrade-previous-version

    User's image

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.