[OpsMgr 2012] Is VMPD working on Microsoft Visio 2013 Professional ? (#VMPD #Authoring #Opsmgr )

After having forget using VMPD on my computer, I today wanted to make it working. Going on the download page show me that only Microsoft Visio Premium 2010 is supported !

What about Microsoft Visio 2013 Pro ? Hope I'll not have to downgrade my soft version !

Let's also try to launch MSI file and install VMPD on my Visio 2013. Installation is successful and I can start 'Design Management Pack in Visio'. Great !

Let's now use a template 'Application with single server role' and add the needed values like Service Name, event ID and TH and when done click on Generate MP : 

An exception occured : 

Same issue I add when using Visio 2010 an my Seven computer. Nothing has changed. too bad !

I've tried a lot of things and finally ungroup the shape and this makes VMPD able to save the MP !

Even if not supported, VMPD is also able to work on Visio Pro 2013 ! Good new !

This posting is provided "AS IS" with no warranties.

[OpsMgr 2012] Boris Yanushpolsky 's Tools by Daniele Muscetta - New update

Here is the latest update from Daniele :

•  May 9th 2013 with MPViewer 2.3 that now can also handle MP Bundles that contain multiple ManagementPacks in a single bundle.

Many thanks to him to always improve the tools !

Get latest updates directly on : http://blogs.msdn.com/b/dmuscett/archive/2012/02/19/boris-s-tools-updated.aspx

This posting is provided "AS IS" with no warranties.

[OpsMgr 2012] VSAE – Include File Content

David Allen, has posted on April 3, 2013, an article to show how to include your own vbs, ps1 or JS script in your authored management pack.

Full article is here

The include syntax in this example is $IncludeFileContent/Scripts/MonitoringScript.vbs$, and this is generated based on the path of the file.  In this MP, I stored the VBS file in a folder called Scripts, which is why “Scripts/MonitoringScript.vbs” is added to “IncludeFileContent”.

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007R2][OpsMgr 2012] Management Pack samples - Authoring

Brian Wren published in summer 2012 MP samples that have been on OpsManJam for some time.

Direct link to Brian's article

• Sample Management Pack - Business Hours

Sample management pack for Operations Manager 2007 and System Center 2012 Operations Manager.

This management pack provides an example of configuring monitors and rules to run only during business hours.  Examples are provided for a service monitor, a monitor running a script, and monitors and rules based on a Windows event.  Two different monitor types are used for events.  These have identical functionality but illustrate two different strategies for configuring monitor types.
Each monitor and rule must specify parameters for the System.ScheduleFilter module.  StartTime and EndTime provide the time that the monitor or rule should begin functioning, while EndTime specifies the time that it should stop functioning.  DaysOfWeekMask specifies the days of the week that the schedule applies to as described in the following article: http://msdn.microsoft.com/en-us/library/ee692976(v=MSDN.10).aspx.
Both event monitors trigger a critical state from an event with a number of 101 and a source of EventCreate.  They return to healthy with an event number of 102.  The service monitor watches the running state of the Alerter service,  The script monitor will set a state according to the Successful parameter on the monitor type.  If the Successful parameter is false, then a critical state is set.  If the Succesful parameter is true, then a healthy state is set.
All rules and monitors are targeted at a class called MPAuthor.BusinessHours.Target.  This is discovered by creating a registry key at HKLM\SOFTWARE\MPAuthor\BusinessHours. This registry key must be on the same agent computer where the test events are created.

• Sample Management Pack - Network Devices

 This is a sample management pack for Operations Manager 2007 R2.
This management pack provides an example of monitoring network devices.  This includes providing custom monitoring for different brands of SNMP devices and monitoring Syslog mesages from devices that do not support SNMP.
A class is created for each type of SNMP device based on Microsoft.SystemCenter.NetworkDevice.  This provides a target for monitors and rules specific to each type.  For devices that do not support SNMP, a class is created based on System.HardwareComponent.  A device for each type of device is created based on this class that provides the target for monitors and rules specific to that type.

Discovery for SNMP devices is targeted at Microsoft.SystemCenter.NetworkDevice since this represents network devices that have already been discovered.  The name of the target is used to determine the type of device and which class should be created.  Discovery for devices not supporting SNMP is performed from a text log that lists the Name, IP Address, and Type for each device to discover.  This discovery is targeted at a proxy agent that is discovered from a registry key at HKLM\SOFTWARE\MPAuthor\NetworkDevices.  This registry key must also contain a value called ConfigFIle that contains a path to the configuration file.

The classes for the devices are all unhosted.  Unhosted object are typically managed on the RMS, but the discovery scripts create a special containment relationship that causes the object to be managed on the proxy agent.  Any monitors or rules targeted at these classes are loaded on the agent computer.  The managed devices should be configured to send SNMP traps and Syslog messages to the proxy agent.

• Sample Management Pack - Working with a Property Bag

 This is a sample management pack for Operations Manager 2007 R2 and System Center 2012 Operations Manager.
This management pack provides an example of a script returning multiple values in a property bag.  A single monitor type is used that accepts a parameter to specify the desired property. Also illustrated is the use of data source modules returning different data types.  Rules and monitors can use the data source returning the type they require, while they all share the same script.

The script collects different pieces of data from a file.  The name of the file must be specified in the FileName parameter of any rule or monitor.

All rules and monitors are targeted at a class called MPAuthor.PropertyBag.Target.  This is discovered by creating a registry key at HKLM\SOFTWARE\MPAuthor\PropertyBag. This registry key must be on the same agent computer with the file.

• Sample Management Pack - Diagnostics and Recoveries

 This is a sample management pack for Operations Manager 2007 R2 and System Center 2012 Operations Manager.
This management pack provides an example of a recovery running after a diagnostic.  The recovery only runs if specific criteria is received from the diagnostic output.  It also illustrates how to pass property bag data from the monitor to the diagnostic and the recovery.

