ianmclachlan
asked on
Exchange 2010 Migration to 2016
Hi Guys,
We have recently implemented a new 2016 Exchange server that will be taking over from our current 2010 one. It's in a sort of hybrid configuration at the moment with just the mailboxes needed to move across. However, before pulling the trigger and moving them all over I have been testing with one account. At the moment it's not working as I had anticipated. What I have proven so far is:
Mail from 2016 mailbox --> 2016 mailbox ... works
Mail from 2010 mailbox --> 2016 mailbox ... doesn't work.
error: #550 5.1.1 RESOLVER.ADR.ExRecipNotFou
Mail from 2016 mailbox --> 2010 mailbox ... doesn;t work. No bounced message or error
Mail from 2016 mailbox --> External ... works
Mail from External --> 2016 mailbox ... works
Mail from 2010 mailbox --> External ... works
Mail from External --> 2010 mailbox ... works
Mail from 2010 mailbox --> 2010 mailbox ... works
This in itself is not a major issue, as it indicates that everything would be working fine if ALL mailboxes are moved over on 2016.
However, my problems is that when I create a new profile on my desktop for the user that has been moved to 2016. Outlook doesn't connect. I get a : Exchange users "the set of folders cannot be opened" (Outlook 2016)
I feel I must of missed a vital step, and was hoping someone could perhaps point me in the right direction
Regards
We have recently implemented a new 2016 Exchange server that will be taking over from our current 2010 one. It's in a sort of hybrid configuration at the moment with just the mailboxes needed to move across. However, before pulling the trigger and moving them all over I have been testing with one account. At the moment it's not working as I had anticipated. What I have proven so far is:
Mail from 2016 mailbox --> 2016 mailbox ... works
Mail from 2010 mailbox --> 2016 mailbox ... doesn't work.
error: #550 5.1.1 RESOLVER.ADR.ExRecipNotFou
Mail from 2016 mailbox --> 2010 mailbox ... doesn;t work. No bounced message or error
Mail from 2016 mailbox --> External ... works
Mail from External --> 2016 mailbox ... works
Mail from 2010 mailbox --> External ... works
Mail from External --> 2010 mailbox ... works
Mail from 2010 mailbox --> 2010 mailbox ... works
This in itself is not a major issue, as it indicates that everything would be working fine if ALL mailboxes are moved over on 2016.
However, my problems is that when I create a new profile on my desktop for the user that has been moved to 2016. Outlook doesn't connect. I get a : Exchange users "the set of folders cannot be opened" (Outlook 2016)
I feel I must of missed a vital step, and was hoping someone could perhaps point me in the right direction
Regards
Going to 2016 is pretty straight forward, most mail flow issues are resolved the first time you reboot the 2016 server? (Please tell me you have done this at least once after sorting your mailstores out?)
Then if theres still bother, exchange tools queue viewer is where to go next.
</P>
ASKER
Thanks for all your help and suggestions.
I seemed to have fixed the first issue with no mail routing between 2010 --> 2016 and vice versa. It seemed to be the relay receive connector I have on 2010. The 2016 server was listed which stopped the mail routing.
I just now need to fix why the Outlook Clients (Office 2016) aren't joining to any new mailboxes on the 2016 server. I'll look at the DNS suggestion above. Should I have two A records (mail.domain.com and autodiscover.domain.com) pointing to both 2010 & 2016 or just one pointing to 2016?
Again guys, really appreciate your help !!!
I seemed to have fixed the first issue with no mail routing between 2010 --> 2016 and vice versa. It seemed to be the relay receive connector I have on 2010. The 2016 server was listed which stopped the mail routing.
I just now need to fix why the Outlook Clients (Office 2016) aren't joining to any new mailboxes on the 2016 server. I'll look at the DNS suggestion above. Should I have two A records (mail.domain.com and autodiscover.domain.com) pointing to both 2010 & 2016 or just one pointing to 2016?
Again guys, really appreciate your help !!!
Autodiscover should always point to the new Exchange 2016.
mail.domain.com should point to new server, you can create another a record for the old server e.g. oldmail.domain.com , legacy.domain.com or something. Any certificates will need updating as well.
mail.domain.com should point to new server, you can create another a record for the old server e.g. oldmail.domain.com , legacy.domain.com or something. Any certificates will need updating as well.
ASKER
Thanks again for the comments.
I'll change my DNS to point to new server which I assume will still allow existing clients which haven't been migrated to still operate. I was hoping to have a pure hybrid environment where I could test some migrated clients to make sure things like Outlook and other remote mail applications work before commiting the other users. Everyting I've read has suggested this should work "out of the box" providing firewall publishing rules etc are in place pointing to new server. However, I just want the comfort of making sure before pullling the trigger. I don't fancy having to reconfig users Outlook or phone settings after commiting.
Again, I appreciate the help
I'll change my DNS to point to new server which I assume will still allow existing clients which haven't been migrated to still operate. I was hoping to have a pure hybrid environment where I could test some migrated clients to make sure things like Outlook and other remote mail applications work before commiting the other users. Everyting I've read has suggested this should work "out of the box" providing firewall publishing rules etc are in place pointing to new server. However, I just want the comfort of making sure before pullling the trigger. I don't fancy having to reconfig users Outlook or phone settings after commiting.
Again, I appreciate the help
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Please make sure Exchange server authentication is enabled in Default receive connectors.
For coexistence to work IIS auth with Basic,NTLM,Negotiate is enough. Users with Exchange 2010 mailbox will connect automatically. Exchange 2016 will do the work. It will proxy/redirect the traffic to Exchange2010.
Please check this.
https://www.experts-exchange.com/questions/29107641/Exchange-2010-2016-migration-Outlook-Anywhere-Authentication-question.html?anchorAnswerId=42614167#a42614167
Please check this to configure your Exchange 2016 URLs
https://www.experts-exchange.com/articles/31221/Fix-for-Exchange-server-2016-2019-certificate-and-related-issues.html
Please check this for easy CSR creation.
https://www.experts-exchange.com/articles/28662/Easy-CSR-creation-Exchange-2007-2010-and-2013.html