- We have a single Active Directory domain (and thus forest) and a single site.
- There is no Edge Server.
- There are some Public Folders but since their use will cease, there is no need to migrate them.
Active Directory environment
I will only summarize the Active Directory requirements here (for full details please consult the Exchange Server Deployment Assistant and related links).
- The Forest Functional Level (or mode) must be at Windows 2003 or above.
- The Schema Master must run at least Windows 2003 SP2 (standard or enterprise, 32 bit or 64 bit - that does not matter).
- Domain controllers in general must run at least Windows 2003 SP2.
- In every site where Exchange will be installed, there must be a global catalog server running at least Windows 2003 SP2.
My test domain controller is a Windows 2008 R2 SP1 server.
My Forest Functional level is Windows 2008 R2.
Exchange server hardware and operating system
In summary, we need:
- A 64 bit operating system (Exchange 2010 is 64 bit only) - either Windows 2008 SP2, Windows 2008 R2 or Windows 2012 (SP3 is required for Windows 2012). Standard version is acceptable unless we want to use Database Availability Groups (DAGs). In that case, we must use the Enterprise version of Windows server (the Enterprise version of Exchange is not necessary for a DAG).
- Windows 7 SP1 for the Exchange Management Tools.
- Memory requirements vary based on roles. 4 GB is minimal for production. 8 GB is better. Some environments may require more memory.
- Storage: any current hard drive will have sufficient space. RAID arrays for the OS, log files and databases are preferred for fault tolerance. Larger environments will most likely use SAN storage, far beyond the scope of this post.
- Client support: Outlook 2007, 2010, 2013, IE 7 to 11 (for OWA premium client).
The above is a simple summary. For a complete (and updated) list of compatible clients, please consult the Exchange Server Supportability Matrix:
Exchange Server Supportability Matrix
Preparation of Active Directory (schema extension)
I would run:
- DCDIAG (various "switches" are possible here - please consult the documentation).
- REPADMIN /replsum
- REPADMIN /showrepl
PS C:\> Add-WindowsFeature RSAT-ADDS
PS C:\> Add-WindowsFeature NET-Framework
- Of course, the location and the name of the folder containing the Exchange setup files will vary.
- We must execute the commands in Powershell (not the simple command line interface).
- We must precede the setup command with .\
- /ps is an abbreviated form of prepareSchema (we can use that as well).
- /p is an abbreviated form of prepareAD.
- If we have multiple domains, we will have to run additional commands in each of those domains.
Note: right-click on the folder to view the properties. We can filter the results so only attributes with values are displayed.
After the schema upgrade, the "Forest (rangeUpper)" value should be 14734 and the "Forest (objectVersion)" should be 14322:.
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-ISAPI-Filter,Web-Digest-Auth,Web-Dyn-Compression,Web-WMI,Web-Asp-Net,NET-HTTP-Activation,RPC-Over-HTTP-Proxy –Restart
Yes, one can copy and paste that text into the Powershell console.
Note: I opted to execute the "setup" commands for schema and general Active Directory preparation. This required the installation of .NET Framework 3.5.1 and related features. So some features were installed before executing the script.
There is one more small script to run afterwards:
Set-Service NetTcpPortSharing -StartupType Automatic
As you probably can see, this sets the start type of the NetTCPPortSharing service to automatic.
The file name was: Windows6.1-KB2550886-x64
This is a hotfix for the Cluster Service.
Office 2010 Filter Pack
In particular, I used a file named "FilterPack64bitv2".
Once all the prerequisites are installed, we can install Exchange 2010 itself.
We can use either the GUI, clicking "Next" as needed, or the command line. I'll use the second option here.
This command should suffice:
PS C:\E2K10SP3> .\setup.com /r:"c,h,m" /ExternalCASServerDomain:mail.mitserv.net
Note: we have to navigate to the location of the installation files. We can indicate "setup.com" or simply enter "setup". Either will work.
At this point, I installed Rollup 6 for Exchange 2010 SP3 as well as Windows updates in general.
This concludes the preparation for and the installation of Exchange 2010 SP3 (RU6).