On the Transport role server: exClientServer
Create a shared folder: witness
Assign the ClusterAdministrator (cluster service account) with FULL access permissions on both shared permission and security permission.
configure the MNS quorum to use the file share witness
On Cluster NODE1:
Cluster mycluster res "Majority Node Set" /priv MNSFileShare=\\ExClientServer.itsme.com\Witness
System warning 5024 (0x000013a0).
The properties were stored but not all changes will take effect until the next time the resource is brought online.
Run the following command (twice)
Cluster mycluster GROUP "Cluster Group" /MOVE
Cluster mycluster Group "Cluster Group" /Move
If you have other resource groups, run "Cluster mycluster GROUP "other group" /move
========================
Make sure that both S2003Ex1 and S2003Ex2 are the owner of the Cluster Group resource. And make sure S2003Ex1 owns the Cluster Group.
Run Exchange 2007 SP1 on S2003Ex1;
It works.
==========
According to Microsoft Recommendation, an alias for the computer name: ExClientServer should be used.
By default, computers running Windows Server 2003 do not listen for requests using alias names. As a result, connection attempts may fail with the following error message when hosting the file share on Windows Server 2003: "System error 52 has occurred. A duplicate name exists on the network."
You must create a registry value.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
Add Value, and then add the following registry value:
Value name: DisableStrictNameChecking
Data type: REG_DWORD
Radix: Decimal
Value: 1
