Monitoring SCSM 2012 Management Servers with SCOM 2012 was not possible by using SCOM 2012 agents. During an upgrade process from SCSM 2010 to SCSM 2012 you even need to remove the SCOM agent before the upgrade. After a successful upgrade, the SCOM 2012 agent cannot be deployed back to the box. This is due to some shared code. So the only way to monitor a SCSM 2012 Management Server with SCOM 2012 was using an agentless approach … normally not a thing that is preferred. But with System Center 2012 Service Pack 1 Agent-based Monitoring for SCSM 2012 Management Servers is back!
When Service Pack 1 is installed or when doing a fresh Installation of SCSM 2012 with SP1, the SCOM 2012 Agent is automatically deployed to the Management Server box. The only thing you need to do is to configure it. In the Control Panel you can see that the Operations Manager Agent item that waits for proper configuration.
The SCOM 2012 Agent can also report back to a SCOM 2007 R2 Management Server.
By default the SCOM agent uses ADDS integration to find a SCOM Management Server. If you have this feature configured your SCOM agent will find the correct Management Server itself.
Depending on your SCOM environment you need to configure the SCOM agent to use a specific SCOM Management Server.
After configuration is done, make sure your SCOM infrastructure allows the manual installation of SCOM Agents because this is treated as a manual installation. If needed, approve the new SCOM Agent. Now you are ready to monitor your SCSM Management Servers with a SCOM agent in place – as in the old days
When you don’t want to manually configure the SCOM Agent you can also push the SCOM Agent using a SCOM Management Server or deploy the SCOM Agent with SCCM or something else.