Automating OpsMgr Part 2: SMA Runbook for Creating ConfigMgr Log Collection Rules

Introduction This is the 2nd instalment of the Automating OpsMgr series. Previously on this series: Automating OpsMgr Part 1: Introducing OpsMgrExtended PowerShell / SMA Module Few weeks ago, I have also published a post: Collecting ConfigMgr Logs To Microsoft Operation Management Suite – The NiCE Way, which demonstrated how to use an OpInsights integrated OpsMgr management group and NiCE Log File MP to collect ConfigMgr client and server logs into Microsoft Operation Management Suite. The solution I provided in that post included few sealed management packs and a demo management pack which includes few actual event collection rules for ConfigMgr

Automating OpsMgr Part 1: Introducing OpsMgrExtended PowerShell / SMA Module

Background The OpsMgrExtended PowerShell and SMA module is a project that I have been working on since August last year. I am very glad that it is now ready to be released to the community. This module is designed to fill some gaps in the current OpsMgr automation solutions provided natively in System Center 2012 suite. This module can be used as a System Center Service Management Automation (SMA) Integration Module, as well as a standalone PowerShell module. Currently, the following products are available when comes to creating automation solutions for OpsMgr: OpsMgr native PowerShell module OpsMgr Integration Pack for System

Session Recording for My Presentation in Microsoft MVP Community Camp Melbourne Event

Last Friday, I presented in the Melbourne MVP Community Camp day, on the topic of “Automating SCOM Tasks Using SMA”. I have uploaded the session recording to YouTube. You can either watch it here: If you’d like to watch it in full screen, please go to: https://www.youtube.com/watch?v=QW99bVFKg80   Or on YouTube: https://www.youtube.com/watch?v=QW99bVFKg80 You can also download the presentation deck from HERE. And Here’s the sample script I used in my presentation when I explained how to connect to SCOM management group via SDK:

Overall, I think I could have done better – as I wasn’t in the best shape

Microsoft MVP Community Camp 2015 and My Session for SMA Integration Module: OpsMgrExtended

On next Friday (30th Jan, 2015), I will be speaking at the Microsoft MVP Community Camp Day in Melbourne. I am pretty excited about this event as this is going to be my first presentation since I have become a System Center MVP in July 2014. My session is titled “Automating SCOM tasks using SMA”. Although this name sounds a little bit boring, let me assure you, it won’t be boring at all! The stuff I’m going to demonstrate is something I’ve been working on during my spare time over the last 6 month, and so far I’ve already written

A SMA Integration Module For SharePoint List Operations

Background Many Microsoft System Center Orchestrator and Service Management Automation (SMA) users may agree with me, that these two automation platform does not have feature rich end user portals natively. Although System Center Service Manager can be used as a user portal for triggering SCORCH/SMA runbooks, Microsoft SharePoint is also a very good candidate for this purpose. Integrating SharePoint with Orchestrator and SMA is not something new, many people have done this already. i.e. System Center Universe America 2014 – Orchestrating Daily Tasks Like a Pro (by Pete Zerger and Anders Bengtsson) Service Management Automation and SharePoint (by Christian Booth

Using SMA to Building Your Own Microsoft OpsMgr Management Pack Catalog On SharePoint 2013

Background Over the years that I’ve been working with OpsMgr, for me, the Microsoft Pinpoint MP Catalog was a one stop shop for getting Microsoft management packs. More information about the Pinpoint MP Catalog can be found in Marnix’s post: http://thoughtsonopsmgr.blogspot.com.au/2010/07/pinpoint-management-pack-catalog.html Based on the information came out in TechEd Europe 2014, looks like there will be changes introduced to the System Center Pinpoint site (http://channel9.msdn.com/Events/TechEd/Europe/2014/Ch9-34, from 09:00 onwards). And it seems the link from Marnix’s post https://pinpoint.microsoft.com/systemcenter is no longer valid. So I’ve decided to do some experiment, see if I can generate and maintain a Microsoft MP catalog on-premise,

My Experience Manipulating MDT Database Using SMA, SCORCH and SharePoint

Background At work, there is an implementation team who’s responsible for building Windows 8 tablets in a centralised location (we call it integration centre) then ship these tablets to remote locations around the country. We use SCCM 2012 R2 and MDT 2013 to build these devices using a MDT enabled task sequence in SCCM. The task sequence use MDT locations to apply site specific settings (I’m not a OSD expert, I’m not even going to try to explain exactly what these locations entries do in the task sequence). In order to build these tablets for any remote sites, before kicking

A Simplified Way to Send Emails and Mobile Push Notifications in SMA

Background For those who knows me, I’m an OpsMgr guy. I spend a lot of time in OpsMgr and I am very used to the way OpsMgr sends notifications (using notification channels and subscribers). In OpsMgr, I like the idea of saving the SMTP configuration and notification recipients’ contact details into the system so everyone who has got enough privilege can use these configurations (when configuring alert subscriptions). Over the last few months, I have spent a lot of time on SMA (Service Management Automation). As I started building more and more runbooks and integration modules, I really miss the

Clean Up SMA Database After a Module Deletion

Background I noticed an issue while I was writing a SMA integration module. I once made an mistake in the .json file and I noticed I couldn’t import the updated module back to SMA even after I firstly deleted the old version. I’ll explain this issue using a sample dummy module. Reproducing The Issue To reproduce the issue, I firstly created a dummy module with 3 files: The module .psm1 and the connection file .json (notice there’s a connection field named “ComputerName” in the .json file): I zipped and imported this module into SMA, everything looks good so far. and

SMA Management Pack Could Not Connect To Database Alerts – My Troubleshooting Experience

I’ve setup 2 servers for the SMA environment in my lab a while back. Yesterday, I loaded the SMA MP (version 7.2.89.0) into my OpsMgr management group. Needless to say, I followed the MP guide and configured the Database RunAs profile. However, soon after the MP is loaded, I started getting these 2 alerts: The Service Management Automation web service could not connect to the database. The Service Management Automation worker server could not connect to the database. To troubleshoot these alerts, I firstly unsealed the management pack Microsoft.SystemCenter.ServiceManagementAutomation.2012R2.mp, as this is where the monitors are coming from. The Data

%d bloggers like this: