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
Labels:

Comments

  1. Joe ThompsonMarch 12, 2014 at 2:34 PM

    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. seravina danniellaOctober 25, 2017 at 9:00 AM

    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

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-CliXml ConvertTo-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 t...
Post a Comment
Read more

Toying with audio in powershell

Controlling mute/unmute and the volume on you computer with powershell. Add-Type -TypeDefinition @' using System.Runtime.InteropServices; [Guid("5CDF2C82-841E-4546-9722-0CF74078229A"), InterfaceType(ComInterfaceType.InterfaceIsIUnknown)] interface IAudioEndpointVolume { // f(), g(), ... are unused COM method slots. Define these if you care int f(); int g(); int h(); int i(); int SetMasterVolumeLevelScalar(float fLevel, System.Guid pguidEventContext); int j(); int GetMasterVolumeLevelScalar(out float pfLevel); int k(); int l(); int m(); int n(); int SetMute([MarshalAs(UnmanagedType.Bool)] bool bMute, System.Guid pguidEventContext); int GetMute(out bool pbMute); } [Guid("D666063F-1587-4E43-81F1-B948E807363F"), InterfaceType(ComInterfaceType.InterfaceIsIUnknown)] interface IMMDevice { int Activate(ref System.Guid id, int clsCtx, int activationParams, out IAudioEndpointVolume aev); } [Guid("A95664D2-9614-4F35-A746-DE8DB63617E6"), Inte...
3 comments
Read more

Creating Menus in Powershell

I have created another Powershell module. This time it is about Console Menus you can use to ease the usage for members of your oranization. It is available on GitHub and published to the PowershellGallery . It is called cliMenu. Puppies This is a Controller module. It uses Write-Host to create a Menu in the console. Some of you may recall that using Write-Host is bad practice. Controller scripts and modules are the exception to this rule. In addition with WMF5 Write-Host writes to the Information stream in Powershell, so it really does not matter anymore. Design goal I have seen to many crappy menus that is a mixture of controller script and business logic. It is in essence a wild west out there, hence my ultimate goal is to create something that makes it as easy as possible to create a menu and change the way it looks. Make it easy to build Menus and change them Make it as "declarative" as possible Menus The module supports multiple Men...
Post a Comment
Read more