asked on Exchange 2010 to 2013 Migration
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?
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?
ExchangeEmail ServersOutlook
Last Comment
Simon Butler (Sembee)
ASKER
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 http://blogs.technet.com/b/msaad/archive/2010/09/24/default-authentication-methods-in-exchange-2010-cas-and-mailbox-servers.aspx
SSL cert is OK, no errors there,
Have checked the IIS vDirs and all the authentication settings are as per the defaults http://blogs.technet.com/b/msaad/archive/2010/09/24/default-authentication-methods-in-exchange-2010-cas-and-mailbox-servers.aspx
ASKER CERTIFIED SOLUTION
Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
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.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a questionAll of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
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.
Simon.