Notifications
Clear all
Topic starter
We ran into an issue today and I wanted to share the experience in the hopes that some of you might avoid it.
We are on CPS 12.3.1, which required us to get synced up to Azure AD with Azure AD Connect (running on our DC servers). This has not presented any issues until we recently installed .NET 4.7.2 as part of a Windows update. This update caused Azure AD Connect to spike the CPUs on the servers to 100% and keep them there, which caused all sorts of issues downstream (see links below - we are not alone). We are researching how to rollback this .NET update. In the mean time, we have disabled Azure AD Connect, which (temporarily) resolved the issue. I have reached out to CPS Support to determine the consequences of disabling Azure AD Connect from a Centricity perspective.
Posted : August 9, 2018 8:54 am
I had the same issue and did the same thing. I would like to get to the bottom of this but have more important things to do for now. I did see the kb article you referenced and figured that M$ would eventually fix this since both AD connect and .NET are their products plus they already seem to be aware of the problem. I only had that AD connect thing on one DC. For the record, I only had upgraded my test server at the time I had to disable the service. I did an upgrade to production and was able to run the AD connect Powershell script with no issues. I would think that the sync would update my AD with the cloud so I should be OK with this setup for a few more CPS versions. Once there are significant parts of CPS in the cloud this workaround won't work.
From what I understand the Azure AD thing was not a requirement for 12.3.1 but requirement to do some type of MU thing and it will only be necessary at the beginning of the year. Hopefully it will be fixed by then.
On the upside, I no longer receive emails telling me that I have a sync problem with "a user or group". I was getting them and would log in only to find no issues according the Azure AD control panel. One would think that this kind of stuff would be addressed already as Azure AD has been out long enough to make M$ quite the player in the cloud arena.
Mike Zavolas
Tallahassee Neurological Clinic
Posted : August 10, 2018 12:36 am
Have you heard back from GE on this? By the way, which version of Windows are you running on your DCs? I am on 2012r2.
Posted : August 14, 2018 3:06 am
Topic starter
We are running Windows Server 2016. We did hear back from GE, but we do not have a definitive answer yet. Our case has been escalated to L2 Support.
The good news is that we were able to roll back the update and get Azure AD Connect back up and running. However, I still want to get to the bottom of this and figure out what could go wrong if this system is not running.
Posted : August 14, 2018 3:17 am
Stop the service AzureADConnectHealthSyncMonitor on the server running AAD. This resolves the issue and does not seem to impact the functionality.
Posted : September 6, 2018 1:22 am
