** EDIT WITH SIMPLIFIED QUESTION:

Should I be able to manually create a profile in my Exchange 2013 environment without knowing the GUID@DOMAIN server name?  When I specify the Ex2010 server name and Outlook Anywhere settings, the server name does not auto-resolve to the GUID as other threads suggest.  I am curious whether others are able to manually create a profile without  knowing the GUID@domain.

--

Hi all,

Our computers have Outlook configured to automatically configure a profile without any intervention.  The profile is pointing to Exchange 2010, which is still running in our environment with Exchange 2013.  When a user logs into a computer and launches Outlook for the first time, Outlook fails to connect and a "Cannot open your default-email folders" error occurs.

• I have verified that the Outlook Anywhere settings are configured correctly. 
• If I delete the profile and create a new one using Autodiscover, everything works fine.
• Occurs on all clients - 2007, 2010, 2013, fully patched).

To troubleshoot, I attempted to manually create a new profile.  I supplied the Exchange 2010 server name, and configured Outlook Anywhere.  When hitting "Check Name", the server name stays to Exchange 2010 (does not switch to GUID@domain.com).  When I launch Outlook, the connection fails.  Again, an autodiscovery succeeds.

From my reading, it appears that Outlook should be updating the profile with the new GUID server name when it attempts to connect.  The RPCClientAccessServer setting on the Exchange 2013 databases points to the Exchange 2010 CAS Array names. 

Any ideas?

Thanks for your hel

• Edited by GrandmasterPhil 5 hours 37 minutes ago

Hi

Did you update autodiscover to point to the Exchange 2013 server? You shouldnt need to set the RPCClientAccessServer settings on Exchange 2013 as it is intelligent enough to know where the mailbox is located etc.

Thanks for the reply . 

AutodiscoverInternalURI is pointing to the Exchange 2013 environment,  and is working fine when auto creating the profile.  The Test Autodiscover function returns the correct URL for the mailboxes.   The problem comes when manually creating a profile.  Other threads indicate that a manually created profile should auto change the server name when the Check Name option is selected,  but mine remains with the Ex2010 cas name listed on the database, and the creation fails. 

However,  if the user had previously connected to Ex2010 prior to the mailbox move,  the profile successfully changes to Ex2013. Only during manual creation does it fail,  which is a problem because our existing PCs are configured to create profiles without autodiscover.