Exchange 2010 Client Access behavior in coexistence with Exchange 2003 and 2007

I answered a post on Technet regarding this so I thought I would post it here as well.

There is no possibility to replace a Exchange 2007 CAS server with a Exchange 2010 CAS server. Exchange 2010 CAS does not support rendering mailboxes from legacy versions of Exchange. In the scenarios below I have included both Exchange 2003 and 2007.

For OWA:

  • When the Exchange 2007 mailbox is in the same AD Site as Exchange 2010 CAS, Exchange 2010 CAS will silently redirect the session to the Exchange 2007 CAS.
  • When the Exchange 2007 mailbox is in another Internet facing AD Site, Exchange 2010 CAS will manually redirect the user to the Exchange 2007 CAS.
  • When the Exchange 2007 mailbox is in a non-Internet facing AD site, Exchange 2010 CAS will proxy the connection to the Exchange 2007 CAS.
  • When the server is running Exchange 2003, Exchange 2010 CAS will silently redirect the session to a pre-defined URL.

For ActiveSync:

  • When the Exchange 2007 mailbox is in the same AD Site as Exchange 2010 CAS and the device supports Autodiscover, Exchange 2010 CAS will notify the device to synchronize with Exchange 2007 CAS.
  • When the Exchange 2007 mailbox is in the same AD Site as Exchange 2010 CAS and the device does not support Autodiscover, Exchange 2010 CAS will proxy the connection to Exchange 2007 CAS.
  • When the Exchange 2007 mailbox is in a non-Internet facing AD site, Exchange 2010 CAS will proxy the connection to the Exchange 2007 CAS.
  • When the server is running Exchange 2003, Exchange 2010 CAS will proxy the connection.

For Outlook Anywhere:

When migrating Outlook Anywhere you move the Outlook Anywhere endpoint from the Exchange Exchange 2007 CAS to the Exchange 2010 CAS. Exchange 2010 CAS will then proxy the Outlook MAPI RPC to either the Exchange 2007 Mailbox server or the Exchange 2010 Mailbox server depending on the mailbox home server.

So in all scenarios for OWA and Activesync you would still need the Exchange 2007 CAS to handle requests for Exchange 2007 mailboxes. Thanks for reading and as usual, please let me know if you have any further questions!

Advertisements

3 Responses to Exchange 2010 Client Access behavior in coexistence with Exchange 2003 and 2007

  1. Balal Ahmad says:

    what if i have Exchange 2007 with mailbox and client Access and want to add Exchange 2010 as only mailbox serve and use the Client Access of Exchange 2007 , can i do this ?

  2. Tash says:

    I have an existing client access array for exchange 2007. I have now installed 2 exchange 2010 CAS servers (Same AD site.Same forest, same subnet where the exchange 2007 cas/ht/mbx servers reside). When I run the get-clientaccessarray cmdlet on Exchange 2010, I get a blank response. I checked and the CAS array with the FQDN of prod-mailbox.xyz.com does exist for this AD site. So here’s my question, when the clients mailboxes are moved to the new exchange 2010 database, the outlook user profile will still point to the existing cas array (prod-mailbox.xyz.com) yet, the mailbox will not be there.
    The existing exchange 2010 mailbox servers and databases are pointing the localhostname.server.name for CAS. How can I create or these servers to the existing CAS array or can’t I?
    What will happen? I hope I didn’t’ ramble on too much, but this is a huge concern.
    Thanks in advance for your response.
    Tash

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: