You are on page 1of 9

1. Whats New in Exchange Server 2013?

Below are the new features in Exchange Server 2013


1. New Unified Management console called Exchange Admin Center
2. Server Roles architecture changed to two Server Roles Mailbox Server Role and Client
Access Server Role
3. Public Folders are now in Mailbox Databases which can be replicated to other mailbox
databases
4. Site Mailbox introduced to allow the user to access the SharePoint sites and emails from
Outlook 2013, using the same client interface
5. Exchange 2013 Offers greater integration with SharePoint 2013 and Lync 2013
6. Brand new Outlook Web App optimized for tablets and mobile devices and also for
desktops and laptops
7. Unified Messaging in Exchange 2013 comes with same voice mail features in Exchange
2010, but the architecture change to have only two server roles made all the UM related
components, services and functionality are now available in Mailbox Server Role
8. Users can Move Mailboxes in batches where it has an option to send mailbox move
reports as emails
9. Lot of enhancement in the Database Availability Group like Managed Availability and
Managed Store etc
10. Exchange work load is a new feature in Exchange 2013 defined for the purpose of
Exchange System Resource Management
11. Exchange 2013 is completely rewritten so deploying and keeping exchange 2013 to up to
date is now easier
12. Data Loss Preventions is a new feature which allows to protective the company sensitive
data and inform user of internal compliance policies
2. What is Exchange Admin Center?
Exchange Admin Center is the new web based Exchange Management Console for Exchange
Server 2013, it allows for ease of use and is optimized for management of On-Premises, Online
and hybrid Exchange deployments. EAC replaces Exchange Management Console and
Exchange Control Panel, but ECP is still the url for Exchange Admin Center
New features in Exchange Admin Center
1. List View More than 20,000 objects can be viewed in EAC, where legacy ECP allows
only 500 objects
2. Add/Remove columns for recipients

3. Public folders can be managed from Exchange Admin Center


4. Long running process will be notified in the notification bar
5. Role Based Access Control user editor can be done from EAC
6. Unified Messaging tools like call statistics, and user call logs can be accessed from EAC
3. Explain the Exchange 2013 Architecture?
Legacy versions of Exchange 2007 and Exchange 2010 released with 5 server roles, ie, Mailbox,
Client Access, Hub Transport, Unified Messaging and Edge Transport server. Server role
architecture has been changed in Exchange 2013 which released with only two server roles.
Mailbox Server role It holds the same function of Mailbox, the client access protocols, Hub
Transport and Unified Messaging server role in Exchange 2010
Client Access Server role work as the client access server role in Exchange 2010, Exchange
2010 work as only stateless server, where it doesnt do any data rendering, and nothing will be
stored or queued in Client Access Server role. CAS offers all usual client access protocols:
HTTP, POP and IMAP, and SMTP
4. Why Exchange 2013 architecture has been changed with two server roles?
Exchange 2007 and 2010 were architect with certain technology constraint that existed at that
time, where CPU performance was the Key constraint when Exchange 2007 was released and to
alleviate the situation Server roles were introduced. However server roles in Exchange 2007 and
Exchange 2010 are tightly coupled
Nowadays, CPU horse power is less expensive and it is not a constrain factor, with that
constraint lifted, primary goal for Exchange 2013 is simplicity of scale, hardware utilization and
failure isolation. So Microsoft reduced the number of server roles to two as Client Access Server
Role and Mailbox Server Role
5. What are the benefits on the architecture change by having two server roles in
Exchange 2013?
Having two server roles with Mailbox Server includes all the traditional components fount in
Exchange 2010: the client access protocols, transport service, mailbox databases and unified
messaging and the Client Access Server role to provide authentication, limited redirection and
proxy services. New architecture provides the below benefits