In this example, the diagnostic runs in response to a service monitor.  If the specified service is stopped, then the diagnostic runs.  The service used is the WMI Performance Adapter (WmiApSrv), but this can be changed in the properties of the monitor.  The diagnostic runs a script that collects an error code value from the registry at HKLM\SOFTWARE\MPAuthor\DiagnosticAndRecovery\ErrorCode.  If the error code is 3, then the recovery will run.  If it is any other value, the recovery will not run.  The recovery is a script that restarts the service.

A sample diagnostic and recovery are provided for both VBScript and PowerShell.  The functionality of each are identical and only one of the diagnostics should be enabled at a time.

• Sample Management Pack - Process Data Source

 This is a sample management pack for Operations Manager 2007 R2 and System Center 2012 Operations Manager. 
This management pack provides an example of a script processing the output of a data source.  The data source is followed by a probe action that changes the output data type to a property bag. Monitors and rules using the data type specify the property bag values that they require.  Two samples are provided, one using Windows PowerShell and the other using VBScript.
The specific example expects XML in the description of an event.  This simulates a condition where all errors in the application create a Windows event with the same name number and source. The XML includes the specific number and description of the error.  The expected XML format is below.  Sample rules expect an event with a number of 101 and a source of EventCreate.  The EventCreate utility can be used to create sample events.
All rules and monitors are targeted at a class called MPAuthor.ProcessDataSource.PowerShell.Target or MPAuthor.ProcessDataSource.VBScript.Target.  This is discovered by creating a registry key at HKLM\SOFTWARE\MPAuthor\ProcessDataSource. This registry key must be on the same agent computer that the sample event is created on.

• Sample Management Pack - Registry Monitor

 This is a sample management pack for Operations Manager 2007 R2 and System Center 2012 Operations Manager.
This management pack provides an example of a monitor based on a registry value.  A monitor type is included that will periodically check a specified registry value and compare it to a desired value.  The monitor provides the path to the value, the duration to check, and the value to compare it to.
The included monitor checks the value at HKLM\SOFTWARE\MPAuthor\RegistryMonitor\TestValue and sets the monitor to a critical state if the value is not "ThisValue".  A different registry value and desired value can be used by changing the configuration of the monitor.
All rules and monitors are targeted at a class called MPAuthor.RegistryMonitor.Target.  This is discovered by creating a registry key at HKLM\SOFTWARE\MPAuthor\RegisterMonitor. This registry key must be on the same agent with the registry value being checked.

• Sample Management Pack - Linked Reports

 This is a sample management pack for Operations Manager 2007 R2 and System Center 2012 Operations Manager.
This management pack provides an example of linked reports.  Two linked reports are included as follows:
Availability Report - The user is not required to provide values for any of the parameters other than the objects.  The data included is from the previous seven days.  The dialog box to select the objects is filtered to only include instances of MPAuthor.LinkedReports.Target.
Performance Report - The user must select the object and date range but does not need to select the details of the report.  It is configured to include performance data from two rules - MPAuthor.LinkedReports.CollectScriptPerformance and MPAuthor.LinkedReports.CollectWMIPerformance.
All rules and monitors are targeted at a class called MPAuthor.LinkedReports.Target.  This is discovered by creating a registry key at HKLM\SOFTWARE\MPAuthor\LinkedReports. This registry key must be on at least one agent computer.  The sample rules and monitor will run on these agents.

• Sample Management Pack - Cookdown

 This is a sample management pack for Operations Manager 2007 R2 and System Center 2012 Operations Manager.
This management pack provides an example of workflows running scripts that support cookdown.  Two example rules are provided in both VBScript and PowerShell with with one supporting cookdown and the other not supporting cookdown.
The sample rules collect as performance data the file size for all files in a specified folder.  The rules are targeted at the class MPAuthor.Cookdown.File, so the agent will run a separate instance of the rule for every file.  The data source module for the rule not supporting cookdown requires the path of the file as a parameter.  Since this will be different for every instance, the module cannot cookdown.  The first data source module for the rule supporting cookdown also requires the file path, but this is used in a condition detection module.  The data source module running the script does not require this parameter.  Since the folder path parameter will be the same for all files, that data source module does cookdown.
Each rule will create an event in the Operations Manager event log to verify each running instance.  The rules that cookdown should create a single event while the rules not supporting cookdown should create multiple events.  Each of the rules is disabled and needs to be enabled before they run.
The event numbers created are as follows:
821 - No Cookdown - VBScript
822 - Cookdown - VBScript
823 - No Cookdown - PowerShell
824 - Cookdown - PowerShell
The discovery for MPAuthor.Cookdown.File is targeted at a class called MPAuthor.Cookdown.Target.  This is discovered by creating a registry key at HKLM\SOFTWARE\MPAuthor\Cookdown. This key must have a value named FolderPath that contains the path of the folder containing the files.  The folder must exist on the agent computer and contain one or more files to discover.

• Sample Management Pack - Discovery

 This is a sample management pack for Operations Manager 2007 R2 and System Center 2012 Operations Manager. 
This management pack provides several examples of different kinds of discovery. Several classes and relationships are included in the management pack to support the sample discoveries.   A basic description is provided for each below, and a more complete description is provided for each Discovery in the management pack.

- Registry Discovery
Creates an instance of a particular class if certain conditions are true.
- Script Discovery
Script to discover instances of a particular class. 
- Script Discovery for Unhosted Class
Script to discover instances of an unhosted class.
- WMI Discovery
WMI discovery to discover instances of a particular class. 
- Discover Containment Relationship with Script
Script to discover instances of a containment relationship.  A script is used because logic is required to parse the a property collected from a registry value.
- Discover Containment Relationship with Registry
Discover a containment relationship from registry values without using a script.  This discovery can only be used when the property value collected from the registry does not need to be parsed.
- Group Population for a Group
Uses GroupPopulator to populate a group with all instances of a particular class.
- Group Population for Distributed Application
Uses GroupPopulator to populate a distributed application with all instances of a particular class.
- Group Population for Computer Group
Uses GroupPopulator to populate the a group  with all instances of Microsoft.Windows.Computer that have an instance of another class.dfg

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007R2][OpsMgr 2012] Basic Troubleshooting Discovery Script

