This week I encountered a rather strange issue with the AD Assessment solution within OMS. The OMS agent installation went fine, and we were able to collect events, security and auditing and performance data but as you can see here the AD Assessment solution wasn’t working:
I first verified that all the requirements for the solution were met:
- Agents must be installed on domain controllers that are members of the domain to be evaluated.
- The Active Directory Assessment solution requires .NET Framework 4 installed on each computer that has an OMS agent.
- Add the Active Directory Assessment solution to your OMS workspace using the process described in Add Log Analytics solutions from the Solutions Gallery. There is no further configuration required.
I also verified that the AdvisorAssessment.exe file was added to servers with agents.
In OMS I ran the following query to confirm my domain controllers were meeting the requirements:
Type=Operation and Solution=ADAssessment | sort OperationStatus
Of course I had already cleared the health service cache and restarted the Monitoring Agent service several times, and forced the AD Assessment to run again by deleting the LastExecuted registry key since normally it runs only every 7 days:
HKLM\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\Management Groups<Your MG Name Here>\Solutions\ADAssessment
When you remove that key and restart the health service the OMS agent will think that the AD Assessment has never run and will force it to run again.
That’s when I discovered the following error in the OperationsManager log:
After analyzing the error several times the first thing that came into my mind was a .Net compilation error. But .Net Framework 4 was installed right? So this could not be the issue?
Just to be 100% sure, I verified which version of .Net was installed. It was indeed Framework 4 but the Client Profile version:
This customer had a requirement to still use.Net Framework 4.0 which is not recommended as it’s end of life and not supported anymore by Microsoft. Please ensure you are using the latest version if you can.
I deleted the registry key to force the AD Assessment to run again, restarted the Monitoring agent and couple of minutes later AD Assessment data started to show up in OMS:
So be careful which version of .Net you are installing. It needs to be the full version of .Net.
Starting with the .NET Framework 4.5, the Client Profile has been discontinued and only the full redistributable package is available. Optimizations provided by the .NET Framework 4.5, such as smaller download size and faster deployment, have eliminated the need for a separate deployment package. The single redistributable streamlines the installation process and simplifies your app’s deployment options.
Hope this helps,