Unlike Previous versions , Exchange 2013 Coexistence is done with ease without much complexity involved. but understanding the nature of the legacy clients is very important.
Once we make sure Exchange 2013 is completely configured. We got to re route the mail flow and URL name space , these procedure will explain using the same name space without introducing new name spaces
For Example (Choosing a typical example for better understanding)
My Outlook Web App URL is
https://mail.testcareexchange.biz/owa/
My MX record pointing to
testcareexchange.biz == > Mail.testcareexchange.biz
which points to Exchange 2010.
Now I want to switch over to Exchange 2013 by changing the MX and A record of mail.testcareexchange.biz , autodiscover.testcareexchange.biz
Before doing this – We will see the things should be looked at
How Internal Outlook (Connected to Exchange 2010) Will affect ?
Internal Outlook clients Which are connected to Exchange 2010 is not going to affect anyways.They will be still connected to Exchange 2010
How autodiscover going to work from External world ?
Once autodiscover.testcareexchange.biz points to exchange 2013. All requests will be proxied to the Exchange 2010 Server.
How Exchange 2010 Outlook anywhere clients going to connect once the switch over happens ?
All Exchange 2010 Outlook clients request will be proxy the requests to exchange 2010
Exchange 2010 Outlook anywhere should be enabled.
NTLM should be enabled in exchange 2010 server – Adding to Basic authentication.
How Outlook Web App going to work ?
Outlook Web App request will be proxied once it determines the location of the mailbox server
how to Verify Proxy works – you can login to Exchange 2013 Server
Browse
https://localhost/owa
Use a Exchange 2010 mailbox creds , Request should get proxied and Exchange 2010 Owa should open.
How Exchange Active Sync going to work ?
Active Sync Client requests will be proxied to Exchange 2010
How Exchange Web Services going to work ?
Exchange Webs Services requests going to be proxied to Exchange 2010
How IMAP – POP going to work ?
It will use the InternalConnectionSettings property value for each Exchange 2010 Client Access and it will attempt to connect to it .
Nice work sathesh…
Hi Sathesh,
Is there need to create Legacy record in external & internal DNS server?
if it is then what sever i point a legacy Record to exchnage 2010 or Exchange 2013?
For 2010 to 2013. no legacy records are required
Hi Satheshwaran,
Thanks for your articles,
I need an advice on setting up exchange 2013 coexistence with EX2010.
My plan 2 front End (CAS) and 2 backend (Mailbox) at US site
2 front End (CAS) and 2 backend (Mailbox) at India site
Both CAS on NLBS
Both Mailbox on DAG
I would like know how can we configure it across the WAN?
Many thanks in advance.
Regards
NM
Please get a load balancer – without spending money on CAS boxes .
It will act as a reverse proxy solution as well .
It just need to reach other, No extra configuration required.
Hi
I have two CAS 2010 and two MB 2010 servers. Plus two exchange 2013. I am having issues with client who connects via direct access are popping for authentication once I change my DNS and point to CAS2013.
Once I point the DNS back to CAS2010 all are good but users in Exchange 2013 get effected.
How can I resolve this.
Please advise
S
Hi
I have two CAS 2010 and two MB 2010 servers. Plus two exchange 2013. I am having issues with client who connects via direct access are popping for authentication once I change my DNS and point to CAS2013.
Once I point the DNS back to CAS2010 all are good but users in Exchange 2013 get effected.
How can I resolve this.
Please advise
S
Need more info. what effect ? is it prompting ? check what all dns records are in place. how they are connected currently ?
Hi Satheshwaran
what do you mean about “NTLM should be enabled in exchange 2010 server – Adding to Basic authentication.”, shall I enable the NTLM authentication on RPC on all Exchange 2010 CAS servers?
because I didn’t enable the NTLM and after cutover to exchange 2013 the outlook couldn’t connect but ActiveSync worked fine also OWA.
so please let me know how can I fix this issue.
Simple words NTLM auth doesnt prompt or user and pass sooner.
Basic does.
–
Enable NTLM – If your using Exchange 2013. please read about HTTP over MAPI As well