** 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 Friday, March 20, 2015 1:47 AM

With Exchange 2013 you really need to allow autodiscover to resolve the user's smtp address (Automatic configuration of profile) to the GUID and provide the configuration for that user.  That is the easiest way to do it. 

However, although I wouldn't recommend this, but if for some reason you want to manually configure the profile for a user, you can get the Exchange GUID from the EMS and enter <ExchangeGUID>@domain.com and then the name should properly resolve.

In my experience yes they are.  I have not been able to get this to work using just a server name.  I've always needed to use a mai