Do you ever get script errors from a discovery scripts?  Or you aren't discovering something that you feel should be discovered?

There are many ways to troubleshoot this discovery process, this will cover the “basics”.

Kevin Holman wrote an article here that explain how to retrieve a discovery script that is failing and how to execute it, passing the required parameter.The goal here is to get the script to run manually – and see if it throws an error, or returns the expected data.

Read the full article here

Stefan Stranger added some checks his help in his article :

1. Verify that MP has been committed on agent
2. Check agent for eventlog errors
3. Check management server for errors
4. Verify that discovery is running
5. Enable debug events in script
6. Debug script on agent

Read the full article here

In my side, the first article I've posted was :

[SCOM 2007] Authoring Management Pack - Create a VBS discovery with a debugging functionnality - PART I

With 2 others parts :

[SCOM 2007] Authoring Management Pack - Create a VBS discovery with a debugging functionnality - PART II

[SCOM 2007] Authoring Management Pack - Create a VBS discovery with a debugging functionnality - PART III

Hope wil all this references, troubleshooting a discovery will be easier for you !

This posting is provided "AS IS" with no warranties.

[SCOM 2007] Authoring Management Pack - Create a VBS discovery with a debugging functionnality - PART III

The first time the discovery script given in Part II is executed on a targeted machine, it try to read the debugging key in the registry.

If the key is not found, it creates a it in HKLM\SOFTWARE\Microsoft\Microsoft Operations Manager\Debugging.

The default value for the key is FALSE - That means that all the functions that are used for the debugging mode (See PART I) will not work.

If you want to activate the debugging mode on a specific server, just change the key value to TRUE on this server.

When discovery has run, you also have a property discovered in your main class that reflect the debug mode value.

It's now easy to work with the function that creates events in the Operations Manager Event Log in your script :

call sub_LogMPScriptEvent (10211, "My Event", Err, DebugModeValue,strMPScriptName,MOMEVENTLOGINFORMATION)

Where

- DebugModeValue is set with the value of the registry key created/read by the discovery

- strMPScriptName is the name of the discovery script

- MOMEVENTLOGINFORMATION is set with value 0

- 10211 will be the event number created in Operations Manager Event log.

Why using this debug mode : 

Last time I've used this key was to understand why my discovery script was well working when I was launching the VBS with a cscript with parameter in a shell (no script issue, property bags were set) but when the Discovery was lauched by SCOM, nothing was discovered !

I've also create an event that give all the variable used to set the property bags, imported the new MP, change the key on the server to set the debug mode to TRUE and force the discovery.

Analysing the Operations Manager log show me that I' was using a variable that didn't reflect the computer name and was always set to the same value... meaning that SCOM was not abled to discovers the services for the computer name since the computer name had a false value.

I've change the script to use the good displayName for the computer and tested it. The discovery was always working with no errors but this time, services were discovered ! :)

If you have any question, don't hesitate to contact me.

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007 R2][OpsMgr 2012] Authoring performance collection rules for cluster disks – the *RIGHT* way.

Kevin Holman has published a very interesting article on his blog : >>>   Here   <<<

He recently wrotes about the Windows Server Operating System Management pack version 6.0.6989.0 HERE.  In the “known issues” section of that article – He discussed that the MP is solid – except there are no performance collection rules for cluster disks, such as latency, or free space, to leverage in your reports.

We now have three different types of common disks in Windows servers (Logical Disks, Cluster Disks, and Cluster Shared Volumes).  This means we have to have three different sets of rules targeting each class, for collecting performance data. 

This article will be a walk through on how to correctly create performance collection rules, to collect performance data from Cluster disks.  It can be used as an example on how to collect performance data from any multi-instance object.

For the community – He has attached his Addendum management pack below, so you can use it as a guide or optionally modify it/seal it and use it directly.

Microsoft.Windows.Server.ClusterSharedVolumeMonitoring.Addendum.zip

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007R2][OpsMgr 2012] MP Authoring: Targeting RMS or MS?

Tao Yang has created a new script for SDK connection to be able to use the same script on a SCOM 2007 and on a SCOM 2012. Basically, the script now reads the default SDK service computer name from the registry of each management server and connect to this SDK machine instead of local computer. in 2007, this registry value points to RMS and in 2012, it points to the management server itself.

Read more on his blog

This posting is provided "AS IS" with no warranties.

[OpsMgr 2012] Boris Yanushpolsky 's Tools updated for OpsMgr 2012 by Daniele Muscetta - New update

Thanks once again Daniele and Boris for their job.

In order to not let those tools go to waste, since many people use them, Daniele Muscetta have asked Boris Yanushpolsky to give him the code of his tools and allow him to update and maintain those tools going forward.

Here is the last update from Daniele on August 29th 2012  : MPViewer 2.1.2 contains fixes to show Perf Objects, Counters and Frequency for some more modules.

Get lastest updates directly on : http://blogs.msdn.com/b/dmuscett/archive/2012/02/19/boris-s-tools-updated.aspx

• MPViewer

The previous version 1.7 (that works with OpsMgr 2007 and 2007 R2) was released here. Version 2.1.2 has been updated to work with OpsMgr 2012, and now includes support for MPB files (MP Bundles) as well as the ability to Unseal and Unpack MP Bundles.
Warning: only MP Bundles that contain a single ManagementPack are supported; there are some Service Manager MPBs that contain multiple ManagementPacks in a single bundle, and this tool currently cannot deal correctly with those.

• OverrideExplorer

The previous version 3.3 (that works with OpsMgr 2007 and 2007 R2) was released here. Version 3.5 has been updated to work with OpsMgr2012 and includes some minor fixes, as well as the capability to Export all overrides to an Excel spreadsheet.

• Proxy Settings

The previous version 1.1 (that works with OpsMgr 2007 and 2007 R2) was released here. Version 1.2 is functionally identical to the previous version but has been just recompiled to work with OpsMgr 2012 SDK.



