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

Monitoring Orchestrator runbook events from Operations Manager

Today I will follow up on my colleague’s post Mr ITblog (Knut Huglen) about monitoring Orchestrator Runbook events.  He has build a nice double up SNMP loopback feature that does self monitoring in Orchestrator resulting in entries written to a special Windows Eventlog. Now we need to raise alerts in SCOM when one of his runbooks fails or sends a platform event, who knows there could be trouble lurking in his paradise.

We are not going to do anything fancy, however these are the steps we will be focusing on today:
Create a Management Pack for our customizations Create rules that collects the events from the orchestrator serverOff we go then and fire up the SCOM console and a powershell window. First we create a MP, I am going to use powershell to do this, however you may use the SCOM console as well (Administration – ManagementPacks – Action: Create Management Pack):

Import the Management Pack into SCOM and move on to the Authoring section in the SCOM console. Create a new rule:

Give the…

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…

Powershell – Log like you mean it

How do you do logging in powershell? Why should you do logging? What should you log? Where do you put your log? How do you remove your log? How do you search your log? All important questions and how you answer then depends upon what your background is like and the preferences you have. This will be a 2 part blog post and this is part 1.

Why should you log?

Well it is not mandatory, however I have 2 reasons:
Help with debugging a script/module/functionSelf documenting script/module/function
Firstly; Do you know any program that does not contain any bugs? Working with IT for the last 2 decades, I cannot name one. When you create scripts/modules/functions, you will create bugs, that is where they live and try to make your life a living mess.

Secondly: Adding a little extra information to your logging will make them self documenting. Do you like writing documentation? Well I normally am not fond of it and use logging while debugging to get two birds with one stone.

What should you log?