This returns the state
of the cluster and resource ownership:
Get-ClusteredMailboxServerStatus [-Identity < ServerIdParameter > ]
[-DomainController < Fqdn > ] [ < CommonParameters > ]
The result of Get-ClusteredMailboxServerStatus in the test environment shows that MB100 is the
active node and also has the quorum resource:
Identity : mb100ccr
ClusteredMailboxServerName : MB100CCR.ExchangeExchange.local
State : Online
OperationalMachines : {MB100 < Active, Quorum Owner > , MB101}
FailedResources : {}
IsValid : True
ObjectState : Unchanged
To show how the cluster would look offline, use the Stop-ClusteredMailboxServer cmdlet to shut
down the cluster. It is important to use PowerShell cmdlets, not the Cluster Administrator utility to
perform these actions. The Cluster Administrator utility is not Exchange aware. The PowerShell cmdlets
perform additional checks to ensure the passive node is up to date. Cluster Administrator does not
perform any of these checks and could cause problems. Also, the cmdlets allow an administrator to
comment on the failover reason.
Part III: Working with PowerShell in a Production Environment
350
Stop-ClusteredMailboxServer -Identity < MailboxServerIdParameter >
-StopReason < String > [-DomainController < Fqdn > ] [ < CommonParameters > ]
The StopReason string parameter is required, and should provide an explanation as to why the
administrator is taking the cluster offline.
Pages:
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495