How I do it: SCOM alert handling/management

This week I had a discussion with some colleagues about SCOM alert handling/management. When do I close an alert? How do I do that? What about the monitors causing the alert?  How can we automate this stuff? What about roll-up monitors? A lot of questions and I never took the time to think about that…


Reporting RunAsAccount usage information in a SCOM 2012 (R2) Management Group

A few days ago I was asked if I had a script to list all RunAsAccounts in a SCOM Management Group and their associated RunAsProfile (“Which profile uses which account?” or "Which account is used in which profile?"). I had none, but in my youthful carelessness I thought, that couldn’t be rocket science… Ok, it…

2

An approach to automate SCOM service account password change – part 1/3: background and process

Changing SCOM Service account passwords can be challenging and complex. MVP Marnix Wolf has written an excellent blog post about all necessary steps we have to take to change passwords in all the different locations like AD, Windows OS (Service), RunAs accounts, SQL Reporting configuration etc. But as SCOM is a powerful and mighty tool…


Quick note from the field: SDK/DAS Service account needs SCOM admin role membership

Configuring a high secure SCOM Management Group with the least amount of privileges possible can be challenging. Thanks to my colleagues Kevin Holman and Sergio Carrilho there is an excellent document which describes all accounts and their required access rights: SCOM Security Account Matrix Please be aware, that you also assign the SDK/DAS service account…


Removing SCOM workflows via PowerShell and SDK

This is just a short post about how to remove SCOM workflows (Rules,Monitors and Overrides) via PowerShell. As you may have noticed, our OpsMgr PowerShell module provides several Cmdlets  for GETting workflows, but not for removing them: So, how do we remove a workflow? If you know the correct methods and how to use them,…


An approach of collecting and analyzing SCOM 2012 SDK connections

Knowing WHO logged on to SCOM WHEN, from WHERE and HOW LONG this session lasted can be very helpful information for SCOM Admins. As we have a recommended limit of simultaneous open Operations consoles of 50 (details see here) it is also very useful to know the total amount of connected users in your environment…