Exchange 2010 SP1 Hosting Lab (1) Installation
This is the first post of a series of articles which describe the steps executed in preparing exchange 2010 SP1 Hosting Lab.
The lab characteristics can be summarized as follow:
- Active Directory
- Server Name: LAB02AD01
- IP address: 192.168.2.11
- Operating System: Windows 2008 R2 Enterprise
- Exchange CAS-HUB
- Server Name: EXCHCHT01
- IP Address: 192.168.2.12
- Operating System: Windows 2008 R2 Standard
- Exchange Mailbox
- Server Name: EXCHMBX01
- IP Address: 192.168.2.13
- Operating System: Windows 2008 R2 Enterprise
- Domain FQDN: LAB02.local
- Domain NetBIOS: LAB02
- Username: Administrator
Future LAB Expansion plan:
- DAG for mailbox
- NLB for CAS-HUB
- Publishing
This Articles will be divided into 3 sections:
- Active Directory Preparation
- Prerequisite Requirements
- Roles Installation
Preparing Active Directory for hosting is similar to the regular version, you just need to add /hosting in the end.
You can find below the different parameters you can use”
I followed the below in this lab:
- Login LAB02AD01
- Open Cmd with Administrative Privilege
- Run the following: setup /prepareschema /hosting
- Login LAB02AD01
- Open Cmd with Administrative Privilege
- Run the following: setup /prepareAD /organizationName:LAB02 /hosting
Active Directory is now prepared for Hosting, hence you will need to use the /hosting for all the installation.
Installing Exchange roles in a hosting environment is similar to the regular installation, hence, the same prerequisites are needed.
you can check them at https://technet.microsoft.com/en-us/library/bb691354.aspx
for this lab, I have installed the requirements for windows 2008 R2.
Prerequisites
- Make sure that the functional level of your forest is at least Windows Server 2003, and that the schema master is running Windows Server 2003 with Service Pack 1 (SP1) or later. For more information about the Windows functional level, see Managing Domains and Forests.
- The full installation option of Windows Server 2008 with SP2 or later or Windows Server 2008 R2 must be used for all servers running Exchange 2010 server roles or management tools.
- For all server roles other than the Edge Transport server role, you must first join the computer to the appropriate internal Active Directory forest and domain.
Required Exchange 2010 SP1 Hotfixes for Windows Server 2008 R2
The following hotfixes are required for the Client Access server for Windows Server 2008 R2:
- Install the update described in Knowledge Base article 979099, An update is available to remove the application manifest expiry feature from AD RMS clients. Without this update, the AD RMS features may stop working.
- Install the hotfix described in Knowledge Base article 982867, WCF services that are hosted by computers together with a NLB fail in .NET Framework 3.5 SP1. For more information, see these MSDN Code Gallery pages:
- For additional background information, see KB982867 - WCF: Enable WebHeader settings on the RST/SCT.
- For the available downloads, see KB982867 - WCF: Enable WebHeader settings on the RST/SCT.
- Install the update described in Knowledge Base article 979744, A .NET Framework 2.0-based Multi-AppDomain application stops responding when you run the application.
- Install the update described in Knowledge Base article 983440, An ASP.NET 2.0 hotfix rollup package is available for Windows 7 and for Windows Server 2008 R2. For more information, see these MSDN Code Gallery pages:
- For additional background information, see KB983440 - Win7 rollup package (PR for QFE 810219).
- For the available downloads, see KB983440 - Win7 rollup package (PR for QFE 810219).
After installing the requirements, I will install the roles and features required for each roles, and the install Exchange 2010 Sp1.
Starting with the Exchange CAS-HUB Server, I did the following:
From an elevated powershell, run the following:
- Import-Module ServerManager
Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy -Restart
From the Command prompt
- Go to the exchange setup location
- run setup /mode:install /roles:CA,HT /hosting
For the exchange Mailbox Server, I did the following:
From an elevated PowerShell, run the following:
- Import-Module ServerManager
Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server -Restart
From the Command prompt
- Go to the exchange setup location
- run setup /mode:install /roles:MB /hosting
That’s it for this article, the next article in this series will discuss the configuration of exchange.
Comments
Anonymous
January 01, 2003
great, i'll test itAnonymous
September 13, 2010
Nice Rony :) waiting your next artical we need some configuration stuff.Anonymous
October 21, 2010
Awesome article, please continue posting, it's very helpful. I just add that in my case the KB979099 was not necessary, but FilterPack64bit and KB977020 was mandatory for successful HT and CA prerequisite checks. ThanksAnonymous
September 22, 2011
hey man thanks for this blog when will you continue to the 2nd part? CheersAnonymous
March 08, 2012
That’s it for this article, the next article in this series will discuss the configuration of exchange. Where is configuration ? Thanks!