exchangeexchange.local???
$FSW_Share_Full_Path=???Mbfsw.exchangeexchange.local\MNS_FSW_MBCCR???
2. From the root of the C drive on the Client Access Server, create the FSW path:
Mkdir $Dir_Path
Part III: Working with PowerShell in a Production Environment
340
3. Next, assign the full permission for the cluster service account to the share:
Cacls $Dir_Path /G BUILTIN\Adminsitrators:F $User_Perm
4. Create the file share and grant the cluster service account full control:
Net share $Share_Name=$Dir_Path /GRANT:???$User,FULL???
5. Create the DNS entry for the FSW CName:
Dnscmd $DNS_Server /recordadd $DNS_Zone $Share_DNS_NAME CNAME $FSW_Server_Name
In order for the CAS to respond to requests with a different hostname, follow http://support
.microsoft.com/kb/281308 to implement security workarounds if the connection returns an error
when making a connection.
6. Next, configure the MNS quorum to use the new FSW. This command should be run on the active
node:
Cluster $Cluster_Name res ???Majority Node Set??? /priv
MNSFileShare=$FSW_Share_Full_Path
7. If the command is successful it will output a warning stating that the changes just made will not
take immediate effect. Open the FSW file share and see that it created a new directory. This is
where the cluster will store its quorum files.
Pages:
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483