Hello! If you are reading this I assume you are having a problem with CPU usage on your Microsoft Azure Active Directory Connect Server. This fix goes over the problem with Server 2016, but I’m sure this will point you in the right direction if you are using another server version. This fix should cover Server 2012r2, Server 2012, and Server 2008r2.
If your Windows 2016 server running Microsoft Azure Active Directory Connect has high CPU usage, check to see if the service Microsoft.Online.Reporting.MonitoringAgent.Startup is causing the high CPU usage. If so (which I assume it is for the majority of people running these two pieces of software in conjunction), the problem is due to updates to .NET framework 4.7 not working well with that service. There is a fix. Some people will find that Microsoft Azure Active Directory Connect will update itself and fix this issue (which it will, someday), but if you’re not willing to wait until your name is drawn from the hat, you can force this to happen.
You may find other articles reference uninstalling KB’s that made the changes to .Net framework, but not so fast. This is a “work around” and not a “fix” to the issue. Removing KB’s is not the answer, patching Azure Active Directory Connect is.
Download AADC version 1.1.880 from https://www.microsoft.com/en-us/download/details.aspx?id=47594
After downloading, run the installer. After installation is complete, launch AADC to “update” the components needed. You should see a screen like this:
You must provide an account that is an Enterprise Admin in your local domain, as well as an account that is a Global Administrator in your Azure tenant.
You may have to reboot your server 2x to get the CPU to calm down, but I took me zero reboots before I noticed the fix working, but I’d reboot anyways. If the fix worked, you will now see:
Please use the comments below to ask any questions or provide me with updates to the problem.