Broken, but just wait! - High CPU usage issue in Azure AD Connect Health for Sync - update - 8/16/18

home | blog | Teh Internet | guest blog |rants | political | projects | Gwen and Liam | Citadel patched | Tools | Scouts


- Careful Chrome users, this search box might be "Not secure"


We will update this article when the new version of the Azure AD Connect is available. It is the middle of August, no article update, but updates for the AD Connect are available....
So, don't apply updates, and just wait... - at lest for the lesser AD Connect customers...
https://support.microsoft.com/en-us/help/4346822/high-cpu-issue-in-azure-active-directory-connect-health-for-sync
Short version for when they redact the best part of the article: (or make it a 404)
Symptoms
You experience slow performance and high CPU usage (reaches to 100%) issue in a machine that runs Azure Active Directory (Azure AD) Connect Health for Sync monitoring agent. In task manger, you notice that the process MIcrosoft.Online.Reporting.MonitoringAgent.Startup uses the high CPU usage.

The issue is not limited to specific Azure AD Connect Health versions and operating system versions. 

Cause
This issue occurs because June 2018 update of NET framework 4.7.2 is installed in the machine, and Azure AD Connect Health for Sync monitoring agent does not fully support this update.

The following .NET framework update would cause the high CPU issue of monitoring agent:

.Net framework update

OS version

KB4338420

Windows Server 2008

KB4338606

Windows Server 2008 R2

KB4054542

Windows Server 2012

KB4054566

Windows Server 2012 R2

KB4054590

KB4338814

KB4338419

KB4338605

KB4345418

General

Resolution
For Connect Health for AD DS and AD FS:

To resolve this issue, install the Azure AD Connect Health Agent, version 3.1.7.0 that is released on July 2018.
It can be downloaded from Connect Health public documentation.

For Azure AD Connect:

A new version of the Azure AD Connect will be released soon. It will contain a fix for this high CPU usage issue.
We will update this article when the new version of the Azure AD Connect is available.

Last Updated: Jul 25, 2018



[æ]