With the release of Spectrum 9.2.3 (H10) the SCOM connector can now be used with SCOM 2012. This version provides installation tolerance, but does not
leverage any new functionality provided by SCOM 2012.
The main differences between SCOM 2007 and 2012 is the elimination of the RMS (root management server).
In the past we deployed one SCOM connector on the RMS and all the SCOM alerts would propagate up to the RMS and thus one connector could send all SCOM
alerts to Spectrum.
Microsoft has eliminated the RMS as a single point of failure. So now you need to deploy a connector to each SCOM management server that you wish to
collect alerts from. One connector can only attach to one landscape, so the landscapes in Spectrum need to reflect the devices each management server is
managing, or the alerts will be dropped.
SCOM Connector in a Distributed SpectroSERVER (DSS) Environment
When the SCOM server connects to a connector on the main location server (MLS), only models that are present on the MLS have corresponding CA Spectrum
alarms created for System Center Operations Manager alerts. Any System Center Operations Manager alerts that are forwarded to the MLS are not subsequently
forwarded to other location servers in the DSS environment.
For SCOM 2007:
When the SCOM Connector is deployed in a Distributed SpectroSERVER (DSS) environment, SCOM Connector must be subscribed to the Root Management Server (RMS)
and System Center Operations Manager only forwards alerts to a single connector. The connector must be configured to connect to the SpectroSERVER that is
managing the same set of servers and hosts as the System Center Operations Manager server and essentially does not support DSS configurations
Also required is the mention the Root Management Server (RMS) hostname for "SCOMHost" field in .scomrc file.
For SCOM 2012:
SCOM 2012 doesn't have the concept of Root Management Server (RMS) and each SCOM Management Server (MS) is peer with other Management Server (MS) in
Multiple SCOM connectors should be deployed in a Distributed SpectroSERVER (DSS) environment with the limitation that each connector must be subscribed to
single SCOM Server and configured to single SpectroSERVER in the DSS. The SCOM Server and the SpectroSERVER must manage the same set of devices. In this
specific scenario, DSS configuration can be achieved.
If SCOM Connector is connecting to SCOM 2012 Server, it is required to mention the Management Server (MS) for SCOMHost" field in .scomrc file
Once you install a SCOM connector, you have to edit the .scomrc file for your specific configuration.
New section in the scomrc.example in 9.2.3 (H10):
# This setting specifies the web URL port used to access the SCOM web
# console. The default is 51908 when connector is connecting to SCOM 2007.
# The default is 80 when connector is connecting to SCOM 2012 and above.
# SCOMWebConsoleApp = <SCOM_web_console_application>
# This setting specifies the web console application name of SCOM web console.
# For example :- http://<SERVER_NAME>:<PORT>/OperationsManager.
# The default is OperationsManager. The setting is applicable for SCOM 2012
# and above.
This information is targeted to be included in a future update to product documentation.