Powershell Commands to configure Gateway Server / Agent Failover

re: Powershell Commands to configure Gateway Server / Agent Failover

Ravigu — Wed, 22 May 2013 08:43:25 GMT

How many MS/Gw can be configured as failover? Do we have any limit for this ?

re: Powershell Commands to configure Gateway Server / Agent Failover

Jimmy Harper — Tue, 02 Apr 2013 14:35:29 GMT

That would work, but even if you keep the GWs pointed at the primary during the upgrade, they will failover to the secondary whenever they can't connect to the Primary.

re: Powershell Commands to configure Gateway Server / Agent Failover

Sridhar — Mon, 01 Apr 2013 14:09:27 GMT

Yes , indeed it worked .. thanks .

I have 2 MS in my environment and 4 GW's . All my GW are connected to Primary MS and secondary as failover.

I am planning to upgrade scom 2012 to SP1 , would this approach work , if I don't need monitoring to be hampered at any point in time :

Move all GW to secondary MS and then patch Primary , reboot etc . Then move all GW's back to primary MS and patch secondary MS .

Let me know your thoughts on this.

re: Powershell Commands to configure Gateway Server / Agent Failover

Jimmy Harper — Fri, 22 Mar 2013 16:44:53 GMT

What you will need to do here is first set the Failover MS to nothing...do this by using a server name that does not exist:

$failoverMS = Get-SCOMManagementServer | where {$_.Name –eq 'FAKE_SERVER_NAME.DOMAIN.COM'}

Now, run the "Verify" commands to verify that the Primary MS is still the same and the Failover MS is empty.

Now proceed with the original commands to set Primary/Failover.

There may be a better way to do this, but this is what I came up with in my lab and it seemed to work as expected...test on one of the GWs first to verify.

re: Powershell Commands to configure Gateway Server / Agent Failover

Sridhar — Fri, 22 Mar 2013 11:09:02 GMT

I have 2 MS and 6 GW that all report to primary MS (MS1) . I configured my gateways to primary (MS1) and secondary management servers (MS2) few days back. Now , we need to spread the load of GW half to MS1 as their primary ( for which MS2 would be failover) and remaining half to MS2 as their primary (for which MS1 would be failover) . Can we do this?

If I run the command for this configuration I get the error "the failover MS can not be the same as primary".

I belive this is due to my earlier configuration where we had all GW reporting to MS1 as primary and MS2 as secondary . How can I now distribute the GW load equally between 2 management server ?

Help ..!!

re: Powershell Commands to configure Gateway Server / Agent Failover

Jimmy Harper — Tue, 05 Mar 2013 17:24:33 GMT

The PowerShell commands can be run from any computer that has the SCOM Command Shell installed...it does not need to be run from an Agent. I usually use one of the Management Servers.

re: Powershell Commands to configure Gateway Server / Agent Failover

Narayn — Tue, 05 Mar 2013 17:16:35 GMT

How do I configure failover on an agent where PowerShell is not available. For example if PowerShell is not already installed. By default the SCOM agent does not appear to install any PowerShell cmdlets.

re: Powershell Commands to configure Gateway Server / Agent Failover

Stefan Roth — Wed, 03 Oct 2012 12:39:43 GMT

Excellent post!

re: Powershell Commands to configure Gateway Server / Agent Failover

Jimmy Harper — Wed, 03 Oct 2012 00:12:12 GMT

Thanks Jonathan and Joe....I've updated the OpsMgr 2012 command to use -PrimaryServer and use separate lines for setting primary and failover.

re: Powershell Commands to configure Gateway Server / Agent Failover

Jonathan — Tue, 02 Oct 2012 22:42:39 GMT

Were you able to get this to work in 2012?

#Agents reporting to GATEWAY_1 - Failover to GATEWAY_2

$primaryMS = Get-SCOMManagementServer | where {$_.Name –eq 'GATEWAY_1.DOMAIN.COM'}

$failoverMS = Get-SCOMManagementServer | where {$_.Name –eq ' GATEWAY_2.DOMAIN.COM'}

$agent = Get-SCOMAgent | where {$_.PrimaryManagementServerName -eq 'GATEWAY_1.DOMAIN.COM'}

Set-SCOMParentManagementServer -Agent: $agent -PrimaryManagementServer: $primaryMS -FailoverServer: $failoverMS

I get an error. Seems we need to execute set- once for primary, then again for failover.

Also, I think -PrimaryManagementServer has changed to -PrimaryServer.