Exchange 2003 coexistence with Exchange 2010 (Edge, OWA, Certificate, DNS considerations)
I'm most of the way through transitioning our Exchange 2003 environment to Exchange 2010 and I have a couple of questions that I hope someone can help me with. Let me explain my current configuration first:
1 Exchange 03 server we'll call EX03 (in DMZ)
1 Exchange 10 server with CA, Hub and MB roles installed, we'll call this EX10 (not in DMZ)
1 Edge 10 server, no subscription configured yet (in DMZ)
Routing connector between EX03 and EX10
1 test mailbox on EX10, moved from EX03 (mailflow is fine)
We use a wildcard ssl cert
Public DNS: 2 A records named mail.domain.com and mail2.domain.com point to our public ip that our ASA directs to EX03. There are 2 MX records named mail and mail2. I wish I knew why there were 2.
Internal DNS: 2 cname records named mail.domain.com and mail2.domain.com that point to the 03 mail server. 3 MX records named 'mail', 'EX03' and 'EX10'
OWA address is mail.domain.com It uses windows authentication on EX03 and forms based on EX10.
In IIS on EX03 there are 2 host headers configured. mail.domain.com and mail2.domain.com
Ok, so now that you have all that information, here are my questions:
Currently, when I go to mail.domain.com and login with an account who's mailbox is on EX03, I successfully login to Outlook Web Access. When I go to mail.domain.com and login with the test account who's mailbox is on EX10, I get 'page cannot be displayed'. But ONLY if I am outside of the network. If I'm inside the network, it does forward over to Outlook Web APP. But the url does not say mail.domain.com... it says ex10.domain.com
I would like to have a period of coexistence where users are seamlessly redirected to Outlook Web App even when visiting mail.domain.com After the coexistence and after all the mailboxes have been moved, I would like to configure the edge server and decommission EX03.
I'm almost there but am starting to get confused by OWA, certificates and potentially DNS. I read in another article about configuring a 'legacy' url, but I don't quite understand what that entails.
Does the Client access server need to be in the DMZ if it is to be "internet facing"? I'm sure the Edge server doesn't handle OWA, Active Sync, Autodiscover, etc? Only internet email.
What is the best way for me to proceed from here to make sure the rest of the transition is smooth?
1 Exchange 03 server we'll call EX03 (in DMZ)
1 Exchange 10 server with CA, Hub and MB roles installed, we'll call this EX10 (not in DMZ)
1 Edge 10 server, no subscription configured yet (in DMZ)
Routing connector between EX03 and EX10
1 test mailbox on EX10, moved from EX03 (mailflow is fine)
We use a wildcard ssl cert
Public DNS: 2 A records named mail.domain.com and mail2.domain.com point to our public ip that our ASA directs to EX03. There are 2 MX records named mail and mail2. I wish I knew why there were 2.
Internal DNS: 2 cname records named mail.domain.com and mail2.domain.com that point to the 03 mail server. 3 MX records named 'mail', 'EX03' and 'EX10'
OWA address is mail.domain.com It uses windows authentication on EX03 and forms based on EX10.
In IIS on EX03 there are 2 host headers configured. mail.domain.com and mail2.domain.com
Ok, so now that you have all that information, here are my questions:
Currently, when I go to mail.domain.com and login with an account who's mailbox is on EX03, I successfully login to Outlook Web Access. When I go to mail.domain.com and login with the test account who's mailbox is on EX10, I get 'page cannot be displayed'. But ONLY if I am outside of the network. If I'm inside the network, it does forward over to Outlook Web APP. But the url does not say mail.domain.com... it says ex10.domain.com
I would like to have a period of coexistence where users are seamlessly redirected to Outlook Web App even when visiting mail.domain.com After the coexistence and after all the mailboxes have been moved, I would like to configure the edge server and decommission EX03.
I'm almost there but am starting to get confused by OWA, certificates and potentially DNS. I read in another article about configuring a 'legacy' url, but I don't quite understand what that entails.
Does the Client access server need to be in the DMZ if it is to be "internet facing"? I'm sure the Edge server doesn't handle OWA, Active Sync, Autodiscover, etc? Only internet email.
What is the best way for me to proceed from here to make sure the rest of the transition is smooth?
Refer the below link for the Method-1:
http://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-2010/
http://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-2010/
ASKER
prashubvp:
Thank you. I have read the simple talk article before and I'm looking for some additional clarification.
"Method-1:
You have to change the Public DNS Records to point to Ex10 and add legacy.Ex03.com url in exchange 2010 to redirect the EX03 owa request to the mailboxes residing in Exchange2003"
There are currently 2 A records and 2 mx records pointing to EX03 from Public DNS. So I would change the A records of the Public DNS to point to EX10?
Does it matter if the CAS is not in the DMZ? Currently, EX03 is in the DMZ, (10.10.10.1) while EX10 is a different subnet (192.168.1.1). The Edge server is in the DMZ (10.10.10.1) but is not configured yet. Will having an Edge subscription at all affect how the CAS works?
In EMC on EX10, under Server > Client access, I am able to set the internal and external urls of owa, active sync, etct.. what url would I put in what field given what I'm trying to do? Internal and External are set to http://mail.domain.com in all cases.
Thank you. I have read the simple talk article before and I'm looking for some additional clarification.
"Method-1:
You have to change the Public DNS Records to point to Ex10 and add legacy.Ex03.com url in exchange 2010 to redirect the EX03 owa request to the mailboxes residing in Exchange2003"
There are currently 2 A records and 2 mx records pointing to EX03 from Public DNS. So I would change the A records of the Public DNS to point to EX10?
Does it matter if the CAS is not in the DMZ? Currently, EX03 is in the DMZ, (10.10.10.1) while EX10 is a different subnet (192.168.1.1). The Edge server is in the DMZ (10.10.10.1) but is not configured yet. Will having an Edge subscription at all affect how the CAS works?
In EMC on EX10, under Server > Client access, I am able to set the internal and external urls of owa, active sync, etct.. what url would I put in what field given what I'm trying to do? Internal and External are set to http://mail.domain.com in all cases.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I had everything right except for the http redirect. I followed this article to get it working. I hate it when stuff like this comes down to a check box. Lesson learned. Thanks for your help.
http://briandesmond.com/blog/redirecting-owa-urls-in-exchange-2010/
http://briandesmond.com/blog/redirecting-owa-urls-in-exchange-2010/
You have to change the Public DNS Records to point to Ex10 and add legacy.Ex03.com url in exchange 2010 to redirect the EX03 owa request to the mailboxes residing in Exchange2003
Method-2:
You add one more new Public DNS (A record will do) entry for Ex10 (Example: email.domain.com) and add this one as an alias address to migrated mailboxes (mailboxes moved from ex03 to EX10) and you can access the owa using new URL email.domain.com (inform the migrated users to use the new URL to access the OWA)