This script should be run
for every physical disk resource that Exchange is using. For more information about resource
dependencies for Exchange Server 2007, please see the Microsoft 2007 help file ( .chm ).
One last component needs to be configured for this cluster. You may have noticed that the data and logs
reside on the same logical drive. The Move-StorageGroupPath from within the Exchange Management
Shell can correct this. By specifying the -LogFolderPath as the T:\logs path, the EMS will check the
path, create the folder if it does not exist, and prompt you to verify the movement of the log files. This
action will take the database offline, and will have to be brought online manually. Hence another cmdlet
to move the log files to the correct location. This script adds in an additional feature; it requires the use of
the Exchange Management Shell. It is perfectly acceptable to run this from within the EMS, however if
you want to try this script with all of the previous scripts to create a deployment script, you must add in
the Exchange Management PowerShell.
$Disk3_Drive (reused from disk section)
Add-PSSnapin Microsoft.Exchange.Management.PowerShell.Admin
Move-StorageGroupPath ???First Storage Group??? -LogFolderPath
$Disk3_Drive.Insert($Disk3_Drive.Length,???\Logs???
Chapter 13: Single Copy Clusters
383
This script may seem a little excessive at first, but it takes PowerShell, calls the Exchange snap - in for
PowerShell, calls an Exchange cmdlet, and then uses part of the native .
Pages:
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530