Tag: agent

Where is my System Center Management Service in SC 2012 R2?

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:

image

But that is not all folder location is also changed:

image

You will notice the change also in the Control Panel:

image

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.

First install OpsMgr Agent Before Installing OpsMgr or SCSM Console

I’ve ran into an issue where I couldn’t install SCOM 2012 SP1 agent on a server. I was getting the following error:

The System Center 2012 – Operations Manager agent cannot be installed on a computer on which the Operations Manager management server, gateway server, Operations console, operational database, web console, System Center Essentials, or System Center Service Manager is already installed.

The server had OpsMgr and SCSM consoles installed because it was Orchestrator server. To resolve my issue I had to remove both consoles in order to be able to install the OpsMgr agent. I’ve removed both consoles installed the agent and than installed the consoles again.

I cannot remember having this issue with SCOM 2007 R2 but definitely had it with MOM agent 2005 and MOM 2005 Consoles. It will be better if such dependencies are removed in System Center vNext.

Updated: Microsoft System Center 2012 Service Pack 1 Configuration Manager – Clients for Additional Operating Systems

The SCCM clients for operating systems different than Windows are updated to reflect the recently released CU1. You can grab the bits from here.

Re-install SCOM 2012 SP1 Agent on your SCSM SP1 Management Servers – Updated

As most of you probably know SCSM 2012 SP1 comes with built-in SCOM 2012 SP1 agent. You juts install your SCSM SP1 management server and late you can configure your SCOM 2012 SP1 agent from the control panel. So far seems good but there could be situation where your SCSM management server is working normal and your SCOM agent is failing for some reason. So one of the solution would probably be to re-install the SCOM agent right? But how to do that as SCSM management server and the SCOM agent are connected tightly? The solution is to reinstall the SCSM management server. Heavy task but at least there is a solution. So here are the general steps you need to follow to do that:

1. Backup your SCSM management server.

2. Backup the encryption key of the SCSM management server.

3. Uninstall the SCSM management server from Control Panel.

4. Remove any registry keys left from the installation. Examples:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\System Center
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\System Center Operations Manager
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HealthService
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MOMConnector
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OpsMgr Config Service
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OMCFG
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OMSDK
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OpsMgr Config Service Per Agent
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OpsMgr SDK Service
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\System Center Management APM

5. Install SCSM 2012 SP1 management server again with the encryption key you’ve backed up.

6. Configure SCOM SP1 agent from the Control Panel.

This information was provided by Travis Wright – PM @ Microsoft. Thanks Travis for the support. I haven’t tested this but if you are in such situation and you have backup do not be afraid to try it.

————————–UPDATE———————————————–

After some discussions with community members we discovered that SCSM 2012 Self Service Portal SP1 role does not install builtin SCOM agent. The only way to install SCOM agent is to do it prior installing SSP role. Of course to re-install the agent will mean that you have to remove SSP role, re-install the SCOM agent and install SSP role. But be careful with that approach because you may loose some portal customizations you have done. Also I am not sure if MSFT will support such approach of installing the SCOM agent prior SSP role. I would recommend to monitor that server agentless.

I’ve also spoke to Travis Wright and he stated that SCSM team does not have plans to add bultin SCOM agent on the SSP role in any of the future URs.

Dell MP Suite, version 5.0.1. Part III: Server Monitoring by Marnix Wolf

Part III of must read article series here.