SCOM Management Pack Creator V3.0 New Features

Dujon Walsham • 14 June 2019

Whats New in V3.0

The SCOM Management Pack Creator V3.0 is now completed and now entering the testing phase which will then be aimed to be released sometime in June.

Below is a list of all of the new features in this version which is a very big development change in its previous versions structure.

Now an Importable Module!

The SCOM Management Pack Creator latest version is now a fully importable module.

So this means that you can now use CMDlets to build out the entire management pack and can perform not only each part or the whole management pack individually, this applies to management packs which would use custom classes as well as default management packs which would be applicable to i.e. WindowsComputer classes etc

The wizard functions which you see in the previous version still works alongside this module. So you have the option to run the function which can build the MP in a Wizard fashion or you can run functions individually to create any part of the management pack you require.

Functions also contain help messages now when prompted press !? for more information.

Management Pack Family Creation

Another wizard function has now been added to the solution which will allow you to build a Management Pack family.

For example in a lot of management pack releases you will get the following;

  • Library Management Pack
  • Discovery Management Pack
  • Monitoring Management Pack
Where each consist of there own individual sets of classes, now the SCOM Management Pack Creator V3.0 will be able to build your management packs split into individual management packs with references built-in so they know which MP to refer to.

New Powerful function - Get-SCOMClassID CMDLet

A new function has been added which is called Get-SCOMClassID

The power of this function is with in conjunction to completing management pack builds on different functions which accept a pipeline and also accept a parameter with pipeline property name.

For example this command has switches to obtain the following;

  • File which contains the Classes
  • File which contains the folder classes
Once entered, this command can dynamically see every single class in any file which you choose which is great if you dont want to investigate a management pack to find what name you gave the class as this can dynamically display the list and select for you. Then add to part of the command and use to pipeline to another command.


Output Files now in .MPX files

The previous version had the outputs in .XML files, which was a good way to copy the output and place into your Visual Studio Project.

Now this has been changed, so now all of the outputs will be in .MPX files which allows you to import the MPX file directly into your Visual Studio Management Pack project without having to copy anything across.

Multiple Discoveries or Multiple Monitors can be added to one .MPX file

Though the previous version multiple discoveries and monitors could be created. But the only limitation was that they could only contain one discovery or monitor per .XML file.

This has now been changed, so now in a wizard form or function form you can now add as many as you want into one .MPX file which makes it a lot easier when creating discoveries or monitors.

Additional Monitors Added

The Windows Event Manual Reset and Timer Rest monitors have now been added into the module.

UNIX/Linux Support

You can now create discoveries, monitors and tasks for any UNIX/Linux computers which you are monitoring within SCOM.

Creation of Tasks

You can now create Agent Based Tasks in the module.

This is available for both Windows and UNIX/Linux systems.

Creation of Diagnostic/Recovery Tasks

You can now create Diagnostic and Recovery tasks which can be added to any of the monitors which you have.

Product Knowledge Article Linking

Each Monitor or Discovery you create can now have a Knowledge base article attached it. These are optional fields so you can enter a null value if you wish for this not to be created.

Bug Fixes

  • Add-SCOMMPWindowsPowerShellScriptRule - Part spelling mistakes or misplacements have now been corrected.
  • Discoveries contained properties of classes which had no TypeID attached to them
  • Script or function would fail if Null Value was given.

Microsoft Endpoint Manager: In-Place Upgrade or Side by Side Part 4 - SQL Server Requirement Analysis

by D Walsham • 13 December 2021
Looking through the current SQL Server topology and how it affects our decision

Microsoft Endpoint Manager: In-Place Upgrade or Side by Side Part 3 - Current Branch Upgrade Approaches

by D Walsham • 19 November 2021
Impact of Current Branch Upgrades

Microsoft Endpoint Manager: In-Place Upgrade or Side by Side - Part 2 - Operating System Considerations

by D Walsham • 29 October 2021
Introduction

Microsoft Endpoint Manager: In-Place Upgrade or Side by Side

by D Walsham • 7 October 2021
Introduction

Endpoint Manager: Device Estate Cleanup

by D Walsham • 6 October 2021
Introduction

Modern Workplace Management: Creating Applications Common Practices - LOB vs Win32 Package

by D Walsham • 3 September 2021
Introduction

Modern Workplace Management: Build Endpoints Without SCCM Part 6

by D Walsham • 12 August 2021
All the parts of the series we went into great detail about how we analyse an end to end solution and how we would design a solution in which would allow us to build endpoints without SCCM being a dependency. Whilst we did this, there is another scenario which we have not touched on yet, which is the hybrid scenarios. In a perfect world ideally you would have your Azure Active Directory within the cloud, every machine meets the recommended requirements for Windows 10, everything is imported into Intune/Autopilot and everyone is happy. But we know this isn't realistic in all cases. Many organisations cannot just simply up and go from on-premise into the cloud therefore the checkpoint here is of course getting into hybrid solutions such as; Co-Management Between Intune and SCCM Hybrid AD with Azure AD and On-Premise AD syncing together These things can play a very interesting part in how you would tackle this if you envisage the next step in the blueprint is to be in a position in which you can build and manage endpoints soley within Intune. With this final part of the series we will go in-depth in how the common hybrid setups look like and how we go about moving into the next step of being able to manage and build devices without SCCM.

Modern Workplace Management: Build Endpoints without SCCM Part 5

by D Walsham • 29 July 2021
In continuation from the previous part where we had discussed how we create the "on site" piece of the solution, this was the part which would allow us to get our endpoints into a state in which they would essentially be ready to go through the Autopilot process. Which leaves our next piece of the puzzle, to begin the configuration of the actual backend side that resides within our Endpoint Management console. And you will see how everything ties up together to satisfy the full end to end process of getting an unknown (or known) device to proceed thorough the whole workflow to be finally managed by Intune without the aid of SCCM taking part in any of the prerequisites or preparation at hand.

Modern Workplace Management: Build Endpoints without SCCM Part 4

by D Walsham • 15 July 2021
In this part we are now going to look into the technical step by step points on how we put everything together. In the previous part we spoke about the structure of how we would asses whether a machine was actually ready to be built with Autopilot or not with a build checklist process which would step through all areas which would cover an endpoints eligibility. Now with everything planned out we finally want to step into making things reality by putting everything together.

Endpoint Manager: Find machines not in Autopilot

by D Walsham • 2 July 2021
When it comes to managing your endpoints in endpoint manager, one of the things you may be looking to do is to get all of your Intune registered machines to also be enrolled as Autopilot devices. Now we can of course just have the deployment profile deployed to all machines and then hit the "Convert targeted machines to autopilot" but this might not necessarily be feasible for every client. We may want to perform some due diligence first so we can at least understand what devices in Intune are not in Autopilot.
Show More