All the above tools require the Operations Manager Console being installed on the machine where you run them, as well as the .NET framework 4.0.
According to my information, the above three tools were the most used/useful. Feel free to comment if need any other one being updated and/or have bug reports or feature requests – albeit I don’t promise I will be able to fix or update everything
Disclaimer
Just like their predecessors, it is necessary to make clear that this posting is provided "AS IS" with no warranties, and confers no rights.
Use of included utilities are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
Changelog / Updates
[Updated on March 8th 2012 with MPViewer 1.9.1 that contains a fix for the Excel export of some MPs]
[Updated on March 15th 2012 with MPViewer 2.0 that now allows you to Unseal/Unpack MPs and MPBundles]
[Updated on March 21st 2012 with OverrideExplorer 3.5 which now allows to export Overrides to Excel]
[Updated on July 19th 2012 with MPViewer 2.1 that now shows the PublicKeyToken for referernces/dependencies]
[Updated on August 29th 2012 with MPViewer 2.1.2 that contains fixes to show Perf Objects, Counters and Frequency for some more modules]

Sources : http://blogs.msdn.com/b/dmuscett/archive/2012/02/19/boris-s-tools-updated.aspx

This posting is provided "AS IS" with no warranties.

[OpsMgr 2012] Wait is over ! We can now download the new SCOM authoring tools

Here we are ! VMPD and VSAE tools are available ! Remember I had posted that documentation was accessible on the Technet but the tools were not released ! It's now done !

What a good new ! I'll test them as soos as possible !

The System Center 2012 Visio MP Designer—VMPD—is an add-in for Visio 2010 Premium that allows you to visually design a System Center Operations Manager Core Monitoring Management Pack.

Version:

1.0 CTP1

Date published:

6/28/2012

File name	Size
MPDesigner.Installer_x64.msi	4.6 MB	Download
MPDesigner.Installer_x86.msi	4.6 MB	Download

Overview

The System Center 2012 Visio MP Designer—VMPD—is an add-in for Visio 2010 Premium that allows you to visually design a System Center Operations Manager Core Monitoring Management Pack. VMPD generates a Management Pack that is compliant to the MP Authoring Best Practices by simply dragging and dropping Visio shapes to describe your application architecture and configuring them through the Shape Properties.

Feature Summary

• Visually describe your application architecture which generates classes and discoveries.
• Visually add monitoring to create monitors and rules.
• Start quickly from our pre-canned single server and multi-server patterns.  

System requirements

Supported operating systems: Windows 7, Windows 8 Release Preview, Windows Vista

• Other Software: Microsoft Visio Premium 2010

Instructions

1. Download the MSI that corresponds to the version of Microsoft Office you have. (Most customers have the 32-bit version of Office.
2. Ensure Microsoft Visio Premium 2010 is not running.
3. Execute the MSI to install.
4. Open Microsoft Visio Premium 2010. Click File --New -- then the Software and Database category -- then System Center Operations Manager Core Monitoring Management Pack.

The System Center 2012 Visual Studio Authoring Extensions—VSAE—is an add-in for Visual Studio 2010 Professional provides Lifecycle Management Tools to support Management Pack Authoring.

Version:

1.0

Date published:

6/28/2012

File name	Size
VisualStudioAuthoringConsole.msi	20.5 MB	Download

Overview

The System Center 2012 Visual Studio Authoring Extensions—VSAE—is an add-in for Visual Studio 2010 Professional provides Lifecycle Management Tools to support Management Pack Authoring.

Feature Summary

• VS Projects for Monitoring MPs, System Center 2012 MPs including Operations Manager and Service Manager.
• MP Item Templates for quick creation of MP Items.
• XML MP Item Templates (generates MP XML for editing).
• Template Group Item Templates (Abstract your intent from MP XML).
• Snippet Templates (generates MP XML from CSV)
• IntelliSense for MP XML for the following versions:
• System Center Operations Manager 2007 R2
• System Center 2012 Operations Manager
• System Center 2012 Service Manager
• Integrates into Visual Studio Project System with *.mpproj.
• Enables building within VS & MSBuild.
• Supports custom build tasks (simply edit *.mpproj or *.sln)
• Build multiple MPs (multiple *.mpproj) in a solution.
• Integrates into any VS supported Source Control systems.
• MP Navigation Features
• Management Pack Browser for browsing MP Items.
• Go to Definition
• Find All References
• ResKit Tools integrated
• Workflow Simulator
• Generate Visio Diagram
• MP Best Practice Analyzer
• MP Spell Checker
• MP Cookdown Analyzer

System requirements

Supported operating systems: Windows 7, Windows 8 Release Preview, Windows Vista

• Other Software: Microsoft Visual Studio 2010 Professional or higher

Instructions

1. Download the MSI.
2. Ensure Microsoft Visual Studio 2010 Professional is not running.
3. Execute the MSI to install.
4. Open Microsoft Visual Studio 2010 Professional. Click File - New - Project - Management Pack.

This posting is provided "AS IS" with no warranties.

[OpsMgr 2012] 10 reasons NOT to use the Visual Studio Authoring Extensions VSAE

Amazing title given by Michel Kamp in his weelkly post ! Something that we all think that he shouldn't write this. Of courses, it was just to have your attention. Insteresting post to read - it gives some functionalities with screenshots !

Also here are the 10 reasons to use the VSAE tool for MP authoring  :

• SourceSafe integration
• MP object viewer
• Find references
• Simulating your workflows
• Jump to referenced MP objects.
• Intellisense
• Build and deploy
• Management objects templates
• Convert your ‘old’ OM07 MPs
• It just a must have.

He will continue to write about the tons of great features that are build in the VSAE.

Read more on the original post.

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007R2] Where is my created group gone - Cannot retrieve my group to apply overrides

Issue :
Suppose a group is created in a non-sealed MP. A discovery is created in a other unsealed MP with the enable state by default to false. You want to override the discovery for the group created in the first non-sealed MP.
SCOM interface doesn't show you all the groups and you cannot retrieve your group !

