Feb 25, 2014

How to install and configure Exchange 2013 on Windows 2012 R2


In this article we are going to show you how to setup exchange 2013 under windows 2012 R2. This step by step guide will help to demonstrate and deploy exchange mail server in production environment. In this lab we will not cover Active Directory and Windows installation.

Prerequisites:

Active Directory Forest and Domain functionality mode of Windows Server 2003 or higher

Domain Controller OS:

Windows Server 2008 R2
Windows Server 2012 R2 Datacenter edition

Exchange Server OS:

Windows Server 2008 R2 SP1
Windows Server 2012 R2 Datacenter edition

Windows Feature pre-reqs for the mailbox and client access roles:

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, 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

Download



Step1 - Installing windows features:

Start > Run > powershell (enter the following to start windows feature installation)

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, 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


Windows Feature installation Screenshot (Figure 1)

Windows Feature installation completed (Figure 1.1)

Reboot your machine:




Installing remaining prerequisites





Unified Communication Managed API (Figure 2)





















Filter Pack (Figure 3)

 












Filter Pack SP1 (Figure 4)








Step2 - Installing Microsoft Exchange 2013

Click [Don’t check updates right now] Then click [Next]


The installation files will be copied locally from the setup program.


Click Next



Click [I accept terms in the license agreement] Click Next


Click [Don’t use recommended settings] Click Next


In the Server Role Selection section, you need to select the Mailbox and Client access roles. The management tools will be installed automatically. Additionally select to automatically install windows roles and features are required (We did this in an earlier step).

Click Next.


Click Next

Enter a name for your exchange organization. Leave unchecked (apply active directory split permissions security model). 


This screen will perform readiness checks.


Setup will configure any prerequisites and verify exchange is ready to be installed. Since we have preinstalled all prerequisites, exchange is ready to install.

Click Install


Installation started. This will take several minutes to complete


When installation completes you need to reboot the server before you do anything else. After you have restarted the server you can then begin to manage your Exchange 2013 server.


Congratulation, we have completed exchange 2013 installation.

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.

Accessing the EAC

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://exchangeserver/ecpthe internal URL is used to access the EAC from within your organization’s firewall.

External URL: https://mail.yourdomain.com/ecp the 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.

This is our newly installed exchange web-based management console (Enter username and password to get in)


 
Once you logged in. You can manage everything from here.


I have created one mailbox for user “info” lets access it through outlook web access. Enter the address in browser address bar https://mail.yourdomain.com/owa



This is info mailbox


 

Post a Comment

 
TECH SUPPORT © 2012 - Designed by INFOSBIRD