problems with mailbox migration


We want to move gradually from exchange 2010 to 2016. Exchange 2016 is installed and configured. The primary exchange server for now is the 2010 which holds the entire mailboxes. I want to move the mailboxes without the trouble of creating new profile for each user in their outlook. So I'm running tests on test mailboxes but with no success. If it's a new mailbox which I created on the new server the autodiscover works just fine. however, when I migrate a mailbox from the old server to the new one it stops working. when I try to create a new profile in outlook the autodiscover won't work properly, it says it can't contact the exchange server. I need to type in the name of the old server in order to complete the new profile.
any ideas?
Elad HelpdeskAsked:
Who is Participating?
Elad HelpdeskAuthor Commented:
I had a deeper problem with the autodiscover, It kinda sometimes worked and sometimes didn't. I searched the web and came across this article which said I need to recycle the autodiscover pool periodically. It seemed a good solution since I noticed that the autodiscover works OK after restarting the server. Another thing I noticed was that I get an error when I try to do iisreset. So this solution was a nice patch but I continued searching for a better solution. I read somewhere that I need to upgrade to the latest CU (which is 9). I wasn't able to upgrade, the pre checks said there is a problem starting a service called web management service. No matter what I did I wasn't able to start this service. I googled up and this article helped me solve the problem with the service. After that I upgraded to the latest CU and the autodiscover works fine ever since.
I think the real problem was the un-start-able service and not the CU but it doesn't really matter as long as it works.
Tom CieslikIT EngineerCommented:
There is a few methods you can use to migrate your mailboxes out from Exchange 2010 to 2016/O365
There is a perfect article about it.
Please read it and select method is convenient for you
Tom CieslikIT EngineerCommented:
Also check your DNS setting. It looks like for some reason your MX record is still pointing to OLD server
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Marshal HubsEmail ConsultantCommented:
Check step by step guide to migrate mailboxes from exchange 2010 to 2016 :
Kurt JohnsonTechnical ManagerCommented:
Just wanted to confirm if you have followed Exchange deployment assistant guide?
It is available from Microsoft team and provides step-wise instructions by checking all necessary prerequisites based upon your current environment.
You can gather more information at

I would also add below articles containing step by step details while need to migrate from Exchange 2010 to 2016 :
Hope, this helps you.
SysToolsData Expert - Recovery,Backup,MigrationCommented:
Please check out this helpful link of Migration from Exchange 2010 to Exchange 2016 account without any data-loss:
Elad HelpdeskAuthor Commented:
Problem is solved! :)
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.

All Courses

From novice to tech pro — start learning today.