SCOM 2012 R2 – Monitor a Windows Service

In this post I will give detailed instructions on how to monitor a Windows service through SCOM 2012 R2.

For this example I will be creating a monitor to monitor a service called ‘LP360 License Server’ which only occurs on a single server

  1. Within the SCOM console, Navigate to the ‘Authoring’ tab, expand ‘Management Pack Objects’ and select ‘Monitors’SCOM - Authoring Monitors
  2. Right click on ‘Monitors’, expand ‘Create a Monitor’ and select ‘Unit Monitor…’SCOM - Authoring Monitors - Create Unit Monitor
  3. Expand ‘Windows Services’ and select ‘Basic Service Monitor’SCOM - Create Unit Monitor - Monitor Type
  4. From the drop-down menu, select the management pack that you wish to place this monitor into. For custom monitors I create a management pack which i have called ‘Service Monitoring’. Then click ‘Next’
  5. Give your monitor a name that is unique and specific to what you are monitoring, I called mine ‘LP360 License Server’SCOM - Create Unit Monitor - General
  6. Select a monitor target. if this service is specific to an operating system such as Server 2008 R2, then search for and select ‘Windows Server 2008 R2 Computer’ of the Discovery management pack. Otherwise select ‘Windows Computer’ to cover all Windows server and clients. Then click ‘Next’
  7. Select a ‘Parent monitor’ from the drop-down box. for custom monitors I create an Aggregate Rollup Monitor which is called ‘Custom Services’. If you have not got a custom one, select ‘Availability’, it can always be changed later
  8. Because this service is only on one server, I do not want the monitor enabled by default. Untick ‘Montor is enabled’, then click ‘Next’
  9. If you are confident of the service name then type it in the box. I strongly suggest clicking on the ‘…’ buttonSCOM - Create Unit Monitor - Service Details
  10. Click ‘…’, type the server name and click ‘OK’SCOM - Create Unit Monitor - Select Windows Service - Select Computer
  11. Locate the service you wish to monitor and click ‘OK’. When you use this method there can be no doubt as to the service nameSCOM - Create Unit Monitor - Select Windows Service
  12. Click ‘Next’
  13. The default health states are fine for monitoring services, so unless you have specific requirements for something different, click ‘Next’SCOM - Create Unit Monitor - Configure Health
  14. I turn on alerts for all service monitors, select ‘Generate alerts for this monitorSCOM - Create Unit Monitor - Configure Alerts
  15. Change the ‘Alert description’ to something that makes sense for you, mine is ‘The ‘LP360 Server’ Service has stopped.”
  16. Click ‘Create’
  17. Search ‘Monitors’ for your monitor, locate it under ‘Windows Computer’. Right click, expand ‘Overrides’, then ‘Override the Monitor’. Select ‘For a specific object of class: Windows Computer’SCOM - Create Unit Monitor - Search - Override
  18. Search for the server that is running the service, select the server and click ‘OK’SCOM - Create Unit Monitor - Override - Select Object
  19. Tick the ‘Override’ box the corresponds to the ‘Enabled’ parameter, then change the ‘Override Value’ to ‘True’. Click ‘OK’SCOM - Create Unit Monitor - Override - Enable
  20. Navigate to the ‘Monitoring’ tab, then select ‘Windows Computers’SCOM - Search for server - Right Click - Open
  21. Search for the server you just created the override for. Right click on the server, expand ‘Open’, select ‘Health Explorer’ for your server
  22. Navigate to where you placed the monitor, in my case it was ‘Custom Services’. Depending on your setup, you may have to clear the filter, it will be a yellow bar at the top of the left paneSCOM - Health Explorer - LP360
  23. Click on State Change Events to confirm when the monitor became active. It could take up to an hour for the monitor to become active. This is dependent on the amount of clients you are monitoring and the performance of your SCOM infrastructure

SCOM 2012 SP1 – Agent Not Monitored

Symptoms

After installing/attaching agents the state is displayed as “Not monitored”

Image

Note: The agent will likely appear this way after first installing/attaching. wait 24 hours for it to auto-configure and only assume failure if it is still showing the same status after this

Resolution

  1. Connect to server that is displayed as “Not monitored”
  2. Open the run box and type “Services.msc”Run - services.msc
  3. Locate service named “System Center Management”Services - System Center Management
  4. Right click and stop serviceServices - Right click menu
  5. Browse to C:\Program Files\System Center Operations Manager\Agent
  6. Change folder name to “Health Service State Old”SCOM - Health Service State folder
  7. Start service and make sure that a new folder is createdSCOM - Health Service State folder new
  8. Wait 5 minutes and refresh SCOM console to ensure that agent is now monitoredSCOM - Agent monitored