OMS – Service Map Solution – Unsigned Driver Windows Server 2016


Hi,

A new Service Map solution got released for OMS lately (until now 25/11/2016 only available in US region) :
https://docs.microsoft.com/en-us/azure/operations-management/-suite/operations-management-suite-service-map

The solution requires an additional service to be installed as documented over here:
https://docs.microsoft.com/en-us/azure/operations-management-suite/operations-management-suite-service-map-configure

This image gives you more insight on how the “Microsoft Dependency Agent” works together with the “MMA/OMS Agent”

agents

 

When trying to install the “Microsoft Dependency Agent” on Windows Server 2016, I noticed following error:
oms_service_map_driver

And when looking at my OMS workspace, I noticed that there wasn’t any data available for the server (RRAS):
oms_service_map_nodata

These 2 drivers are used:

  • Driver path=”C:\Windows\system32\drivers\depagent.sys”
  • Driver path=”C:\Windows\system32\drivers\mdaafd.sys”

When I look at the Details of the drivers, I see that the depagent.sys isn’t signed: (mdaafd.sys is signed)
drivers

As a workaround, I disabled “Driver Signature Enforcement” as documented over here:
https://support.microsoft.com/en-us/help/17419/windows-7-advanced-startup-options-safe-mode
oms_service_map_boot

Disabling Secure Boot (https://msdn.microsoft.com/en-us/library/windows/desktop/hh848062(v=vs.85).aspx) would resolve the issue as well. But probably not recommended.

When looking at my OMS workspace I now saw data appearing for the server (RRAS):
oms_service_map_data

The solution is just awesome and will give you insight in you monitored environment.

*UPDATE* (30/11/2016) The OMS team is aware of the problem and they are working with the internal signing team to get things right in the next build.

 

Comments (0)

Skip to main content