The most of you start wander “Where is the EMC (Exchange Management
Console) in Exchange Server 2013?” Well, some things remain the same as login
in the new Exchange Server 2013, and other things change (this is the
technology). Let’s see together which are the things are new in Exchange Server
2013, one of those is the EMC (Exchange Management Console).

Where
is the EMC (Exchange Management Console) and how where we can find it?
Almost everything in new Exchange 2013 is web-based management console, not EMC
(Exchange Management Console) but EAC (Exchange Administration Center), that
allows for ease of use and is optimized for on-premises, online, or hybrid
Exchange deployments. The EAC replaces the Exchange Management Console (EMC)
and the Exchange Control Panel (ECP), which were the two interfaces that were
used to manage Exchange Server 2010. One of the advantages of having the
web-based EAC is that you can partition access from the Internet/Intranet from
within the ECP IIS virtual directory to allow or disallow management features.
This allows you to permit or deny access to users trying to access the EAC from
the Internet outside of your organizational environment, while still allowing
access to an end-user’s Outlook Web App Options.

How can I login to EAC?

If we navigate to IE (Internet Explorer) and type http://server
FQDN/ecp (in my scenario is https://e2013.cloud.com/ecp

and voila, you are now logged in the new EAC old EMC console..

Supported browsers

For the best experience with the EAC, use one of the operating system and browser combinations labeled “Premium”.

• Premium: All functional features are well-supported and fully tested.
• Supported: Has same functional feature support as premium; however, supported browsers will be missing features that the browser and operating system combination doesn’t support.
• Unsupported: The browser and operating system isn’t supported or tested.

As we mention in Part1, Exchange Server 2013 has 2 server roles, Mailbox Server role and Client Access
Server role. We have the option to install either single server role or both the roles on the same computer.
In any case of installation role, CAS Role or both servers roles (CAS and Mailbox), Exchange Management Tools will be
installed together.

After you extract the Exchange-x64.exe file, start the exchange 2013 installation by click on the
setup file available on the installation file. Below window appears up,
check the option “Connect to the Internet and check for Updates” and click next to
continue.

On the Introduction page, read the information and click next to continue. If you plan
to use to Deployment assistant click on the necessary option.

Accept on the License Agreement page and click Next to continue

On the Error Reporting Window, Click Yes and Click Next to continue

Next step will automatically check for the required software if is installed in the
Server, if any issue appear, it will prompt you to fix it. If no error click
Next to Continue

On the Server Role Selection Windows, if it is standalone installation select both the
Mailbox and Client Access Server role and click Next to continue

Installation Space and Location windows will allow an option to change the installation
path, make necessary change or leave the default path and click Next

Type the Exchange Organization name and click Next 

Malware Protection Setting, this option is new in Exchange 2013 which will by default
scan all the emails, if you are using other option disable the option and click
Next to continue

If this Exchange 2013 server is an internet facing client access server then check the
option and enter the internet domain name. If not leave it as it is and click
Next to continiue.

On the Customer Experience Improvement Program, read the information, choose the
required option and click Next to continue

Readiness check windows will check of the all the options prior to install the Exchange
Server 2013. If everything is normal, then the installation will start.

Once the readiness check is completed Exchange Server 2013 installation will happen.
Once it is completed, click finish is complete the installation.

Enjoy..

In this post, we will see step by step the process of Exchange Server 2013 Preview installation in Windows Server 2012. 

The new Exchange Server 2013, split in 2 roles Client Access Server and Mailbox Server (In addition, Exchange 2013 Preview works with the Exchange 2010 Edge server role.)  The Mailbox server includes all the traditional server components found in Exchange 2010: the Client Access protocols, Hub Transport service, Mailbox databases, and Unified Messaging. The Mailbox server handles all activity for a given mailbox. The Client Access server provides authentication, redirection, and proxy services. The Client Access server itself doesn’t do any data rendering. The Client
Access server is a thin and stateless server. There is never anything queued or stored on the Client Access server. The Client Access server offers all theusual client access protocols: HTTP, POP and IMAP, and SMTP.

Before we proceed, we need to check the prerequisites for Exchange Server 2013, let’s see what we need to check before we begin:

• Make sure that the functional level of your forest is at least Windows Server 2003, and that the schema master is
  running Windows Server 2003 with SP1 or later.
• The full installation option of Windows Server 2012 and Windows Server 2008 R2 SP1 must be used for all servers
  running Exchange 2013 Preview server roles or management tools.
• You must first join the computer to the appropriate internal Active Directory forest and domain.
• Some prerequisites require you to reboot the server to complete installation.

To prepare Active Directory for Exchange 2013 Preview, you must install the following software on the computer that will be used to prepare Active Directory:

• Microsoft .NET Framework 4.5
• Windows Management Framework 3.0

After you install the software, open Windows PowerShell and install the Remote Tools
Administration Pack.

On a Windows Server 2012 computer, run the following command:
Add-WindowsFeature RSAT-ADDS

OS prerequisites for both the CAS and Mailbox roles:
Do the following to install the required Windows roles and features:

1. Open Windows PowerShell.
2. Run the following command to install the required Windows components.

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

After you’ve installed the operating system roles and features, install the following
software in the order shown:

1. Microsoft Unified  Communications Managed API 4.0, Core Runtime 64-bit
2. Microsoft Office 2010 Filter Pack 64 bit
3. Microsoft Office 2010 Filter Pack SP1 64 bit

For Exchange 2013 Preview, you must also uninstall Microsoft Visual C++ 11 Beta Redistributable
(x64). This must be done after you’ve installed UCMA, but before you run Exchange 2013 Preview Setup.
To uninstall Microsoft Visual C++ 11 Beta Redistributable (x64), do the following:

1. Open Control Panel > Programs and Features.
2. Select Visual C++ 11 Beta Redistributable (x64) – 11.0.50531 and then click Uninstall.
3. In Microsoft Visual C++ 11 Beta setup, click Uninstall.
4. When Microsoft Visual C++ 11 Beta is uninstalled, click Close.

To be continue….