Implementing Exchange clusters with W2K3 and VMware GSX

With VMware GSX Server installed three Win2003 systems (easy to install a system replication two), each system allocates 1G of memory (to ensure smooth operation), in the VMware GSX Server "HOST" in the memory set to 4G, Because the server has to do other useful, do not occupy. After installing three win2003, I first add a card to each of each, the first network card to Vnet0 (Networking), the second set to Vnet1 (heartbeat, configured in the VM as Hostonly).

Set up for each machine:
nodea:vnet0:192.168.1.2 mask:255.255.255.0 dns:192.168.1.254 vnet1:10.1.1.2
nodeb:vnet0:192.168.1.3 mask:255.255.255.0 dns:192.168.1.254 vnet1:10.1.1.3
adser:vnet0:192.168.1.254 mask:255.255.255.0 dns:192.168.1.254 vnet1:10.1.1.1

Configure Adsev as AD service server (set to AD and DNS servers only), select "Custom" when setting, ad domain name is work.com

NodeA and NodeB are made into Adser member servers, logged in with the administrator

Two. Create a shared disk cabinet

Cluster shared disk cabinets require at least one Quorum disk and a shared disks, so we need to create two SCSI disks. Enter into command mode
F:/vm/disk>vmware-vdiskmanager.exe-c-S 200mb-a lsilogic-t 2 QUORUM.VMDK

F:/vm/disk>vmware-vdiskmanager.exe-c-S 4gb-a lsilogic-t 2 SHAREDISK.VMDK
After creation, there are four new files in the directory
Quorum-flat.vmdk
Quorum.vmdk
Sharedisk-flat.vmdk
Sharedisk.vmdk

Three. Configure virtual machines

Shut down three systems, select "Edit Virtual machine settings" in the virtual machine interface to add the hard disk, choose "Use a existing Virtual disk", add Quorum.vmdk, SHAREDISK.VMDK respectively.

Double-click the newly added disk, select "Advance" in the pop-up Disk Properties window, choose Virtual Device node for the new hard drive: QUORUM.VMDK choose "SCSI 1:0", SHAREDISK.VMDK selected

"SCSI 1:1". (problems may occur if you do not set this up)

Open the Vmx file in the two virtual machine directories, and add on the last line:
Disk.locking= "FALSE"
Scsi0:1.sharedbus= "Virtual"
Scsi1:1.sharedbus= "Virtual"

After starting these three systems, the newly identified hard drive is converted to a basic disk and then named: Q Partition Volume Label: Quorum and S-Partition volume label: Sharedisk

Three.. Configuring Win2003 Clusters
The NIC Vnet1 of each node (NODEA,NODEB) is set to a single rate and half-duplex to stabilize the communication between nodes.
Right-click on each node's Nic Vnet1, properties-----Advanced----WINS----Click Disable NetBIOS over TCP/IP
Back to the Network Connections window, click Advanced---Advanced settings---Adapters and bindings---Move the connection "local connection 2" where Vnet1 is located to the first.

The IP for cluster is set to: 192.168.1.5, with the name: Workcluster
1. Turn the NodeB off. Open NodeA
2. On NodeA, click Start > Administration Tools > Cluster Administrator (or run Cluadmin.exe) to open Cluster Administrator.
3. When the cluster connection is turned on to create a new cluster, press OK, the New Server Cluster Wizard appears, and, as Next,
Set the domain to work.com and enter in the cluster Name: Workcluster, press the next step.
4. Set the computer name to Nodea,r next, in the Profiling Settings window, you will check to see if NodeA meets the criteria set up for clustering, and if you pass the check, it will tick before each item. If it is not correct, please check. Press the next step when the check is complete.
5. In the IP address bar, enter: 192.168.1.5, press the next step.
6. In the Cluster service account, enter the account, administrator, and password for managing the cluster, and the network domain.
7. In the recommended cluster setting, press quorum to set the quorum disk to Q
8. Start setting up the cluster, and if you do, each item in the analysis will tick, or try again. Check for faults.
9. After the cluster is established, Cluster Administrator displays the cluster hierarchy.
10. In Cluster Administrator, point to the network, connect the Vnet1 to local 2, right-click the property, and click "Allow internal cluster communication only", as determined.
11. Turn on NodeB, turn on Cluster Administrator, change the contents of the operation to add nodes to the cluster, and enter Workcluster in the cluster name., follow the prompts step by step.
12. Test the cluster functionality. In Cluster Administrator, the cluster group under the right key group, select the Move group, and determine that all resource owners within the group are converted from NodeA to NodeB. When the resource is converted to NodeB, the Nodea,nodeb is turned on to access the Q disk, and the Q disk is found only on the NodeB, indicating that only the node that owns the resource can access the resources.

