I encountered this error when attempting to configure SCOM monitoring of a Service Manager server.
For those that may not be aware, you cannot push a SCOM Agent through the SCOM console onto a system the is running System Center Service Manager. Why is that? Well, because Service Manager is built on top of SCOM. What that means, is that they use a lot of the same code base. And, if you have ever installed SCOM, you will know that you can’t install a SCOM Agent onto the SCOM Management Server, it’s self-monitoring.
However, since Service Manager is a separate component of the System Center product (as Microsoft labels “System Center” as a single product, and each application/tool as separate “components” of that product), Microsoft has included a “Microsoft Monitoring Agent” with the installation of Service Manager.
When you install Service Manager, the Microsoft Monitoring Agent is automatically installed with it. If you navigate to Control Panel > System and Security, you will see an entry for the Microsoft Monitoring Agent.
When you click on the item, it will open the Microsoft Monitoring Agent Properties dialog.
Now, normally you could just click Add, and then enter the required information. However, when I attempted to do so, I encountered the following error:
“The Management Group configuration could not be saved.”
I also received a notice show: “IDS_DLG_STOPPINGMANAGEMENTSERVICE, IDS_DLG_STARTINGMANAGEMENTSERVICE”.
The issue is because the Management Group details is already added, even though they don’t appear in the Microsoft Monitoring Agent Properties.
To correct this issue, open Registry Editor and navigate to: HKLM\System\CurrentControlSet\Services\HealthService\Parameters\Management Groups
You will notice that that there will be an entry for the Management Group, even though it doesn’t show up in the Control Panel Applet.
So, you will need to delete this entry, and then restart the Health Service. Open Services, find the Microsoft Monitoring Agent, right-click and choose Restart.
NOTE: In System Center 2012 R2 Operations Manager, the SCOM Agent is renamed as “Microsoft Monitoring Agent”. In System Center 2012 and SP1, it is still labelled as “System Center Management Service”.
After you restart the service, you should be able to successfully add the Management Group in the Control Panel Applet, and be able to successfully monitor Service Manager systems with Operations Manager.
MiCloud 