Exchange Server 2013 has been out there for a while for new deployments however only after the release of Exchange Server 2013 CU1 that the transition became a supported scenario (transition from Exchange Server 2007 and 2010 organizations)
In Today’s post we are going over the process to deploy a new Exchange Server 2013 CU1 (Cumulative Update 1) on a Windows Server 2012. The same procedure can be used when deploying a new organization or adding a new Exchange Server to an existent organization (Exchange Server 2007 or 2010).
There are a few requirements when performing a transition from Exchange Server 2007/2010 organization to Exchange Server 2013 and we will be covering those items in future posts.
Exchange Server 2013 has a new architecture related to the server roles, and in this current version, we have two roles to choose from Mailbox or Client Access Server. In this post, we are going to deploy our server with both roles, which is the case in the vast majority of small environments where High Availability and fault tolerance are not a requirement.
There are a couple of prerequisites to deploy Exchange Server 2013, first let’s download all the requirements before going to the technical steps. Here is a list of all software pieces required for our deployment:
- Exchange Server 2013 CU1 or newer CU
- Microsoft Unified Communications Managed API 4.0
- Microsoft Office 2010 Filter Pack 64 bit (only for Mailbox role)
- Microsoft Office 2010 Filter Pack SP1 64 bit (only for Mailbox role)
Logged on the server that will be our future Exchange Server we can start installing the Operating System features required to support an Exchange Server 2013, the following cmdlet has all components (this cmdlet comes from Official documentation).
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation
The above cmdlet in action can be seen in detail in the figure below.
A restart is a good thing, after that we will need to deploy UC using default values, and finally if we are going to have Mailbox role the Microsoft Office Filter Pack and its Service pack are required as well.
Deployment using graphical interface…
Now that we have all software perquisites in place and Exchange Server 2013 CU1 extracted to a local folder on the server we can open that folder and run setup.exe and these follow steps can be used to install the new Exchange Server 2013.
1. In the Check for Updates? Page. Let’s check for any new updates (default setting) and then click Next.
2. In the Downloading Updates page. If there is no updates available just click Next.
3. In the Introduction page. It is just a welcome page, click Next.
4. In the License Agreement page. If we are okay with the license agreement, just click on I accept the terms in the license agreement and then click Next.
5. In the Recommended Settings page. Let’s leave default settings where our server will check online solutions for any error and it will report usage feedback to improve the next generation of the product. Click Next.
6. In the Server Role Selection page. Here we can define which roles will be installed on the current server. In this post, we are going to deploy a single server and for that reason we will select both roles and then click Next.
Note: If you decided to separate roles for the servers, then the recommendation is to install first the Mailbox Server role.
7. In the Installation Space and Location page. By default, the installation folder is C:Program FileMicrosoftExchange ServerV15 and we will leave those default values. Click Next.
Note: During a Recover Server operation, it is always easier to restore when using the default path. If your organization uses a different standard, make sure that the drive where you are going to install is well documented for Disaster Recover purposes.
8. In the Exchange Organization page. This page will only show up if that is the first server to be installed in your Active Directory, if that is the case you need to define an Organization Name, if this page is not displayed then you already have an Exchange Organization in place.
9. In the Malware Protection Settings page. That is a new feature of Exchange Server 2013 and by default is enabled, we can always go back and disable afterwards. Let’s leave default settings which is No and then click Next.
10. In the Readiness Checks page. If we installed all prerequisites properly then we will have an install button available otherwise, we need to check all warning/critical issues and fix them based on the description provided by the setup process.
11. In the Setup Completed page. The installation process results will be displayed and we should have similar results to the one shown in the figure below. Let’s click on Finish and restart the computer.
After restarting our new Exchange Server 2013 we need to start, validating the new deployment and a few steps can be useful, as follows:
Check the new icons created by the Exchange Server 2013 installation process which are: Exchange Toolbox and Exchange Management Shell
- · Run Test-ServicesHealth to check if all Exchange Server 2013 have started properly
- · Check the setup logs located on the folder C:ExchangeSetupLogs
- · Check the Event Viewer logs to validate any error related to Exchange
That is it to install a new Exchange Server 2013! Bear in mind that planning is required to add a new Exchange Server 2013 in an environment with any other version of Exchange and the same rule applies to production environments.
Latest posts by Anderson Patricio (see all)
- Why it is taking so long to receive a message in my Exchange Server? - March 2, 2015
- DPM 2012 R2–ID 30146 unkown error protecting Exchange - February 26, 2015
- How to deploy WSUS to support VMM Update Server - February 25, 2015
- Fixing Network Compliance in VMM - February 24, 2015