The official TechNet documentation for establishing a Windows 2008 / Exchange 2007 SP1 cluster can be found at:
What I want to do in this blog post is outline an alternate method for installing the cluster different from the instructions referenced above for Windows 2003 clustered nodes.
The first recommendation that I make when establishing the cluster service is to not use the GUI mode setup included with Exchange 2007. My main rational for this advice is that when GUI mode setup fails you generally have to revert to command line setup to correct conditions and repeat the setup operations. With this in mind it’s much easier to start with the command line setup and continue through.
In each of the links above you will see that the basic structure of a command line setup for the active roles installation is:
setup.com /mode:install /roles:mailbox /newCMS /cmsName /cmsIPAddress [/css] [/cmsDataPath]
The passive role installation is:
setup.com /mode:install /roles:mailbox
The way to think about the active role command is the combination of the passive role (setup.com /mode:install /roles:mailbox) with the establishment of the clustered services (setup.com /newCMS /cmsName /cmsIPAddress [/css] [/cmsDataPath]).
These commands do not have to be run together. With this in mind my second recommendation is to establish the passive role first on each clustered node. I recommend this for a few reasons:
Now I will outline for you the steps that I use when establishing a Windows 2008 / Exchange 2007 SP1 Cluster. Please refer to these additional blog posts for some other helpful information regarding these installations:
In all instructions below the assumption is that the cluster service and appropriate quorum type have been established and fully configured. The instructions also outline only the establishment of the Exchange resources, the TechNet documentation referenced above should be used to establish the specific cluster service requirements and other installation / management tasks for an Exchange 2007 SP1 clustered installation on Windows 2008.
Windows 2008 / Exchange 2007 SP1 Cluster Continuous Replication (CCR)
At this point the replication service will begin copying log files from the new databases created and bring both sides into synchronization. This completes the setup of a Windows 2008 / Exchange 2007 SP1 CCR cluster.
Windows 2008 / Exchange 2007 SP1 Single Copy Cluster (SCC)
By using these steps you should hopefully be able to simply your Exchange 2007 SP1 clustered installation on Windows 2008 and more easily address errors that may arise during the clustered setup.
This was a big help for me.
We were having issues with the “MSExchangeServiceHost” service failing to start. I manually started the service and reran setup.com as you described and wa able to get it installed. Then being able to install the cluster role after the fact was a big help.
This may not be the recommended way but here is how my installs would go in the future:
So this is how we should do it next time:
Active and Passive Nodes:
Run setup.exe, try to install *mailbox* role
If/when it fails run this:
C:\Windows\system32>net use y: <install source, if not local>
Y:\software\exchange2007>setup.com /Mode:Install /roles:mb
(if this still fails manually start the “MSExchangeServiceHost” service and try again, worked for me)
Then, after *both*nodes are working run this on the *active* node
Y:\software\exchange2007>setup.com /newcms /cn:<cluster virtual server name> /cip:<active ip>,<passive ip>