Hi All,

So after reading various blogs and posts - I finally managed to get Exchange 2013 installed and set up correctly in co-existence environment along with Exchange 2010. Everything is working fine - emails are flowing in both the directions internally and externally. However, Ive got a minor issue to which I need some advise to look into right direction.

When I move the mailbox from Exchange 2010 to Exchange 2013, once the move is completed if mailbox is opened in Outlook 2007, users get notification The exchange administrator has made the changes and requires you to quit and restart the outlook. When you click OK, its trying to configure the profile and open the outlook but gives another message Cannot open your default e-mail folder. Microsoft Exchange is not available. Either there are network problems or the Exchange computer is down for maintenance. When we click OK on message it quits the outlook. When I load the outlook 2007 again, the same message appears.

However, I can go and setup the outlook profile manually for the mailbox which is migrated to Exchange 2013 and it works fine. But it will be a painful process to configure the profile manually for thousands of users. 

What could be the root cause of this problem? and how can I fix it?

Await to hear from you guys.

Regards,

Vishal.

I've run into this and it can be myriad things.  Make sure Exchange 2010 is patched to the supported interoperability version.  Make sure that all Exchange 2010 virtual directories and Outlook Anywhere are configured compatibly with Exchange 2013 in terms of URLs and authentication settings.

Hi Ed,

Thank you for your reply. All the settings for Virtual Directories are configured exactly the same as in Exchange 2010. 

I am really stumped and struggling to get anywhere with this weird problem. Also, found another issue where -- creating profile manually - mailbox name doesn't get resolved by Exchange 2013 server, but with Exchange 2010 server.

What would cause this behavior? and how to go about troubleshooting?

Kind regards,

Vishal.

Do you have Autodiscover pointed to Exchange 2013?

Hi Vishal,

Please make sure Exchange 2013 is Internet facing and the service URLs have been configured correctly in the coexistence environment.

For autodiscover service, please confirm whether the autodiscover.domain.com is pointed to Exchange 2013. I suggest we can create a new mailbox in Exchange 2013 and check whether the Outlook connection can work fine for new Exchange 2013 mailbox.

Additionally, we can test the Exchange 2013 account with the Microsoft Remote Connectivity Analyzer tool to check the autodiscover service:

https://testconnectivity.microsoft.com/

Regards,

Hi Wnnie,

Thank you for your reply. 

1. Exchange 2013 is internet facing. I can easily access the internet from that.

2. All the serviced URL's configured correctly exactly the same as in Exchange 2010. Checked so many times over and over again.

3. As far as I am aware that I configured autodiscover correctly. When I run this command - Get-ClientAccessServer | fl - it returns both Exhcange 2013 and Exchange 2010 server info. 

4. I will try creating a new test mailbox in Exchange 2013 and see whether outlook 2007 resolves the profile by itself. Will update you with the results.

5. I already tried TestConnetivity tool, but will give it a go again and update the results.

Kind regards,
Vishal.

Hi Winnie,

1. So I created a new mailbox on Exchange 2013. Logon to pc as a new user, opened outlook 2007 - and it came up with an error message - "Microsoft exchange is unavailable". Then clicked Work offline and it came up with another error message - "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The connection to Microsoft exchange is unavailable. Outlook must be online or connected to complete this action". Clicked ok and that brought up the window where you provide the Exchange Server name and mailbox name and click on check names.

Tried to provide the server name for Exchange 2013 i.e. hostname, guid - but nothing worked. But strange thing was as soon as I typed the server name for Exchange 2010 and clicked on check names - it resolved the mailbox name and also updated the server name to Exchange 2013.

What could be causing this behaviour? Await to hear from you.

Kind regards,

Vishal.

Repeating:

Do you have Autodiscover pointed to Exchange 2013?

Hi Vishal,

According to your further description, the new created Exchange 2013 users also can't connect to Exchange 2013 automatically. I think the issue should be related to the autodiscover serivce in Exchange 2013.

Please check what Ed said about the autodiscover DNS. Please make sure the autodiscover.domain.com is pointed to Exchange 2013. Then run the following command to set it:

Set-ClientAccessServer -Identity CAS2013 -AutodiscoverServiceInternalUri https://autodiscover.domain.com/autodiscover/autodiscover.xml

In Exchange certificate, please make sure the autodiscover.domain.com is included in the certificate which is assigned with IIS service.

If the issue persists, please collect the TestConnetivity tool results here for further troubleshooting.

Re

Hi Ed,

Thanks for your reply. Yeah, I have re-checked the settings for AutoDiscover in DNS and it's all pointing to Exchange 2013 Server. I also have set the autodiscover to Exchange 2013 by running the following command:

Set-ClientAccessServer -Identity Email AutodiscoverServiceInternalUri https://autodiscover.domain.com/autodiscover/autodiscover.xml (replaced autodicover.domain.com with our url)

I run this command Get-ClientAccessServer | Select Name,AutodiscoverServiceInternalURI, AutodiscoverSiteScope | Fl (on Exchange 2013) and I get the output as shown below:

Await to hear from you on further troubleshooting.

Regards,

Vishal.

Hi Winnie,

Thanks for your reply. Yeah, I have double checked the DNS for AutoDiscover and all the entry seems to be correct and pointing to Exchange 2013 server. 

I had run the command as mentioned by yourself after installing Exchange 2013. However, I ran it again today. 

Yeah, autodiscover URL has already been mentioned in SSL certificate in Exchange 2013.

What will be the best option to send the Test Connectivity result across? Await your response.

Regards,

Vishal.

Hi Ed and Winnie,

I'll upload the Test Connectivity Analyser result tomorrow. But in the mean time do you guys think that there could be a problem with outlook anywhere? I'll post the details about outlook anywhere config too.

Many thanks for your help guys.

Regards,

Vishal.

Make sure you have the latest patches/updates installed on Outlook 2007.  Outlook 2007 needs to have at least SP3 and November 2012 Cumulative Update.  Here's the minimum supported Outlook versions for Exchange 2013:

http://social.technet.microsoft.com/wiki/contents/articles/845.outlook-versions-supported-by-exchange-200720102013online.aspx

Hi Corey,

Thanks for your response. Yeah I have checked the Outlook 2007 version - it has all the right patches/updates installed.

Regards,

Vishal.