Answered by:
Azure AD Connect Health Sync Monitor High CPU Usage

-
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!
- Moved by AshokPeddakotla-MSFTMicrosoft employee, Moderator Tuesday, June 5, 2018 11:52 AM Better suited here : moved from CS
Question
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
KB40545662012R2
I uninstalled KB4054566 (the others were not installed) and the issue appears to have gone away.
KB4054566 is .NET 4.7.2Andrew
- Proposed as answer by mmccollum2 Sunday, June 10, 2018 11:01 PM
- Marked as answer by T3chGuy007 Saturday, June 16, 2018 6:44 PM
All replies
-
-
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
-
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
-
-
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
KB40545662012R2
I uninstalled KB4054566 (the others were not installed) and the issue appears to have gone away.
KB4054566 is .NET 4.7.2Andrew
- Proposed as answer by mmccollum2 Sunday, June 10, 2018 11:01 PM
- Marked as answer by T3chGuy007 Saturday, June 16, 2018 6:44 PM
-
-
-
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
-
-
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.
-
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.
-
-
-
-
@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
- Edited by BulletproofJohn Friday, June 22, 2018 10:39 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
-
@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
- Edited by andyoakeley Sunday, June 24, 2018 1:23 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.
- Edited by BulletproofJohn 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- Proposed as answer by ZhiweiW-MSFT Friday, June 29, 2018 8:46 PM
- Edited by ZhiweiW-MSFT Friday, June 29, 2018 8:47 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.
- Edited by PieterPretorius Wednesday, July 11, 2018 3:50 AM
-
-
-
-
-
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
-
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
-
-
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.
-
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
-
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
-
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.
-
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
-
Same issue this morning. Uninstalled KB4338420, Server 2008 R2's version of the .NET update, and all back to normal.
- Proposed as answer by DavidGRobinson Friday, July 13, 2018 6:57 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
-
-
-
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:
had to uninstall KB 4338613 & KB 4338605
And same for KB 4340558 as per this
had to uninstall 4338424
- Edited by scerazy Monday, July 23, 2018 9:38 AM
-
-
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
-
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." ?
-
-
-
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
-
-
-
-
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- Edited by Júnior Sávio Friday, July 13, 2018 1:28 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
-
-
-
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.
-
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
-
-
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.
-
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.
-
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. :(
-
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
-
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.
-
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.
-
-
-
-
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
- Edited by Erwin26 Tuesday, July 17, 2018 12:47 PM
- Merged by SadiqhAhmed-MSFTMicrosoft employee, Moderator Thursday, July 19, 2018 6:52 PM Similar query
-
-
-
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
-
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
-
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.
-
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.
-
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
-
Microsoft is working on the new agent release. We have an update of the status.
-
Microsoft is working on the new agent release. We have an update of the status.
-
Microsoft is working on the new agent release. We have an update of the status.
-
Microsoft is working on the new agent release. We have an update of the status.
-
-
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.
-
-
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
- Edited by Péter Meszaros Wednesday, July 18, 2018 4:58 PM
- Proposed as answer by JustAnotherSupportPerson Monday, July 23, 2018 10:43 PM
-
-
-
-
Any status update, can we expect a patch today before COB?
- Edited by Eric S. Periard 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
-
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.
-
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
-
I have the same issue:
Server 2012 Standard
Azure AD Connect 1.1.819None 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 -
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
-
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
-
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
-
-
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
-
-
Server 2012 R2, uninstalled KB4338605 to get back to normal CPU usage.
- Proposed as answer by Poppabear1220 Monday, July 23, 2018 1:39 PM
-
-
-
-
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!- Edited by David.Schmidt.88 Monday, July 23, 2018 10:20 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...
- Edited by David.Schmidt.88 Monday, July 23, 2018 11:38 AM
-
-
-
-
-
-
-
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
-
Thanks djoye! This worked for me on my 2012 R2 server!!
- Proposed as answer by Poppabear1220 Monday, July 23, 2018 1:43 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
-
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.
-
-
-
-
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 AMI 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
-
-
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 -
-
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
-
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.
-
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.
-
-
-
-
-
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.
-
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
-
-
-
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.
-
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
-
-
<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.
-
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
-
-
-
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
- Edited by Mike Crowley Thursday, July 26, 2018 9:29 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
-
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. -
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
LINK to updated agent
http://go.microsoft.com/fwlink/?LinkID=820540
-
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
-
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
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
- Edited by TheUntouchable Friday, July 27, 2018 8:42 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
-
Microsoft has an article on this:
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
-
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
-
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.
-
@ 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
- Proposed as answer by Farooque Arian Friday, July 27, 2018 2:33 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
LINK to updated agent
http://go.microsoft.com/fwlink/?LinkID=820540
- Edited by chrisloup Friday, July 27, 2018 3:35 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.
-
Chris, the update isn't available for download yet. For now, just uninstall the hotfix.
- Edited by Mike Crowley 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?
- Edited by Peter van de Beek Friday, July 27, 2018 7:01 PM
-
>>As one asked above here, how can we trigger the auto update?
I don't think so.
Mike Crowley
My Blog -- Baseline Technologies
- Edited by Mike Crowley Friday, July 27, 2018 8:11 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.
-
>>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.
-
-
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
-
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.
-
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.
-
-
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
-
-
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
-
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
-
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.
-
-
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
-
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
-
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.
-
Update now available for manual download also https://dirteam.com/sander/2018/07/30/azure-ad-connect-version-1-1-880-0-is-now-available/
-
-
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
-
-
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
-
According to TeckLyfe, version 1.1.880.0 was released on 8/1/2018. Microsoft Download Page. So far so good.
-
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
-
-
-
-
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
-
-
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
-
-
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.
-
-
-
I upgraded AAD Connect to 1.1.880.0. After the upgrade i installed back kb4345418. Everything is normal, no high cpu usage since
- Proposed as answer by Péter Meszaros Tuesday, August 7, 2018 11:30 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.
-
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.- Edited by Eric Kool-Brown Wednesday, August 8, 2018 11:35 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?
-
-
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.
-
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.
- Edited by Trevor Jacobson Monday, August 13, 2018 9:29 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>
-
-
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.
-
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!
- Proposed as answer by Benkelberg, Rainer Monday, August 20, 2018 2:03 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
-
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
-
-
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
KB40545662012R2
I uninstalled KB4054566 (the others were not installed) and the issue appears to have gone away.
KB4054566 is .NET 4.7.2
Andrew
-
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
About 1 hour ago and the CPU consumption is normal, problem solved- Proposed as answer by autopole Wednesday, August 29, 2018 8:26 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.226.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 normalI 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 Oliver Geissler Friday, November 2, 2018 11:39 AM