If you haven’t download it yet you can do that from the following address and the download will be a file called Exchange-x64.exe. After finishing the download, we need to double click the executable and extract the contents to a folder. In this article let’s create a folder called EX2013.
After extracting the contents, open the same folder and double click setup.exe (the last file from the list).
The new installation process has a couple of new features besides of the new design. The first one is that now the setup is able to check on the Internet and validate the last rollup, security and language packs available and this option allows the setup itself to be updated.
The first stage of the setup wizard is to connect to the internet and search for new updates. These are the main steps of the first stage:
- In the Check for Updates page . Let’s use the default setting and click on Next, this process may take some time.
- On the Downloading Updates page. Wait for the Next button to be available and then click it
The setup will take some time to copy files (In the Preview version we had a next button but it was removed in this final version). Now, the Introduction page is shown and the real deployment will start. The following steps can be used to finalize the deployment:
- On the Introduction page. That’s our official welcome page, on this page we can find a couple of links about Exchange Server 2013, let’s click Next.
- On the License Agreement page. After reading the license agreement and if you agree with it, please select I accept the terms in the license agreement and then click Next.
- On the Recommended Settings page. We can decide if we are going to provide usage feedback to Microsoft and also check online for a solution when an error occurs. Let’s leave the default settings (Use recommended settings) and click Next.
- On the Checking Required Software page. If all required software is installed the Next button will be available, if you take more than 10 seconds to take an action the wizard will move forward to the next page automatically.
- On the Server Role Selection page . In this page we have the first big change in Exchange Server 2013 where our 5 (five) roles that were introduced in Exchange Server 2007/2010 are replaced by just two roles: Mailbox Roles and Client Access Role. Based on our scenario we are going to install the Mailbox server (UYEX01) using GUI and the other server will be based on the command-line. Click Next.
Bear in mind that we still have the option Automatically install Windows Server roles and features that are required to install Exchange Servers which will install all Operating System components to support the selected roles.
- On the Installation Space and Location page. In this section we can validate the disk available and the amount required to deploy Exchange Server 2013 and define the installation location for the product. Let’s leave the default settings and click Next.
- On the Exchange Organization page. Since we are building our environment from scratch a new organization will be required. The Exchange organization boundary is our Active Directory forest. Let’s name our Organization and click Next.
Note: if you want to split permissions where the Exchange Administrators won’t be able to manage Active Directory objects then the option Apply Active Directory split permissions security model to the Exchange Organization should be selected.
On the Malware Protection Settings page . That is a new feature of Exchange Server 2013, where we have Malware protection and this option can be managed through Exchange Administration Center or Exchange Management Shell afterwards. Let’s leave the default settings and click Next.
- On the Readiness Checks page . In this section we will have a summary of all pre-requisites and if the server is ready to receive Exchange Server 2013. If we have missed any software component we will be notified at this stage and we need to fix it before moving forward. If all testing went fine, then the Install button will be available and we can proceed to the next step.
At this point all the required features were installed on the server. Just run Get-WindowsFeature in a PowerShell session and you will notice that all features are shown as installed.
In some cases the readiness can display that all features are not installed, if that is the case run a Get-WindowsFeature and if you see the features required by Exchange showing as InstallPending, just restart the server and run the setup again and you will be fine.
- On the Setup Progress page (Figure 09). The process may take some time depending on your hardware configuration and it is divided in 13 stages (Yes, the bar goes 1 to 100% for each stage). If everything goes well we will receive information that the Setup has completed and the Complete button will be available. In this release there isn’t an option to open Exchange Management Console because it doesn’t exist anymore. From now on, our admin interfaces will be through Exchange Admin Center and Exchange Management Shell.
Installing Exchange Server 2013 using command-line
The installation process is similar to what we have in Exchange Server 2007/2010 where it is done by setup.exe from the main folder of the Exchange Server 2013 installation folder. We can run the setup.exe only to find out the available switches but in order to install a Mailbox role we can run the following command: .\Setup.exe /role:ClientAccess,ManagementTools /IacceptExchangeServerLicenseTerms as shown in figure 10.
To get the domain fully prepared, we need the membership of Domain Admins, Schema Admins, and Enterprise Admins. Indeed, using a user account that is a member of all three of those groups will give you all the rights you need.
In some larger organizations, though, getting a user account that is a member of all three of these groups is impossible. In some cases, the Exchange Server administrator may have to make a request from the Active Directory forest owner to perform some of the preparation tasks on
behalf of the Exchange Server team. For this reason, it is important to know the permissions that are required to perform the different setup tasks, as shown
Task Group Membership
|Setup /PrepareSchema or setup /ps||Schema Admins and Enterprise Admins|
|Setup /PrepareAD or setup /p||Enterprise Admins|
|Setup /PrepareDomain or setup /pd||Domain Admins|
|Install Exchange Server 2013||Administrators group on the Windows server and Exchange|
Troubleshooting the installation process…
Exchange setup process has been improved with each new release and the readiness check will clear most of the possible issues before the installation process starts, however, if you are still having issues you can always check the log files generated by the setup process. These log files can be found in C:\ExchangeSetupLogs and each file contains log information that allows us to track down the steps being performed by the setup process (Figure 11).
You can check the logs to track all steps performed during the setup process in the ExchangeSetup file.
Exchange Admin Center
The Exchange Admin Center (EAC) is the web-based management console in Microsoft Exchange Server 2013 that’s optimized for on-premises, online, and hybrid Exchange deployments. The EAC replaces the Exchange Management Console (EMC) and the Exchange Control Panel (ECP), which were the two interfaces used to manage Exchange Server 2010.
One advantage a web-based EAC provides is that you can partition Internet and intranet access from within the ECP IIS virtual directory. With this functionality, you can control whether users are allowed to have Internet access to the EAC from outside of your organization, while still allowing an end user to access Outlook Web App Options. For more information, see Turn off access to the Exchange admin center.
Looking for the Exchange Online version of this topic? See Exchange admin center in Exchange Online.
Looking for the Exchange Online Protection version of this topic? See Exchange admin center in Exchange Online Protection.
Because the EAC is now a web-based management console, you’ll need to use the ECP virtual directory URL to access the console from your web browser. In most cases the EAC’s URL will look similar to the following:
- Internal URL:
https://<CASServerName>/ecpThe internal URL is used to access the EAC from within your organization’s firewall.
- External URL:
https://mail.contoso.com/ecpThe external URL is used to access the EAC from outside of your organization’s firewall. Some organizations may want to turn off external access to the EAC. For details, see Turn off access to the Exchange admin center.
To locate the internal or external URL for the EAC, you can use the
Get-EcpVirtualDirectory cmdlet. For details, see Find the internal and external URLs for the Exchange admin center.
If you’re in a coexistence scenario, where you’re running Exchange 2010 and Exchange 2013 in the same organization, and your mailbox is still housed on the Exchange 2010 Mailbox server, the browser will default to the Exchange 2010 ECP. You can access the EAC by adding the Exchange version to the URL. For example, to access the EAC whose virtual directory is hosted on the Client Access server CAS15-NA, use the following URL:
https://CAS15-NA/ecp/?ExchClientVer=15. Conversely, if you want to access the Exchange 2010 ECP and your mailbox resides on an Exchange 2013 Mailbox server, use the following URL:
The user you use should be a member of Organization management group, the user you used to install the Exchange server is a member be default, if you want to add another user to this group, you should use the installation user to operate.
The section describes the user interface elements that are common across the EAC.
The cross-premises navigation allows you to easily switch between your Exchange Online and on-premises Exchange deployments. If you don’t have an Exchange Online organization, the link will direct you to the Office 365 sign-up page. To learn more, see Exchange Server Hybrid Deployments.
This is the first level of navigation for most of the tasks that you’ll perform in the EAC. The feature pane is similar to the console tree from the EMC in Exchange 2010. However, in Exchange 2013 the feature pane is organized by feature areas as opposed to server roles, and there are fewer clicks to find what you need.
- Recipients This is where you’ll manage mailboxes, groups, resource mailboxes, contacts, shared mailboxes, and mailbox migrations and moves.
- Permissions This is where you’ll manage administrator roles, user roles, and Outlook Web App policies.
- Compliance management This is where you’ll manage In-Place eDiscovery, In-Place Hold, auditing, data loss prevention (DLP), retention policies, retention tags, and journal rules.
- Organization This is where you’ll manage the tasks that pertain to your Exchange Organization, including federated sharing, Outlook Apps, and address lists.
- Protection This is where you’ll manage anti-malware protection for your organization.
- Mail flow This is where you’ll manage rules, delivery reports, accepted domains, email address policies, and send and receive connectors.
- Mobile This is where you’ll manage the mobile devices that you allow to connect to your organization. You can manage mobile device access and mobile device mailbox policies.
- Public folders In Exchange 2010, you had to manage public folders by using the Public Folder Management Console, which was located outside of the EMC in the Toolbox. In Exchange 2013, public folders can be managed from within the public folders feature area.
- Unified Messaging This is where you’ll manage UM dial plans and UM IP gateways.
- Servers This is where you’ll manage your Mailbox and Client Access servers, databases, database availability groups (DAGs), virtual directories, and certificates.
- Hybrid This is where you’ll set up and configure a Hybrid organization.
Activate Exchange Server
In ECP, from the left side menu, click on servers, then in the right pane, click Enter Product Key, click general ,then enter the key.