The process of installing Exchange 2013 using the guided GUI is pretty straightforward, provided you’ve taken care of the prerequisites, prepared for gotchas (about which, more later) and planned your deployment carefully.
For the purpose of capturing the process, I created an Amazon Web Services based test environment (similar to the one described here) consisting of a domain controller, an Exchange 2010 server and the server on which Exchange 2013 was installed.
All servers are Windows 2012 R2 and the domain functional level is Windows 2012.
So, the scenario is that you’re installing Exchange 2013 into an existing Exchange 2010 SP3 organization and all roles have been selected.
Before running Setup.exe on your target host you should make sure the following is true:
1.) Microsoft Office Filter Pack Ver 2.0 is installed
2.) The service pack for the Office Filter Pack is installed
3.) Media Foundation is installed (to support the Unified Communications API) – to install, from a Powershell session run the following as admin: Install-WindowsFeature Server-Media-Foundation (note: a server reboot is required).
4.) Microsoft Unified Communications Managed API 4.0 is installed
5.) Windows 2012’s firewall has been configured to allow all inbound traffic from domain members as described in this blog post (this is done to prevent a known issue in which, after installing Exchange 2013, Remote Desktop connections are denied because of a modification to the firewall rules ).
Once all of the prerequisites have been satisfied, you can run Setup.exe.
The first screen provides an overview of your installation options:
By clicking Next, you’ll be taken to the License Agreement page:
You can choose to either use – or forego – Microsoft’s recommended settings
Next, you’ll choose what server roles to install. In our scenario, all components are selected. Note that in Exchange 2013, server roles have been simplified quite a bit as explained in detail in this Technet article.
As with previous versions of Exchange, you choose the target folder for the application binaries.
One of the new elements of the setup process is choosing whether or not to deploy Exchange 2013’s anti-malware features. In our scenario, we’re choosing to disable this feature (because another product is in-place).
Next, the setup process will verify that the installation prerequisites have been satisfied.
In my installation, I neglected to install the Unified Communications API and received this error message:
Once that was taken care of, clicking “Retry” moved the process along.
Now the setup process begins to make actual progress.
There are 15 steps (details dependent upon the roles selected earlier in the install process).
Note that, as explained in this Technet article, the two building blocks of Exchange 2013 – Mailbox and Client Access – have assumed responsibility for all of the platform’s operational components. The installation process reveals parts of this design.
1.) Organization Prep
2. – 3.) Copying files
4.) Installing language files
5.) Restoring services (stopped during step one)
6.) Language file installation
7.) Installing Management Tools
14.) Finalizing Setup
Once setup is complete and your server has reset, you can begin managing Exchange 2013.
Exchange 2013 introduces admins to the Exchange Admin Center which replaces Exchange 2010’s Exchange Management Console.
The default URL is https://your-exchange2013-server-name/ecp
The first time you logon, you may be redirected to OWA. To work around this, try the following URL from the console of the Exchange 2013 server:
In a future post, we’ll review navigating the EAC and performing basic administrative tasks, such as migrating users between databases.