Exchange 2010 to 2013 Migration

tetrauk used Ask the Experts™
OK, looking at migrating exchange 2010 to 2013,

Have setup and installed 2013 and moved a single mailbox to the new server.

When we open Outlook 2013 for that related mailbox we get a password prompt, when I checkout the Outlook 'Connection Status' Window it seems the password box is the Outlook connecting back to the old 2010 server. (does not happen for users with mailboxes on 2010 server)

I'm wondering if its trying to connect to public folders held on the 2010 server, as I cannot view public folders without entering the password.

From what I understand moving public folders to 2013 is a one time deal, you move and you don't move back, whereas before in migrations I have always replicated, tested and then finally removed the old one. this means that I can't test my theory until I move all mailboxes to the 2013 server, piss everyone off with password prompts, and finally move the public folders and hope all works OK.

1) Am I missing something?
2) Is there a better way?
3) Can we solve the password prompt thing and not annoy everyone? (ticking remember does nothing)
4) Current thought it to 'Disk to VHD' the 2010 server, capture the 2013 VHD as it is and then move both to a test environment, spin up and give it a go, but this seems a little excessive. Thoughts?
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Most Valuable Expert 2014

Pity you use public folders, as it significantly simplifies the migration if you can eliminate them beforehand.
You shouldn't be getting prompts for public folder access, so that suggests the authentication settings are incorrect somewhere.
You need to have unique URLs for both Exchange 2010 and 2013 for it to work correctly, with trusted SSL certificates in place. Read the coexistence documentation on TechNet.
Ensure that you have the correct settings for public folders on the Exchange 2013 database.

Also remember that authentication prompts in Outlook can mean other things - the biggest one being that the SSL certificate setup is not correct.



Any specific article to look through?

SSL cert is OK, no errors there,
Have checked the IIS vDirs and all the authentication settings are as per the defaults
Most Valuable Expert 2014
Start with this on the Exchange team blog:

That covers most things.

I would also check this TechNet article for the public folder bit:

It should be pretty seamless, but if something isn't right on the Exchange 2010 server, then everything breaks very quickly as you have found.


Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial