Skip to main content

Bulk Import Operations Manager 2012 Management Packs

Read a post today from Joe Thompson regarding this subject. Really liked the idea with bulk import of Management Packs. The scenario is like this: You have a folder or several folders with a bunch of Management Packs and you want to install only those that is currently not installed.

I hope Mr Thompson does not mind me changing his Powershell script and "improving" it slightly if you ask me :-)

[cmdletbinding()]
Param
(
    [ValidateScript({Test-Path $_ -PathType 'Container'})]
    [string] $ManagementPacksPath
)

Write-Verbose "Creating an array of file names from the path $ManagementPacksPath"
$MPfiles = (Get-Item -Path "$ManagementPacksPath\*" -Include *.mp*).Name
[int]$CountMatching = 0
$InstallList = @()

foreach($MP in $MPfiles)
{
    Write-Verbose "Getting MP properties using SCOM cmdlet and the parameter 'ManagementPackFile'"
    $MPproperties = Get-SCOMManagementPack -ManagementPackFile "$ManagementPacksPath\$MP"
    $CountMatching = 1

    Write-Verbose "Checking if Management Pack is installed"
    $CountMatching = (Get-SCOMManagementPack -id $MPproperties.id.guid | Measure-Object).Count
    Write-Verbose "Get-SCOMManagementPack returned $CountMatching MPs with id $($MPproperties.id.guid)"
    
    if ($CountMatching -eq 0)
    {
        Write-Verbose "Adding $MP to the install list"
        $InstallList += $MP
    }
}

if($InstallList.count -gt 0)
{
    Write-Verbose "Installing Management Packs in folder $ManagementPacksPath"
    Import-SCOMManagementPack -Fullname $InstallList -ErrorAction SilentlyContinue
}
else
{
    Write-Verbose "InstallList is empty, all Management Packs in folder $ManagementPacksPath is installed"
}

What changed you ask? Well I am a bit particular about Powershell scripts and like to use [cmdletbinding()] since that gives med the option to use the Write-Verbose cmdlet and use logging when I want it by adding the –Verbose parameter to my scripts/functions. 

Secondly Operations Manager has the cmdlet Get-SCOMManagementPack which has a parameter called ManagementPackFile. This makes it possible to “load” the Management Pack in a variable and access all the properties like it was installed, thus we can use the Management Pack GUID to check against the installed Management Packs in Operations Manager. Makes it a little more robust and proper if you ask me. 

Thirdly I like to use parameter validation and this gave me a opportunity to use a special one:

[ValidateScript({Test-Path $_ -PathType 'Container'})]

By decorating the parameter with this entry, you will receive a nice warning if you assigned a non-excising path as a parameter to the script file. Look ma, no If-statement.

Mr Thompson also mentioned a DSC resource he is working on. Would be kind of cool to do a "ENSURE" on a Management Pack. Looking forward to reading more about that later.

In a future post I might expand this a little to check for version match and using the powershell Management Pack download tool (finding MP).

Cheers

Comments

  1. Tore, great improvements to the script, don't mind at all! I have also started a community DSC Resource collection for System Center. This enhanced script would definitely be an improvement if added to the MP Bulk Import DSC Resource I've already written... https://github.com/PowerShellOrg/DSC/tree/master/Resources/cSystemCenterManagement

    Joe

    ReplyDelete
  2. Thank you for sharing this information. I find this information is easy to understand and very useful. Thumbs up!


    Melbourne App Developer
    (10 URL)

    ReplyDelete

Post a Comment

Popular posts from this blog

Developing PowerShell modules for REST APIs – Part1

Over the years I have developed different PowerShell modules for different web APIs. I thought it would be a good idea to write a 2 series post about how you could go about to do this. This will be a 2 part blog series where we will run through the entire process of building a module for a REST API. I will try my best to keep this as simple as possible and leave more advanced stuff for a follow up post if the interest is there.What you needDepending on your experience with source control and PowerShell in general, you might want to use GIT or some other software repro for the code. In addition we are going to create a test REST API using the splendid UniversalDashboard PowerShell module created by Adam Driscoll. It is available on the PowershellGallery. Other prerequisites are built-in to Powershell. I will assume that you will be following along using at least PowerShell version 5 or greater.
What is HTTP metods for REST API.The primary or most common HTTP verbs used are POST, GET, PU…

Build your local powershell module repository - ProGet

So Windows Powershell Blog released a blog a couple of days ago (link). Not too long after, a discussion emerged about it being to complicated to setup. Even though the required software is open source (nugetgalleryserver), it looks like you need to have Visual Studio Installed to compile it. I looked into doing it without visual stuidio, however I have been unable to come up with a solution. I even tweeted about it since I am not an developer. Maybe someone how is familiar with “msbuild” could do a post on how to do it without VS.

Anyhow one of my twitter-friends (@sstranger) came to the rescue and pointed me in the direction of ProGet, hence the title of this post. ProGet comes in 2 different licensing modes
Free (reduced functionality)Enterprise (paid version with extra features)The good news is that the free version supports hosting a local PowershellGet repository which was my intention anyway. So off we go and create a Configration that can install ProGet for us. This is the conf…

Serialize data with PowerShell

Currently I am working on a big new module. In this module, I need to persist data to disk and reprocess them at some point even if the module/PowerShell session was closed. I needed to serialize objects and save them to disk. It needed to be very efficient to be able to support a high volume of objects. Hence I decided to turn this serializer into a module called HashData.



Other Serializing methods

In PowerShell we have several possibilities to serialize objects. There are two cmdlets you can use which are built in:
Export-CliXmlConvertTo-JSON
Both are excellent options if you do not care about the size of the file. In my case I needed something lean and mean in terms of the size on disk for the serialized object. Lets do some tests to compare the different types:


(Hashdata.Object.ps1)

You might be curious why I do not use the Export-CliXML cmdlet and just use the [System.Management.Automation.PSSerializer]::Serialize static method. The static method will generate the same xml, however we …