Wednesday, 24 February 2016

Reset Health on Alert Closure.

SCOM has two alert types. Monitors and Rules. 
Both need to be handled differently when resolving. Normally Monitor alerts will self close when the alert has been resolved, but in some cases we have users who will inadvertently close a monitor alert. 
 It can also be difficult to have users fully understand the difference between a rule and a monitor, and act appropriately. If the monitor alert is closed, and the underlying issue not resolved (eg low disk space), then you will not get further alerts unless the health state changes back to healthy and then unhealthy again.

Ideally it's easier to tell users just to "close" alerts, and not to have "reset health".

This posting on the Technet Wiki was one solution I'm implementing to make it easier for users.

Wednesday, 2 September 2015

OMS Performance Data

OMS can now collect performance data. Take a look at the link for more info

Friday, 7 August 2015

Emailing outstanding alerts from SCOM

Sometimes it's good to have a list of SCOM alerts mailed out, especially if your SCOM environment is not connected to a job management system.  
In our environment, we email out a list of alerts that are in the "New" resolution state, as a gentle reminder for people to sort it out.

I've split the email up with monitors and rules separately, due to the way we use SCOM. But its very straightforward to alter the script to not have this.
Add it as a scheduled task.
It's available on the TechNet Wiki

Monday, 3 August 2015

Microsoft Ignite NZ

Self-plug : I will be doing a joint presentation at Microsoft Ignite NZ in September on OMS, and analysing your data in the cloud.  Come to the session if you want to hear more about OMS being used in real life.

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}