Actually I was looking for some other things in SCOM 2012 R2 as I suddenly noticed some interesting naming convention of the SCOM services…
Until SCOM 2012 Sp1 the Windows services on the management server were named like this…
In SCOM 2012 R2 the Windows services on the management server are named like this…
For an easy to follow check this table…
Management server:
| SCOM 2012 SP1 | SCOM 2012 R2 |
| System Center Data Access Service (OMSDK) | System Center Data Access Service (OMSDK) |
| System Center Management Configuration (cshost) | System Center Management Configuration (cshost) |
| System Center Management (HealthService) | Microsoft Monitoring Agent (HealthService) |
| System Center Management APM (System Center Management APM) | Microsoft Monitoring Agent APM (System Center Management APM) |
| System Center Audit Forwarding (AdtAgent) | Microsoft Monitoring Agent Audit Forwarding (AdtAgent) |
If you look at an agent monitored server you will find the following services as you might expect from the table above…
Agent monitored server:
| SCOM 2012 SP1 | SCOM 2012 R2 |
| System Center Management (HealthService) | Microsoft Monitoring Agent (HealthService) |
| System Center Management APM (System Center Management APM) | Microsoft Monitoring Agent APM (System Center Management APM) |
| System Center Audit Forwarding (AdtAgent) | Microsoft Monitoring Agent Audit Forwarding (AdtAgent) |
If you need to restart services make sure you look at the appropriate service…
Thanks Stefan, really helpful. 🙂
Thank you very much, your blog commenting lists are great help to me in building inbound links to my blog.
Why are some of them disabled?
Hi
Because some of the features e.g. APM, ACS which require some of these services are not enabled by default.
Cheers,
Stefan