I will describe the steps necessary to install a CCR on Windows 2008 SP2 Servers. Names of the CCR Nodes are CCR1.chakka.local and CCR2.chakka.local with 192.168.1.93/24 and 192.168.1.94/24 as the IP. Both servers have two NICs, name one as Public and another as Heartbeat. Configure the Public NIC with ip, subnet mask, default gateway and…
I will describe the steps necessary to install a CCR on Windows 2008 SP2 Servers.
Names of the CCR Nodes are CCR1.chakka.local and CCR2.chakka.local with 192.168.1.93/24 and 192.168.1.94/24 as the IP. Both servers have two NICs, name one as Public and another as Heartbeat.
Configure the Public NIC with ip, subnet mask, default gateway and dns (internal network ips, in my case it is 192.168.1.0 network). Configure the Heartbeat NIC with a different network ip and subnet mask, in my case 172.16.0.0 network). Don’t give the heartbeat nic a default gateway or dns ip. Also configure the advanced options as shown in the screenshot.
Make sure that the NIC binding as in the correct order with Public NIC first in the order. Go to Advanced -> Advanced Settings and change the order if needed.
Add both the nodes to the domain. Install the Exchange 2007 pre-requisites for Windows 2008. Open command prompt and copy/paste the following and press enter to install.
Once the install finishes, restart the server. Login to the server and go to Admin Tools -> Failover Cluster Management Tool.
If you are not using a domain admin account, the following error will be displayed.
Click on “Create Cluster” and follow the wizard.
Add both the nodes.
Say no to validation. We will run it later.
Give a name to the cluster, this is NOT the name which Outlook clients will use to connect. Give a cluster ip address. The IP should be in the same range as your domain network.
Click Next and the cluster will be created.
Launch Failover Cluster Management and Rename the networks as Public and Heartbeat for easier administration.
Take the properties of the Public Network and configure as shown below.
Take the properties of the Heartbeat Network and configure as shown below.
Create a folder named cluster1share (can name anything, but try ot use meaningful names) on a DC or Hub Transport Server. Share and give the cluster account full control as follows.
Log back into your first cluster node and launch Failover Cluster Management -> More Actions -> Configure Cluster Quorum Settings and follow the wizard.
Change the Quorum settings to Node and File Share Majority (Third Option) and click Next
Browse to the server where the file share was created and specify the path (It has to be a UNC path, \servernamesharename).
Click Next and Finish.
Run a Validation Test before you install exchange. To do that, click on “Validate A Configuration” and follow the wizard.
Once everything is green, you can install the Active Clustered Role of Exchange 2007 Server. Run the Exchange setup from the Exchange 2007 DVD and follow the wizard. Proceed through the wizards as a normal installation, select Custom Installation in the Installation type.
Select Active Clustered Mailbox Role.
Select Cluster Continuous Replication and specify a name for the Clustered Mailbox Server (CMS). This is the name which Outlook uses to connect to the server.
Give an IP address for the CCR Cluster and click Next.
Once the readiness check completes successfully, click Install.
Now, login to your second ccr node and run exchange setup. Only change in the option is to select the Passive Clustered Mailbox Role in the Installation type.
Cloud Architect & Blogger with interests in Microsoft 365, Azure, AWS & PowerShell. I am active on Experts Exchange & TechNet forums and I am a technical author for SearchExchange. Follow me on Twitter, LinkedIn, or Facebook for the latest updates. For consultancy opportunities, drop me a line.