Skip to main content

Operations Manager–Gateway servers and failover with Powershell dynamic parameters


Been thinking about doing a post about failover in SCOM with gateway servers. The idea is that you have several (2 or more) SCOM management servers in your management group. As you start to build your first gateway server, the question about failover/high availability for the gateway comes walking down the street. No problem, powershell comes to the rescue and provides you with a cmdlet you can use – Set-SCOMparentManagementServer.

All nice and dandy, however you can only set the primary management server or the failover server, not both at the same time. In addition you have to provide the cmdlet with gateway and management server objects. You cannot just specify their names. These are by no means huge issues, however I wanted to play around with the dynamic parameter in Powershell and decided to get to work.

Just a fair warning. Dynamic parameters are not pretty in Powershell, however if you put a little effort into the logic, it is quite reasonable to understand. What do we need to create one:
  1. System.Management.Automation.ParameterAttribute object (attributes you decorate with [Parameter] in your functions
  2. System.Collections.ObjectModel.Collection[System.Attribute] (a collection to hold your attributes)
  3. An array of values your parameter accepts
  4. System.Management.Automation.RuntimeDefinedParameter (an object containing the name of the parameter, the type and the attribute collection)
  5. System.Management.Automation.RuntimeDefinedParameterDictionary (a dictionary containing all the parameters; the parameter name and the RuntimeDefinedParameter object)
All of this has to be wrapped in an DynamicParam block. Your function will also need one or all of the BEGIN, PROCESS or END blocks or else your function will not work. I chose to use the BEGIN block.


The function needs the OperationsManager module to work since the dynamic parameters are retrieved from the Get-SCOMmanagementServer cmdlet. One big advantage with this dynamic parameter approach is reduced error handling since the parameters will contain objects that exist in the scope we are working in (SCOM).

Furthermore the OperationsManager module is missing a cmdlet. At least I have not found a way to remove a failover server from a gateway configuration. Please note that a Gateway server may have one (1) primary ManagementServer and zero or several failover ManagementServers. Well digging around I found this post by Andreas Zuckerhut where he lays out the foundation for my need to create the missing cmdlet. Be warned, I have tested this in several environments, however use this at your own risk.
Here is your Remove-SCOMGatewayFailover function also with dynamic parameters:




Popular posts from this blog

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"), Interfa…

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


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 …

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…