In this quick post, we’ll have a look at how to install a typical Exchange 2010 Service Pack 3 installation on Server 2012, which is fully supported with the latest service pack for Exchange 2010, Service Pack 3. We’ll avoid the organization preparation and post-install configuration as nothing has changed between 2008 R2 and 2012; this guide is based on an install into an existing domain with Exchange installed on another server.
First and foremost – update your Windows Server 2012. There’s a few bugs that cause issues with installing the .NET Framework 3.5 on a fresh 2012 install, so making sure you’re up to date with Windows Updates can avoid any pain.
Next, install the role and feature pre-requisites from a PowerShell prompt. These differ slightly from the Windows 2008 R2 guidance:
Add-WindowsFeature NET-Framework-Core,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,Web-Mgmt-Tools,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,Web-Asp-Net,Web-Client-Auth,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Http-Redirect,Web-Http-Tracing,Web-ISAPI-Filter,Web-Request-Monitor,Web-Static-Content,Web-WMI,RPC-Over-HTTP-Proxy -Restart
Extract Exchange 2010 SP3 to a convenient location
Download Exchange 2010 SP3 and extract it to a convenient location. We install directly from Service Pack 3 – all Exchange Service packs are slip-streamed.
Installing Exchange from the command prompt
After installing the pre-reqs, you can perform an unattended, typical install by opening an elevated command prompt and executing the following command:
setup.com /mode:install /r:ca,ht,mb
Installing Exchange from the GUI
Or, if you prefer, launch setup.exe and perform a GUI-based installation. You’ll notice the GUI looks slightly out of place in Windows Server 2012, but functions perfectly:
Finalise your installation
Open the Exchange Management Console, or the Exchange Management Shell. You’ll see that the EMC looks familiar, but takes some of the new Windows Server 2012 GUI styling. Looks good, doesn’t it!
A quick note regarding the Exchange Management Shell
If you examine the shortcut for the Exchange Management Shell, you’ll see that it launches under PowerShell version 2.0. This indicates that you won’t necessarily be able to take advantage of PowerShell 3.0 features directly within the Exchange Management Shell, although the rest of your Windows 2012 server has the PS 3.0 facilities.