Exchange 2007 and Exchange 2013 Coexistence

I am in the researching/planning stage for my upgrade from Exchange 2007 to Exchange 2013. Both at the same location, same forest and same domain. To throw a twist into this scenario we recently changed our name thus I also need to update our domain name from mail.oldname.com to mail.newname.com  

Information that I have found states " You need to create a legacy domain name system (DNS) host name so your legacy Exchange environment (Exchange 2007) and Exchange 2013 can coexist. During coexistence, we recommend creating and using, for example, a host name of legacy.contoso.com. "

It seems as though because I am changing our domain name that I could just keep the mail.oldname.com associated with the Exchange 2007 server and create the new dns entry mail.newname.com and point that to the Exchange 2013 server.  

Does this sound correct?
LVL 1
preshomesAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Amit KumarCommented:
Hi,

Actually whenever you upgrade any version of exchange to new version, then it is required to publish two mail URLs one is legacy and one is new. Because until you complete migration of all users you will have to use both mail DNS else atleast one of version's exchange users won't be able to access mails.

Things about domain changing, I wanted to know one thing is it you are renaming Active directory domain or just changing your e-mail domain. If it is e-mail domain change then you install Exchange 2013 first then apply new email recipient's e-mail address domain policy on all users with existing domain's SMTP address so atleast mails will start delivering on both domains.
0
AmitIT ArchitectCommented:
Renaming domain means lot of work. Not only Exchange you might have other servers and application. I might not suggest to perform domain rename. Better you stick to current domain or create new forest and domain and perform cross-forest migration or you can use resource forest concept. Read this:
https://technet.microsoft.com/en-IN/library/aa998031(v=exchg.150).aspx
0
it_saigeDeveloperCommented:
No this is not correct.  You *have* to use a record named legacy.whateveryourdomainis.com.  This also means that you have to use an SSL that includes the legacy.whateveryourdomainis.com and mail.whateveryourdomainis.com.  Now, you can use legacy.whateveryourolddomainis.com, but it would just be easier to use the current domain in the long run.

Also starting with Exchange 2010 it is no longer necessary to use a legacy record.

Edit:  My "No this is not correct" comment is meant to answer the author's question, not any comments made by others.

-saige-
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

preshomesAuthor Commented:
I am not NOT renaming our Active Directory domain just the dns entry for how the server will be accessed.

I have already made this server authoritative for our new name and a year ago I switched all my users over to using new email addresses with the new email domain name.

Right now I have internal and public DNS records for mail.oldname.com and autodiscover.oldname.com pointing to our Exchange 2007 server.  I also have the internal and public DNS record for mail.newname.com pointing to the same Exchange 2007 server but of course since the domain is different you get the SSL error because the name does not match.

The end result would be that I want to move from Exchange 2007 to Exchange 2010 then use the new email domain name to access OWA, autodiscover, Outlook Anywhere, etc...

Would the best way to go about this be to cut over to the new server using the old domain name and then after the migration change everything over to the new email domain name?
0
AmitIT ArchitectCommented:
If that is the case, You don't need to create anything new. Setup your 2013 server. Once you plan to move user to 2013. First you cutover your service to 2013. Like OWA or Active sync. Just need to point DNS record to 2013. Then you start moving mailboxes to 2013 server. During this migration. Exchange 2013 will automatically redirect to 2007 user. Read this guide:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx

adding one more KB
http://msexchangeguru.com/2013/05/10/exchange2013-migration/comment-page-14/
0
preshomesAuthor Commented:
Amit - you are suggesting that I don't need to create the legacy.oldname.com record?

Steps:

1. Install Exchange 2013 server roles
2. Change firewall to direct SMTP, OWA, ActiveSync connections to new Exchange 2013 server instead of the current 2007 server
3. When email comes in or if someone accesses their mailbox via OWA the users will be directed to the 2007 server until their mailbox is moved to Exchange 2013 mailbox?
0
AmitIT ArchitectCommented:
Some confusion at my part, you need that legacy url due to authentication issue. Here is a better article:
http://silbers.net/blog/2014/01/22/exchange-20072013-coexistence-urls/
0
Amit KumarCommented:
Hi preshomes,

As a part of migration, you will have publish both DNS legacy and new one. Time by time when you will be moving users on new exchange servers so new users will be able to access mails with new URL.

DNS records like this:

Exchange 2007: legacy.mydomain.com

Exchange 2013: newmail.mydomain.com
Exchange 2013: Autodiscover.mydomain.com

As I already stated that if you want to change E-mail domain so apply new recipient e-mail address policy which will contains old and new e-mail addresses (primary SMTP) to avoid any mail loss and also change OWA URL of exchange 2007 to new domain as well so your migration will be error less.

Once you are done with this please follow below mentioned articles to complete migration task:

Exchange 2007 to Exchange 2013 Part1, Part2, Part3, Part4
0
preshomesAuthor Commented:
Thank you for the information everyone.  I think I am going to just worry with the upgrade first and then once that is complete then I will look at changing the domain name.

Just to make sure I am clear on this...    its perfectly fine for the the legacy.mydomain.com and the mail.mydomain.com  point to the same public ip.  I just change my firewall to point to the new Exch2013 server but when the new Ex2013 server gets that communication it proxies it to the Ex2007 server until that persons mailbox is moved to Ex2013?
0
preshomesAuthor Commented:
I also have a spam filter in front of the Ex2007 server and once it checks for Spam it sends it to my Ex2007 server. Once I change this to the new Ex2013 server will it also proxy that smtp connection and email to the Ex2007 server?
0
it_saigeDeveloperCommented:
No, they have to point at two different public IP's addresses.  As for the spam filter, you should change it so that it delivers mail to the 2013 server since the 2013 server will eventually be your only mail server.

-saige-
0
preshomesAuthor Commented:
If that's the case then it looks like I will have to preform a rapid migration versus a coexistence migration.  My DB's are only a total of 45GB
0
AmitIT ArchitectCommented:
45GB, you can do it during weekend easily. if you plan everything properly. It should not take 2-3 hours to complete the migration.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
preshomesAuthor Commented:
Yeah... that's what I figure at this point.  Thanks for all your help!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.