The reason is an unsealed MP cannot be referenced by any other MP

3 ways to solve this issue :

1. Create the group in the same MP that contains the rule/monitor or discovery to override
2. Seal the MP that contains the rule/monitor or discovery - Overrides will be stored in the non-sealed MP that contains the group. Reference to the sealed MP will be created in the non-sealed MP.
3. Seal the MP that contains the group - Overrides will be stored in the non-sealed MP that contains the overrided rule/monitor or discovery. One limitation will be that the group will only accept new members only if it's a dynamic populated group.Reference to the sealed MP will be created in the non-sealed MP.

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007] How to create a group of all Windows Computers that are NOT a member of another group

Kevin Holman has pushished a post few weeks ago that is very interesting since it answers a pretty common request.

>>>>>>>>>> Click Here to open the original post <<<<<<<<<<

Suppose you have the following scenario:  You are monitoring 1000 Windows Server with OpsMgr.  In your management group, you have 100 servers that are Test/Dev machines, and you have 900 that are production.  You need a simple way to treat these servers differently, for overrides, and creating notifications or incidents, or even scoping your views.  You want to ensure that you don’t send critical pages, emails, or create incidents on these lab/test/dev machines.

The challenge is – our notifications, views, and overrides don’t have the ability to have an “exclude” function… to say “show me everything except alerts from these machines”

Once again, thanks to Kevin ! :)

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007] How to create a group of objects that are contained by an other group

First I would like to thanks Kevin Holman for his post http://blogs.technet.com/b/kevinholman/archive/2010/09/09/how-to-create-a-group-of-objects-that-are-contained-by-some-other-group.aspx

I've work on the MP he has provided is his post and added 3 groups to answer this interesting customer request.

The request was to be able to make an override on the monitor "Percentage of Committed Memory in Use" in the OS MP for all SQL servers. Not so easy to do it since you retrieve at least 3 monitors "Percentage of Committed Memory in Use" - one in each Windows Server xxxx Operating System class. We have also to build 3 groups, one per OS version.

And to be really clean, I have to create 3 dynamic groups that contains Operating System.objects - one by OS version. Dynamic groups because customer asked the override to be created for all SQL servers monitored.

1. One group of Operating System = 2008 and server is SQL server
2. One group of Operating System = 2003 and server is SQL server
3. One group of Operating System = 2000 and server is SQL server

As explained by Kevin, this is not doable within the SCOM console, you have to edit group in the authoring console.

The way to proceed will be the same as the one explained by Kevin. I've also add some other references to the Microsoft Windows Server xxxx MPs :

Then you are able to create 3 classes OS2000GroupSQL, OS2003GroupSQL and OS2008GroupSQL and the 3 associated discoveries:

1. Populate OS Group – SQL – 2008 Server
2. Populate OS Group – SQL – 2003 Server
3. Populate OS Group – SQL – 2000 Server

For each discovery, choose a target class, which will be the Group class we just created earlier. Select the “Discovered Classes” tab and add Microsoft.SystemCenter.InstanceGroupContainsEntities in the “Discovered relationships and their attributes”.
Then select the Configuration tab, Browse for a Type and select Microsoft.SystemCenter.GroupPopulator. Give a module ID - then you may have an error that must be ignored.
On the configuration screen – select “Edit”
We will be replacing the XML showing in Notepad with an example I have written.  Highlight all but the first line and delete it.

Then paste this for the 2008 discovery :

<RuleId>$MPElement$</RuleId>
  <GroupInstanceId>$MPElement[Name="Custom.Group.Example.OS2008GroupSQL"]$</GroupInstanceId>
  <MembershipRules>
    <MembershipRule>
      <MonitoringClass>$MPElement[Name="Server2008!Microsoft.Windows.Server.2008.OperatingSystem"]$</MonitoringClass>
      <RelationshipClass>$MPElement[Name="MicrosoftSystemCenterInstanceGroupLibrary!Microsoft.SystemCenter.InstanceGroupContainsEntities"]$</RelationshipClass>
      <Expression>
        <And>
          <Expression>
            <RegExExpression>
              <ValueExpression>
                <Property>$MPElement[Name="Windows!Microsoft.Windows.OperatingSystem"]/OSVersionDisplayName$</Property>
              </ValueExpression>
              <Operator>ContainsSubstring</Operator>
              <Pattern>2008</Pattern>
            </RegExExpression>
          </Expression>
          <Expression>
            <Contained>
              <MonitoringClass>$MPElement[Name="Windows!Microsoft.Windows.Computer"]$</MonitoringClass>
              <Expression>
                <Contained>
                  <MonitoringClass>$MPElement[Name="MicrosoftSQLServerLibrary!Microsoft.SQLServer.ComputerGroup"]$</MonitoringClass>
                </Contained>
              </Expression>
            </Contained>
          </Expression>
        </And>
      </Expression>
    </MembershipRule>
  </MembershipRules>
</Configuration>


Save the discovery, save your MP and import it in your DEV environment ! :)

You will be able to retrieve your new group in the authoring part :
Note I've keep the group created by Kevin.

Just right click on it and select “View Group Members” - the group OS Group - SQL - 2008 Server should be populated with OS 2008 objects corresponding to SQL server installed in Windows server 2008 or 2008 R2 and all other version.



You can download my MP for testing purpose here in this folder

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007] Best practices to use for creating and configuring overrides

Here are some best practices given by Microsoft to configure overrides in Operation Manager 2007.

Store overrides in a separate management pack

For each management pack that you use in System Center Operations Manager 2007, create an additional management pack in which to store overrides. For example, after you import the Active Directory management pack, create an Active Directory Override management pack. Then, store any overrides that you configure for the Active Directory management pack objects in the Active Directory Override management pack.

Do not use the Disable command in the Overrides menu to create an override to disable monitors, rules, or object discoveries

When you want to disable a management pack object, do not use the Disable the ObjectName command on the Overrides menu. Instead, click the Override option to override the object. Then, follow these steps:

