Previously on Microsoft Azure Operational Insights Preview Series:
- Microsoft Azure Operational Insights Preview Series – System Update Assessment (Part 1)
- Microsoft Azure Operational Insights Preview Series – Malware Assessment (Part 2)
- Microsoft Azure Operational Insights Preview Series – Log Management (Part 3)
- Microsoft Azure Operational Insights Preview Series – Capacity Planning (Part 4)
- Microsoft Azure Operational Insights Preview Series – Change Tracking (Part 5)
- Microsoft Azure Operational Insights Preview Series – Time Matters in Dashboard (Part 6)
- Microsoft Azure Operational Insights Preview Series – SQL Assessment (Part 7)
- Microsoft Azure Operational Insights Preview Series – Connecting Directly with Microsoft Monitoring Agent (Part 8)
- Microsoft Azure Operational Insights Preview Series – Alert Management (Part 9)
- Microsoft Azure Operational Insights Preview Series – The Azure Portal Experience (Part 10)
- Microsoft Azure Operational Insights Preview Series – Usability Improvements (Part 11)
There is a new Intelligence Pack on the horizon. This IP uses the same model for information like the SQL Assessment IP. You can just go Intelligence Pack Gallery and add it:
After adding it you will need to wait up to 4 hours until you see some results:
As far as I understand you do not need special accounts to make it work. You may need to bounce the SCOM agent on the domain controllers to make it work according to Daniele Grandini, Tao Yang and Cameron Fuller.
After those 4 hours you should start see that tile filled with information:
Digging into it it has the same look and feel like SQL Assessment IP.:
Let’s see how a recommendation looks like:
Clicking on one of the affected objects goes to Search:
As this IP follows the same structure as the SQL Assessment one you can use similar or the same queries to find the information you need.
And btw after adding it we’ve found a real world problem by the recommendations from AD Assessment IP. This is a very nice addition to the Azure Operational Insights service.
I also found DC’s on 2008 R2 SP1 needed Windows Management Framework 3 or 4 (for PowerShell). Then bumping the SCOM agent got them reporting.
Yes,
Assessment IPs require framework 4 – http://blogs.technet.com/b/momteam/archive/2014/05/29/advisor-error-3000-unable-to-register-to-the-advisor-service-amp-onboarding-troubleshooting-steps.aspx
https://www.opinsights.azure.com/FAQ