Tag: MP Authoring

While I was working on the recently published ConfigMgr 2012 Client MP in VSAE, I needed to add few images as icons for the ConfigMgr 2012 Client class that I defined. I couldn’t find any articles on the net explaining how to do so in VSAE for OpsMgr MP’s. Instead, I found this article on how to do it for a Service Manager MP. It wasn’t too hard to figure out how to do this for OpsMgr MPs, all I had to do is to look at the Microsoft.SystemCenter.Library in VSAE. It turned out adding images for classes in OpsMgr

Like this:

I’ve written a OpsMgr management pack to monitor ConfigMgr 2007 clients in the past. The MP was published in this blog. Over the last month or so, as part of a project that I’m working on, I have written a Management Pack to monitor ConfigMgr 2012 Clients via OpsMgr 2012. This MP provides individualised monitoring for ConfigMgr 2012 clients, where the Microsoft ConfigMgr 2012 management pack does not. To be honest, I wasn’t really happy with the ConfigMgr 2007 Client MP that I wrote almost 2 years ago. I think there are a lot of areas that needs improvement. So

Like this:

I wrote this simple management pack couple of weeks ago to detect new SMB (Shared Folders) connection as well as disconnection events on OpsMgr agents. The MP contains two (2) WMI event rules, one for new connection event and one for disconnection event. Each rule generates a Informational alert: New Connection alert: Disconnection Alert: I’ve used the Microsoft.Windows.WmiEventProvider.EventProvider module as the data source module for both rules. The WMI queries used for these rules are: New Connection Rule: [sourcecode language=”SQL”] Select * from __InstanceCreationEvent within 1 where TargetInstance ISA ‘Win32_ServerConnection’ and TargetInstance.ShareName !=’IPC$’ [/sourcecode] Disconnection Rule: [sourcecode language=”SQL”] Select

Like this:

I’ve updated the OpsMgr Self Maintenance MP for OpsMgr 2012 again this weekend. the latest version is now 2.1.0.0. The following is what’s new in this version: Bug fix for the MP backup rule The alert parameter and alert message was configured incorrectly. when the alert is generated for the failed backup, the error from the script was not displayed in the alert description: This is now fixed, the alert description is correctly displayed: New Rule: Detect Manually Closed Monitor-Generated Alerts As any OpsMgr operators /administrators should know, monitor generated alerts should not be closed manually. There are many articles

Like this:

I have published the OpsMgr Self Maintenance Management Pack Version 1.0 on this blog few months ago. Over the last couple of month, I’ve been working on the version 2.0.0.0 of this MP during my spare time. It has taken a lot longer than I thought because it was hard for me to find blocks of spare time to sit down and work on it. It is now complete and the list below is what has been added / changed in the version 2.0.0.0: A rule that detects user-defined overrides in the Default MP A rule that configures failover management

Like this:

Not sure if this issue has been blogged before. Yesterday, while I was working on a management pack project, I noticed that if I created a new VBScript file within VSAE (In Visual Studio), the script will not run when I test it in command prompt. To replicate this issue again, I firstly created a brand new VBScript file inside the project: Then added one line to the script and saved it: Now, when tried to run it via the command prompt, I got a error saying there’s an invalid character at position (1,1) – which is the beginning of

Like this:

When writing management packs for an application / system, it is very common to have multiple management packs included in the end monitoring solution. i.e. a library MP, a discovery MP, a monitoring MP, etc. Back in the old days when using the OpsMgr 2007 R2 Authoring console, these separate management packs need to be created separately. If one of these MPs (i.e. the library MP) is referenced in other MPs (i.e. discovery MP and monitoring MP), the referenced MP (i.e. the library MP) needs to be developed and sealed prior to making the references in the referencing MPs (i.e.

Like this:

At work, in one of the OpsMgr 2007 management groups, we have 3 sets of Australian state / territory based computer groups. Let’s say they are App-A, App-B, and All computers groups. so each state has 3 computer groups (i.e. NSW App-A, NSW App-B and NSW All Computers). By default, for computer groups, the Health Rollup Policies for the Health Rollup dependency monitors are configured to use the worst state of any member: Yesterday, there was a requirement to change the health rollup policies for these groups from the “Worst state of any member” to a percentage value of 95%

Like this:

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

Like this:

Don’t you hate it when you’ve just released a piece of work to public and you found an issue with it? Well, this is what happened to me today. Yesterday and released the OpsMgr Self Maintenance MP, and today, I found an issue with the 2012 version. After the MP is imported and the “OpsMgr 2012 Self Maintenance Operational Database LocalizedText Table Health Monitor” has been enabled via an override, you’ll soon get this alert from one of the management servers: The PowerShell script failed with below exception System.Management.Automation.IncompleteParseException: White space is not allowed before the string terminator. at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable