First I would like to mention that if you don’t need connectivity to On Premise data you can sign up for a free Power BI account read more about it here.
Before you can jump into building these reports you will need to configure the Service Level Target (SLT) and Service Level Objectives (SLO) in SCOM here is a good walk through by Kevin Green of how to configure the SLT and SLO.
Part 1 – Setting up the data for our dashboard
Microsoft has added System Center 2012 R2 to the volume licensing site.
In this blog post I am going to show you a bug I found and how to create the override to silence the alerts. The bug has been reported to Microsoft.
In version 3.1.6011.0 of the System Center 2012 Virtual Machine Manager Monitoring MP there is a bug when monitoring a VMware environment. If you have added a Vcenter server to your VMM environment you will see alerts like the image below. “VGS not Installed”
In this post I am going to cover how to setup you SCOM environment to be the System Center Advisor gateway.
In my lab I have an issue where SQL doesn’t always start when my VM is rebooted this causes the SCOM services not to start up as well, in our production environment we every once in a while will have something happen that causes SQL to fail. So I created some runbooks that will monitor SQL and the SCOM services. If you are running more than one SCOM management server or running a SQL cluster you will need to create these runbooks for each server.
Monitor SQL Service – Runbook
If you are installing SCOM for the first time on a Windows 2012 Server here is the Powershell to install all of the IIS prerequisites for the Web console
Before running this script make sure you have a GPO in place for the sxs install files
If you try to install the SCOM agent on a SharePoint server that already has the SCSM self-service portal installed, the install of the SCOM agent will fail. To resolve this the only option is to uninstall the SCSM self-service portal then install the SCOM agent and reinstall the SCSM Self-service Portal.
Since most of the configuration for the self-service portal is stored in the SCSM database this process can be done fairly easily as long as you have not done any major modifications to the self-service portal and where having a well-documented change process in place comes into play.
During my upgrade to SCOM 2012 SP1 I decided to not install the web console while troubleshooting other errors with the Management Server. When I reinstalled the web console I was getting a 401 unauthorized: Access is denied due to invalid credentials error.
The solution to fix this on a new install of the web console was to change the authentication provider order.
Open IIS, highlight the operationsmanger application open authentication
I wanted to share this Management Pack I found that looks to be some great work by Tao. His blog post can be found here. Looks like I can turn off a few of the runbooks I have built once I get this installed and configured.
In this blog post I am going to cover the steps required to install the Chargeback Management Packs.
Log on to your Operations Manager Server
Copy the files from you SCSM server or open a powershell prompt to them and run ImportToOM.ps1