Azure AD Connect Health Sync Monitor High CPU Usage

Question

Hello.  I have Azure AD Connect installed on my server to sync our on-premise domain with Office 365 and I'm noticing the Azure AD Connect Health Sync Monitoring Service is always running high CPU usage.  The actual process is Microsoft.Identity.Health.AadSync.MonitoringAgent.Startup.exe.  Is there a reason for this or a way to fix it?  Right now, I'm just stopping the Azure AD Connect Health Sync Monitoring Service(AzureADConnectHealthSyncMonitor) and my resources go back to normal.  I'm running Azure AD Connect 1.1.819.0 so it is the latest version.  If I restart the service, things are normal for a few minutes before this process spikes again.  Any help would be appreciated.  Thanks!

Answer 1

Seeing the same.

---

Andrew

Answer 2

We are also experiencing this issue.

Restarting the services bring it back to normal. Then slowly it was ramp up to 25% after 10 mins or so, then to ~60% and then 90%+

Re-installing or re-registering does not seem to make any difference

Answer 3

same here

server 2008 R2 with Azure AD Connect 1.1.819.0

Microsoft.Identity.Health.AadSync.MonitoringAgent.Startup.exe file version 1.1.30.32 (1/19/18) 

restarting returns cpu to normal but a few hours later and its back again

I believe its one of these updates:

KB4103713

KB4103768

KB4095874

Answer 4

Server 2012 R2

Azure AD Connect 1.1.819

Health Agent for Sync 3.0.164

I'm seeing the same thing as well.

