Hi, I'm the midst of co-exist between Exchange 2010/2013. I have issues where none of internal users that migrated to Exchange 2013 not able to connect via Outlook 2010/2013. OWA is running fine without issue. Using MCA, the issue due to port is blocked but I have verified that firewall on Exchange 2013 server is turn off all.

    1. Exchange 2010/2013 cert is using public CA cert.

    2. Both outlook anywhere external URL for Exchange2010/2013 is set to outlook.domain.com. internal pointing to server.domain.com. while autodiscover is set to autodiscover.domain.com.

   3. user mailbox in exchange 2010 do not have any issue

while if I try to logon, the error look like below:

Cannot open your default e-mail forlders. You must connect to microsoft exchange with the current profile before you can synchronuze your folder with your outlook data file (.ost).

what else should I check ?

many thanks.

Hi Developer_75,

One thing you could try, although probably not the most convenient of workarounds, is to setup a new mailbox profile for each user that isn't able to connect to the new Exchange server, and then resync their mail. Before doing this, try creating a new user on the new Exchange server and setting that up in Outlook on a new profile. If that works it means your new Exchange server is working and the issue lies with the migrated profiles. If it doesn't work, do let us

Yes, i have creating new profile but still not working. Still giving same error message. The one that realized that user profile is resolved and showing exchange 2010 cas array instead of exchange 2013 mbx server. Any idea?

Are these new users that are having issues or migrated users? Are users in a different AD site then Exchange?

Also can you go into the Account Settings in your Mail Profile > Click Change > More Settings  and post a screen shot of your security tab.  While you're there it might be helpful to make sure that autodisocover is returning the correct settings for Outlook Anywhere.

Also run get-casmailbox -identity <2013user> | fl mapi*

Are you going through a load balancer?  If so, try a host file to route around the load balancer and see if that helps.

it impacted new and migrated users.

security tab is tick. while running get-casmailbox, it show

mapienabled=true

yes, we're using load balancer (WNLB) for our CAS array exchange 2010.

no idea how to move forward.

it impacted new and migrated users.

security tab is tick. while running get-casmailbox, it show

mapienabled=true

yes, we're using load balancer (WNLB) for our CAS array exchange 2010.

no idea how to move forward.

what about 2013 any load balancing going on there? also try launching outlook with the /rpcdiag switch and see what it's trying to connect to. 

Hello,

What server does outlook.domain.com and autodiscover.domain.com point to, Exchange 2013 FE or 2010 CAS?

You can also do a Outlook Test Email AutoConfiguration by the following steps:

a. While Outlook is running, click the CTRL key and then right-click the Outlook icon in the system tray and then select Test Email Autoconfiguration.

b. Confirm that your email address is in the address field, uncheck Use Guessmart and secure Guessmart authentication boxes. Then click the Test button.

Thanks,

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

Hi,

domain and autodiscover address pointing to Exchange 2013 FE.

Can Exchange 2010 CAS array proxy to Exchange 2013 server ?

We have fallback to exchange 2010 cas array due to this issue and may require Ms assistance to troubleshoot further. our environment is exchange 2010SP3 with Exchange 2013 CU8.

I found a solution by Set-OutlookProvider EXPR -CertPrincipalName msstd:mail.mydomain.com. I set it EXCH too. used this KB article as example after reading some post in google.

http://ilantz.com/2013/06/29/exchange-2013-outlook-anywhere-considerations/

http://blogs.technet.com/b/umutg/archive/2011/01/31/all-about-set-outlookprovider.aspx

• Marked as answer by Developer_75 6 hours 42 minutes ago