The command to move the MB002 mailbox resources from MB002A to MB002B
for server maintenance would look like this:
Move-ClusteredMailboxServer MB002 -TargetMachine MB002A -MoveComment ???Moving
resource to perform maintenance on MB002B.???
The Get-ClusteredMailboxServerStatus cmdlet verifies that the resource move was correctly
processed. Additional verification can be performed using the cluster administrator. The CMS can only
be moved to a node that does not have another CMS already running on it, must be a member of the
same MSCS cluster, and will maintain the operational state (online or offline) on the new node it had on
the old node. Figure 13 - 19 shows the cluster status.
Figure 13-19
Putting It All Together
Throughout the chapter, individual components of an SCC install have been presented to show that
there are numerous tasks that are required to make the cluster functional. By using PowerShell, these
individual components have scripted to allow for reusable variables, faster deployment, and a
documented repeatable process. The methodology of showing each individual script and how it
automates a subcomponent was designed to lead the Exchange administrator to the point of putting all
of the scripts together to have a fully automated deployment of SCC. The following script does that.
Pages:
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533