Might be (Similar Family KB's to Knob Country).

KB4103725

KB4096417

KB4095875

KB4054566

So far nothing fixes bringing my server to it's knees

Answer 5

Server 2012 R2

Azure AD Connect 1.1.819

Health Agent for Sync 3.0.164

I'm seeing the same thing as well.

Might be (Similar Family KB's to Knob Country).

KB4103725
KB4096417
KB4095875
KB4054566

2012R2
I uninstalled KB4054566 (the others were not installed) and the issue appears to have gone away.

KB4054566 is .NET 4.7.2

---

Andrew

Answer 6

Thanks, i'll try this and report back, sure hope the Azure AD Connect client gets an update as this should be affecting lots of DCs.

Answer 7

@all:

Let us know if the issue persists after uninstalling the KB4054566 update.

Answer 8

Hi,

I've just uninstalled KB4054566 as well (nothing else was installed and it's been 20 mins and it's sitting there twiddling its thumbs. The memory usage has gone up from 40MB to 55MB but the CPU is at 0%

Thanks for the advice Andy

Answer 9

Confirmed for me, KB4054566 was the issue.

Answer 10

This problem started for me approximately 5 weeks ago and being unable to find a solution and knowing how critical Azure AD Connect was to our environment, I opened a support case with Microsoft.  After involving a couple different departments they told me that I needed to remove this software and that software, none of which had any impact.  Finally they told me that I had to install AD Connect on a different server -- guess what, CPU hit 100% on that one too and it was a fresh build, fully patched.

Today they told me that "my support case was being archived because they found a product limitation that will not let them fix the problem."  In other words, we can't find the problem so we are closing your support case and sending you away.

By the way, I removed KB4054566 from both servers and the problem has not reappeared since, although it has only been a couple hours -- in the last month it had been 15-20 minutes after killing the service, it would restart and use 100% again.

Answer 11

What a shock that Microsoft isn't going to do anything to resolve the issue.  In our environment, we have to keep our systems patched due to compliance reasons so uninstalling KB4054566 isn't an option.  I have just stopped the Azure AD Connect Health Sync Monitoring Service and the problem hasn't returned.

Answer 12

Same problem here, resolved by removing the KB noted.

Answer 13

Hello I am from Azure AD Connect Health team. Our team is investigating the High CPU usage issue on our high priority. I will update in this thread soon.  

Answer 14

Hello I am from Azure AD Connect Health team. Our team is investigating the High CPU usage issue on our high priority. I will update in this thread soon.  

Answer 15

@T3chGuy007

What are the odds that I'd literally be listening to some Demon Hunter while troubleshooting high CPU usage on an Azure-based VM running AD Connect, and notice your avatar? Good stuff!

As another data point, I have each symptom noted in this thread, but KB405466 is NOT installed. Unless that KB has been superseded by something else there's got to be another root cause

Answer 16

@BulletproofJohn

Ha.  Gotta love Demon Hunter!

Hopefully, Microsoft releases a patch to fix this issue so environments can stay patched.

Answer 17

@T3chGuy007

As another data point, I have each symptom noted in this thread, but KB405466 is NOT installed. Unless that KB has been superseded by something else there's got to be another root cause

KB4054566 not KB405466

Also - What OS?

.Net 4.7.2 has a different KB depending on the OS.

https://support.microsoft.com/en-au/help/4054531/microsoft-net-framework-4-7-2-web-installer-for-windows

Server 2008R2 "Microsoft .NET Framework 4.7.2"

Server 2012 = KB4054542

Server 2012R2 = KB4054566

Server 2016 = KB4054590

---

Andrew

Answer 18

Ah, that's what I get for not reading the thread carefully enough. Yes, I'm running Server 2016 and .NET 4.7.2 was installed via KB4054590. No issues after removing it. So my experience is consistent the others in this thread. Thanks for the info.

Answer 19

Hello,

After our investigation, we are seeing potential high CPU impact of Connect Health monitoring agent with .NET Framework KB in :

KB4054542 , KB4054566 , KB4054590

AAD Connect Health team is releasing the new agent release to handle the compatibility issue in staged roll out through auto upgrade.

Zhiwei Wang

Answer 20

I had the same problem on server 2016.

Azure AD Connect 1.1.819

Update KB4054590 was not installed.

I uninstalled KB4338814 which resolved the problem.

Answer 21

I had the same problem on server 2016.

Azure AD Connect 1.1.819

Update KB4054590 was not installed.

I uninstalled KB4338814 which resolved the problem.

Answer 22

A little late to the party but I had the same problem today (july 11, 18) after my W2012 R2 installed update KB4338815, 89030 and 3434558.    KB 4054566 was not installed. 

I uninstalled KB4338815 but it did not solve the problem.  

Answer 23

Same issue here, W2008 R2, full up to date

Uninstalling KB4087364 did nothing, the other ones are not installed

Answer 24

We've just seen this today also.

Server 2016, AAD Connect 1.1.819.0. Started after installing KB4338814, uninstalling it fixed the problem on both our live and staging servers.

Glad we have a test domain and that this update supports removal! 

Answer 25

Also having this issue with 2008 R2, tried to uninstall latest cumulative KB4338818 & reboot but it does not help. After a while process Microsoft.Identity.Health.AadSync.MonitoringAgent.Startup.exe is again at 100% AAD Connect is also 1.1.819.0

Answer 26

A little late to the party but I had the same problem today (july 11, 18) after my W2012 R2 installed update KB4338815, 89030 and 3434558.    KB 4054566 was not installed. 

I uninstalled KB4338815 but it did not solve the problem.  

Same Issue, yesterday after updates KB4338815 and KB4338419.

Win2012R2

Answer 27

We're seeing this too on Server 2008R2.  KB4054566 is not installed, but two other .net 4.7.1 updates came in yesterday and today:

KB4338420 - today (7/11/2018)

KB4229728 - Yesterday (7/10/2018)

we're removing them now and will post again the results.

Answer 28

I have a similar issue. Azure Windows 2016 VM, running as a DC with the AAD Connect installed. Yesterday,  the Cumulative Update KB4338814 was installed. The Azure AD Connect Health Sync Monitoring Service pushed the CPU to 100%. I removed the KB4338814 and the CPU dropped to normal. I installed .net Framework 4.7.2, and the service pushed the CPU to 100%. I removed it and the CPU dropped to normal.

Answer 29

Same situation as everyone else. 

Server 2012 R2 
Azure AD Connect 1.1.647 (older version)
Last night two updates were installed: KB4338419 and KB4338815. 

First step was to uninstall KB4338419. No effect. Still 99% CPU usage.
Second step was to uninstall KB4338815. Irritatingly though, when i rebooted, Windows automatically re-installed KB4338419. (Along with KB4284815) With that said, removing KB4338815 seems to have resolved the issue for now. CPU is now operating normally. 

Interestingly, there was a thread on /r/syadmin this morning regarding KB4338814 (The Server 2016 version of KB4338815) and some serious known issues. Not sure if it's related as the known issue is with DHCP. Though one has to think that if this update has serious issues like that with DHCP, then there are probably other issues that aren't known. 

---Edit----
So it turns out i was wrong. KB4338815 was not the issue. The CPU usage went back up to 99% after about 15 minutes. I then re-uninstalled KB4338419 and rebooted. Everything is back to normal after an hour. So i'm now leaning toward the culprit being KB4338419. 

Answer 30

Sorry for the cross post, but want to add another problem with KB4338814: https://social.msdn.microsoft.com/Forums/azure/en-US/ab74b11e-3e6b-4a72-b8ba-017a604aa993/kb4338814-causes-microsoft-vbscript-runtime-error-800a01ad-activex-component-cant-create-object?forum=WindowsAzureAD

Answer 31

Same situation as everyone else. 

Server 2012 R2 
Azure AD Connect 1.1.647 (older version)
Last night two updates were installed: KB4338419 and KB4338815. 

First step was to uninstall KB4338419. No effect. Still 99% CPU usage.
Second step was to uninstall KB4338815. Irritatingly though, when i rebooted, Windows automatically re-installed KB4338419. (Along with KB4284815) With that said, removing KB4338815 seems to have resolved the issue for now. CPU is now operating normally. 

Interestingly, there was a thread on /r/syadmin this morning regarding KB4338814 (The Server 2016 version of KB4338815) and some serious known issues. Not sure if it's related as the known issue is with DHCP. Though one has to think that if this update has serious issues like that with DHCP, then there are probably other issues that aren't known. 

---Edit----
So it turns out i was wrong. KB4338815 was not the issue. The CPU usage went back up to 99% after about 15 minutes. I then re-uninstalled KB4338419 and rebooted. Everything is back to normal after an hour. So i'm now leaning toward the culprit being KB4338419. 

Same issue, updated last night and the Service went 100%. Uninstalling KB4338419 fixed the issue for now. I hope Microsoft fix this stuff so i can keep my servers updated.

Answer 32

Same issue. I just installed the following updates and the CPU of this process went to 100%.

• 2018-07 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows 8.1 and Server 2012 R2 for x64 (KB4340558)
• Windows Malicious Software Removal Tool x64 - July 2018 (KB890830)
• Microsoft .NET Framework 4.7.2 for Windows Server 2012 R2 for x64 (KB4054566)
• 2018-07 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4338815)

My setup:

• Windows Server 2012 R2
• Microsoft Azure AD Connect 1.1.819.0
• Microsoft Azure AD Connect Health agent for sync 3.0.164.0
• Microsoft Azure AD Connect synchronization services 1.1.819.0

Answer 33

Same issue this morning.  Uninstalled KB4338420, Server 2008 R2's version of the .NET update, and all back to normal.

Answer 34

Same issue here with 100% CPU usage after updates.

Uninstalling KB4338419 resolved the issue for us.

Answer 35

Same issue . Yesterday I installed the following updates and the CPU usage for this process went to 99%.

• 2018-07 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows 8.1 and Server 2012 R2 for x64 (KB4340558)
• Windows Malicious Software Removal Tool x64 - July 2018 (KB890830)
• Microsoft .NET Framework 4.7.2 for Windows Server 2012 R2 for x64 (KB4054566)
• 2018-07 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4338815)
• 2018-07 Security Update for Adobe Flash Player for Windows Server 2012 R2 for x64-based Systems (KB4338832)

