It’s SO tedious to track down the update rollup version of SCOM, as the SCOM console still doesn’t have this information available (only major releases!), so you end up looking through the registry or digging into files trying to look at the file version manually.
I wrote this little script in PowerShell. Simply CD into the drive where SCOM is installed and it will track down the SCOM install directory for you, then pull out the Update rollup version and return it to screen.
Dunno what it is, but a lot of SCOM information STILL persists on the web in VB Script and refering to SCOM 2007, when 2012 R2 has been out for YEARS now!
In this blog post, I’ll walk you through monitoring a log file for changes, and throwing an alert if the log file hasn’t changed. And we’ll do it in PowerShell, as the good saint Snover intended.
How to make a two-state monitor in PowerShell
We’re gonna make a monitor, so launch SCOM, and go to Authoring->Management Pack Objects, Monitors. If you don’t see the Authoring tab, you’ve got a baby account and need some added perms.
Right click Monitors and choose add new Unit Monitor.
Pick Scripting – Generic, Timed Script Two State Monitor and find a Management Pack to put this bad boy in.
Give it a name and a description, and then target it to Windows Server Operating System. Continue reading