Many of you have been asking how you can transition your existing Exchange environment to Exchange 2010 from a client access perspective. For most of you, this will also mean coexisting with legacy...
Updated Jul 01, 2019
Version 2.0
Blog Post
Hi Ross,
Great article! Only wish you'd done it a couple of weeks ago, it would've saved me lots of research and head-scratching :)
From the online documentation:
http://technet.microsoft.com/en-nz/library/dd638158(en-us,EXCHG.140).aspx
Coexistence with Outlook Web Access
If a user with a mailbox on an Exchange 2007 Mailbox server connects to an Exchange 2010 Client Access server in the same Active Directory site, they will be redirected to an Exchange 2007 Client Access server within that site. If a user with a mailbox on an Exchange 2007 Mailbox server connects to an Exchange 2010 Client Access server in a different Active Directory site and there is no Internet-accessible Client Access server in the destination Active Directory site, they will be proxied to an Exchange 2007 Client Access server within the destination Active Directory site. As with Exchange 2007, if a user accesses an Exchange 2010 Client Access server in an Active Directory site that is different from the one where their mailbox resides and there is an Internet-accessible Client Access server in the Active Directory site that contains the user's mailbox, then the user will be redirected to the Client Access server in the destination Active Directory site. When a user’s mailbox is on Exchange 2007, they will experience the Exchange 2007 versions of OWA during co-existence. That user will get the Exchange 2010 functionality of OWA when their mailbox is moved to Exchange 2010.
Is there any way of changing the behaviour so that a user accessing a mailbox on a 2007 server via the 2010 CAS within the same site is proxied through the 2010 CAS rather than being redirected? For small organisations that only have a single public IP address, it would simplify the configuration if they didn't have to worry about a legacy URL and associated certificate.
Thanks
Martin
Great article! Only wish you'd done it a couple of weeks ago, it would've saved me lots of research and head-scratching :)
From the online documentation:
http://technet.microsoft.com/en-nz/library/dd638158(en-us,EXCHG.140).aspx
Coexistence with Outlook Web Access
If a user with a mailbox on an Exchange 2007 Mailbox server connects to an Exchange 2010 Client Access server in the same Active Directory site, they will be redirected to an Exchange 2007 Client Access server within that site. If a user with a mailbox on an Exchange 2007 Mailbox server connects to an Exchange 2010 Client Access server in a different Active Directory site and there is no Internet-accessible Client Access server in the destination Active Directory site, they will be proxied to an Exchange 2007 Client Access server within the destination Active Directory site. As with Exchange 2007, if a user accesses an Exchange 2010 Client Access server in an Active Directory site that is different from the one where their mailbox resides and there is an Internet-accessible Client Access server in the Active Directory site that contains the user's mailbox, then the user will be redirected to the Client Access server in the destination Active Directory site. When a user’s mailbox is on Exchange 2007, they will experience the Exchange 2007 versions of OWA during co-existence. That user will get the Exchange 2010 functionality of OWA when their mailbox is moved to Exchange 2010.
Is there any way of changing the behaviour so that a user accessing a mailbox on a 2007 server via the 2010 CAS within the same site is proxied through the 2010 CAS rather than being redirected? For small organisations that only have a single public IP address, it would simplify the configuration if they didn't have to worry about a legacy URL and associated certificate.
Thanks
Martin