1. The Client Access Server and Mailbox Server become Loosely Coupled. All process
and activity for a specific mailbox occurs on the mailbox server that holds the active
database copy, eliminating concerns of version compatibility between CAS and Mailbox
Server
2. Version Upgrade flexibility Client Access server can be upgraded independently and in
any order.
3. Session affinity to client access server role is not required In Exchange 2013, Client
access and mailbox components available on the same mailbox server, because the
client access server simply proxies all connections to a specific mailbox server, no
session affinity is required
4. Only two namespace is required for Exchange 2013
6. What is change related to MAPI access using outlook in Exchange 2013?
Two server role architects changed the outlook client connectivity behaviour; RPC is no longer a
supported direct access protocol. This means that all the outlook connectivity must take place
using RPC over HTTP knows as Outlook Anywhere. Because of this behaviour, there is no need
to have RPC client access service on CAS which reduces two name spaces that required for
site-resilient solution.
7. Explain the change in outlook client connection behaviour when compared with
Exchange 2010?
Outlook clients no longer connect to a server FQDN as they have done in all previous versions of
Exchange. Outlook uses Autodiscover to create a new connection point comprised of mailbox
GUID, @ symbol, and the domain portion of the users primary SMTP address. This change
results in a near elimination of the unwelcome message of Your administrator has made a
change to your mailbox. Please restart. Only Outlook 2007 and higher versions are supported
with Exchange 2013.
8. What is Managed Store in Exchange 2013?
Managed store is the name of the newly rewritten information store
process, Microsoft.Exchange.Store.Service.exe andMicrosoft.Exchange.Store.worker.exe, it is
integrated with Microsoft Exchange replication server to provide higher availability through
improve resiliency. Also the Managed store has been architected to enable more granular
management of resource consumption and faster root cause analysis though improved
diagnostics.

Managed Store works with replication service to manage mailbox databases, which continues to
ESE as DB engine, Exchange 2013 includes change the mailbox database schema that provides
many optimization over previous versions of Exchange and Replication Services is responsible
for all availability related to Mailbox Servers. This change provides faster database failover and
better disk failure handling.
9. What is a Site Mailbox?
Site Mailbox is a new type of mailbox in Exchange 2013, where it improves collaboration and
user productivity by allowing access to both documents in a SharePoint site and email messages
in outlook 2013 using the same client interface.
10. What happened to Public Folders in Exchange 2013?
Special type mailbox called Public folder mailbox introduced in Exchange Server 2013, which will
store both the hierarchy and public folder content. This provides an advantage of the existing
high availability and storage technologies of the mailbox store. Legacy Public folder database
concept not in exchange 2013 and Public Folder replication now user the continuous replication
model as like Mailbox Database.
11. How the Mail flow Occur in Exchange Server 2013?
Due the architectural change, Mail flow in Exchange 2013 occurs via Transport Pipeline, it is
collection of Transport services, connections, components and queues that work together to
route the messages to the categorizer in the transport service on a mailbox server inside the
organization.
Messages from outside organization enter the transport pipeline through a receive connector in
the Front End Transport service on a client access server and then routed to the Transport
Service on a Mailbox Server and the Mailbox Transport Delivery Service deliver the email to local
mailbox database
Message from inside organization enter the Transport Service on a Mailbox Server in following
ways, receive connector, Pick Up or Replay Directory, Mailbox Transport Service or Agent
Submission. Those emails can be relayed to Front End transport service on Client Access Server
using the Transport Service on Mailbox Server and sent outside
12. Explain the New Transport Pipeline in Short?

Front End Transport Service in Client Access Server acts as a stateless proxy for all inbound and
outbound external SMTP traffic for Exchange 2013 organization. It wont inspect message
content, only communicates with the Transport Service on a Mailbox Server, and doesnt queue
any messages locally.
Transport Service in Mailbox server is identical to Hub Transport server, it handles all SMTP mail
flow for the organization, perform message categorization, and performs content inspection. It
wont communicate directly with Mailbox Database that task will be handled by Mailbox Transport
Service. So the Transport Service routes messages between the mailbox transport service, the
transport service and the front end transport service.
Mailbox Transport Service running on Mailbox server consists of two separate services: the
Mailbox Transport Submission Service and Mailbox Transport Delivery Service.
Mailbox Transport Delivery Service receives emails from Transport Service on the local or
different mailbox server and connects to the local mailbox databases using Exchange RPC to
deliver the message
Mailbox Transport Submission Service connects to local mailbox database using RPC to retrieve
messages and submits the messages over SMTP to the Transport Service on the local Mailbox
server or other Mailbox Servers.
13. What are the enhancements in Batch Mailbox Move on Exchange 2013?
Below are the enhancements on Exchange 2013 Batch Mailbox Moves,

Multiple mailboxes move in large batches.

Email notification during move with reporting.

Automatic retry and automatic prioritization of moves.

Primary and personal archive mailboxes can be moved together or separately.

Option for manual move request finalization, which allows you to review a move before
you complete it.

14. What are new options included in Exchange 2013 related with High Availability and
Site Resilience?
Managed Availability Internal Monitoring and recovery are integrated to prevent failures,
proactively restore services, and initiate failovers automatically or alert admin to take action.

