Beruflich Dokumente
Kultur Dokumente
How to combine the Exchange 2013 infrastructure with the legacy Exchange
infrastructure.
Page 2 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
Sound complicated and hard? I prefer to use the words: interesting and challenging!
The purpose of this following article series is to clarify the fog around the subject of
the Exchange 2013 coexistence environment.
The purpose of this article series is not to provide a step by step instruction for
building Exchange 2013 coexistence environment.
My main purpose was to enable the reader to understand the logic or the why
part, for doing a specific task or follow a specific instruction when implemented an
Exchange 2013 coexistence environment.
The requested result was to review the client protocol connectivity flow in the
Exchange 2013 coexistence environment of: Exchange 2013\2010 coexistence
environment and Exchange 2013/2007 coexistence environment but its almost
Written by Eyal Doron | o365info.com | Copyright 2012-2015
Page 3 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
impassable to start right ahead with the technical description of the client protocol
connectivity flow in the Exchange 2013 coexistence environment without knowing
the different parts of the Exchange architecture and infrastructure and, without
knowing the unique charters of Exchange clients such as: Outlook, OWA or
ActiveSync (mobile).
Page 4 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
Page 5 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
Page 6 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
Public facing Exchange site and Public facing Exchange CAS server
General concept of: Exchange Legacy infrastructure
Proxy versus redirection
Exchange 2013 as a focal point concept
Public versus external Exchange infrastructure
For your information
Page 7 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
1. Client connectivity
If we want to simplify the whole Exchange infrastructure, we can say that the
Exchange infrastructure exists for:
Page 8 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
In the context with the Exchange environment, the term: client connectivity or client
protocol connectivity, relate to the path or the road between the Exchange clients
and his destination: his mailbox. In the Exchange environment, Exchange clients
cannot access directly to their mailbox or to their Exchange Mailbox server. Instead,
Exchange clients will need to address the Exchange server who holds the CAS
(Client Access Server) role, and the Exchange CAS server will have to find the right
way for the specific user mailbox.
The way to the user mailbox or the path to the user mailbox depends on many
variables such as the Exchange clients mailbox version, the Active Directory site
structure, the available Exchange CAS servers, the specific mail protocol that the
Exchange clients use and so on.
The path that will be selected by the Exchange CAS server to get to the user mailbox
described as: client connectivity or client protocol connectivity.
Page 9 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
We can relate to the term client protocol connectivity flow as a journey that the
Exchange client must pass for
Page 10 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
The diagram display only simplified path through the client protocol connectivity
Page 11 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
flow because in an Exchange 2013 coexistence environment, we will see that the
journey is much more complicated and consists of many steps
2. Mail flow
The term Mail flow, is used for describing the path or the road that a specific mail
item will need to get through from the point that is sent by the source recipient,
until the end point in which he accepted by the destination receipt. The subject of:
Mail flow is a very essential component in the Exchange environment, but in this
article series, we will not relate to this area and instead will focus only in the subject
of client connectivity or client protocol connectivity.
Page 12 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
For example: Exchange 2013 can be installed and successfully communicate with
existing Exchange 2007 and Exchange 2010 infrastructure but not with Exchange
2003 infrastructure.
Page 13 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
Page 14 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
Page 15 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
Page 16 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
Page 17 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
Instead, the purpose is to expand the level of your knowledge about the Exchange
coexistence environment and provide a high level view
Page 18 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
3. Pure curiosity
Curiosity, is not a rude word! This is the sticky part in which I praise glorifies the
beauty of the Exchange coexistence environment. I relay thinks that the
architecture of Exchange is really interesting and challenging, and Im always happy
to learn and understand more and more about the Exchange architecture, and at
the same time, except that I can never understand all of this infrastructure, and
really knows each of his parts.
Page 19 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
Page 20 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
Page 21 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
Exchange infrastructure provides many web services such as: Autodiscover, the
Availability service (Free/Busy time), Automatic reply (out of office), mail tips,
calendar sharing, offline address book and much more. Regarding the subject if:
mail client, Exchange provides services for a variety of mail client such as:
Internet client that uses the mail protocols: POP3, IMAP4 and SMTP
Mobile client that uses the ActiveSync protocol.
Web client that uses HTTP and HTTPS protocol.
Outlook client that uses: RPC, RPC/HTTP, RPC/HTTPS or MAPI/HTTPS
Page 22 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
Add to this salad the subject of different authentication protocols such as: Basic,
NTLM and Kerberos and we get quite a mess.
Each of the Exchange versions relates and implements this services and protocols
in a different way and, in an Exchange coexistence environment, we will need to
make all of these protocols, and services work together.
2. Exchange multi role architecture
Exchange architecture is based upon a concept that described as: multi role
architecture. Each of the Exchange role has different responsibilities and specific
way for communication with the other Exchange roles and guesses what? Each of
the Exchange versions is implementing the role architecture in a different way.
For example, the multi role architecture that was very popular in the Exchange 2007
and Exchange 2010 environments are updated, and the new Exchange 2013
architecture is based on a different implementation of the multi role architecture.
Instead of spreading the roles between different Exchange servers, the Exchange
2013 architecture is based upon a concept in which a single Exchange server will
have most of the Exchange roles and the responsibility for each of the Exchange
Page 23 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
3. Complex infrastructure
In the following diagram, we can see a brief summary of the modern environment
or in other words, the thing that Exchange server need to deal with. For example:
Outlook version the term: Outlook client can be translated to many types of
Outlook client versions such as: Outlook 2007, 2010, and 2013. Despite the fact
that we use the term: Outlook for describing these clients, each of the Outlook
versions is different and implemented the communication channel with an
Exchange server in a different way.
Outlook communication protocols at the current time, Outlook version 2013
support the following type of communication protocols: RPC, RPC/HTTP,
RPC/HTTPS or MAPI/HTTPS. So when we say a sentence such as: Outlook client is
communicating with the Exchange server, to which protocol we are referring?
Outlook internal versus external client
Page 24 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
Before we start with the actual description of the client protocol connectivity flow
Exchange 2013 in a coexistence environment, its important to review the different
parts of the Exchange environment, the charters of these parts in the Exchange
legacy environment verse the Exchange 2013 environment and how to create the
magic that will glue of these parts together. In more technical words: what are
the required configurations setting that we will need to implement and what the
reason for this configuration is.
Page 25 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
So lets start our journey in the mysterious and fascinating world of the Exchange
2013 coexistence environment!
Page 26 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
Part 00/23 The Exchange 2013 coexistence article series index page
This is the index page that will enable you to find your way around the maze of
the Exchange 2013 coexistence article series.
Part 01/23 Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
An introduction to the subject of Exchange 2013 coexistence environment basic
terms and concepts that will be reviewed in the article series.
Part 02/23 The importance of Exchange 2013 CAS in Exchange 2013 coexistence
environment | Part 1/2
The article is the first of two, in which we will review the subject of: Exchange CAS
2013 role in an Exchange 2013 coexistence environment.
Page 27 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
Part 03/23
Page 28 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
Part 12/23
Page 29 of 29 | Part 01#23 | Exchange 2013 coexistence environment and client protocol
connectivity flow | The prefix
The article is the first of four, in which we will review the subject of: client protocol
connectivity flow, in an Exchange 2013/2010 coexistence environment.
Part 21/23 Autodiscover and Outlook client protocol connectivity flow in
Exchange 2013/2010 coexistence environment | 2/4
The article is the second of four, in which we will review the subject of:
Autodiscover and Outlook client protocol connectivity flow, in an Exchange
2013/2010 coexistence environment.
Part 22/23 OWA client protocol connectivity flow in Exchange 2013/2010
coexistence environment | 3/4
The article is the third of four, in which we will review the subject of: OWA client
protocol connectivity flow, in an Exchange 2013/2010 coexistence environment.
Part 23/23 ActiveSync and Exchange web service client protocol connectivity
flow in Exchange 2013/2010 coexistence environment | 4/4
The article is the fourth of four, in which we will review the subject of: ActiveSync
and Exchange web service client protocol connectivity flow, in an Exchange
2013/2010 coexistence environment.