Our setup:

• Windows Server 2012 R2 Datacenter
• Microsoft Azure AD Connect 1.1.819.0
• Microsoft Azure AD Connect Health agent for sync 3.0.164.0
• Microsoft Azure AD Connect synchronization services 1.1.819.0

Uninstalling ,KB4338419, KB4054566 and restarting the server restored the process back to normal CPU usage patterns on our 2012 R2 server.

Answer 36

Same for me on the physical Windows 2016 box.  Removed 4338814 and CPU fell back to normal.

Answer 37

Same high CPU issue on a Server 2016 box after applying 2018 July's patches.

Answer 38

Seeing exactly the same on 2012 R2, but I do NOT have KB4338419, KB4054566 installed

I have KB 4340006 installed (Success), but can not uninstall it, as it says Not installed during wsus /uninstall

As per this:

https://support.microsoft.com/en-gb/help/4340006/security-only-update-for-net-framework-3-5-sp1-4-5-2-4-6-4-6-1-4-6-2-4

had to uninstall KB 4338613 & KB 4338605

And same for KB 4340558 as per this

https://support.microsoft.com/en-us/help/4340558/security-and-quality-rollup-updates-for-net-framework-3-5-sp1-4-5-2-4

had to uninstall 4338424

Seb

Answer 39

Also having same issue on Server 2012 Datacenter. We reverted back before newest updates, but would like to have our servers up-to-date.

Answer 40

Same here. After installing 2018-07 Cumulative Update for Server 2016 (KB4338814) CPU usage spikes to 100% after about 10 minutes of uptime.

