Guidance for customers using the Microsoft Operations Manager agent for on-premises end points

With the recent release of the new OMS Microsoft Monitoring Agent (MMA) for Windows that allows multi-homing support, we’ve been getting a few questions about the approach and guidance that we have for customers using the regular Operations Manager agent for their on-premises end points. For example, take the case of the Operations Manager customer who is on OpsMgr 2012 R2 UR9 and has those agents reporting into an OMS workspace. The agent that came with OpsMgr is not able to do OMS workspace multi-homing so what can they do to enable this functionality?

For these customers, we would suggest that they consider not using the agent that comes with OpsMgr and start using the MMA from Microsoft Update instead. The current MMA version is backwards compatible and supported with all OpsMgr 2012 R2 management groups.

Note that the update on MU will only upgrade the previous version released for OMS (currently 7.2.10375.0) and it will not show up for OpsMgr 2012 R2 agent versions.  Those will remain on the Update Rollup cadence. This means that if you want to switch from the OpsMgr 2012 R2 version of the agent you will need to use your standard software distribution mechanism to push it out. For example:


For more information regarding the various agent installation options, please see

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group