I noticed a interesting link the other day in the Run As Account dialog of the SCOM 2016 console.

SCOM can encrypt communication between Management servers, using a certificate. This isn’t mandatory, unless you use Gateway servers, but it is going to make your security team happy.

I had a funny one at work the other day. We have a legacy SCOM 2007 R2 environment that just monitors our remaining Windows 2003 servers (I know don’t get me started!

Groups are something that took me a while to get my head round.

Containments help you populate groups as well as structure Distributed Applications (DAs).

I’ve started authoring SCOM management packs as part of a project I’m working on.

If you create a custom view in SCOM 2012 R2 ( and possibly previous versions), you may notice that it doesn’t update in the full console each time you install a new version of your management pack.

I’ve recently been working on a SCOM 2012R2 proof of concept and had to set up the first client server that was not part of the domain.

I’ve recently been working on a SCOM 2012R2 proof of concept and had to set up the first client server that was not part of the domain.

I’ve recently setup some dashboards in SCOM 2007 R2 for colleagues who haven’t used SCOM much before.