A question about an APM issue in the OMS agent deployed from Azure.
My customer has Azure Virtual Machines that hosts Microsoft Identity Manager 2016 SP1 (MIM). One of the MIM components, MIM Portal, rely on SharePoint 2013. This customer also uses System Center Operations Manager (SCOM) and deployes their SCOM Agents using the "OMS virtual machine extension for Windows" (https://docs.microsoft.com/en-us/azure/virtual-machines/windows/extensions-oms).
Problem description:
The current version of the "OMS virtual machine agent extension for Windows" breaks SharePoint 2013 resulting in a “Page cannot be displayed” error. The root cause seems to be related to an issue reported in this Microsoft blog post: https://blogs.technet.microsoft.com/momteam/2017/03/21/apm-feature-in-scom-2016-agent-may-cause-a-cr.... A follow up post describes a work-arround for this issue as Microsoft is still working on a final solution: https://blogs.technet.microsoft.com/momteam/2017/06/06/update-on-apm-fix-for-agent-crashing-issue-sh.... The work-around is reinstalling the agent with a NOAPM command-line switch.
The work-around described above is not a solution for the long term because the agent is updated by Microsoft Azure without user input involved. The default installation and update enables the APM option again, resulting in outage of this platform. The preferred solution is making sure that VMs can be equipped with the “OMS virtual machine agent extension for Windows” with the NOAPM switch enabled. Current documentation on the Microsoft site does not describe an option to do so. (https://docs.microsoft.com/en-us/azure/virtual-machines/windows/extensions-oms). Is there a way to achieve this?
