VMWARE Server – Installing Exchange 2007 SP 1 Using CCR on Windows 2008 – Part 2…

In my previous article on this subject (located here: http://telnetport25.wordpress.com/2008/02/16/vmware-server-installing-exchange-2007-sp-1-using-ccr-on-windows-2008-rtm-part-1/ I explained how you can configure VMWARE server 1.0.3 to run Windows 2008 server and what sort of resource allocation of the host that you should be looking to provide your VMWare Guest in order to get a reasonable test environment running.

Before I begin the second part of this series I would like to briefly go over a couple of additional tips that I have found since the first version – thanks to Brett Johnson for publishing these little nuggets on his Blog (Brett’s post is located here: http://blogs.technet.com/brettjo/archive/2008/02/14/what-s-new-when-installing-ex2007sp1-ccr-on-a-ws08-cluster.aspx):

  • When installing the pre-requisite components (using serverManagerCMD) there is a log file of the action created in c:windowslogsServerManager.txt
  • Brett’s article contains a modified way of Installing the clustering which includes a couple of tweaks for the cluster service

In this article I would like to cover the following aspects of Installing Exchange 2007 SP1 on Windows Server 2008

  • Overview of installing the passive CCR node
  • Installing Exchange 2007 SP 1

Overview of installing the passive CCR node:

If you have followed the previous article at this stage we should have the following configuration:

A x64 host computer running VMWARE server 1.0.4 or 1.0.3 (you can perhaps use previous versions of VMWARE server, but I have only tested with the two versions mentioned here).

At least one domain controller configured as a Guest machine running Windows 2003 server (or Windows 2008)

One Primary CCR node running as a Guest – configured like so:

CPU 2 Processors
Memory 2048
SCSI 0:0 C: 15 GB
SCSI 0:1 B: 6.5 GB (Optional Drive)
SCSI 0:2 S: 6.5 – Exchange Installation Disk (Recommended Under VMWARE)
SCSI 0:3 X: 2.5 GB (Recommended)
Network Interface 1 Bridged via the Host
Network Interface 2 Custom – set to VMNET2

The guest machine will have the following installed & configured:

  • Windows 2008 Enterprise Edition Service Pack 1
  • Have both the Public and Heart_Beat Network interfaces configured with the correct IP addresses
  • Be a member of the correct Windows domain
  • Have all disks partitioned and formatted within Windows
  • Have IP V6 DISABLED unless you intend to use it
  • Have Windows Failover Clustering Installed and configured (as a MNS cluster)
  • Have all of the Exchange Server prerequisite features installed (see part 1 of this article for two batch files that can automate this process)

If everything conforms to the above specifications we are ready to being the installation of the passive node.

VMWARE Config:

The Passive Node should be configured identically to the Primary Node under VMWARE (see specifications above)

Windows Installation and Configuration:

The installation and configuration of Windows should be identical to the primary node – with the following exceptions:

  • The NETBIOS name needs to be different
  • Both the LAN and Heart_Beat IP addresses need to be different to that of the primary node

Every other aspect of the configuration should be the same as to what we did in Part 1 (ensure that you have also installed all of the Exchange 2007 pre-requisite services using the batch files provided in part 1), however when you get to the point of running the command which installs the Clustering Service on your node:

ServerManagerCMD -i Failover-Clustering

The process changes slightly.

Installing Failover clustering on the passive node:

When you have installed Windows, correctly configured networking, partitioned up and formatted the drives and then installed Failover clustering on the passive node you need to navigate to [ Start -> Programs -> Administrative Tools -> Failover Clustering ] – this will then open the Failover Cluster Management Tool (FCM).

From the left hand node plane of the FCM – right click on the Parent node entry (entitled “Failover cluster Management”) and from the context menu that appears choose “Manage a cluster” – see below:

When you have clicked on the “Manage a cluster” option the following dialog box will open:

Here you will need to either browse for – or type in the name that you assigned to your cluster (again covered in part 1) – when you are happy with the selection click on the “OK” button.

The FCM will then connect to the cluster that you have specified – if successful the left hand node plane will populate with the details of your cluster – you will see an entry entitled “Nodes” – right click on this value and from the context menu that appears choose the “Add Node” value – see below:

This will then open up the “Add Node” wizard welcome page – see below:


Click on the “Next” button this will take you to the “Add Servers” section of the Wizard:

Browse for – or – type in the name of your passive node (the machine that you are working on) and then click on the “Add” button – this will then place the name in the “Selected Servers” area of the window – then click “Next”:

You will then be presented with the Validation screen – here I suggest that you choose (at least for the purposes of this article) the “No” option and then click on the “Next” button:

You will then be presented with the “Confirmation” screen – here click on the “Next” button:

The Cluster wizard will now go away and perform the required actions to add the new node to the cluster.

When the wizard has finished you will be presented with a summary report of the actions that have been take – this will include any warnings / errors that were encountered along the way – in the example that I have provided above you will see a number of warnings which allude to resources not being found – this is because in my test lab I had already installed Exchange 2007 on the primary node – the wizard has detected that the passive node in its current state cannot support all resource types (namely the Exchange resources) that have been found on the primary.

Click on the “Finish” button to complete the cluster installation.

Installing Exchange 2007 SP1 on Windows 2008 Primary Node:

Log onto your Primary node and then navigate to the location of the Exchange 2007 SP1 installation binaries – which in my configuration is “B:Exchange2007–SP1setup.exe” (If you have not updated the Schema or Domain for Exchange at this stage do not worry it will be performed as part of the Exchange installation).

When “Setup.exe” has been executed the following screen will be displayed:

Click on the “Step 4: Install Microsoft Exchange Server 2007 SP1” option which will then present you with the following screen:

On this screen click on the “Next” button which will present you with the License agreement screen:

Choose the “I accept the terms in the License Agreement” and then click on the “Next” button:

You will be presented with the error reporting options screen – here choose the option that best suites you and then click on the “Next” button:

You will now be presented with the Installation options screen – choose the “Custom” installation and if you have chosen to follow the VMWARE guest specifications that I have provided you will the to change the “Specify the path for the Exchange Server installation” to Drive S: (Exchange Installation Binaries) then click on the “Next” button.

You will then be presented with the Server Roles Selection screen – here tick the “Active Clustered Mailbox Role” and then click on the “Next” button:

You will then be presented with the Cluster Settings screen, here ensure that the “Cluster Continuous Replication” option is selected, then provide a name for your clustered Exchange server instance in the “Clustered Mailbox Server Name” area – and if you have followed the VMWARE guest configuration that I have suggested change the “Specify the path for the Clustered Mailbox Server Database Files” to “X:ExchangeMDBData” and then click on the “Next” button:

Now the above screen may look a little new to you, that’s because it is!; Essentially this is the part of Exchange Server 2007 SP 1 Setup where if you are installing a CCR cluster on Windows 2008 you can configure your separate IP Subnets (remember that in Exchange RTM and if installed on Windows 2003 all CCR cluster nodes need to remain in the same IP Subnet).

  • If your CCR nodes exist in the same IP subnet then you will only need to provide an IP address in the “First Subnet” area – therefore you should type in unique IP address to be assigned to the Exchange Virtual Server in the single Subnet.
  • If your CCR nodes exist in different UP subnets you will need to tick the “Second Subnet” box and then provide another IP address that is unique in that Subnet – should a Failover occur the CCR cluster will then be assigned to that IP address.

When you have finished configuring the correct IP information click on the “Next” button:

Setup will then perform its readiness checks – and as per usual if any issues are found they will be highlighted to you prior to installation:

When you are happy with the results of the readiness checks, and there has been no fatal errors encountered click on the “Install” button.

Exchange setup will then go away and install the required files on your Active Node.

When finished you should be presented with a screen which looks like the above when you click on the “Finish” button you will be asked to reboot the Node (this is a little different from the installation on Windows 2003 which normally would not request a reboot:

Installing Exchange 2007 SP1 on Windows 2008 Passive Node:

The installation of Exchange 2007 SP 1 on the Passive node is pretty much the same as the Primary with the only differences being:

On the Server Role Selection Screen (above) you need to tick the “Passive Clustered Mailbox Role

You will not be asked for IP settings.

Remember that you should keep all disk paths that you specified for the Primary (or Active) Node the same for the Passive.

After you have run through the processes above – you should have a fully functional CCR cluster working on Windows 2008

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.