Professional Documents
Culture Documents
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,
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
Outlook 2003 support and RPC over TCP method of Mailbox access is 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
High Availability concepts CCR, LCR, SCR & SCC are not available
Managed folders
Ability to connect to users linkedIn account and add the contacts automatically to OWA
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
S/MIME support
19. What are the prerequisites required to Install Exchange Server 2013?
Below prerequisites are required to install Exchange Server 2013
Operating System:
Additional Prerequisites:
Domain Controller:
Outlook 2013