c
 

  

Ê

ÊÊÊ
ÊÊÊ ÊÊÊ ÊÊ Ê
Ê
ÊÊÊ
ÊÊÊÊÊÊ Ê
Ê

ÊÊÊ
ÊÊÊ ÊÊ Ê
Ê!ÊÊ Ê
Ê
ÊÊÊ"#$ÊÊ%ÊÊÊ &Ê
Ê

'Ê($$Ê Ê Ê

&Ê
Ê

Before beginning be sure of the following:

áÊ he cluster-servers-to-be are domain members (no standalone servers)

áÊ ºou have Domain Admin rights
áÊ All cluster-servers-to-be are installed with Windows 2003 Enterprise Server
áÊ Shared disks are present (Basic Disks, N S)
áÊ -inimum of 2 network adapters present per node
áÊ ºou have a list of the IP-addresses you want to use

h he first step, create a domain account for use with the Cluster Service. (e.g. _ClusterService).
his account can be a normal Domain User. After creating the account add the user to the local
administrators group on the cluster nodes.

 -ake sure the following services are disabled on all cluster nodes:
Distributed Link racking Client
ask Scheduler
Wireless Configuration

 Check the Power Options on all cluster nodes and make sure the power savings are disabled.

 Install Network DC Access on all cluster nodes

Go to the Control Panel and Add/Remove Programs. Select the Windows Components and go to
Application Server. Select Enable Network DC Access. After installing restart the Distributed
ransaction Coördinator Service and, if present, the -icrosoft -essage Queuing.

Configure the network cards on all cluster nodes.

Rename a network connection to Private Network and one to Public Network. his way you
have a better overview of your network connections.

= Set the binding order on all cluster nodes. Go to the Control Panel and select Network
Connections in the menu. Go to Advanced en select Advanced Settings. -ake sure the Public
Network is the first connection to bind and Private as second.

 Set the network settings on the Private Network connection on all cluster nodes.
ill in the IP-address and Subnet -ask of the network connection. Do not fill in DNS Servers,
Gateway and WINS Servers. -ake sure that Register this connection in DNS is off. Also Disable
NetBIOS over CP/IP.
or best practice force the duplex/speed on 10 -b/s Half duplex, even though you might have a
GigaBit networkcard.
-ake sure ³ ile and print sharing for networks client´ and ³Client for -icrosoft Networks´ are
off.

m Set the network settings on the Public Network connection on all cluster nodes.
ill in the IP-address, Subnet -ask, DNS, WINS and Gateway of the network connection. Set
the duplex/speed fixed on for example 100 -b ull Duplex. his is also -icrosoft Best Practise.

 On the first node start the Cluster Admin and select Create a new cluster.
After the Welcome screen click Next

On the Cluster Name and Domain screen, select the domain and Cluster Name. Click Next

On the Select Computer screen, select the computer name of the first node. Click on Advanced

Select ypical ( ull) Configuration, click Ok

he Wizard is now analyzing the hardware- and software configuration of your server. Click on
Next when this is done.

On the IP Address screen fill in the IP Address for the Cluster -anagement ools. Click Next
On the Cluster Service Account fill in the user properties for the user created in step 1. Click Ok

On the Proposed Cluster Configuration screen Select the Quorum button.

Select the disk for use with the Quorum. Click Ok.

Now the Cluster is being created and started. Click Next and inish
Check if the Cluster service is started.

h On the second node (and third etc.) start the Cluster Admin. Select Add Nodes to cluster and
type in the Cluster or Server name.

After the Welcome screen click Next

On the Select Computers screen fill in the name of the second node and click on Add.
he Wizard is now analyzing the hardware- and software configuration of your server. Click on
Next when this is done.

On the Cluster Service Account screen fill in the password and domain for the account created in
step 1. Click Next
On the Proposed Cluster Configuration check if everything is in order. Click on Next

On the Adding Nodes to he Cluster screen wait for the cluster to be configured. Click on Next
and inish
Do step 10 for every node you want to add.

hh Start the Cluster Admin on one of your nodes. Right-click on the Cluster Name and select
Properties. Go to the ab Network Priority and make sure the Private Network is on top. Click
Ok.
h Select Cluster Configuration and then Networks. Right-click on the Private Network and
select Properties. Select Internal Cluster communications only (private network) and click on Ok
h Right-click on the Cluster Group and Select New Resource. ill in the following information :
Name : -SDC Resource
Description : -SDC Resource
Resource ype : Distributed ransaction Coordinator
Group : Cluster Group
Click Next
On the Possible Owners screen select All Nodes and add them to the Possible Owners. Click
Next

