I am currently in the middle of an Exchange migration from 2010 to 2013. Everything has gone perfectly until this point.

I migrated a user over to the new server with no issue. I can send, receive, and access through OWA. However, if I create a new Outlook profile, with the Server set as the FQDN (server.internaldomain.local), place the user name (test), and check name, it will find the user and underline the Server and User Name since they've been resolved. This is all normal, but when I go to open Outlook, I get the error:

Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost).

If I log in as the user and it auto-creates the profile when first opening Outlook, it works with no issues. It connects to mail.externaldomain.com as the server and I can send and receive mail.

1. I have not modified any certificates

2. I have not modified the autodiscoverInternal record for the new server

Hi,

Your config is working perfectly fine as it is expected to work.

This is by design

Please read the below for the reason :

Outlook clients no longer connect to a server FQDN as they have done in all previous versions of Exchange. Outlook uses Autodiscover to create a new connection point comprised of mailbox GUID, @ symbol, and the domain portion of the users primary SMTP address. This simple change results in a near elimination of the unwelcome message of Your administrator has made a change to your mailbox. Please restart. Only Outlook 2007 and higher versions are supported with Exchange 2013.

Your auto-discover is working perfectly fine since it is able to autocreate the new user profiles.

You are good to go with this setup :)

Hi,

I have notice your autodiscover service work fine in your post.

What is your outlook version?

Please upgrade your outlook to the latest version in order to have a better performance.

Based on my knowledge, now with Exchange 2013, the rpcendpoint is no more the mailbox server, but now is a string with the mailbox GUID + the primary smtp domain.

Another big difference between Exchange 2013 and the previous version is that now it use rpc over https for both inside and outside connection. Make sure Outlook Anywhere is correctly configured,

Also refer to Sathish's response to understand the reason.

Regards ,

David 

• Edited by David Wang_Microsoft contingent staff 5 hours 37 minutes ago