Wednesday 29 July 2015

IIS Log rollover for OMS with SCOM alerting

Microsoft recommends that machines loaded into Microsoft Operations Management Suite (OMS that are running IIS, have their log rollover set to hourly.

However, once machines are added into OMS, it's entirely possible the IIS logs are changed, new sites are rolled, etc.  And there is no easy way to see if that had been done, or stay on top of it.

 As a solution I throw an alert in SCOM if any site is not configured to 'hourly'.
See my TechNet wiki articlefor a howto, and a handy script to set up IIS Log rollover via PowerShell.

Monday 20 July 2015

I published an article about displaying OMS updates in SCOM.   Looks like I picked up the gold award System Centre from the Technet Wiki Ninja's. yay!

Thursday 16 July 2015

Getting group overrides

A simple script to return a list of overrides against a group in SCOM.

# MUGetSCOMGroupOverrides.ps1
# Script to retrieve overrides for a specific group
# Scripy by Darren Joyce
# Last updated 16/7/15

if (!$name){
    $name = read-host 'What is the name of the group?'

$groupid = (Get-SCOMGroup $name).Id
Get-SCOMOverride | where {$_.ContextInstance -eq $groupid}

Wednesday 15 July 2015

Alerting on OMS Solution Pack update notification

OMS (Microsoft Operations Management Suite) pushes management pack updates automatically down to your on-premise SCOM, as part of Microsoft's rapid releases.
Unfortunately there is no easy way to see when this happened, so *if* something broke - it's harder to associate with a change.

(change control - time for a rethink?)

I threw together this script to query the SCOM database and return any MP updates in the last 24 hours. And then built an alert in SCOM to tell me if it had any results from that script.