My Experience of Using Silect MP Studio During Management Pack Update Process

Thanks to Silect’s generosity, I have been given a NFR (Not For Resell) license for the MP Studio to be used in my lab last November. When I received the license, I created a VM and installed it in my lab straightaway.  However, due to my workloads and other commitments, I haven’t been able to spend too much time exploring this product. In the mean time, I’ve been trying to get all the past and current MS management packs ready so I can load them into MP Studio to build my repository. Today, one of my colleagues came to me

Updated Management Pack for Windows Server Logical Disk Auto Defragmentation

Background I have been asked to automate Hyper-V logical disk defragmentation to address a wide-spread production issue at work. Without having a second look, I went for the famous Autodefrag MP authored by my friend and SCCDM MVP Cameron Fuller. Cameron’s MP was released in Octorber, 2013, which is around 1.5 year ago. When I looked into Cameron’s MP, I realised unfortunately, it does not meet my requirements. I had the following issues with Cameron’s MP: The MP schema is based on version 2 (OpsMgr 2012 MP schema), which prevents it from being used in OpsMgr 2007. This is a

VMM 2012 Addendum Management Pack: Detect Failed VMM Jobs

Background My MVP friend Flemming Riis needed OpsMgr to alert on failed VMM jobs. After discovering that the native VMM MPs don’t have a workflow for this, I have offered my help and built this addendum MP to alert failed and warning (Completed w/ Info) VMM jobs: I thought it is going to be a quick task, turned out, I started writing this MP about 1 month ago and only able to release it now! The actual MP is pretty simple, 2 rules sharing a same data source which executes a PowerShell script to detect any failed and warning jobs

OpsMgr Weather Monitoring MP Updated

I got an email from someone up in Sweden the other day in regards to the Weather Monitoring MP that I released few months ago. I’ve been made aware that a negative temperature reading is being recorded as a positive value (i.e. –8 degrees is being collected as 8 degrees). First of all, apologies for this mistake. I wrote the PowerShell script for the probe action module back in July last year, when most of world was in summer. I didn’t even think about negative values and I couldn’t test it anyway… Last night, I spent some time fixing the

SCOM Management Pack: Detecting USB Storage Device Connect and Disconnect Events

There was a requirement at work that people need to be notified when a USB storage device (USB key or portable USB hard disks) is connected or disconnected from SCOM monitored Windows computers. So I wrote a 2 very simple alert generating rules to detect USB Mass Storage Device creation and deletion WMI event. I set both rules to run every 60 seconds so within 60 seconds of the event, an Information alert is generated in SCOM: Alert for USB Storage Device Connection Event: Alert for USB Storage Device Removal Event: I have also created a dynamic group called Virtual

SCOM Management Pack: Daylight Saving Time Change Detection

I wrote this management pack to detect system time changes that are caused by daylight saving. It’s called “Custom Daylight Saving Detection”. Background: When supporting a infrastructure that has servers across the globe, it is hard to keep track of daylight saving schedules for all time zones. There is a requirement that we need to be notified when the Windows servers have entered/exited daylight saving time. Functionalities: This management pack generates alerts when: the agent computer has entered / exited Daylight Saving time. the agent computer is entering / exiting Daylight Saving time within a configurable number of days (default is

%d bloggers like this: