Beruflich Dokumente
Kultur Dokumente
The current article, is the fourth article of four articles series, on the subject of:
Exchange 2013/2007 coexistence environment and mail client protocol
connectivity flow.
Page 2 of 18 | Part 19#23 | ActiveSync and Exchange web service client protocol
connectivity flow in Exchange 2013/2007 coexistence environment | 4/4
In this article, our main focus is reviewing two types of client protocol connectivity
flow in Exchange 2013/2007 coexistence environment:
Page 3 of 18 | Part 19#23 | ActiveSync and Exchange web service client protocol
connectivity flow in Exchange 2013/2007 coexistence environment | 4/4
Note other Exchange clients such as Outlook and OWA, that can connect the
internal (or to the external) Exchange infrastructure.
When the ActiveSync (Mobile) client connects the Public facing Exchange CAS
server, based on the provided user credentials, the Public facing Exchange CAS
server finds out where is the user mailbox is hosted and route (Proxy) the
communication request to the internal Exchange infrastructure.
The internal routing of the ActiveSync (mobile) client communication request is
implemented by using the internal ActiveSync URL address.
Scenario 1: mobile (ActiveSync) client | User mailbox located on New York
site.
Scenario charters: an ActiveSync Exchange 2007 client, need to access his mailbox.
Exchange user type: Exchange 2007 client (Exchange user whom his mailbox is
hosted on the Exchange 2007 mailbox server).
Exchange mailbox server location: the Exchange 2007 Mailbox server who hosts
the user mailbox, is located on the New York site.
Page 4 of 18 | Part 19#23 | ActiveSync and Exchange web service client protocol
connectivity flow in Exchange 2013/2007 coexistence environment | 4/4
Note the special charter of mobile Exchange 2007 clients in an Exchange 2013
coexistence environment is that the Exchange 2013 CAS will not directly connect
the Exchange 2007 CAS but instead, proxy the Exchange 2007 ActiveSync client
request to Exchange 2013 Mailbox server.
The ActiveSync client protocol connectivity flow, will be implemented as follows:
1. Mobile (ActiveSync) client, connects the New York Public facing Exchange CAS
by using the server name: mail.o365info.com and, provides his user credentials.
2. CAS2013 uses the user credentials and performs the Active Directory lookup.
CAS2013 determines that:
o The user mailbox version is: 2007
o The Exchange 2007 mailbox server that host the user mailbox, is located at
the New York site
o There is a local Exchange CAS 2007 in the site (the New York site)
3. CAS2013 will proxy the ActiveSync client request + the ActiveSync user
credentials to the local Exchange 2013 Mailbox server.
4. Exchange 2013 Mailbox server proxy the ActiveSync client to the local CAS2007
by using the internal Exchange 2007 CAS ActiveSync URL address (Number 3).
5. The CAS2007 will accept the request and forward (Proxy) the ActiveSync client
connection request to the Exchange 2007 Mailbox server (Number 4).
6. Exchange 2007 mailbox server fetch the required user mailbox content and
send back the data to the CAS2007 (Number 5).
7. CAS2007 proxy back the information\data to Exchange 2013 Mailbox server
(Number 6).
8. Exchange 2013 Mailbox server proxy back the information\data to CAS2013
(Number 7).
9. CAS2013 provides the required information to the external ActiveSync client
(Number 8).
Page 5 of 18 | Part 19#23 | ActiveSync and Exchange web service client protocol
connectivity flow in Exchange 2013/2007 coexistence environment | 4/4
Page 6 of 18 | Part 19#23 | ActiveSync and Exchange web service client protocol
connectivity flow in Exchange 2013/2007 coexistence environment | 4/4
Scenario charters: an ActiveSync Exchange 2007 client, need to access his mailbox.
Exchange user type: Exchange 2007 client (Exchange user whom his mailbox is
hosted on the Exchange 2007 mailbox server).
Exchange mailbox server location: the Exchange 2007 Mailbox server who hosts
the user mailbox, is located on the Los Angles site.
The Los Angles site is an Intranet site (non-Public facing Exchange site)
The ActiveSync client protocol connectivity flow, will be implemented as follows:
1. Mobile (ActiveSync) client, connects the New York Public facing Exchange CAS
by using the server name: mail.o365info.com and, provides his user credentials.
2. CAS2013 uses the user credentials and performs the Active Directory lookup.
CAS2013 determines that:
o The user mailbox version is: 2007
o The Exchange 2007 mailbox server that host the user mailbox, is located at
the Los Angles site
o There is no local Exchange CAS 2007 in the site (the New York site)
3. CAS2013 will proxy the ActiveSync client request + the ActiveSync user
credentials to the local Exchange 2013 Mailbox server.
4. Exchange 2013 Mailbox server proxy the ActiveSync client to the Los Angles
Exchange 2007 CAS by using the internal Los Angles Exchange 2007 ActiveSync
URL address (Number 3).
5. The Los Angles Exchange 2007 CAS will accept the request and forward (Proxy)
the ActiveSync client connection request to the Exchange 2007 Mailbox server
(Number 4).
6. Exchange 2007 mailbox server fetch the required user mailbox content and
send back the data to the Los Angles Exchange 2007 CAS (Number 5).
7. Los Angles Exchange 2007 CAS proxy back the information\data to Exchange
2013 Mailbox server (Number 6).
8. Exchange 2013 Mailbox server proxy back the information\data to CAS2013
(Number 7).
9. CAS2013 provides the required information to the external ActiveSync client
(Number 8).
Page 7 of 18 | Part 19#23 | ActiveSync and Exchange web service client protocol
connectivity flow in Exchange 2013/2007 coexistence environment | 4/4
Page 8 of 18 | Part 19#23 | ActiveSync and Exchange web service client protocol
connectivity flow in Exchange 2013/2007 coexistence environment | 4/4
Page 9 of 18 | Part 19#23 | ActiveSync and Exchange web service client protocol
connectivity flow in Exchange 2013/2007 coexistence environment | 4/4
Scenario charters: mobile (ActiveSync) client, need to get access to his mailbox.
Exchange user type: Exchange 2007 client (Exchange user whom his mailbox is
hosted on the Exchange 2007 mailbox server).
Exchange mailbox server location: the Exchange 2007 Mailbox server who hosts
the user mailbox, is located on the Madrid site.
The Madrid site considers as Public facing Exchange site and the Madrid Public
facing Exchange CAS server are published with a regional
namespace: mail.o365info.com
The special charter of this scenario is that the users mailbox, is located on a
different Exchange site and additionally, the destination site is a Public facing
Exchange site
Page 10 of 18 | Part 19#23 | ActiveSync and Exchange web service client protocol
connectivity flow in Exchange 2013/2007 coexistence environment | 4/4
For this reason, the behavior of Exchange CAS 2013 server is different because, the
Exchange CAS 2013 server will not implement any more the redirection method
(451 redirect message) for ActiveSync clients.
Page 11 of 18 | Part 19#23 | ActiveSync and Exchange web service client protocol
connectivity flow in Exchange 2013/2007 coexistence environment | 4/4
In our scenario, the New York Public facing Exchange CAS server know that the
user mailbox is located at the Madrid site and additionally, that the Madrid site has
a Public facing Exchange CAS server.
Theoretically, the New York Public facing Exchange CAS server can redirect the
Exchange ActiveSync to this server, but instead, the New York Exchange 2013 CAS
will choose to use the Proxy method.
Its clear that this method is not efficient from the point of view of the New York
Public facing Exchange 2013 CAS server because theoretically, the Madrid Public
facing Exchange CAS server should have served the Madrid ActiveSync (mobile)
client, but using the Proxy method, will ensure that the mobile (ActiveSync) client
communication will be successfully completed.
The ActiveSync client protocol connectivity flow, will be implemented as follows:
1. Madrid Mobile (ActiveSync) client, connects the New York Public facing
Exchange CAS by using the server name: mail.o365info.com and provides his
user credentials.
2. CAS2013 uses the user credentials and performs the Active Directory lookup.
CAS2013 determines that:
o The user mailbox version is: 2007
o The Exchange 2007 mailbox server that host the user mailbox is located at the
Madrid site
3. CAS2013 will not send a redirection request to the Madrid ActiveSync client, but
instead, proxy the ActiveSync client request + the ActiveSync user credentials to
the Madrid Public facing Exchange CAS server by using the external Madrid
Public facing Exchange CAS server ActiveSync URL address (Number 2).
4. The Madrid Public facing Exchange CAS server will accept the request and
forward (Proxy) the ActiveSync client connection request to the internal
Madrid Exchange 2007 Mailbox server (Number 3).
5. The internal Madrid Exchange 2007 Mailbox server fetch the required user
mailbox content and send back the data to the Madrid Public facing Exchange
CAS server (Number 4).
6. Madrid Public facing Exchange CAS server proxy back the information\data to
New York Public facing Exchange CAS server (Number 5).
7. New York Public facing Exchange CAS server provides the required information
to the external ActiveSync client (Number 6).
Page 12 of 18 | Part 19#23 | ActiveSync and Exchange web service client protocol
connectivity flow in Exchange 2013/2007 coexistence environment | 4/4
Additional reading
Page 13 of 18 | Part 19#23 | ActiveSync and Exchange web service client protocol
connectivity flow in Exchange 2013/2007 coexistence environment | 4/4
Page 14 of 18 | Part 19#23 | ActiveSync and Exchange web service client protocol
connectivity flow in Exchange 2013/2007 coexistence environment | 4/4
Page 15 of 18 | Part 19#23 | ActiveSync and Exchange web service client protocol
connectivity flow in Exchange 2013/2007 coexistence environment | 4/4
The Exchange 2007 user mailbox, is hosted on the New York site (Exchange 2007
Mailbox server who is located on the New York site).
Scenario charters: an external Exchange 2007 client, need to get Exchange web
services.
1. Internal Exchange clients connect the Exchange 2013 CAS server and asking for
Autodiscover information.
2. CAS2013 uses the user credentials and performs the Active Directory lookup.
CAS2013 determines that: the user mailbox version is: 2007
3. CAS2013 sent to the Exchange 2007 Autodiscover information that includes the
information on the Exchange web services URL address. The URL address is
based on the Exchange 2007 legacy namespace.
4. The Exchange 2007 client gets the Autodiscover information and saves it for
later use.
5. When the Exchange 2007 needs specific Exchange web services, such as
Availability Service (Free\Busy time) he will contact the Exchange 2007 CAS
server using the Exchange 2007 CAS legacy namespace (Number 3).
Page 16 of 18 | Part 19#23 | ActiveSync and Exchange web service client protocol
connectivity flow in Exchange 2013/2007 coexistence environment | 4/4
The Exchange 2007 user mailbox, is hosted on the New York site (Exchange 2007
Mailbox server who is located on the New York site).
New York includes two Public facing Exchange CAS server: the Exchange 2007
CAS Public facing Exchange CAS server that is published using the public
name: legacy.mail.o365info.com and the Exchange 2013 CAS Public facing
Exchange CAS server that is published using the public name:mail.o365info.com
Page 17 of 18 | Part 19#23 | ActiveSync and Exchange web service client protocol
connectivity flow in Exchange 2013/2007 coexistence environment | 4/4
Page 18 of 18 | Part 19#23 | ActiveSync and Exchange web service client protocol
connectivity flow in Exchange 2013/2007 coexistence environment | 4/4
Additional reading