Uninstalled KB4338814 and it drops back to 0%.

Using Azure AD Connect 1.1.819.0

Answer 41

I have had the same issue and have also found after removing 2018-07 Cumulative Update for Server 2016 (KB4338814) does resolve the high CPU usage coming from Azure AD Connect Health Sync Monitoring Service(AzureADConnectHealthSyncMonitor).

When is (ETA please) the rollout going to occur via auto-update of the AADConnect client for the AADConnect Health Agent, as stated by @ZhiweiW-MSFT "AAD Connect Health team is releasing the new agent release to handle the compatibility issue in staged roll out through auto upgrade." ?

Answer 42

Same issue here, server 2016 after installing  2018-07 Cumulative Update for Server 2016 (KB4338814).

Answer 43

exchange server 2016

I'm now uninstallingKB4338814

Answer 44

Hello,

After our investigation, we are seeing potential high CPU impact of Connect Health monitoring agent with .NET Framework KB in :

KB4054542 , KB4054566 , KB4054590

AAD Connect Health team is releasing the new agent release to handle the compatibility issue in staged roll out through auto upgrade.

Zhiwei Wang

Any update on when a new agent release will happen?  We just noticed our servers where AD Connect is installed have CPU usage through the roof due to this incompatible update.  Would prefer to update the agent than remove the .Net Framework update.

Answer 45

For workaround, I stopped the Windows service "Azure AD Connect Health Sync Monitoring Service" and set it to start manually. Not the optimal solution but better than 100% cpu usage.

Answer 46

Any resolution? We have the same problem.

KB4054566 - was not installed.

Answer 47

Same here. KB4054566 NOT installed running high cpu. Any resolution?

Thanks

Eric

Answer 48

Server 2012 R2 Datacenter

I uninstall all updates installed on 12/07/2018 and CPU fell back to normal..

kb4338815
kb4338419
kb4054566
kb4340558
KB4338605
kb4339093
kb4340006
kb4338824

Answer 49

From the above list is it only KB 4340006 (or specifically KB 4338613/4/5 & KB 4338605) that are the problem (maybe also kb4340558?)

Answer 50

Windows Server 2012 R2 Standard

KB4338419 not installed, and still have high cpu usage. 

As others have stated, we have stopped the Azure AD Connect Health Sync Monitoring Service and the CPU usage dropped back to normal. 

Answer 51

Have you seen a spike in memory since stopping Azure AD Connect Health Sync Monitoring Service?

Answer 52

I have not seen a spike in memory after stopping the service. 

Thanks,
Kyle

Answer 53

Thanks Kyle, i'm on 2008 R2 standard and I've noticed a small increase in memory but that's much better then the CPU being fully pegged.

Answer 54

We removed 4054566 from several servers and CPU went back to normal.

We still have a couple of customer that don't have of the mentioned KBs are CPU is still high.

Any word on when the next update will be released?

Answer 55

Server 2016 datacenter here. Removing KB4338814 did the trick.

Answer 56

Uninstalling KB4338814 resolved this for me, too. Server 2016 Datacenter.

Answer 57

Same issue here.  I'm going to disable the Azure AD Connect Health Sync Monitoring Service for the time being on a test server and see what happens in a day or two.  If AzureAD is still in sync and the world hasn't ended, I'll be disabling it on about 30 of my client's servers too.

dcc

---

dcc

Answer 58

From the above list is it only KB 4340006 (or specifically KB 4338613/4/5 & KB 4338605) that are the problem (maybe also kb4340558?)

I needed to uninstall :
4338613

4338605

4338419

Reboot.

Then it relaxed.

Answer 59

Hi, this does not work for me.

Rolling back 4338613 & 4558605 & 4338419 and reboot, resulted in a 20 minutes relaxed state. Then it started all over again with almost 100% load on all cores on my 2012R2 DC.

Answer 60

I too and having this issue, server 2016 fully patched so it definitely broke after 4338814, i stopped and disabled the 2 Azure AD health services and sync'ing to office365 is still working just fine, so like MS said, they're aware of the issue and will push an auto-update out soon.  I'll just wait for that.  

Answer 61

Hello,

After our investigation, we are seeing potential high CPU impact of Connect Health monitoring agent with .NET Framework KB in :

KB4054542 , KB4054566 , KB4054590

AAD Connect Health team is releasing the new agent release to handle the compatibility issue in staged roll out through auto upgrade.

Zhiwei Wang

Any ETA here?

