AA-in-CA
asked on
Exchange 2007 & 2013 coexistence: should external IP for "legacy.mydomain.com" be different than for "mail.mydomain.com"?
My customer has a single Exchange 2007 server, and wants to upgrade to a single Exchange 2013 server. We will need both servers to coexist for a period of time, so that we can move mailboxes from 2007 to 2013 in a careful, controlled way.
According to the Exchange Server Deployment Assistant tool, we need to register a unique A record for the old server with our public DNS provider. The Assistant suggests using "legacy.mydomain.com", for example. Our regular record is mail.mydomain.com, which we will point to the external IP of the Exchange 2013 server. Here is the Assistant's exact text:
You need to create a legacy domain name system (DNS) host name so your legacy Exchange 2007 environment and Exchange 2013 can coexist. For example, if your domain name is currently contoso.com, you're likely using a host name of mail.contoso.com or www.contoso.com for external client access to Exchange. During coexistence, we recommend creating and using, for example, a host name of legacy.contoso.com. You'll associate the legacy host name with your existing Exchange 2007 server and associate your current host name (for example, mail.contoso.com) with your Exchange 2013 Client Access server. Your end users will not see or use the legacy host name. It will be used by Autodiscover and Client Access servers when redirecting legacy users to a legacy server.
Client connections, including Exchange ActiveSync, Outlook Web App, POP3, and IMAP4, will be proxied or redirected depending on the protocol being used. After the legacy host name has been configured, users will be able to access their mailbox regardless of whether it's on Exchange 2007 or Exchange 2013. If you're upgrading from Exchange 2007 to Exchange 2013, the following will happen:
--ActiveSync and Outlook Anywhere connections will be proxied from Exchange 2013 to Exchange 2007.
--Outlook Web App connections be redirected from Exchange 2013 to Exchange 2007.
--Exchange Web Service (EWS) connections rely on Autodiscover to provide the correct URL to the client.
So, we need to tell our public DNS provider to create an A record for legacy.mydomain.com. I have a few questions about this:
1) Should the legacy record point to the same external IP as the regular record, or a new one? In other words, if mail.mydomain.com points to 73.24.96.23, should legacy.mydomain.com also point to 73.24.96.23?
I would guess that it should point to the same IP, so that 2013 can proxy/redirect connection attempts to the 2007, like the Assistant says.
2) If the answer to #1 is no, and legacy.mydomain.com needs to have its own IP, on the router that will accept external connections for legacy.mydomain.com, do I need to forward any ports, like 25, 80, etc. Do I forward them to the 2007 server, or the 2013 server?
Thank you!
According to the Exchange Server Deployment Assistant tool, we need to register a unique A record for the old server with our public DNS provider. The Assistant suggests using "legacy.mydomain.com", for example. Our regular record is mail.mydomain.com, which we will point to the external IP of the Exchange 2013 server. Here is the Assistant's exact text:
You need to create a legacy domain name system (DNS) host name so your legacy Exchange 2007 environment and Exchange 2013 can coexist. For example, if your domain name is currently contoso.com, you're likely using a host name of mail.contoso.com or www.contoso.com for external client access to Exchange. During coexistence, we recommend creating and using, for example, a host name of legacy.contoso.com. You'll associate the legacy host name with your existing Exchange 2007 server and associate your current host name (for example, mail.contoso.com) with your Exchange 2013 Client Access server. Your end users will not see or use the legacy host name. It will be used by Autodiscover and Client Access servers when redirecting legacy users to a legacy server.
Client connections, including Exchange ActiveSync, Outlook Web App, POP3, and IMAP4, will be proxied or redirected depending on the protocol being used. After the legacy host name has been configured, users will be able to access their mailbox regardless of whether it's on Exchange 2007 or Exchange 2013. If you're upgrading from Exchange 2007 to Exchange 2013, the following will happen:
--ActiveSync and Outlook Anywhere connections will be proxied from Exchange 2013 to Exchange 2007.
--Outlook Web App connections be redirected from Exchange 2013 to Exchange 2007.
--Exchange Web Service (EWS) connections rely on Autodiscover to provide the correct URL to the client.
So, we need to tell our public DNS provider to create an A record for legacy.mydomain.com. I have a few questions about this:
1) Should the legacy record point to the same external IP as the regular record, or a new one? In other words, if mail.mydomain.com points to 73.24.96.23, should legacy.mydomain.com also point to 73.24.96.23?
I would guess that it should point to the same IP, so that 2013 can proxy/redirect connection attempts to the 2007, like the Assistant says.
2) If the answer to #1 is no, and legacy.mydomain.com needs to have its own IP, on the router that will accept external connections for legacy.mydomain.com, do I need to forward any ports, like 25, 80, etc. Do I forward them to the 2007 server, or the 2013 server?
Thank you!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Let now think your current exchange URL is https://mail.mycompany.com/ with exchange 2007 now we are going to use same with Exchange 2013
For that create Legacy A record in local DNS point to Exchange 2013
Next-> change all exchange 2007 URL with https://Legacy.mycompany.com and Exchange 2013 with https://mail.mycompany.com/
Change Autodiscover URL https://legacy.mycompany.com/Autodiscover/Autodiscover.xml
above will fix Internal and external request too.
Now your exchange2013 CAS is internet facing with same Public IP and SAN certificate .
whenever any external or internal user will try to access https://mail.mycompany.com Exchange CAS 2013 will response and once user type his credential after it will get route to exchange 2007 or 2013 mailbox server depend open where his mailbox reside.