Exchange 2010 Installation
On the day of the RTM release of Exchange 2010, I successfully installed the RC version on a virtual machine. My delay was not due its difficulty. I ran into those virtual machine foibles such as running out of disk space and accidental shut downs by sons who want to get on www.lego.com.
It would also have speeded up if I found a comprehensive list of the software prereqs. It may be out there but I decided to just run the setup and see what kicked back. So here is what I found:
- Windows Server 2008 SP2. (See note below)
- .net Framework. This is a feature within Windows Server 2008.
- Powershell 2.0. This was mentioned in my previous blog. A hyperlink concerning this is listed on the Setup page.
- Internet Information Service (IIS). This is role in Windows Server 2008.
- World Wide Web service (W3SVC), a sub role of IIS.
- Additional sub roles of W3SVC:
IIS 7 Basic Authentication
IIS 7 Windows Authentication
IIS 7 Digest Authentication
IIS 7 .NET Extensibility
IIS 7 Dynamic Content Compression
IIS 7 Static Content Compression
IIS 7 .NET Extensibility
IIS 6 Metabase Compatibility
IIS 6 Management Console
Web Server (IIS) Tools
- HTTP Activation (under .NET Framework 3.0 Features\WCF Activation\HTTP Activation). This enables additional check boxes under W3SVC.
- Windows Process Activation Service Process Model (I couldn’t figure out where the check box was for this. It was checked through one of the above roles or features.)
- 2007 Office System Converter: Microsoft Filter Pack
During the system check, even after getting the above items running, there were these notifications:
Warning:
If Microsoft Outlook 2003 is in use, you should replicate the free/busy folder on this server to every other free/busy server in the organization. This step should be performed once Setup completes.
Error:
The start mode for the Net.Tcp Port Sharing service must be set to Automatic before Setup can continue.
The Net.TCP Port Shareing service was disabled by default.
The setup process is straight forward. It queried for only a few items before running through the installation:
- CAS server name. This is the intended FQDN for a CAS role that will receive Internet email. I entered the current organization’s “mail.shogun.local” name which is currently hosted by the Exchange 2k3 server.
- The Exchange 2003 server for the Routing Group Connector between the two organizations.
- Participation in the error reporting process.
- Type of Installation. This is the choice between typical and custom. The typical install includes the Mailbox, Hub Transport and Client Access Service roles. Custom allows you to pick and choose. I chose Typical.
Thus with all of the needed information is ran without error, specifically on the final attempt.
Now, here are some steps I learned in cleaning up the botched installation. It failed late in the game thus there was still information about it in Active Directory. Since it was all in Active Directory, I resolved to use ADSI Edit to delete some of the objects. I also used PowerShell to reconfigure the organization to rid it of the failed installation:
- Deleted public and mailbox databases from the Databases node. One big change in Exchange 2010 is the separation of databases from their servers. So there is a new node listing all of the databases.
- Delete the server from the server node.
- Created a new routing group connector between the new Exchange server and the Exchange 2003 server. I used the new-routinggroupconnector command for this. Constructing the command was pretty simple since an example in the get-help new-routinggroupconnector -full output was exactly what I needed.
- Deleted the original routing group connector with the remove-routinggroupconnector command in Powershell.
- Deleted the instance of the original routing group connector in the Exchange 2003’s portion of Active Directory using ADSI Edit.
After this, it appeared that the botch installation was no more to be remembered. I’ll add more steps if I find additional remnants.
Note: After posting this blog, I found the Technet page concerning the prereqs. I know I should be looking for this before hand, but I was just playing around with the install for training purposes. http://technet.microsoft.com/en-us/library/bb691354.aspx
Here are some additional tidbits to be aware of...
It would also have speeded up if I found a comprehensive list of the software prereqs. It may be out there but I decided to just run the setup and see what kicked back. So here is what I found:
- Windows Server 2008 SP2. (See note below)
- .net Framework. This is a feature within Windows Server 2008.
- Powershell 2.0. This was mentioned in my previous blog. A hyperlink concerning this is listed on the Setup page.
- Internet Information Service (IIS). This is role in Windows Server 2008.
- World Wide Web service (W3SVC), a sub role of IIS.
- Additional sub roles of W3SVC:
IIS 7 Basic Authentication
IIS 7 Windows Authentication
IIS 7 Digest Authentication
IIS 7 .NET Extensibility
IIS 7 Dynamic Content Compression
IIS 7 Static Content Compression
IIS 7 .NET Extensibility
IIS 6 Metabase Compatibility
IIS 6 Management Console
Web Server (IIS) Tools
- HTTP Activation (under .NET Framework 3.0 Features\WCF Activation\HTTP Activation). This enables additional check boxes under W3SVC.
- Windows Process Activation Service Process Model (I couldn’t figure out where the check box was for this. It was checked through one of the above roles or features.)
- 2007 Office System Converter: Microsoft Filter Pack
During the system check, even after getting the above items running, there were these notifications:
Warning:
If Microsoft Outlook 2003 is in use, you should replicate the free/busy folder on this server to every other free/busy server in the organization. This step should be performed once Setup completes.
Error:
The start mode for the Net.Tcp Port Sharing service must be set to Automatic before Setup can continue.
The Net.TCP Port Shareing service was disabled by default.
The setup process is straight forward. It queried for only a few items before running through the installation:
- CAS server name. This is the intended FQDN for a CAS role that will receive Internet email. I entered the current organization’s “mail.shogun.local” name which is currently hosted by the Exchange 2k3 server.
- The Exchange 2003 server for the Routing Group Connector between the two organizations.
- Participation in the error reporting process.
- Type of Installation. This is the choice between typical and custom. The typical install includes the Mailbox, Hub Transport and Client Access Service roles. Custom allows you to pick and choose. I chose Typical.
Thus with all of the needed information is ran without error, specifically on the final attempt.
Now, here are some steps I learned in cleaning up the botched installation. It failed late in the game thus there was still information about it in Active Directory. Since it was all in Active Directory, I resolved to use ADSI Edit to delete some of the objects. I also used PowerShell to reconfigure the organization to rid it of the failed installation:
- Deleted public and mailbox databases from the Databases node. One big change in Exchange 2010 is the separation of databases from their servers. So there is a new node listing all of the databases.
- Delete the server from the server node.
- Created a new routing group connector between the new Exchange server and the Exchange 2003 server. I used the new-routinggroupconnector command for this. Constructing the command was pretty simple since an example in the get-help new-routinggroupconnector -full output was exactly what I needed.
- Deleted the original routing group connector with the remove-routinggroupconnector command in Powershell.
- Deleted the instance of the original routing group connector in the Exchange 2003’s portion of Active Directory using ADSI Edit.
After this, it appeared that the botch installation was no more to be remembered. I’ll add more steps if I find additional remnants.
Note: After posting this blog, I found the Technet page concerning the prereqs. I know I should be looking for this before hand, but I was just playing around with the install for training purposes. http://technet.microsoft.com/en-us/library/bb691354.aspx
Here are some additional tidbits to be aware of...
- If you want to use the high availability feature of Exchange 2010, you will need W2k8 Enterprise Edition.
- .net Framework 3.5 SP1 is required. At some point, it was installed on my server however, I didn't specifically launch an installation of it.
- The MS Office Filter Pack is required on HT or MB roles.
- To install all of the required roles and features on a W2k8 server, Exchange 2010 offers a scripts folder with .xml files which can be ran with the ServerManagerCMD command. You can select a script based on the planned Exchange roles.
- To install all of the required roles and features on a W2k8 R2 server, the above web site has PowerShell commands to install them. You can copy and paste it to the Exchange server.
Comments