I’ve decided to make you a Christmas present and developed a S2D solution for OMS.
I’ve been dealing with this issues since the release of R2 and now there is a hotfix for that. Seems that was a bug on Windows Server 2012 R2 side. You can read the full details Kevin Holman’s blog (the one and only).
If you’ve already installed SCOM 2012 R2 you’ve probably noticed that System Center Management Service is gone. Now we have Microsoft Monitoring Agent:
But that is not all folder location is also changed:
You will notice the change also in the Control Panel:
We already know that changes are not only in the name now but the service can actually can be leveraged by other products. Could we see in the future this agent be leverage by other products as well? May be something like Windows Azure Monitoring (WAM) or Windows Azure Operations Manager (WAOM)? We can only speculate for now and wait to see what will happen.
Note 1: This is not the first time the name of the service is changes in 2005 it was MOM, in 2007 RTM/SP1 it was OpsMgr Health Service and in 2007 R2, 2012 and 2012 SP1 it was System Center Management Service.
Note 2: The built-in agent in Service Manager 2012 R2 is also renamed to Microsoft Monitoring Agent in services.msc and Control Panel so if you need to restart Service Manager 2012 R2 health service you have to restart Microsoft Monitoring Agent. The installation folder of the agent is where Service Manager is installed.