Share via

The Entra Connect In-place upgrade encountered issues. Primary and stagging servers are reverted using VM snapshot.

Woody Chiu at RASI 216 Reputation points
2024-07-31T00:41:40.43+00:00

I did an in-place upgrade of both my primary and stagging Entra Connect servers to the latest Entra Connect version 2.3.20.

After the upgrade, I tested all forms of sync runs including Full and delta. They appeared to be fine with "success" status. However, I didn't test export and import. Two days later, Entra ID portal's Entra Connect Health showed some alerts and warnings. The on-prem Entra Connect server's Synchronization Service Manager shows a strange status of "Stopped-extension-dll-exception" when running either export or import while other runs were all "success".

After much research, I decided to revert both server VMs to the incidents right before the upgrades. After reverting the VM servers, all types of runs have "success" status. That's a good thing.

However, the Entra ID portal's Entra Connect Health appeared not able to continuously get the updates, status, and properties of the reverted VM servers.

Meanwhile, I will ignore the portal side status as long as all on-prem Entra Connect servers show "success" on all the synchronization runs.

What should I do to make the Entra Connect Health portal communicate and update with the on-prem reverted Entra Connect servers again?

Your prompt advice will be very much appreciated!

WC

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
13,251 questions
Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
22,163 questions
Accepted answer
  1. Fabio Andrade 1,660 Reputation points Microsoft Employee
    2024-07-31T22:13:32.7733333+00:00

    Hi @Woody Chiu at RASI

    Thanks for reaching out to Microsoft Q&A.

    First, I'd advise you to make sure the connection between the Entra Connect server and Entra endpoints is ok by using the command: Test-MicrosoftEntraConnectHealthConnectivity -Role Sync.

    In case there's no connectivity issues, try re-registering the agents by using the command: Register-MicrosoftEntraConnectHealthAgent -AttributeFiltering $true -StagingMode $false

    Both commands and more information about the Entra Connect Health agent can be found on this documentation: https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-health-agent-install

    Let me know if that's helpful to you.

    Thanks,

    Fabio

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

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.