We are currently migrating from an exchange 2010 cluster with 2 servers (all roles) to a new 2013 cluster (all roles). Prior to moving production mailboxes over, we started testing 2013 by adding dummy mailboxes and running access tests. What we found is that OWA, Active-Sync work fine ... Outlook Anywhere does not.
While starting Outlook for the first time after adding an account, Outlook fires out:
"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 file (.ost)."
Non-Cached:
"Cannot start microsoft outlook. Cannot open the outlook window. The set of folders cannot be opened. Microsoft Exchange is not available. etehr there are network problems or the exchange server is down for maintenance"
After spending a day on the web trying to source out the cause, here's what we know:
- YES - A properly signed certificate is applied and correctly assigned to appropriate services and IIS is restarted on both
- YES - OWA/Active-Sync work correctly without any certificate issues
- YES - Outlook Anywhere settings for internal/external hostnames are set to match the SSL Certificate
- YES - Outlook Anywhere authentication is set to forms based with NTLM (and clients match)
- YES - MAPIBlockOutlookRpcHttp is set to $false on all accounts
- YES - MAPIEnabled is set to $true on all accounts
- YES - Accounts are quickly resolved and added to outlook (issues is only on Outlook startup)
- YES - Cached vs Non-cached mode both fail
- YES - Exchange 2010 accounts work fine
- YES - This Affects Outlook 2013 and 2010 clients
Interestingly:
- If we access 2010 mailboxes through 2013 cas, no issues
- If we access 2010 mailboxes through 2010, no issues
- If we access 2013 mailboxes through 2013 cas, issues
- If we access 2013 mailboxes through 2010, issues
Would really appreciate a few suggestions, no idea what is causing this.