Managed Store Integrated with Microsoft Exchange Replication Service to provide higher
availability
Multiple Databases per disk Exchange 2013 supports multiple databases both active and
passive on same disk.
Automatic Reseed If a disk fails, database copy stored on that disk is copied from the active
database copy to a spare disk on the same server.
Automatic recovery from storage failures
Lagged copies can now care themselves to a certain using automatic log play down
Single copy alert task is removed and included in the managed availability component
DAG networks can be automatically configuration by the system bases on the configuration
settings, DAG now can distinguish between MAPI and Replication networks and configure DAG
network automatically.
15. What are the features discontinued in Exchange 2013 when compared with Exchange
2010?
Below are few features that are discontinued in Exchange 2013

Hub Transport Server Role and Unified Messaging Server

Exchange Management Console and Exchange Control Panel

Outlook 2003 support and RPC over TCP method of Mailbox access is removed

S/MIME, Search folders and Spell check in OWA removed

Linked Connectors are removed

Anti-spam agents can be management only from Exchange Management Shell

Connection filtering agent removed

Managed Folder are removed

Tools like Exchange Best Practice Analyzer, Mail flow troubleshooter, performance
monitor, performance troubleshooter and routing log viewer are removed

16. What are the features discontinued in Exchange 2013 when compared with Exchange
2007?
Below are few features discontinued in Exchange 2013 that are available in Exchange Server
2007

Storage Groups and Public Folder Databases

Exchange WebDAV API and ESE streaming backup API

High Availability concepts CCR, LCR, SCR & SCC are not available

Export-Mailbox / Import-Mailbox Cmdlets and Move-Mailbox cmdlets set

Managed folders

17. Whats New in Outlook Web App 2013?


Lot of new feature available in Outlook Web App 2013 below are few new features

Apps can be accessed from Outlook Web App

Contacts can be linked to see all the data in a single view

Ability to connect to users linkedIn account and add the contacts automatically to OWA

Multiple calendars can be viewed in a Merged view

Streamlined user interface for tablets and smartphones which supports use of touch

18. Inform the features that are not available on OWA 2013?
Below are the features that are available in previous versions but not available on Exchange
Server 2013 Outlook Web APP

Shared Mail folders access is not available

Distribution list moderation cannot be done from OWA

S/MIME support

Reading pane at the bottom of the window

Ability to reply to email messages sent as attachments

Search folders in not available

19. What are the prerequisites required to Install Exchange Server 2013?
Below prerequisites are required to install Exchange Server 2013
Operating System:

Windows Server 2008 R2 Service Pack 1 or later

Windows Server 2012

Additional Prerequisites:

Microsoft .NET Framework 4.5 (pre install in Windows Server 2012)

Windows Management Framework 3.0

Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit

Microsoft Office 2010 Filter Pack 64 bit

Microsoft Office 2010 Filter Pack SP1 64 bit

ADDS and few windows features

Domain Controller:

Forest functional level has to Windows Server 2003

Schema Master run on Windows Server 2003 SP2 or later

20. On which Operating System Database Availability Group is supported?


DAG is supported on Windows Server 2012 Standard or Datacenter Editions or Windows Server
2008 R2 SP1 Enterprise Edition. Windows Server 2008 R2 Sp1 standard edition wont support
DAG
21. On what conditions Exchange 2013 can coexists with previous version of Exchange
servers?
Exchange 2003 and Earlier versions: Not Supported
Exchange 2007: Exchange 2007 SP3 with Update Rollup 10 on all Exchange 2007 servers and
Exchange 2013 CU2 and later can coexist
Exchange 2010: Exchange 2010 SP3 on all Exchange 2010 Servers and Exchange 2013 CU2 or
later can coexist
22. What are the Editions available in Exchange Server 2013?
Exchange 2013 available in two editions: Standard Edition and Enterprise Edition
Standard Edition allows only 5 databases to mounted (including active and passive copy) and
Enterprise Edition allows 50 databases on RTM version of Exchange and 100 databases on CU2
and later versions. Recovery Database will not be counted on this.
23. What will happen to Exchange 2013 RTM version when 120 days trial period expires?
Exchange 2013 functionality will not loss when trial period expires, so you can maintain lab
without having to reinstall the trial version.
24. What the supportable clients that can access Exchange 2013 Mailbox?

Exchange 2013 mailbox can be access by the following clients

Outlook 2013

Outlook 2010 SP1 with Outlook 2010 November 2012 update

Outlook 2007 SP3 with Outlook 2007 November 2010 update

Entourage 2008 for Mac, Web Services Edition

Outlook for Mac 2011

You might also like