On the Dependencies screen add the Cluster Name and Physical disk (Quorum) to the Resource
dependencies. Click inish
h Right-click on the -SD Resource and select Properties. Select the Advanced tab. Do NO
select the Affect Group option and click Ok.
h
Right-click on the -SD Resource and select Bring Online.

h= Start a command prompt and start

cluster.exe /prop

Check the properties which are displayed for EnableEventLogReplication. -ake sure this setting
is 0.
If it¶s not 0 type the following in the command prompt :

cluster.exe /prop EnableEventLogReplication = 0

Check the properties again.

Now you have a perfectly configured basic Windows 2003 Cluster. rom here on you can use
this to cluster for example Exchange 2003, SQL Server or a ile Server.

Ê Ê
Before beginning be sure of the following:

áÊ A Windows 2003 Cluster is present (check how to Install a basic Windows 2003 Cluster)
áÊ Domain Admin rights are present
áÊ his is not the first Exchange 2003 Server
áÊ he following services are not supported on an Exchange 2003 Cluster:
‘Ê -icrosoft Active Directory Connector (ADC)
‘Ê -icrosoft Exchange 2000 Calendar Connector
‘Ê Exchange Connector for Lotus Notes
‘Ê Exchange Connector for Novell GroupWise
‘Ê -icrosoft Exchange Event service
‘Ê Site Replication Service (SRS)
‘Ê Network News ransfer Protocol (NNP)
áÊ Adminpak.msi is installed on all nodes
áÊ Windows 2003 Support ools are installed on all nodes
áÊ Hotfix KB 831464 is installed on all nodes

Step h
  must be done first on all nodes

h Start setup.exe from the Exchange 2003 CD, X:\I386\Setup.exe, where X is the drive letter of
the CD-Rom.
Click Next

 On the License Agreement screen select ] 

and click Next

 On the Component Selection screen select all the necessary components. -ake sure the install
path is      .

 On the License Agreement screen select ] 

and click Next

On the Installation Summary check the settings and click Next

= After installation click inish

 Install Exchange 2003 SP 2.

After installation on all nodes of steps h
  continue«

m Start Cluster Admin and create a new Cluster Group named EVS Group (Exchange Virtual
Server)

 Right-click on the EVS Group and select New Resource.

ill in the following :
ÿ
: EVS Physical Disk
  
: EVS Physical Disk

  : Physical Disk
: EVS Group

Click Next

On the Possible Owners screen add all nodes, click Next

On the Dependencies screen select  resource dependencies and click Next

On the Disk Parameters screen select the Physical Disk and click inish

h Right-click on the EVS Group and select New Resource.

ill in the following :
ÿ
: EVS IP Address
  
: EVS IP Address

  : IP Address

: EVS Group

Click Next

On the Possible Owners screen add all nodes, click Next

On the CP/IP Address Parameters screen fill in the IP Address info and select ³  ÿ


  
 click inish

hh Right-click on the EVS Group and select New Resource.

ill in the following :
ÿ
: EVS Network Name
  
: EVS Network Name

  : Network Name

: EVS Group

Click Next

ill in the name of the Exchange Cluster. Do  select ³ÿ



 
 ´ and
³     
 

³. Click inish

h Right-click on the EVS Group and select Bring Online

h Right-click on the EVS Group and select New Resource.

ill in the following :
ÿ
: System Attendant
  
: System Attendant

  : -icrosoft Exchange System Attendant

: EVS Group
On the Dependencies screen add the following resources to the resource dependencies and click
Next:

áÊ EVS Network Name

áÊ EVS Physical Disk

On the Exchange Administrative Group screen select the correct administrative group and click
Next.

On the Exchange Routing Group screen select the correct routing group and click Next.

On the Data Directory screen enter the path to the Exchange data drive. -ake sure this is on the
shared disk (same as the EVS Physical Disk). Click Next

On the Summary screen check the settings and click inish.

ÿ   If the following error appears, check your network binding order:

he network path was not found.

acility: win32
ID no:c0070035
-icrosoft exchange cluster administrator extenstion

h Go to the EVS Group and right-click on the resource ³       


  
³

Remove the selection ³

 ´ and click Ok.

h
Select the System Attendant resource and select Bring Online.

ºour Exchange 2003 Cluster is now up and running, if all went well. ºou can now easily test a
system failover.