1. In the Override Properties dialog box, click to select the Override check box that corresponds to the Enabled parameter.
2. In the Override Setting column, click False.
3. In the Select destination management pack list, click the appropriate management pack in which to store the override.

Note This method lets you specify a management pack in which to create the override. However, if you click the Disable the ObjectName command, System Center Operations Manager 2007 creates the override in the Default management pack.

Make sure that an overridden parameter is set for every rule and for every monitor that uses the parameter

When you override a parameter, make sure that the parameter is configured for each rule that uses the parameter and for each monitor that uses the parameter. There may be more than one rule or monitor that uses the particular parameter.

For example, the following rules and monitors use the Intersite Expected Max Latency parameter:

Monitors

• AD Replication Monitoring

Rules

• AD Replication Performance Collection - Metric Replication Latency
• AD Replication Performance Collection - Metric Replication Latency: Maximum
• AD Replication Performance Collection - Metric Replication Latency: Minimum
• AD Replication Performance Collection - Metric Replication Latency: Average

For more information about the rules and monitors that use the same parameters, see the "AD and Exchange Script Mappings" document. To obtain this document, download the ADExchMP_script_map.zip package on the following Web site: http://systemcenterforum.org/wp-content/uploads/

Configure overrides for groups instead of for specific instances

We recommend that you configure an override for a group instead of using an override to target a specific instance. Configuring overrides for groups allows for better manageability than what is available if you target a specific instance. To configure an override for a group, follow these steps:

1. Create a group that has the following characteristics:
   • Create the group in the appropriate overrides management pack.
   • Configure the group to contain the particular instances or formulas that target the instances that you want to override.
   For example, create a group that is named AD DC 2003 Role. Then, manually put instances of the AD Domain Controller 2003 Role objects into the AD DC 2003 Role group.
2. Click the For a group command on the submenu of the Overrides menu.
3. In the Select Object dialog box that appears, click the new group that you created.

Test overrides by using an override management pack and groups in a test environment

You can test overrides in one environment and then apply the overrides to another environment. For example, you can test an override in a test environment and then implement the override in a production environment. To do this, follow these steps:

1. Create the test groups in the appropriate override management pack.
2. Add the appropriate instances from the test environment to the test groups. You can explicitly specify the instances. Or, you can use a formula to specify the instances.
3. Perform sufficient testing to validate the override.
4. Export the particular management pack from the test environment.
5. Import the override management pack into the production environment.
6. Populate the groups that are contained in the override management pack by using the appropriate instances from the production environment.

See http://support.microsoft.com/kb/943239 published on December 2007.

This posting is provided "AS IS" with no warranties.

[OpsMgr 2012] Boris Yanushpolsky 's Tools updated for OpsMgr 2012 by Daniele Muscetta

First I would like to thanks Daniele and Boris for their job.

In order to not let those tools go to waste, since many people use them, Daniele Muscetta have asked Boris Yanushpolsky to give him the code of his tools and allow him to update and maintain those tools going forward.
Here is the result of Danielle's Job - the 3 tools bellow are now working with OpsMgr 2012:

Get Latest updates directly on http://blogs.msdn.com/b/dmuscett/archive/2012/02/19/boris-s-tools-updated.aspx

• MPViewer : The previous version 1.7 (that works with OpsMgr 2007 and 2007 R2) was released here. Version 1.9 has been updated to work with OpsMgr 2012, and now includes (limited) support for MPB files (MP Bundles)

• OverrideExplorer : The previous version 3.3 (that works with OpsMgr 2007 and 2007 R2) was released here. Version 3.4 has been updated to work with OpsMgr2012 and includes some additional, minor, fixes.

• Proxy Settings : The previous version 1.1 (that works with OpsMgr 2007 and 2007 R2) was released here. Version 1.2 is functionally identical to the previous version but has been just recompiled to work with OpsMgr 2012 SDK.

Requirement : Operation Manager console + .NET framework 4.0 must be installed on the machine you use to run the tools

Don't hesitate to comment or report bugs to Daniele Muscetta - He will try to fix and update everything.

Remark : Just like their predecessors, it is necessary to make clear that this posting is provided "AS IS" with no warranties, and confers no rights. Use of included utilities are subject to the terms specified at http://www.microsoft.com/info/copyright.htm

This posting is provided "AS IS" with no warranties.

[Authoring MP] MPBPA analysis tool always report "Alerts should have name and description defined"

This is related to the alert configuration. You must verify that

• when you open a rule, switch to configuration and check what is missing in the alert section.
• If it's not there, check display name and description for the alert.

If you have separated out your strings into a language pack instead of putting the english strings into the base MP, then you will have to live with this error.
A best practice should be to have a base MP contains only the ENU strings.

This posting is provided "AS IS" with no warranties.

[SCOM 2007 R2] Authoring Console ask for Microsoft.SystemCenter.Library version 6.1.7221.61 for editing a MP

Article ID: 2590414 - Last Review: November 14, 2011 - Revision: 3.0
KB only applicable to if CU4 or later is installed.
 You are prompted for the latest version of the Microsoft.SystemCenter.Library management pack when you try to edit a new management pack in the Authoring Console in Microsoft System Center Operations Manager 2007 R2 after you install Cumulative Update 4 (CU4) or later versions.

Root cause : This issue occurs because new management packs that are imported or created automatically in Operations Manager 2007 R2 after you install Cumulative Update 4 or later versions have a dependency on the latest version of the Microsoft.SystemCenter.Library management pack (The latest version of the Microsoft.SystemCenter.Library management pack may be version 6.1.7221.61 or a later version).

Resolution :To resolve this issue, download the latest version of the Microsoft.SystemCenter.Library management pack from the Microsoft Download Center, then extract the management pack and copy it to the following folder:%ProgramFiles%\System Center MP Authoring Console 2007
The next time that you use the Authoring Console to edit a new management pack, you will not be prompted for the Microsoft.SystemCenter.Library management pack.



>>>>>>>>>> Download the file here (Microsoft WebSite) <<<<<<<<<<

For more information please read the microsoft web page http://support.microsoft.com/kb/2590414

