In the first part of my blog series about Service Monitoring I’ve described how Service Monitoring could be implemented en what parts of Service Monitoring are important. One of the most important lesson was to create a process around Service Monitoring. You can find the first blogpost in this series here. In this second part I want to talk about the implementation of Service Monitoring in System Center Operations Manager 2012: Distributed Applications.
SCOM 2012 R2
OpsLogix VMware Management Pack and Dashboarding capabilitiesStandard
Last week I had the chance to test the OpsLogix VMware Management Pack for System Center Operations Manager. Recently OpsLogix released the RTM version of this management pack. My goal was to look into the dashboarding possibilities of this management pack. Continue reading
SCOM 2012 Export Overrides Powershell ScriptStandard
Today I was looking for a PowerShell script which can export all overrides based of a specific Management Pack. I found a script of Daniele Muscetta and Pete Zerger from SystemCenterCentral. This script did not worked out of the box on SCOM 2012 so I fixed that and added ‘HTML’ as output option. So with my addition it can be used on SCOM 2012 environments and the output can be a csv or html file.
SCOM 2012 R2 Operational Database Move StepsStandard
Today I had to move a SCOM 2012 R2 Operational Database. I executed this process already for moving a Operational Database to a SQL Always On Cluster. For this move I used the Technet article as a reference. After this move I received from Data Access Service and the Configuration Service a service login error on the database. After double checking the steps made my only conclusion was that SCOM was still connecting to the old server. But what setting was the root cause for the error.