Answer 62

(WS2012R2)

I only needed to uninstall 4338605.

4338613 was installed, but did not need to be removed.

4338419 was not installed AFAICS.

4054566 and 4340558 were definitely not installed, as those installations failed.

Answer 63

Hello,

After our investigation, we are seeing potential high CPU impact of Connect Health monitoring agent with .NET Framework KB in :

KB4054542 , KB4054566 , KB4054590

AAD Connect Health team is releasing the new agent release to handle the compatibility issue in staged roll out through auto upgrade.

Zhiwei Wang

Windows 2012 Server (Not R2).

Having the same issue with the CPU at 99% and I do not have any of the KB shown above installed. 

But I do have 1 Optional Update available (KB4054542). 

I'm actually going to try the opposite by installing the KB above.

If that doesn't work then I'll uninstall it again and hope it might fix the issue. 

Will keep updating everyone after.

Answer 64

Hello,

After our investigation, we are seeing potential high CPU impact of Connect Health monitoring agent with .NET Framework KB in :

KB4054542 , KB4054566 , KB4054590

AAD Connect Health team is releasing the new agent release to handle the compatibility issue in staged roll out through auto upgrade.

Zhiwei Wang

Windows 2012 Server (Not R2).

Having the same issue with the CPU at 99% and I do not have any of the KB shown above installed. 

But I do have 1 Optional Update available (KB4054542). 

I'm actually going to try the opposite by installing the KB above.

If that doesn't work then I'll uninstall it again and hope it might fix the issue. 

Will keep updating everyone after.

Ok, that didn't work. 

Microsoft.Online.Reporting.MonitoringAgent.<g class="gr_ gr_97 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins doubleReplace replaceWithoutSep" data-gr-id="97" id="97">Startup</g> is still at 92%

I'm going uninstall KB4054542 now and hopefully, it'll go away.

Answer 65

Hello,

After our investigation, we are seeing potential high CPU impact of Connect Health monitoring agent with .NET Framework KB in :

KB4054542 , KB4054566 , KB4054590

AAD Connect Health team is releasing the new agent release to handle the compatibility issue in staged roll out through auto upgrade.

Zhiwei Wang

Windows 2012 Server (Not R2).

Having the same issue with the CPU at 99% and I do not have any of the KB shown above installed. 

But I do have 1 Optional Update available (KB4054542). 

I'm actually going to try the opposite by installing the KB above.

If that doesn't work then I'll uninstall it again and hope it might fix the issue. 

Will keep updating everyone after.

Ok, that didn't work. 

Microsoft.Online.Reporting.MonitoringAgent.Startup is still at 92%

I'm going uninstall KB4054542 now and hopefully, it'll go away.

Ok, I uninstalled KB4054542 and it didn't work. 

I'm still having 98% CPU usage from Microsoft Online Reporting. :(

Answer 66

As others have stated, there are some Windows Updates that you can uninstall until the client is fixed, or you can stop the service and set it to manual until the client is fixed.

How to Fix microsoft.online.reporting.monitoringagent.startup High CPU

Answer 67

As others have stated, there are some Windows Updates that you can uninstall until the client is fixed, or you can stop the service and set it to manual until the client is fixed.

How to Fix microsoft.online.reporting.monitoringagent.startup High CPU

Thanks.

I'll change the service to stop and manual since I don't have any of the windows update mentioned installed.  

Answer 68

Adding my own "Me Too".    Seeing the same thing, Microsoft.Identity.Health.AadSync.MonitoringAgent.Startup.exe utilizing high CPU.   I see that The following KB's were installed on 7/11/2018:

KB4338815 - Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4338815)

KB4340558 - 2018-07 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows 8.1 and Server 2012 R2 for x64 (KB4340558)

Server is running Windows Server 2012 R2.  It doesn't utilize the CPU highly right off the bat, takes a while after startup.  Hopefully this data will help someone at Microsoft Diagnose and Resolve.  The patches that I received do not seem to match what others are seeing above.  Also seem to have seen some random unschdeuled reboots from the systems that received these patches as well during the Friday afternoon/Saturday morning timeframes.  One late in the business day on Friday.

Answer 69

Trying out removal of kb4338606, and kb4338420 which were installed 7/12/18, exactly the same day this issue began.  Both of these are updates for .Net Framework 4.6.2 FYI.

Answer 70

Thank you very much

Uninstall of kb4338606, and kb4338420 fixed my problem.

I am running Windows Server 2008R2 and Azure AD Connect 1.1.654.0