This posting is provided "AS IS" with no warranties.

[SCOM 2007] Authoring Management Pack - Create a VBS discovery with a debugging functionnality - PART II

Now we have all needed function (see PART I of this article), we can create a new Management Pack by using the authoring console.

Create a new MP with the Authoring Console : MyNewMP.xml witha "Microsoft.Windows.Local Application" Class nammed MyNewMP.CLS1.

Add a new property to this class : DebugMod

Then create a new discovery MyNewMP.DSC1 that target Microsoft.Windows.Server.Computer and discover the class MyNewMP.CLS1 and all its attributes.

Choose the disovery type : Microsoft.Windows.TimedScript.DiscoveryProvider and schedule it once a day and call your script MyNewMP.DSC1.script.vbs. Click on Parameters and add 3 parameters like :

$MPElement$ $Target/Id$ $Target/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$

In the Script field you will have to paste the discovery script below :

1. First part of the discovery script is to declare and set the variable
2. Option Explicit
3. SetLocale("en-us")
4. '-----------------------------------------------------------------------------------------------------
5. ' DEFAULT VARIABLES AND CONST - Used by the debuging functions and sub
6. '-----------------------------------------------------------------------------------------------------
7. Const REGKEYPATH = "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\Debugging"
8. Const REGISTRYDEFVALUE = "FALSE"
9. Const MOMEVENTLOGERROR = "1"
10. Const MOMEVENTLOGWARNING = "2"
11. Const MOMEVENTLOGINFORMATION = "4"
12. Dim intIndex
13. Dim strRegValue
14. Dim strRegKeyName
15. Dim strMPScriptName
16. Dim strCurrentDebugModeValue
17. Dim oAPI
18. Dim oInst
19. Dim oArgs
20. Dim oDiscoveryData
21. '-----------------------------------------------------------------------------------------------------
22. ' SET THE FOLLOWING VALUES ACCORDING TO YOUR MANAGEMENT PACK
23. '----------------------------------------------------------------------------------------------------
24. strMPScriptName = "MyNewMP.DSC1.vbs"
25. strRegKeyName = "Verbose.MyNewMP"
26. '-----------------------------------------------------------------------------------------------------
27. ' Create the object that connect to MOM API
28. Set oAPI = CreateObject("MOM.ScriptAPI")

The second part of the discovery will be dedicated to all function seens in Part I of this article :

