none
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!
    Tuesday, June 5, 2018 11:45 AM

Answers

  • 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

    • Proposed as answer by mmccollum2 Sunday, June 10, 2018 11:01 PM
    • Marked as answer by T3chGuy007 Saturday, June 16, 2018 6:44 PM
    Friday, June 8, 2018 7:43 AM

All replies

  • Seeing the same.

    Andrew

    Tuesday, June 5, 2018 3:06 PM
  • 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



    • Edited by arrandavis Tuesday, June 5, 2018 11:00 PM Font issue
    Tuesday, June 5, 2018 10:54 PM
  • 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

    Wednesday, June 6, 2018 6:24 PM
  • 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

    Thursday, June 7, 2018 9:09 PM
  • 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

    • Proposed as answer by mmccollum2 Sunday, June 10, 2018 11:01 PM
    • Marked as answer by T3chGuy007 Saturday, June 16, 2018 6:44 PM
    Friday, June 8, 2018 7:43 AM
  • 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.
    Friday, June 8, 2018 5:21 PM
  • @all:

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

    Saturday, June 9, 2018 2:19 PM
    Moderator
  • 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


    • Edited by arrandavis Sunday, June 10, 2018 10:15 PM Clarified update removed
    Sunday, June 10, 2018 10:06 PM
  • Confirmed for me, KB4054566 was the issue.
    Sunday, June 10, 2018 11:01 PM
  • 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.

    Saturday, June 16, 2018 5:24 AM
  • 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.
    Saturday, June 16, 2018 6:48 PM
  • Same problem here, resolved by removing the KB noted.
    Thursday, June 21, 2018 12:03 PM
  • 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.  
    Thursday, June 21, 2018 6:28 PM
  • 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.  
    Thursday, June 21, 2018 6:28 PM
  • @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

    Friday, June 22, 2018 10:37 PM
  • @BulletproofJohn

    Ha.  Gotta love Demon Hunter!

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



    • Edited by T3chGuy007 Saturday, June 23, 2018 1:33 AM
    Saturday, June 23, 2018 1:32 AM
  • @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


    Sunday, June 24, 2018 1:21 AM
  • 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.

    Monday, June 25, 2018 12:59 PM
  • 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
    Friday, June 29, 2018 8:46 PM
  • 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.


    Wednesday, July 11, 2018 3:50 AM
  • 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.


    Wednesday, July 11, 2018 3:51 AM
  • 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.  

    Wednesday, July 11, 2018 9:51 AM
  • Same issue here, W2008 R2, full up to date

    Uninstalling KB4087364 did nothing, the other ones are not installed


    • Edited by Endl_ Wednesday, July 11, 2018 11:47 AM
    Wednesday, July 11, 2018 11:47 AM
  • 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! 

    Wednesday, July 11, 2018 12:59 PM
  • 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

    • Edited by Guest101010 Wednesday, July 11, 2018 1:05 PM
    Wednesday, July 11, 2018 1:04 PM
  • 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
    • Edited by QSPOR Wednesday, July 11, 2018 2:02 PM
    Wednesday, July 11, 2018 2:02 PM
  • 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.

    Wednesday, July 11, 2018 4:10 PM
  • 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.
    Wednesday, July 11, 2018 5:52 PM
  • 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. 

    • Edited by Matt RK Wednesday, July 11, 2018 9:52 PM Clarifying answer
    Wednesday, July 11, 2018 7:59 PM
  • 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
    Wednesday, July 11, 2018 8:52 PM
  • 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.

    Thursday, July 12, 2018 11:04 AM
  • 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
    Thursday, July 12, 2018 11:40 AM
  • Same issue this morning.  Uninstalled KB4338420, Server 2008 R2's version of the .NET update, and all back to normal.
    Thursday, July 12, 2018 1:38 PM
  • Same issue here with 100% CPU usage after updates.

    Uninstalling KB4338419 resolved the issue for us.

    Thursday, July 12, 2018 1:55 PM
  • 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.


    • Edited by Greg from CPI Thursday, July 12, 2018 3:42 PM Added additional info
    Thursday, July 12, 2018 3:17 PM
  • Same for me on the physical Windows 2016 box.  Removed 4338814 and CPU fell back to normal.
    Thursday, July 12, 2018 3:23 PM
  • Same high CPU issue on a Server 2016 box after applying 2018 July's patches.
    Thursday, July 12, 2018 3:28 PM
  • 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


    • Edited by scerazy Monday, July 23, 2018 9:38 AM
    Thursday, July 12, 2018 5:12 PM
  • Also having same issue on Server 2012 Datacenter. We reverted back before newest updates, but would like to have our servers up-to-date.
    Thursday, July 12, 2018 7:25 PM
  • 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
    • Edited by Chaori_ Friday, July 13, 2018 12:18 AM
    Friday, July 13, 2018 12:13 AM
  • 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." ?

    Friday, July 13, 2018 3:33 AM
  • Same issue here, server 2016 after installing  2018-07 Cumulative Update for Server 2016 (KB4338814).
    Friday, July 13, 2018 7:45 AM
  • exchange server 2016

    I'm now uninstalling
    KB4338814


    • Edited by chrisloup Friday, July 13, 2018 8:51 AM added picture
    Friday, July 13, 2018 8:48 AM
  • 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.
    Friday, July 13, 2018 9:34 AM
  • 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.
    Friday, July 13, 2018 12:23 PM
  • Any resolution? We have the same problem.

    KB4054566 - was not installed.

    Friday, July 13, 2018 1:08 PM
  • Same here. KB4054566 NOT installed running high cpu. Any resolution?

    Thanks

    Eric

    Friday, July 13, 2018 1:09 PM
  • 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


    Friday, July 13, 2018 1:26 PM
  • From the above list is it only KB 4340006 (or specifically KB 4338613/4/5 & KB 4338605) that are the problem (maybe also kb4340558?)

    • Edited by scerazy Friday, July 13, 2018 3:46 PM
    Friday, July 13, 2018 3:45 PM
  • 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. 
    Friday, July 13, 2018 4:04 PM
  • Have you seen a spike in memory since stopping Azure AD Connect Health Sync Monitoring Service?
    Friday, July 13, 2018 5:05 PM
  • I have not seen a spike in memory after stopping the service. 

    Thanks,
    Kyle

    Friday, July 13, 2018 5:30 PM
  • 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.
    • Edited by Jes817 Friday, July 13, 2018 7:34 PM
    Friday, July 13, 2018 5:35 PM
  • 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?

    Friday, July 13, 2018 5:43 PM
  • Server 2016 datacenter here. Removing KB4338814 did the trick.
    Friday, July 13, 2018 7:06 PM
  • Uninstalling KB4338814 resolved this for me, too. Server 2016 Datacenter.
    • Edited by Aleksiv95 Sunday, July 15, 2018 4:45 PM Added server version
    Sunday, July 15, 2018 4:43 PM
  • 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

    Sunday, July 15, 2018 8:01 PM
  • 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.

    Monday, July 16, 2018 8:09 AM
  • 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.

    Monday, July 16, 2018 12:53 PM
  • 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.  
    Monday, July 16, 2018 1:36 PM
  • 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?
    Monday, July 16, 2018 1:37 PM
  • (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.

    Monday, July 16, 2018 3:28 PM
  • 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.

    Monday, July 16, 2018 3:36 PM
  • 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.

    Monday, July 16, 2018 3:48 PM
  • 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. :(

    Monday, July 16, 2018 5:04 PM
  • 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

    Monday, July 16, 2018 5:10 PM
  • 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.  

    Monday, July 16, 2018 5:32 PM
  • 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.

    Monday, July 16, 2018 9:28 PM
  • 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.
    Tuesday, July 17, 2018 12:11 AM
  • 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

    Tuesday, July 17, 2018 4:25 AM
  • 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

    Tuesday, July 17, 2018 6:36 AM
  • 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



    Tuesday, July 17, 2018 11:49 AM
  • 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,

    Tuesday, July 17, 2018 12:06 PM
  • 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

    Tuesday, July 17, 2018 12:30 PM
  • 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

    Tuesday, July 17, 2018 12:36 PM
  • 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

    Tuesday, July 17, 2018 3:48 PM
  • 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.

    Tuesday, July 17, 2018 5:40 PM
  • 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.  
    Tuesday, July 17, 2018 9:09 PM
  • 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






    • Proposed as answer by ZhiweiW-MSFT Tuesday, July 17, 2018 10:26 PM
    • Edited by ZhiweiW-MSFT Tuesday, July 17, 2018 10:38 PM
    Tuesday, July 17, 2018 10:26 PM
  • Microsoft is working on the new agent release. We have an update of the status.
    Tuesday, July 17, 2018 10:55 PM
  • Microsoft is working on the new agent release. We have an update of the status.
    Tuesday, July 17, 2018 10:56 PM
  • Microsoft is working on the new agent release. We have an update of the status.
    Tuesday, July 17, 2018 10:56 PM
  • Microsoft is working on the new agent release. We have an update of the status.
    Tuesday, July 17, 2018 10:58 PM
  • 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.

    Wednesday, July 18, 2018 6:55 AM
  • 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.

    Wednesday, July 18, 2018 7:09 AM
  • Do you know when AAD Connect  version will be released?   Do you have any ETA ?
    Wednesday, July 18, 2018 1:05 PM
  • 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


    Wednesday, July 18, 2018 4:56 PM
  • 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?
    Thursday, July 19, 2018 7:18 AM

  • uninstalling KB4054566 fixed two
     2012 R2 machines
    Thursday, July 19, 2018 8:38 AM
  • 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
    • Edited by Endl_ Thursday, July 19, 2018 10:35 AM
    Thursday, July 19, 2018 10:34 AM
  • Any status update, can we expect a patch today before COB?
    Thursday, July 19, 2018 1:32 PM
  • 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
    • Edited by jar03j Thursday, July 19, 2018 3:21 PM
    Thursday, July 19, 2018 3:16 PM
  • 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.

    Thursday, July 19, 2018 6:40 PM
  • 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.

    • Proposed as answer by ZhiweiW-MSFT Thursday, July 19, 2018 6:50 PM
    Thursday, July 19, 2018 6:50 PM
  • 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

    Friday, July 20, 2018 8:37 AM
  • 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.



    • Edited by saleaway Friday, July 20, 2018 4:10 PM
    Friday, July 20, 2018 2:55 PM
  • 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! 😂).



    • Edited by pmdci Friday, July 20, 2018 5:45 PM
    Friday, July 20, 2018 5:37 PM
  • 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.

    • Edited by VersAdm Friday, July 20, 2018 5:58 PM
    Friday, July 20, 2018 5:43 PM
  • Windows 2012 R2, Azure 1.1.614.0

    Uninstalled KB4338605, reboot, still high cpu.

    Uninstalled KB4338419, reboot, no high cpu issue again.

    Saturday, July 21, 2018 4:16 AM
  • 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.....


    • Proposed as answer by Terence Ngan Saturday, July 21, 2018 11:30 AM
    • Unproposed as answer by Terence Ngan Saturday, July 21, 2018 11:30 AM
    • Edited by rol801 Sunday, July 22, 2018 5:42 AM
    Saturday, July 21, 2018 8:22 AM
  • Hi, 

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

    Best Regards,

    Nafis


    Nafis Imtiaz Zaman

    Sunday, July 22, 2018 12:26 PM
  • Server 2012 R2, uninstalled KB4338605 to get back to normal CPU usage.
    • Proposed as answer by Poppabear1220 Monday, July 23, 2018 1:39 PM
    Sunday, July 22, 2018 3:43 PM
  • Is the recommendation to uninstall KB4345418 or to wait for a update to be released of Azure AD Connect
    Monday, July 23, 2018 1:53 AM
  • Hi, this helped me on Win Svr 2016. Thank you guys for your help!

    Regards

    Karel

    Monday, July 23, 2018 9:18 AM
  • Is there any definite ETA (it's been two ETA's past now)?
    Monday, July 23, 2018 9:30 AM
  • 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!
    Monday, July 23, 2018 10:01 AM
  • 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)
    Monday, July 23, 2018 10:23 AM
  • Issue comes back even after reboot, just OK for ~20 minutes, then it uses all the CPU again :(

    EDIT: I am on 819 already...

    Monday, July 23, 2018 11:33 AM
  • I've stopped the service and decided to set the starttype to manual until they've fixed this.
    • Edited by Lampiz Monday, July 23, 2018 11:55 AM
    Monday, July 23, 2018 11:53 AM
  • I just did the same!
    Monday, July 23, 2018 11:56 AM
  • #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

    Monday, July 23, 2018 12:57 PM
  • So is there an open ticket @ MS?
    Monday, July 23, 2018 1:03 PM
  • 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

    Monday, July 23, 2018 1:28 PM
  • 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

    Monday, July 23, 2018 1:30 PM
  • 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
  • KB4338419

    Thanks

Monday, July 23, 2018 1:36 PM
  • Thanks djoye! This worked for me on my 2012 R2 server!!
    • Proposed as answer by Poppabear1220 Monday, July 23, 2018 1:43 PM
    Monday, July 23, 2018 1:39 PM
  • While we still haven't seen any definitive answer on when this will be rolled out, the "Version Release History" page at https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnect-version-history makes no reference to a new version being released.  Still having to play cat and mouse game since May releases of .NET update. 


    • Edited by riveroad Monday, July 23, 2018 3:23 PM
    Monday, July 23, 2018 3:22 PM
  • On my 2008 R2 server I had the same issue, but I did not have KB4054566 to uninstall. Research showed that some machines do not show the KBs for new versions of .Net so I downloaded .Net 4.7.1, uninstalled .Net 4.7.2 and reinstalled .Net 4.7.1 and it has been working fine for days.
    Monday, July 23, 2018 6:55 PM
  • Ditto on the request for a more definitive date. "Later this week" has already turned into "early next week".

    Monday, July 23, 2018 8:21 PM
  • ZhiweiW-MSFT,

    Is there any update on when the new AadSync monitoring agent will be released?  It has now been a week since your last update. I too am running this on Server 2016 and had to uninstall KB4345418.

    Thank you.

    Monday, July 23, 2018 10:39 PM
  • Is the recommendation to uninstall KB4345418 

    If we go ahead with the uninstall, does the machine require a restart or can we restart a service instead? if so which service ?


    • Edited by DanHrv Tuesday, July 24, 2018 12:29 AM
    Tuesday, July 24, 2018 12:23 AM
  • W2K12R2 fully patched … Same issue.

    Argh !!!

    KB4103725 never on the system

    KB4096417  on the system and deleted - not fixed

    KB4095875  on the system and deleted - not fixed

    KB4054566 never on the system

    Had to kill the process.

    All KB's for 2018 - the two already removed, of which none are list in the threads herein:

    Security Update KB4338815 NT AUTHORITY\SYSTEM 7/13/2018 12:00:00 AM 
    Update KB4338419     NT AUTHORITY\SYSTEM 7/13/2018 12:00:00 AM 
    Update KB4338424     NT AUTHORITY\SYSTEM 7/11/2018 12:00:00 AM 
    Update KB4033369     NT AUTHORITY\SYSTEM 2/12/2018 12:00:00 AM 
    Update KB4054854    NT AUTHORITY\SYSTEM 2/12/2018 12:00:00 AM 
    Update KB3134813     NT AUTHORITY\SYSTEM 1/24/2018 12:00:00 AM 

    I literally had to uninstall all the July 2018 updates and I mean all of them.

    It's still spikes, but at least it does not stay there and it is no longer the Microsoft.Identity.Health.AadSync.MonitoringAgent.Startup thing.


    • Edited by DLT3 Tuesday, July 24, 2018 7:36 AM
    Tuesday, July 24, 2018 6:22 AM
  • It does require a system reboot.

    Edit: still no definitive answer/deadline from Microsoft.

    • Edited by Lampiz Tuesday, July 24, 2018 9:31 AM
    Tuesday, July 24, 2018 7:58 AM
  • I logged a support call via my Azure portal and received and updated version of AAD Connect sync (version 1.1.879.0) so I am sure it is close to being released.

    I have not tested the new client with the July updates (KB4345418 + KB4338814 on server 2016) as I had to remove this to get the CPU down, but the latest version of AAD connect sync installed fine and is syncing fine + no CPU issues, I will now need to reinstall the July updates before I can confirm if the issues is resolved
    Tuesday, July 24, 2018 9:36 AM
  • once again, on WinServer2016 too after KB4345418 …

    Is the recommendation to uninstall KB4345418? or wait for the repair Update?

    Thx, Paul


    Tuesday, July 24, 2018 10:59 AM
  • that's encouraging news, but I work for an MSP.  Yesterday i went through about 200 domain controllers for different clients, flagged the ones with pegged CPU's, disabled AAD health monitoring on ~60 of them and set services to disabled.

    I'd love to know when this is going to be released cause this is a major headache.  End users can have difficulty running applications, inability to run quickbooks in multi-user mode, slowness or inability to log into the network, etc etc etc.  I would love to have this resolved ASAP

    Tuesday, July 24, 2018 2:37 PM
  • I have a new server 2016 server and have installed a freshly downloaded copy of azure ad connect (1.1.819.0). I am having the same issue with high CPU. Once I stopped the "Azure AD Connect Health Sync Monitoring Service" everything went back to normal.

    I have not been able to find Microsoft azure ad connect 1.1.879.0 download. I can only find the 1.1.819.0 version.  I would love to find a solution as well.

    Tuesday, July 24, 2018 4:15 PM
  • Hello,

    The issue in this thread scopes within AADConnect (Sync) agent. Connect Health for ADDS was released at beginning for July that fixed high CPU issue. Please upgrade you agent to 3.1.7.0 in your domain controllers to mitigate the high CPU issue.

    Tuesday, July 24, 2018 5:25 PM
  • Hello,

    Latest version of AAD Connect will be released later this week. Uninstalling affected KB can be a temporary solution for now.

    Tuesday, July 24, 2018 5:28 PM
  • Connect Health for Sync monitoring agent will be released through AAD Connect this week.
    Tuesday, July 24, 2018 5:30 PM
  • Several Server 2008 R2 Machines 

    Uninstalling KB4338420 fixes the problem on all of them

    Thanks for sharing solutions!!

    Tuesday, July 24, 2018 6:20 PM
  • KB4054566

    Did worked! thanks.

    Tuesday, July 24, 2018 10:19 PM
  • I have installed the AAD Connect sync (version 1.1.880.0) as supplied in response to creating a support request in the Azure portal. I can confirm that the issue with Azure Active Directory Connect Health Agent for Sync version 3.0.164.0 consuming high amounts of CPU is resolved with the upgraded version of Azure Active Directory Connect Health Agent for Sync, version 3.1.7.0, as supplied with AAD Connect sync (version 1.1.880.0). The Windows Server 2016 LTSB was fully patched to the latest prior to installing this new AAD Connect sync version.
    Wednesday, July 25, 2018 6:29 AM
  • Hi,

    Where did you find it? I can only find the installer for ADFS: https://www.microsoft.com/en-us/download/details.aspx?id=48261

    Thanks.

    Florent

    EDIT Find it here : http://go.microsoft.com/fwlink/?LinkID=820540
    • Edited by Flodu31MVP Wednesday, July 25, 2018 7:13 AM
    Wednesday, July 25, 2018 7:11 AM
  • The link you added is not the Health Agent for Sync intaller but for the AD DS. I was not able to find the installer of AD connect 1.1.880 or and updated Health Agent for Sync..
    Wednesday, July 25, 2018 1:46 PM
  • The new version of Azure AD Connect can currently only be obtained through Microsoft Support.

    It will be released to the public 'soon'.

    Wednesday, July 25, 2018 8:04 PM
  • 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.

    I have this same situation, did you try removing those?
    Wednesday, July 25, 2018 9:39 PM
  • Please can you share the download link for the newest ADSync tool as a Support case for all following this topic?

    We are an MSP with a number of clients using the Sync Tool - all at 100% CPU (Variety of OS versions)

    We cannot just go round installing and uninstalling patches without discussing and explaining to the clients that MS have an issue and a fix is in the pipeline but there is no set date for release. 

    Thank you

    Thursday, July 26, 2018 8:05 AM
  • We have temporarily disabled the service rather than uninstalling any updates. What impact does this have on our environment ?
    Thursday, July 26, 2018 8:05 AM
  • <g class="gr_ gr_13 gr-alert gr_gramm gr_inline_cards gr_run_anim Style multiReplace" data-gr-id="13" id="13">Removing :</g> KB4054542  from 2012, resolved this for me.  Is there a fix for this, as <g class="gr_ gr_89 gr-alert gr_tiny gr_spell gr_inline_cards gr_run_anim ContextualSpelling multiReplace" data-gr-id="89" id="89">i</g> assume it will only come back again.

    Thursday, July 26, 2018 1:23 PM
  • Please can you share the download link for the newest ADSync tool as a Support case for all following this topic?

    We are an MSP with a number of clients using the Sync Tool - all at 100% CPU (Variety of OS versions)

    We cannot just go round installing and uninstalling patches without discussing and explaining to the clients that MS have an issue and a fix is in the pipeline but there is no set date for release. 

    Thank you

    It's less intrusive to disable the AAD connect Health Sync monitoring service for now, and re-enable it when the update to AD Sync is FINALLY rolled out.  I'm hoping to get a copy through azure portal support, we've been given dates of last week, then "later" this week, so who knows.  an actual date would be nice.
    Thursday, July 26, 2018 2:59 PM
  • Is the new release definitely coming this week?  Office 365 support seems clueless and won't provide me the updated release.  Unfortunately, I don't have Azure support or i'd go that route.  

    Thursday, July 26, 2018 3:37 PM
  • Version 1.1.880.0 has finally been released and is available here:

    http://go.microsoft.com/fwlink/?LinkId=615771

    Thursday, July 26, 2018 9:06 PM
  • Version 1.1.880.0 has finally been released and is available here:

    http://go.microsoft.com/fwlink/?LinkId=615771

    Perhaps its starting to roll out, but that GO link is just the generic AAD Connect link, which still points to May's version (819) on the 3 computers I just tried it on. you're actually reaching the 880 bits?

    If so, can you post the direct "download manually" link? for example, the old version is:

    https://download.microsoft.com/download/B/0/0/B00291D0-5A83-4DE7-86F5-980BC00DE05A/AzureADConnect.msi

    Thursday, July 26, 2018 9:27 PM
  • Version 1.1.880.0 has finally been released and is available here:

    http://go.microsoft.com/fwlink/?LinkId=615771

    Perhaps its starting to roll out, but that GO link is just the generic AAD Connect link, which still points to May's version (819) on the 3 computers I just tried it on. you're actually reaching the 880 bits?

    If so, can you post the direct "download manually" link? for example, the old version is:

    https://download.microsoft.com/download/B/0/0/B00291D0-5A83-4DE7-86F5-980BC00DE05A/AzureADConnect.msi

    So just install over the top huh?  Any idea when the auto update will push this out?  Did you test this?
    Friday, July 27, 2018 12:55 AM
  • Please look at "Date Published:" in the release notes.. 5/14/2018

    This is a "old" release, and we are already running on this version, and still see the issue.

    EDIT: That being version 1.1.819.0 you are linking to. Version 1.1.880.0 is not mentioned anywhere in the link you have provided. 
    • Edited by Anqders-B Friday, July 27, 2018 6:26 AM
    • Proposed as answer by Richar F Friday, July 27, 2018 6:49 AM
    • Unproposed as answer by Richar F Friday, July 27, 2018 6:49 AM
    Friday, July 27, 2018 6:22 AM
  • Hello all,

    here is answer for all desperate people. Download this update for MS Azure AD Connect Health agent and install. Instant CPU drop appears and everything is OK.

    I've tested it on my own server 2016

    LINK to article

    https://docs.microsoft.com/en-us/azure/active-directory/connect-health/active-directory-aadconnect-health-agent-install

    LINK to updated agent

    http://go.microsoft.com/fwlink/?LinkID=820540





    • Proposed as answer by Richar F Friday, July 27, 2018 6:52 AM
    • Edited by Richar F Friday, July 27, 2018 7:00 AM
    Friday, July 27, 2018 6:52 AM
  • I have sold the issue using diferrent aproach. 

    AD Connect Health Sync Monitor comunicates on port 5671 searching for AD Connect updates. When the communication is not possible (firewall etc.) it is falling back to port 443 HTTPS. In our case this port has been forwarded to the WWW server using NAT.

    While we enabled 5671 port in Firewall, the communication flows normally and the process is using about 5% CPU maximum

    https://support.office.com/en-us/article/office-365-urls-and-ip-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2?ui=en-US&rs=en-US&ad=US

    • Proposed as answer by christianp Friday, July 27, 2018 8:58 AM
    Friday, July 27, 2018 6:54 AM
  • Hello all,

    here is answer for all desperate people. Download this update for MS Azure AD Connect Health agent and install. Instant CPU drop appears and everything is OK.

    I've tested it on my own server 2016

    LINK to article

    https://docs.microsoft.com/en-us/azure/active-directory/connect-health/active-directory-aadconnect-health-agent-install

    LINK to updated agent

    http://go.microsoft.com/fwlink/?LinkID=820540





    Please be aware that this is only for Connect Healt AD DS, not any other product like AD FS or Sync!

    Like mentioned here:

    https://docs.microsoft.com/en-us/azure/active-directory/connect-health/active-directory-aadconnect-health-agent-install#download-and-install-the-azure-ad-connect-health-agent

    Friday, July 27, 2018 8:16 AM
  • This is how I limited Microsoft.Online.Reporting.MonitoringAgent.Startup from eating all the CPUs

    Task Manager and right click on the Microsoft.Online.Reporting.MonitoringAgent.Startup process.

    • Select "Go to details"
    • Right click on Microsoft.Identity.Health.AadSync.MonitoringAgent.Startup.exe (should be the pre-selected row)
    • Click set affinity, and uncheck "all Processors"
    • Select CPU 0
    • Your CPU usage will drop immediately (mine dropped to 32%)

    This solution will isolate the problem service to one CPU, doesn't fix the issue but seems to at least minimize the problem.
    So far I haven't had any further issues. Restarting may revert the setting (not sure).

    Hopefully Microsoft will release a update soon.




    • Edited by kaosaxis Friday, July 27, 2018 10:37 AM formating
    Friday, July 27, 2018 10:09 AM
  • Microsoft has an article on this:

    https://support.microsoft.com/en-gb/help/4346822/high-cpu-issue-in-azure-active-directory-connect-health-for-sync

    Although, uninstalling the KBs noted have been known to resolve the issue you server may be at risk.

    As I only have AAD Connect on the server (no other roles / features), uninstalling has proven an acceptable solution, especially as we have SCOM sending out floods of emails alerting of the high CPU usage.

    You can remove the hotfix using the following PS example

        $hotfixID = "4338605"
        & wusa.exe /uninstall /KB:$hotfixID /quiet /norestart

    Friday, July 27, 2018 11:12 AM
  • It's released to public but for auto upgrade only installs for now...

    1.1.880.0

    Release status

    7/20/2018: Released for auto upgrade. Release for download will follow shortly.

    https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnect-version-history#118800

    Friday, July 27, 2018 1:03 PM
  • Any way to trigger the auto-upgrade? Or if I turn the services back on any idea how long it would take before it tries to auto-upgrade? I only want to try if its rather quick... bogging down the server with 100% CPU usage for more than a few minutes isn't ideal for us.
    Friday, July 27, 2018 1:10 PM
  • @ all.

    Follow the KB

    https://support.microsoft.com/en-ae/help/4346822/high-cpu-issue-in-azure-active-directory-connect-health-for-sync.

    in my lab, I removed All general updates mentioned in kb and also .net 4.7. It resolved the issue.

    Thanks

    Farooque

    Friday, July 27, 2018 2:32 PM

  • Hello all,

    here is answer for all desperate people. Download this update for MS Azure AD Connect Health agent and install. Instant CPU drop appears and everything is OK.

    I've tested it on my own server 2016

    LINK to article

    https://docs.microsoft.com/en-us/azure/active-directory/connect-health/active-directory-aadconnect-health-agent-install

    LINK to updated agent

    http://go.microsoft.com/fwlink/?LinkID=820540





    I tested richard F direct link to updated agent. it seems to be 3.1.7.0 but i still get high cpu. also port 5671 is open for me. currently I've disabled the service, also how can I tell what version of aadconnect is installed. where can i see the current installed version number (in case I needed to disable it prior to installing 3.1.7.0 


    • Edited by chrisloup Friday, July 27, 2018 3:35 PM
    Friday, July 27, 2018 3:32 PM
  • need a bit of help here. I installed the 3.1.7.0 , should I have uninstalled Microsoft azure ad connect health agent for sync 3.0.103 first? will I lose configuration and need to reconfigure? reason, I didn't set this up 

    I still get the 99% cpu issue and have disabled the service for now.

    
    Friday, July 27, 2018 3:49 PM
  • Chris, the update isn't available for download yet. For now, just uninstall the hotfix.

    Friday, July 27, 2018 4:16 PM
  • As one asked above here, how can we trigger the auto update?

    I got some servers under my administration and I disabled the service for now (Azure AD Connect Health Sync Monitoring Service). Will the auto update still occur even when the specific service disabled? And how to trigger the auto update?

    Friday, July 27, 2018 6:57 PM
  • >>As one asked above here, how can we trigger the auto update?

    I don't think so. 


    Mike Crowley
    My Blog -- Baseline Technologies



    Friday, July 27, 2018 7:52 PM
  • Anyone have an update on this issue?

    At this point we have tried pretty much everything everyone else has with the same results. The hotfix played tricks on us. Before leaving my system hobbled for the weekend I might try that trick someone posted about forcing the services to run on one core so the CPU doesn't peg out...I can't seem to find the link and that is pushing my skills to the limit.

    Friday, July 27, 2018 8:47 PM
  • >>As one asked above here, how can we trigger the auto update?

    I don't think so. 


    Mike Crowley
    My Blog -- Baseline Technologies



    Well… of course it can be triggerd. Anything is triggerd, somewhere, sometime. But I guess that no one knows how, at this point. I would love to let it update itself through the Auto-update mechanism, then interventing it with a manual update.

    Until then, the service is disabled here.

    Saturday, July 28, 2018 6:20 AM
  • Like i posted at least 3 times.. Connect Health for AD DS is a different product then Connect Health for Sync!
    You will have to wait till an update is released for Sync..
    Monday, July 30, 2018 7:48 AM
  • I thought that Microsoft Azure AD Connect contains two sub-parts:

    • Microsoft Azure AD Connect Health agent for sync
    • Microsoft Azure AD Connect synchronization services

    And since Azure AD Connect now is updated to 1.1.880.0, the new "synchronization services" should also be there.

    https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnect-version-history

    Monday, July 30, 2018 12:05 PM
  • I thought that Microsoft Azure AD Connect contains two sub-parts:

    • Microsoft Azure AD Connect Health agent for sync
    • Microsoft Azure AD Connect synchronization services

    And since Azure AD Connect now is updated to 1.1.880.0, the new "synchronization services" should also be there.

    https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnect-version-history


    Sadly the auto upgrade is not doing anything on my side and the download is still not availible..

    1.1.880.0

    Release status

    7/20/2018: Released for auto upgrade. Release for download will follow shortly.


    Monday, July 30, 2018 12:53 PM
  • Yes but the update is not available for download yet, as per your link: 7/20/2018: Released for auto upgrade. Release for download will follow shortly.

    I am on an old version that doesn't have auto update so relying on the download version. Never had a reason to upgrade until this bug I guess. Others I think were wanting to download it since the auto update wasn't pushing it out yet.

    Monday, July 30, 2018 12:54 PM
  • I'm on 1.1.819.0 here at several customers, but no auto-update occurring here.
    Monday, July 30, 2018 2:16 PM
  • 2012R2:

    I am having the same issue.  However, I did not install KB4054566.  I installed the following yesterday and "microsoft.online.reporting.monitoringagent.startup" is hogging my CPU:

    KB4338815, KB4340558, KB4338831, KB890830

    Restart of Azure AD Connect services has helped for about 10 minutes.  As I type this, the "microsoft.online.reporting.monitoringagent.startup" process went up to 80%.  Not cool.



    • Edited by HavNHavNot Monday, July 30, 2018 7:14 PM
    Monday, July 30, 2018 7:12 PM
  • Same here, auto-upgrade enabled but still waiting around.

    Is there seriously no way to kick the process off manually? Or at least post the new version for download, Microsoft?  Jeez.

    Tuesday, July 31, 2018 1:38 PM
  • Same here, auto-upgrade enabled but still waiting around.

    Is there seriously no way to kick the process off manually? Or at least post the new version for download, Microsoft?  Jeez.


    Same issue, not getting the update automatically. a force autoupdate parameter would help, or MS should post the download link in the same time.
    • Proposed as answer by Paul_365('') Tuesday, July 31, 2018 6:22 PM
    • Unproposed as answer by Paul_365('') Tuesday, July 31, 2018 6:22 PM
    Tuesday, July 31, 2018 2:55 PM
  • Automatic upgrade is enabled by default for the following:

    • Express settings installation and DirSync upgrades.
    • Using SQL Express LocalDB, which is what Express settings always use. DirSync with SQL Express also use LocalDB.
    • The AD account is the default MSOL_ account created by Express settings and DirSync.
    • Have less than 100,000 objects in the metaverse.

    From : https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnect-feature-automatic-upgrade

    Tuesday, July 31, 2018 6:23 PM
  • Right, thanks. The question is how can you force an autoupgrade check? Ours is enabled and has been since the update was released but the system hasn't even attempted to upgrade (we know this by reviewing event logs, nothing is logged about an upgrade attempt).

    We need to be able to force the upgrade check or they need to release it for download.

    Tuesday, July 31, 2018 6:33 PM

  • We had auto update disabled, I turned it on, we were a few versions behind, but it has still only upgraded to 1.1.819.0, so I don't think it has been pushed out to auto-upgrade, I believe auto upgrade also checks every 6 hours.
    Wednesday, August 1, 2018 9:38 AM
  • I see the same behavior on the environments from our customers, I just had an exchange with MS Support and they told me the following:

    Thank you for your email.

    The update will push thru 2-3 weeks from now according with our Next Level Team.

    Thanks,

    Cid

    O365 Support Engineer


    Wednesday, August 1, 2018 10:47 AM
  • What are you seeing that point to a check every 6 hours? From what I see using event log filters for IDs between 300-399, from even source "Azure AD Connect Upgrade" it hasn't checked for an upgrade in a week plus.

    Review the troubleshooting section.

    https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnect-feature-automatic-upgrade

    • Edited by PhilipAM Wednesday, August 1, 2018 12:28 PM
    Wednesday, August 1, 2018 12:24 PM
  • It was on an article, maybe this one http://www.enowsoftware.com/solutions-engine/understanding-auto-upgrade-options-in-azure-ad-connect

    Maybe if you disable the auto-update and enable it again it forces it to check? As soon as I enabled it, ours updated straight away, but still only to 1.1.819.0 as mentioned.

    Wednesday, August 1, 2018 1:25 PM
  • Could it be that the new version hasn't been added in the AutoUpgrade channel yet?
    Thursday, August 2, 2018 9:26 AM
  • Hey! Installing the new version of Azure AD Connect (released Aug 1st, 2018) seems to resolve the problem.

    Here is the link to download the most recent version:

    https://www.microsoft.com/en-us/download/details.aspx?id=47594

    The processes is straight forward and will just upgrade the current version installed in the system. No need to reconfigure anything, besides entering the Azure Global Admin account.

    Hope it helps



    • Edited by André Morata Thursday, August 2, 2018 11:04 AM
    • Proposed as answer by neilmyers Thursday, August 2, 2018 1:28 PM
    Thursday, August 2, 2018 11:03 AM
  • Hi,

    The download is available now https://www.microsoft.com/en-us/download/details.aspx?id=47594

    I installed the new version and the Windows updates and I can confirm that the issues was solved for Windows Server 2012 R2

    Cheers

    Thursday, August 2, 2018 12:14 PM
  • Hey! Installing the new version of Azure AD Connect (released Aug 1st, 2018) seems to resolve the problem.

    Here is the link to download the most recent version:

    https://www.microsoft.com/en-us/download/details.aspx?id=47594

    The processes is straight forward and will just upgrade the current version installed in the system. No need to reconfigure anything, besides entering the Azure Global Admin account.

    Hope it helps



    That seems to have done the trick. I had to End task on several instances of Microsoft.Identity.Health.AadSync.* to get the upgrade to run otherwise the installer would end saying that the system was not modified.
    Thursday, August 2, 2018 2:22 PM
  • According to TeckLyfe, version 1.1.880.0 was released on 8/1/2018. Microsoft Download Page. So far so good.
    Thursday, August 2, 2018 3:09 PM
  • The new release is available now: https://www.microsoft.com/en-us/download/details.aspx?id=47594

    Linked from AAD Connect release note https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnect-version-history

    The issue is mitigated and resolved in the new release. Please apply the uninstalled KB if needed.

    Thanks,

    Zhiwei

    • Proposed as answer by ZhiweiW-MSFT Thursday, August 2, 2018 6:28 PM
    Thursday, August 2, 2018 6:28 PM
  • That does appear to be the correct version, despite the version notes still saying it's not available for download.  I'm going to try it and see if it fixes this issue.

    Thursday, August 2, 2018 6:49 PM
  • hi,

    thank you for help I upgrade AD connect to the new version and it's resolve my issue.

    Thanks again,

    Preyash Parekh

    Friday, August 3, 2018 8:32 AM
  • This worked as fix for me on 2 servers thanks!
    Friday, August 3, 2018 11:45 AM
  • I installed the patch from https://www.microsoft.com/en-us/download/details.aspx?id=47594. It updated the main sync engine files (those in "C:\Program Files\Microsoft Azure Active Directory Connect") but didn't touch the monitoring files in "C:\Program Files\Microsoft Azure AD Connect Health Sync Agent".

    The AzureADConnectHealthSyncMonitor continues to suck up all available CPU. The patch does not fix this problem.

    This is on Server 2012 R2, BTW. It has KB4096417 installed. I'll try uninstalling it to see if that helps.

    Thanks,

        Eric

    Friday, August 3, 2018 5:46 PM
  • how do i get past this, I am seeing it on 2 systems.

    

    Friday, August 3, 2018 7:56 PM
  • I installed the patch from https://www.microsoft.com/en-us/download/details.aspx?id=47594. It updated the main sync engine files (those in "C:\Program Files\Microsoft Azure Active Directory Connect") but didn't touch the monitoring files in "C:\Program Files\Microsoft Azure AD Connect Health Sync Agent".

    The AzureADConnectHealthSyncMonitor continues to suck up all available CPU. The patch does not fix this problem.

    This is on Server 2012 R2, BTW. It has KB4096417 installed. I'll try uninstalling it to see if that helps.

    Thanks,

        Eric

    Same issue here, the new version didn't help and it didn't update the problem service.  According to the release notes, it should have updated the health agent too https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnect-version-history

    EDIT: Ran the install\repair and this time it worked.  Problem before was, I stopped at the password prompt, I guess when the password prompt appears, you need to enter your credentials to continue the installation.



    • Edited by saleaway Saturday, August 4, 2018 1:55 PM
    • Proposed as answer by MAX28HST Saturday, August 4, 2018 2:35 PM
    • Unproposed as answer by MAX28HST Saturday, August 4, 2018 2:35 PM
    • Proposed as answer by Eric Kool-Brown Wednesday, August 8, 2018 8:37 PM
    Saturday, August 4, 2018 1:37 PM
  • Version 1.1.880.0 worked this AM! CPU Util 2%.... 

    THANKS!

    Saturday, August 4, 2018 2:37 PM
  • Hi Zhiwei,

    After installing the latest version of the AAD Connect software, the Azure AD Health Manager for sync remains the old version.
    Is it possible to do a manual installation?

    Re-running/repairing the installation didn't forced the software to update to the latest version.

    Please help.

    Sunday, August 5, 2018 7:57 PM
  • Version 1.1.880.0 worked this AM! CPU Util 2%.... 

    THANKS!

    Worked for me too.  CPU is low and holding steady
    Monday, August 6, 2018 6:01 PM
  • Our AutoUpgrade was set to Suspended. I've switched it to Enabled, is it then a matter of time and just waiting around for it to upgrade itself ?
    Tuesday, August 7, 2018 2:07 AM
  • I upgraded AAD Connect to 1.1.880.0. After the upgrade i installed back kb4345418. Everything is normal, no high cpu usage since
    Tuesday, August 7, 2018 8:56 AM
  • I downloaded and installed 1.1.880.0, it runs through an upgrade wizard requiring an o365/azure admin and then your domain admin.   my cpu is now is between 1% and 10% (has been for 4 hours).  I did not remove any KB's.  We are running server 2016 64bit.  Over very easy and less than 10 minutes to install and reboot.

    Tuesday, August 7, 2018 7:23 PM
  • Silly me, I didn't realize that I needed to go through the AADC configuration wizard to complete the update. Not the most user-friendly design...

    At any rate, completing the update via the config wizard did indeed solve the high-CPU-consumption problem.

    The problem with having to wear many hats is that some don't fit properly.

    BTW, a full import was triggered after the update. I thought the metaverse would be preserved but something in the update must have invalidated it.
    Wednesday, August 8, 2018 8:40 PM
  • following update to v1.1.880.0 the service AzureADConnectHealthSyncMonitor fails to start and on investigation can't open "C:\Program Files\Microsoft Azure AD Connect Health Sync Agent\Monitor" folder due to an access denied error.

    can't even takeown of the Monitor folder.

    has anyone hit this issue since updating to new version?


    Thursday, August 9, 2018 10:19 AM
  • Removing KB4338814 fixed it for me.(win 2016 server)

    Is there any way to force the auto-update to run for the Azure AD connect? Mine is enabled but didn't auto update yet to 1.1.880.0

    Thursday, August 9, 2018 5:29 PM
  • following a reboot now got a empty "C:\Program Files\Microsoft Azure AD Connect Health Sync Agent\Monitor" folder but still the service exists so I guess the installer is meant to bin the AzureADConnectHealthSyncMonitor service? I have disabled the AzureADConnectHealthSyncMonitor service for now.
    Friday, August 10, 2018 7:54 AM
  • I'm wondering if anyone has experienced something similar but using the Microsoft Online Services Sign-In Assistant (MSOIDSVC.exe) https://www.microsoft.com/en-us/download/details.aspx?id=28177 along with the Azure AD component installed http://go.microsoft.com/fwlink/p/?linkid=236297. The two seem similar to each other however the one we're using is a bit older. My server hosting a website (running .net 4.6) in Azure has experienced the same CPU spike patterns noted by many here. Since the KB4345418 and KB4338814 updates (and other various windows updates) were applied to our machines on July 27th we've had the slow climb of CPU spikes until it stays at 100% occuring under IIS. Nothing has changed about the website but these updates were applied and seem to be wreaking havoc. Don't want to remove these updates if they're not really the cause of this behavior however.


    Monday, August 13, 2018 9:06 PM
  • So the new release 1.1.880 fixes it?

    No update on this article

    https://support.microsoft.com/en-us/help/4346822/high-cpu-issue-in-azure-active-directory-connect-health-for-sync

    We will install AD Connect for the first time tomorrow on Win2016 + 4.7.2


    <h3>Regards Stephan</h3>

    Tuesday, August 14, 2018 6:00 AM
  • I have not had the High CPU after updating to the new version 1.1.880
    Tuesday, August 14, 2018 5:08 PM
  • Are you running Azure AD Connect on a domain controller? I have installed the latest upgrade on several servers and I have found that when I install it on a domain controller, it fails to upgrade the Azure AD Connect Health Sync Agent. I uninstalled the Health Sync Agent, but couldn't delete the Monitor folder until I rebooted the DC. I'm not running the Health Sync Agent on several DCs at the moment. I think the only way to fix the problem is to completely remove and reinstall Azure AD Connect.

    I have not had this problem when upgrading Azure AD Connect on member servers. The Health Sync Agent gets updated to 3.1.7.0 and all is good.

    Friday, August 17, 2018 12:42 AM
  • Same issue this morning.  Uninstalled KB4338420, Server 2008 R2's version of the .NET update, and all back to normal.
    This helped on Server 2008 R2!
    Friday, August 17, 2018 8:27 PM
  • Thank you

    I have removed the last .NET-updates too on 2008 R2 and server is working well...

    Monday, August 20, 2018 2:08 PM
  • This is resolved if you upgrade to the latest version of Azure AD Connect (1.1.880.0).  It's specifically fixes

    Fixed issues

    • Fixed a bug where the AAD Connect server would show high CPU usage after upgrading to .Net 4.7.2

    I'm on WS2016 (DC) with AADConnect and for some reason it hadn't auto-upgraded.

    https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnect-version-history

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

    • Proposed as answer by BS1010 Tuesday, September 4, 2018 7:06 AM
    Tuesday, August 21, 2018 1:18 PM
  • On the weekend we had update to new version 1.1.880 and it was necessary three reboots for solved CPU issue. Also, the server updated to August patches and work perfectly today. Thank you for share this information, it was usefully.


    • Edited by Erwinls Tuesday, August 21, 2018 3:20 PM
    Tuesday, August 21, 2018 3:18 PM
  • Desinstalé el parche indicado KB4054566 y al principio parecía que el consumo de CPU se había normalizado pero pasado unos minutos volvió a utilizar el 99% de la CPU.

    Realicé un par de reinicios pero no soluciono el problema

    Friday, August 24, 2018 9:58 AM
  • 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

    None of these worked for me, however, on another forum I found out that MS released an updated version of Azure AD Connect Sync Monitor that specifically resolves this issue. Download is here: https://www.microsoft.com/en-us/download/details.aspx?id=47594. My PDC had v1.1.649.0 installed, this newer version (as of this post) is v1.1.880.0. Once the upgrade went through (took me almost 2 hours so give yourself time), restarted and the CPU spike went away.
    Friday, August 24, 2018 4:44 PM
  • This is resolved if you upgrade to the latest version of Azure AD Connect (1.1.880.0).  It's specifically fixes

    Fixed issues

    • Fixed a bug where the AAD Connect server would show high CPU usage after upgrading to .Net 4.7.2

    I'm on WS2016 (DC) with AADConnect and for some reason it hadn't auto-upgraded.

    https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnect-version-history

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

    I finished the upgrade of Microsoft Azure Active Directory Connect to version 1.1.880.0, with no need for any reboot.
    About 1 hour ago and the CPU consumption is normal, problem solved
    • Proposed as answer by autopole Wednesday, August 29, 2018 8:26 AM
    Friday, August 24, 2018 5:12 PM
  • How can I mannually upgrade my AAD Connect ?
    I can't find the aad version 
    Wednesday, September 5, 2018 5:47 PM
  • How can I mannually upgrade my AAD Connect ?
    I can't find the aad version 

    Hi,

    just download the actual Version from https://www.microsoft.com/en-us/download/details.aspx?id=47594.

    Oliver.

    Friday, October 26, 2018 10:06 AM
  • the latest updates does not fix it for me. I have all the versions suggested and after a week or two the service is still consuming 99%cpu and 99% mem. 

    http://puu.sh/BT655/d4764d0e2f.png

    This is Server 2016 standard.

    Tuesday, October 30, 2018 12:06 AM
  • Hi all,

    latest update also doesn't fix it permanently for me.

    OS: Windows 2008 R2
    AADConnect.exe: from 1.1.614 to 1.1.882
    Microsoft.Online.Reporting.MonitoringAgent.dll: from 1.1.30.32 to 1.1.30.42
    .NET Framework: 4.7.2

    26.10.18: Update installed, first it seems to be solved, cause after restarting the service CPU looks fine.
    31.10.18: CPU increases again
    02.11.18: Service "Azure AD Connect Health Sync Monitoring Service" restarted, CPU goes normal

    I think will switch back to previous solution in disabling Azure AD Connect Health Sync Monitoring Service cause this helps me in the past.
    I do not want to mess around with uninstalling this and that, I simply do not have the time for that :-(
    Interesting to see, that a newer OS still has that problem too.

    @Microsoft: Please provide a reliable solution for us!

    Oliver.



    • Edited by Oliver Geissler Friday, November 2, 2018 10:04 AM
    • Proposed as answer by Oliver Geissler Friday, November 2, 2018 11:39 AM
    • Unproposed as answer by