Answer 71

I can confirm that removing KBs:

4338613
4338605
4338419

on a Windows 2012 R2 virtual machine fixed my problem.

Many thanks all. Waiting for Microsoft solution.

Marco Antonioli

Answer 72

Hi,

Microsoft.Identity.Health.AadSync.MonitoringAgent.Startup.exe is useing 95-100% off CPU all times.

How can I fix that that procces isn't using all my CPU?

 small business server 2011 << Server OS

Answer 73

Hi all,

Any updates on this, is it just a waiting game for us while Microsoft Fixes the issues and releases the appropriate updates?

Thanks,

Answer 74

Hi,

I'm also having this problem.

I'm keen to know when MS release an update (either for the Azure Sync Health or something else) to fix this

Thanks,

Greg

Answer 75

Hi,

we have the same problem with our server 2016.

The following updates are installed.

KB4345418

KB4338814

i have create an job in taskscheduler with restart the server every 10 minutes.

Have MS any resolution for us or must we deinstalled the patches?

thanks

Michael

Answer 76

For this issue, you can refer below article

https://randomdashtech.blogspot.com/2018/06/azure-active-directory-connect-high-cpu.html

---

Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer" Mai Ali | My blog:Technical | Twitter: Mai Ali

Answer 77

I'd love to play tag with the updates for Windows Server 2012 R2; which on my server have been installed since may without issue.

I've decided it is best at this time to disable the Azure AD Connect Health Sync Monitoring Service which is creating this problem.

My version is the latest 1.1.819.0. I do not have any of the KB updates mentioned here as being the cause of the high CPU usage. I will of course keep checking for a real fix, but breaking the server to get a notification of a problem isn't an acceptable condition. When I have more time, I will contact microsoft support and log a ticket.

Answer 78

I'd love to play tag with the updates for Windows Server 2012 R2; which on my server have been installed since may without issue.

I've decided it is best at this time to disable the Azure AD Connect Health Sync Monitoring Service which is creating this problem.

My version is the latest 1.1.819.0. I do not have any of the KB updates mentioned here as being the cause of the high CPU usage. I will of course keep checking for a real fix, but breaking the server to get a notification of a problem isn't an acceptable condition. When I have more time, I will contact microsoft support and log a ticket.

Microsoft already knows of the issue.  If you read above you'll see this.  They will publish a new version of Azure AD Health check soon to fix the problem, no ETA yet.  

Answer 79

A .Net patch introduced an optimization which caused the AD Health Monitoring Agent to run at 100% CPU. A fix of Connect Health monitoring Agent for the ADDS and ADFS roles have already been rolled out.

New version of AAD Connect will be deployed later this week. The new agent release will fix the health agent CPU issue. Please keep the agent auto upgrade setting enabled.

After the investigation, the following .NET KB would have the impact in high CPU issue of monitoring agent:

KB4338420 – Server 2008 R2

KB4338606 – Server 2008 R2

KB4054542 - Windows 2012

KB4054566 - Windows 2012 R2

Also, you might also mitigated the issue by uninstalling the following KBs as well.

• KB4054590     
• KB4338814
• KB4338419
• KB4338605

Please consider uninstall them if you have. Please reapply the patches as soon as the AadSync Monitoring Agent is updated.

Thanks,

Zhiwei

Answer 80

Microsoft is working on the new agent release. We have an update of the status.

Answer 81

Microsoft is working on the new agent release. We have an update of the status.

Answer 82

Microsoft is working on the new agent release. We have an update of the status.

Answer 83

Microsoft is working on the new agent release. We have an update of the status.

Answer 84

Thanks for the link

Ive unistalled 

• Server 2008 R2 - "Microsoft .NET Framework 4.7.2"

Tonight I will reboot the server and check if the problem is solved.

Answer 85

This same question was just answered by Microsoft tech over here:

https://social.msdn.microsoft.com/Forums/en-US/e9b621f6-f38c-488e-8fcb-ff85d406f256/azure-ad-connect-health-sync-monitor-high-cpu-usage?forum=WindowsAzureAD#02a21d3b-1ab4-4ea3-8566-928bb660df81

They provided a list of all the KBs to remove for the different Server versions.

Hope that helps.

Answer 86

Do you know when AAD Connect  version will be released?   Do you have any ETA ?

Answer 87

Hi

I had a similar issue with Server 2016 (DC and AAD). The only updates that were installed on the server are:

kb4345418

kb4284833

kb4132216

kb4093137

kb4049065

kb4035631

kb3186568