1. '-----------------------------------------------------------------------------------------------------
2. ' DEFAULT FUNCTIONS - Used for Management Pack debugging
3. '-----------------------------------------------------------------------------------------------------
4. Private Function fct_ReadRegistryKey(ByVal strKeyPath, ByVal strKeyName)
5. 'Read Registry key located on KeyPath\KeyName
6. 'Returns the value of a registry key and eventually a no-value to identify that the key does not exists.
7.            Dim oWshShell
8.             Dim strRegReadValue     'Contains the value of the Registry Key
10.             'Try to read the registry key located to strKeyPath\strKeyName
11.             On Error Resume Next
12.             Set oWshShell = CreateObject("Wscript.Shell")
13.             strRegReadValue = oWshShell.RegRead(strKeyPath &"\" & strKeyName)
15.             'If an error is raised Then we a no-value to identify that the Registry Key does not exist.
16.             If err.number <> 0 Then
17.                         strRegReadValue = ""
18.             End if
20.             On error goto 0
21.             fct_ReadRegistryKey = UCase(strRegReadValue)
23. End Function
24. '-----------------------------------------------------------------------------------------------------
26. Private Function fct_WriteRegistryKey(ByVal strKeyPath, ByVal strKeyName, ByVal strKeyValue)
27. ' Write a Registry value to strKeyPath\strKeyName with value strKeyValue
28. ' blnKeyEdit is set to True or false in case of error.
29.             Dim blnKeyEdit
30.             Dim oWshShell
31.             blnKeyEdit = false
33.             'Try to set strKeyValue to the registry key strKeyPath\strKeyName
34.             On Error Resume Next
35.             Set oWshShell = WScript.CreateObject("WScript.Shell")
36.             oWshShell.RegWrite strKeyPath & "\" & strKeyName , UCase(strKeyValue)
38.             'If setting the registry key strKeyValue is OK Then the function will return a string TRUE.
39.             If err.number = 0 Then
40.                         blnKeyEdit = true
41.             End if
42.             On error goto 0
44.             fct_WriteRegistryKey = blnKeyEdit
45. End Function
46. '-----------------------------------------------------------------------------------------------------
48. Private Sub sub_LogMPScriptEvent(ByVal intErrNumber, ByVal strEventLogMessage, ByRef objError, ByVal strDebugMod, ByVal strScriptName, ByVal strMomEventLevel)
49. ' Log an event in the OperationManager eventLog of the server if it is in debug mode
50. ' It will allow to trace the debugging process of the script of the Management Pack by logging errors and parameters values
52.             Dim strMessage
53.              strMessage=""
54.              'If the debug mode is ON, an event is logged in the Operation Manager eventLog.
55.             If ucase(strDebugMod) = "TRUE" Then
56.                         strMessage = strEventLogMessage & vbCrLf & " " & vbCrLf & _
57.                         "Error number:" & vbTab & CStr(objError.Number) & vbCrLf & _ 
58.                         "Error description:" & vbTab & objError.Description
59.             Call oAPI.LogScriptEvent(strScriptName, intErrNumber, strMomEventLevel, strMessage)
60.             End if
61. End Sub
62. '-----------------------------------------------------------------------------------------------------
64. Private function fct_LogRunningAccount(ByVal strDebugMode)
65. ' Log an event in the OperationManager eventLog of the server if it is in debug mode
66. ' It allows to know under which credentials the script is executed
68.             Dim owshNetwork
69.             Dim strRunningUserID
71.             On Error Resume Next
72.             Set owshNetwork = WScript.CreateObject("WScript.Network")
74.             'Assign user name returned to a variable
75.             strRunningUserID = owshNetwork.UserName
76.             
77.             call sub_LogMPScriptEvent (4005, "sub_LogMPScriptEvent. Script running as user: " & strRunningUserID , Err, strDebugMode,strMPScriptName,MOMEVENTLOGINFORMATION)
79.             On error goto 0
80.             fct_LogRunningAccount = strRunningUserID
81. End Function
82. '-----------------------------------------------------------------------------------------------------
84. private sub sub_LogScriptStartInfo(byRef oArgs, byVal strDebugModeValue, byval strMomLevelEvent, byVal strScriptName)
85. ' Log an event with the default informations. The event contains :
86. ' - The account used to run the script
87. ' - The number of script parameters
88. ' - The values of the parameters
89. ' - The value of the debug mode
91.             Dim owshNetwork
92.             Dim strLogMessage
93.             Dim strRunAsAccount
95.             On Error Resume Next
96.             Set owshNetwork = WScript.CreateObject("WScript.Network")
98.             'Assign user name returned to a variable
99.             strRunAsAccount = owshNetwork.UserName
100.              strLogMessage=""
102.             ' Create the start log Script with launch information data RunAs account, debugmode, arguments)
103.             strLogMessage = vbcrlf & "The script has been launched under following credentials : " &             strRunAsAccount & "." & vbcrlf & vbcrlf & oArgs.count & " arguments have been passed in parameter : "
105.             For intIndex = 0 To oArgs.Count-1
106.                         strLogMessage = strLogMessage & vbcrlf & " - " & oArgs(intIndex)
107.             Next
109.             strLogMessage = strLogMessage & vbcrlf & vbcrlf & "The debug mode value for the Management Pack is set to : " & strDebugModeValue
111.             Call oAPI.LogScriptEvent(strScriptName, 10212, strMomLevelEvent, strLogMessage)
112. End sub
113. '-----------------------------------------------------------------------------------------------------

 And the next part of the discovery will be the main part that will test the number of arguments and create / read the debugging registry key :

1. '-----------------------------------------------------------------------------------------------------
2. ' MAIN CODE START HERE
3. '-----------------------------------------------------------------------------------------------------
4. ' Gets the arguments passed in parameters of the script
5. Set oArgs = Wscript.Arguments
6. ' If the minimals arguments are not set then we exit the script
7. if oArgs.Count < 3 Then
8.    Wscript.Quit -1
9. End If
10. ' Check the value of the registry key on the server to know if the debug mode is ON or not

strRegValue = ""

11. 'By default the registry key is set to : DOES NOT EXIST. See fct_ReadRegistryKey for more information
12. strRegValue = fct_ReadRegistryKey(REGKEYPATH, strRegKeyName)
13. 'If the registry key is TRUE XOR FALSE then the debugmodevalue has a good value
14. If ((strRegValue = "TRUE") Xor (strRegValue = "FALSE")) Then
15.             strCurrentDebugModeValue = strRegValue
16. Else
17.             'If the registry key is empty or not correctly set then a attempt to set to default value is made.
18.             If fct_WriteRegistryKey(REGKEYPATH, strRegKeyName, REGISTRYDEFVALUE) Then
19.                         ' write event 10211 that says the registry key has been created
20.                         call sub_LogMPScriptEvent (10211, "Registry Key " & REGKEYPATH & "\" & strRegKeyName & " With Value = " & REGISTRYDEFVALUE & " has been created", Err, True,strMPScriptName,MOMEVENTLOGINFORMATION)
21.             Else
22.                         ' write event 10210 that says the registry key has not been created
23.                         call sub_LogMPScriptEvent (10210, "Error in creation of the Registry Key " & REGKEYPATH & "\" & strRegKeyName & " With Value = " & REGISTRYDEFVALUE , Err, True,strMPScriptName,MOMEVENTLOGERROR)
24.             End if
25.             strCurrentDebugModeValue = REGISTRYDEFVALUE
26. End if The discovery itself : 'Return Data to the Management PackCall oDiscoveryData.AddInstance(oInst)

Call oAPI.Return(oDiscoveryData)

29.  
30. Dim intSourceType
31. Dim strSourceId0
32. Dim strTargetComputer
33. Dim strManagedEntityId
34. intSourceType =
35. 'Set the arguments for creating the default Management Pack modules.strSourceId = oArgs(0)
36. strManagedEntityId = oArgs(1)
37. strTargetComputer = oArgs(2)
38. 'Create the default management pack classSet oDiscoveryData = oAPI.CreateDiscoveryData(intSourceType, strSourceId, strManagedEntityId)
39. Set oInst = oDiscoveryData.CreateClassInstance("$MPElement[Name='MyNewMP.CLS1']$")
40. call oInst.AddProperty("$MPElement[Name='Windows!Microsoft.Windows.Computer']/PrincipalName$", strTargetComputer)
41. call oInst.AddProperty("$MPElement[Name='System!System.Entity']/DisplayName$", "MyNewMP")
42. call oInst.AddProperty("$MPElement[Name='MyNewMP.CLS1']/DebugMod$", strCurrentDebugModeValue)
44.  
45. call sub_LogMPScriptEvent (10213, "Server "& strTargetComputer & " has been discovered. The debug mode value on this server is set to " & strCurrentDebugModeValue, Err, strCurrentDebugModeValue,strMPScriptName,MOMEVENTLOGINFORMATION)
46. '-----------------------------------------------------------------------------------------------------
47. ' PUT YOUR DISCOVERY CODE AFTER
48. '-----------------------------------------------------------------------------------------------------
49. 'Return Data to the Management PackCall oDiscoveryData.AddInstance(oInst)
51. Call oAPI.Return(oDiscoveryData)

'Log the Management Pack default informations with runas account, debugmode and parameters info call sub_LogScriptStartInfo(oArgs, strCurrentDebugModeValue, MOMEVENTLOGINFORMATION, strMPScriptName)

How to use the debugging functionnality will be explained in PART III

End of PART II

Back to Part I                                                                                         Go to Part III

This posting is provided "AS IS" with no warranties.