Four Building exchange2003 Clusters
When installing the Exchange2003 cluster, the node must be fully open and log in Nodea:,nodeb:

1. Install the Distributed Transaction Coordinator (MSDTC) first. In NodeA: Open Cluster Administrator > Group > Cluster Group > select New > Resource, enter MSDTC Resource in new resource name, change resource resource type to distributed Transaction Coordinator, and Next, Identify all nodes as owners in the potential owner, and in resource dependencies, add the disk Q and cluster names to the right window and press finish. Click on the new MSDTC resource resource and right-click to select Online.
2. If you install exchange2003 on a node, do not install exchange2003 on each node at the same time, which can cause errors. After the installation is complete, you will find that the exchange-related services on each node are only initiated by Exchange manage, others are manual and do not start, When an Exchange Virtual server is established, which node it connects to, the Exchange service for that node starts.
3. Establish an Exchange Virtual server
On NodeA: Start Cluster Administrator > Group > > New > Group, enter Exchange Virtual Server in the name of the new group, and make sure that the usual user does not need to specify the node. The group is offline after it is established. Choose New > Resources in the newly established Exchange Virtual serve group, enter IP address in the name, select IP addresses for the resource type, and next, make sure all nodes are included in the possible owners. In the resource dependencies do not choose, in the TCP/IP address input you are ready to do Exchang IP, such as: 192.168.1.2, network selected vnet0 the connection (local connection).
Also create new network Name. In the newly established Exchange Virtual serve group, on the new > resource, enter Network name in the name, and next, determine that all nodes are included in the possible owner. In resource dependencies, add IP address to the form, and in the network Name parameter, enter the name you want to do Exchang, such as: Exchwork.
Drag the disk S from group 0 in Cluster Administrator into the Exchange Virtual server group. Press Yes. Right-click the Exchange Virtual Server online. When you are online, establish the Microsoft Exchange System attendant. In the Exchange Virtual serve group, select New > Resource > Name enter Microsoft Exchange System Attendant, resource type select Microsoft System attendant, Next, Determine that all nodes are included in the potential owner, network name and disk s are joined in resource dependencies, and follow the wizard step-by-step. When you are done, click Ehange Virtual Server online. So the exchange2003 cluster is complete.
In Nodea:,nodeb: Two nodes, only the exchanger service that connects to the Exchange Virtual server is started, opens the node that is connected to the Exchange Virtual Server (NodeA:), and determines that exchange data is placed in disk S. In Cluster Administrator, right-click the Exchange Virtual Server group, select Move Group, and make sure that you can transfer to the NodeA:.
The Exchange2003 and exchange2003 cluster presets do not enable the POP3,IMAP4 service, and if you want to enable both services in the Exchange2003 cluster, you first need to set these two services manually on each node without starting the service. Take the example of enabling POP3 services. On NodeA: Open Cluster Administrator on the Exchange Virtual server group to create a new > resource, enter Microsost Exchange POP3 in the name, and set the resource type to Microsost Exchange POP3. Make sure all nodes are included in the potential owner and add Microsoft Exchange System Attendan to the resource dependencies. Step by step.