kb4023834

kb3199986

I uninstalled kb4345418 (July cumulative) and the issue didn't return since.

Br,

Peter

Answer 88

I unistalled all updates in the link that where on the server and I unistalled all update since the problem. Restart server and still the problem isn't solved. Is there a other way?

Answer 89

uninstalling KB4054566 fixed two 2012 R2 machines

Answer 90

I don't have KB4338606 on my 2008R2 server, and just uninstalling KB4338420 doesn't change anything

Guess I'll just wait for the AAD Connect Fix

Answer 91

Any status update, can we expect a patch today before COB?

Answer 92

Experiencing the same problem on Server 2016 although none of the mentioned KB updates are installed.

Uninstalled KB4338814 since it appears to be related to KB4345418 after reading the MS article about the update.

So far CPU usage hasn't returned to 99% usage.

Also found this forum post confirming removal of KB4338814 resolved the issue, https://social.technet.microsoft.com/Forums/systemcenter/en-US/03889fbe-c5d1-406f-abb3-69e21b6e336b/excessive-cpu-usage-from-health-service?forum=operationsmanagergeneral

Answer 93

What a shock that Microsoft isn't going to do anything to resolve the issue.  In our environment, we have to keep our systems patched due to compliance reasons so uninstalling KB4054566 isn't an option.  I have just stopped the Azure AD Connect Health Sync Monitoring Service and the problem hasn't returned.

Thanks for everybody's post, we have Server 2008R2 - ADSync 1.1.819.0

After installing KB4087364 + KB4338420 - started getting 100% CPU Usage

If I uninstalled the above KB's and .Net 4.7.2 then I won't be able to open the Azure AD Synchronization Service Manager.

Had to reinstall, set the service mentioned above by T3chGuy007 to manual and so far server CPU usage has been running normal.

Answer 94

New version of AAD Connect will be deployed early next week. The new agent release will fix the health agent CPU issue. Please keep the agent auto upgrade setting enabled.

After the investigation, the following .NET KB would have the impact in high CPU issue of monitoring agent:

KB4338420 – Server 2008 R2

KB4338606 – Server 2008 R2

KB4054542 - Windows 2012

KB4054566 - Windows 2012 R2

Also, you might also mitigated the issue by uninstalling the following KBs as well.

• KB4054590     
• KB4338814
• KB4338419
• KB4338605
• KB4345418 

Please consider uninstall them if you have. Please reapply the patches as soon as the AadSync Monitoring Agent is updated.

Answer 95

I have the same issue:

Server 2012 Standard
Azure AD Connect 1.1.819

None of the previously listed KBs were found, but I removed everything installed within the 24 hrs preceding the issue.  CPU utilization has returned to normal.  I will wait for the AAD Connect patch before attempting to reinstall.

KB4338421

KB4229726

KB4338604

KB4338610

KB4338820

KB4339093

KB4345425

KB4338830

Answer 96

Same issue here on Server 2012 R2 after installing KB4345424.  Uninstalling it didn't solve the problem. I then removed KB4054566 as mentioned above and that did not work either.  Then, finally, I removed KB4338419 and that did the trick.

Answer 97

I am having the same issue, but the infamous KB4054566 was not installed.

