Installing Exchange Server 2010 begins with installing and preparing the operating system.  Exchange Server 2010 can be installed only on Windows Server 2008 Standard Edition or Enterprise Edition.  If you plan on trying out database availability groups and mailbox database copies, you will need to use the Enterprise Edition of Windows Server 2008.Installing Exchange Server 2010 begins with installing and preparing the operating system.  Exchange Server 2010 can be installed only on Windows Server 2008 Standard Edition or Enterprise Edition.  If you plan on trying out database availability groups and mailbox database copies, you will need to use the Enterprise Edition of Windows Server 2008.
 
Once the operating system has been installed, several pre-requisites must be installed. 
 
Operating system components, including RSAT-ADDS (needed on server that will perform schema updates), Web-Server, Web-Metabase, Web-Lgcy-Mgmt-Console, Web-ISAPI-Ext, NET-HTTP-Activation, Web-Basic-Auth, Web-Digest-Auth, Web-Windows-Auth, Web-Dyn-Compression, RPC-over-HTTP-proxy, Web-Net-Ext and Net-Framework.  You can install all of these components at one time (e.g., for the Mailbox, Client Access and/or Hub Transport Server roles) by running the following command:

ServerManagerCmd -i RSAT-ADDS Web-Server Web-Metabase Web-Lgcy-Mgmt-Console Web-ISAPI-Ext NET-HTTP-Activation Web-Basic-Auth Web-Digest-Auth Web-Windows-Auth Web-Dyn-Compression RPC-over-HTTP-proxy Web-Net-Ext -Restart

 

You might have noticed that Failover-Clustering is not listed as a pre-requisite. There is a feature in Exchange Server 2010 called a database availability group that does use Windows failover clustering technologies. However, thanks to another Exchange Server 2010 feature called incremental deployment, you no longer install failover clustering before installing Exchange.  If you decide to use a database availability group, you simply create one, and then add Mailbox servers to it. When you add a Mailbox server to a DAG, we install the Windows failover clustering feature and automatically create a cluster for you. So while you do need to have Exchange installed on an operating system that supports Windows failover clustering, you do not install the failover clustering feature manually, or ahead of time, and you don’t manually create a cluster. It makes deploying highly available mailbox databases quick and easy.

Exchange Server 2010 also supports installing the above pre-requisites by using an Answer File with ServerManagerCmd, and answer files are included in the \AMD64\Scripts folder.  To use them, you run ServerManagerCmd -ip <Name of File>.  For example:

ServerManagerCmd -ip Exchange-CAS.XML

I recommend that you don’t use the XML Answer Files for Exchange-Typical or Exchange-MBX as is, because in the Beta build it mistakenly includs the Failover-Clustering feature, which does not need to be installed before Exchange is installed.  This is a remnant from the Answer Files we had in Exchange 2007 that we’ve since removed.

Next, are the software pre-requisites, which include:

I’ll start by launching Setup.exe from the AMD64 folder.  This launches the Exchange 2010 splash screen:
 
 
 
 
 

As you can see, the Exchange 2010 splash screen is very similar to the one we had in Exchange 2007.  Any needed pre-requisites which are detected, are greyed out, indicating they have been installed, and that you can proceed to the next step.  In this case, I can proceed directly to Step 4: Install Microsoft Exchange.

I click that link and it launches the GUI version of Exchange Setup, beginning with a file copy process, and the initialization of Setup.

 

 
 

Immediately, you might notice some differences from Exchange Server 2007.  First, the Custom Exchange Server Installation option no longer lists any clustered mailbox server roles.  That’s because clustered mailbox servers don’t exist in Exchange Server 2010.  Exchange 2010 includes a new feature called Incremental Deployment.  This feature enables to you configure high availability and site resilience for your mailbox database after Exchange has been installed.

Second, the default path for the Exchange Server installation is new and different. If I choose Custom Exchange Server Installation, the Server Role Selection page appears:

If I choose Typical Exchange Server Installation instead of Custom Exchange Server Installation and click Next, or once I’ve completed the Custom Exchange Server Installation choices and clicked Next, the Exchange Organization page appears:

If the Exchange organization uses Outlook 2003 or earlier, or Microsoft Entourage, then a public folder database is needed so that those clients can access system data, such as Free/Busy information. In that case, you would select Yes on this page.  Since my organization does not use Outlook 2003 or earlier, or Entourage, I can leave the default setting of No and click Next.

The Customer Experience Improvement Program (CEIP) page appears:

 

 

 
 
 
 

Advertisements