Thursday, February 19, 2015

Monitor SCSM 2012 SP1 or R2 with SCOM

Yesterday the question came up if it is a good way to push deploy SCOM agents to SCSM 2012 SP1 or R2 MS and DW role server. The short answer: no! (NO! NEVER! DON’T DO THAT!)

Why? Unfortunately it would be possible to push an agent on those systems. SCOM would determine that there is an existing agent in place and would upgrade it to the most recent version available on the SCOM MS. Monitoring, after that, would work as expected, but the SCSM workflows will collapse. (BTW: who came to the good idea to take parts of SCOM as SCSM base without changing services, processes, logs, …? That is pain in the … consultants/admins head)

The only right way is to install SCSM SP1 or R2 as required (maybe already done). After that you’ll find the “Microsoft Monitoring Agent” on those systems where you can configure your SCOM Management Group information.

If you’ve got SCOM security settings to “Review new manual agent installations in pending management view” you will see them immediately under Pending Management in the SCOM administrative pane. If you’ve checked the option “Automatically approve new manually installed agents” they will get monitored automatically.

The self-service portal is something different (BTW: did you know that we’ve developed an awesome self-service portal? And we will release a new major version these days! More here: More on SSP below.

Here is the official documentation on that (bad luck that they don’t updated the SCSM MP guide):

System Center 2012 – Operations Manager

System Center 2012 – Operations Manager is supported by Service Manager and Service Manager SP1 for connectors and agents. However, only corresponding System Center versions are supported when you register a data source in the Data Warehouse workspace.

System Center 2012 – Operations Manager agents were not supported with System Center 2012 – Service Manager. However, the agent that is automatically installed by System Center 2012 – Service Manager SP1 is compatible with System Center 2012 – Operations Manager and System Center 2012 – Operations Manager SP1. After Service Manager Setup completes, you must manually configure the agent to communicate with the Operations Manager management server.

To validate that the Operations Manager Agent was installed, open Control Panel and verify that the Operations Manager Agent is present. To manually configure the Operations Manager agent, see Configuring Agents.

Operations Manager Agents with the Self-Service Portal and Service Manager console

If you want to monitor a server that will host Self-Service Portal components or the Service Manager console that does not already host other Service Manager roles, then you should deploy the Operations Manager agent to the server before you install the Self-Service portal or the Service Manager console. After you’ve installed either, you should give special consideration to removing the portal or Self Service console. If an Operations Manager agent is installed on the server that hosts the portal or console and you remove the either, then the Operations Manager agent is also removed.

If you have already installed the portal or console to a server that does not host other Service Manager roles, and you want to deploy an Operations Manager agent to it, then the agent deployment will fail. However, you can prevent agent deployment failure by using the following procedure to back up, remove, and restore the Service Manager product registry key.

To back up, remove, and restore the Service Manager product registry key
  1. Export the Service Manager key from HKEY_CLASSES_ROOT\Installer\Products\<ServiceManagerGUID>. You can find the key by searching at the Products node for Data equal to Service Manager.

  2. Delete the registry key.

  3. Deploy the Operations Manager agent to the server.

  4. Import the key you exported from step 2.

All information is provided "as is" without any warranty! Try in lab before. Handle with care in production.


Post a Comment