I basically uninstalled the last three updates (two on 11/7) to see if it solves the problem. Oddly enough the Microsoft.Identity.Health.AadSync.MonitoringAgent.Startup.exe was no longer listed as 90+% CPU time, but I still have 90+% consumption from other stuff! :( Windows Module Installer Worker seems to be the culprit now, but it keeps changing between Windows Module Installer Worker and the .Net Runtime Optimization Service (32-Bit)



Worth mentioning that this all started when I ran AD Connect last evening around 07:30 PM to add support for Hybrid Azure AD Join for Windows 10 devices! I Wonder if there is an easy way to disable the hybrid stuff though.

Here is the VMs usage for the past 24 hours:

Here is the usage for the past 7 days:

*** Now, to add more confusion into the mix... As I finished typing this email, it seems that things are back into normal! ***

For kicks, I decided to force a full AD Sync with PowerShell. The CPU came to a 95% for perhaps a second, staying mostly around 70%, sometimes hitting 85%. Here is monitoring of this VM for the past hour:

If you are curious, here are the updates I have at this moment:

So I **think** my issue has been resolved. Not thanks to Azure Support though. I opened an incident to handle this issue and the first chap who emailed me suggested that I should resize my VM, to which I did not responded well (poor guy! 😂).

Answer 98

Seeing the same

Windows 2012 R2

Yes KB4054566 is .NET 4.7.2 installed, once installed high CPU for Microsoft.Identity.HealthAadSync.MonitoringAgent.Startup.exe ran high CPU.

My workaround was using Task Manager, click the Details tab, <g class="gr_ gr_17 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="17" id="17">right click</g> Microsoft.Identity.HealthAadSync.MonitoringAgent.Startup.exe & select "Set affinity" all boxes checked.  My system is dual processor so I selected only the last 2 processors.  CPU for this process lowered to 12 from 87.  I realize this is a temporary fix but instead of uninstalling KB4054566 or stopping Azure AD Connect Health Sync Monitoring Service as long as the system stays up, looks good until the patch is released.

Answer 99

Windows 2012 R2, Azure 1.1.614.0

Uninstalled KB4338605, reboot, still high cpu.

Uninstalled KB4338419, reboot, no high cpu issue again.

Answer 100

Tried most of the action mentioned above. Uninstall KB4054566 (It does not exist on my server before even install .net 4.7.2) Need it to run some function so not possible to remove it.

Removed KB4338419 - cant help

Set Microsoft.Identity.Health.AaDSync.MonitoringAgent.startup.exe 's affinity only avoids both Core full load. 

Uninstall the Health Sync agent directly... 

I've uninstall AAD Connect in affected Server and install it in another Server 2012R2 . Originally it running Powershell 4.0 , without any .Netframework updates (4.7.2) installed .

But I've installed Powershell 5.1 and .Net 4.7.2 into this server before install AAD Connect. And issue appeared. We had another Server 2012 R2 without any problem for months which dont have Powershell and .net installed. So Now, i removed both .net and powershell from that new Server 2012R2 and but still fail.....

Answer 101

Hi, 

I am using windows 2016. After removing the security update it has also solved my problem.

Best Regards,

Nafis

---

Nafis Imtiaz Zaman

Answer 102

Server 2012 R2, uninstalled KB4338605 to get back to normal CPU usage.

Answer 103

Is the recommendation to uninstall KB4345418 or to wait for a update to be released of Azure AD Connect

Answer 104

Hi, this helped me on Win Svr 2016. Thank you guys for your help!

Regards

Karel

Answer 105

Is there any definite ETA (it's been two ETA's past now)?

Answer 106

I also had this issue on our 2008 R2 (physical server).

Uninstalling .Net 4.7.2 and restarting the services fixed CPU usage (since ~5minutes now)...

Thanks!

EDIT: CPU usage coming up again, will reboot server to see if it helps!

Answer 107

Having the same problem on a Win2016 VM Server in Azure with AD Connect 1.1.6XX installed. Just enabled the auto update feature, can someone tell me how long it takes to get an update? (at least the latest 1.1.8XX)

Answer 108

Issue comes back even after reboot, just OK for ~20 minutes, then it uses all the CPU again :(

EDIT: I am on 819 already...

Answer 109

I've stopped the service and decided to set the starttype to manual until they've fixed this.

Answer 110

I just did the same!

Answer 111

#me too. Later I tried removing KB4345418. This took a lot of time and didn't help, after starting the serviced, the CPU went crazy again. Annoying this.

---

Jan Z

Answer 112

So is there an open ticket @ MS?

Answer 113

Hi,

Azure AD Connect running on windows Server 2012R2 VM

Removed the following Windows Updates:

• KB4338605
• KB4338419

CPU is back to normal, hopefully this might help

cheers

Answer 114

Hi,

Azure AD Connect running on windows Server 2012R2 VM

Removed the following Windows Updates:

• KB4338605
• KB4338419

CPU is back to normal, hopefully this might help

cheers

Answer 115

New version of AAD Connect will be deployed early next week. The new agent release will fix the health agent CPU issue. Please keep the agent auto upgrade setting enabled.

After the investigation, the following .NET KB would have the impact in high CPU issue of monitoring agent:

KB4338420 – Server 2008 R2

KB4338606 – Server 2008 R2

KB4054542 - Windows 2012

KB4054566 - Windows 2012 R2

Also, you might also mitigated the issue by uninstalling the following KBs as well.

• KB4054590     
• KB4338814
• KB4338419
• KB4338605
• KB4345418 

Please consider uninstall them if you have. Please reapply the patches as soon as the AadSync Monitoring Agent is updated.

Hi,

Can you give us a more definitive date please? Also, how would we know if the new version is out?

As per the poster above, i had to uninstall the following KBs:

• KB4338605