I'm currently coexisting with Exchange 2010 and 2013 on premises.  Our Exchange 2013 staff use Outlook 2013.  They are unable to view MailTips (receive warning "We can't show MailTips right now."); they are unable to set out of office replies ("Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again later."); and they have trouble viewing other users' calendars ("No free/busy information could be retrieved.").

They can see OOF and free/busy when using OWA webmail.  I don't believe that I have any MailTips enabled for the site so the warning just appears by default when writing new e-mails in Outlook.

I've read numerous places that my Autodiscover must be incorrect but everything looks to be in place.  I wonder if having Exchange 2010 and 2013 use the exact same InternalUri is causing issues?

Hello

tip: check autodiscover url is accessible from client

Hi,

The best place to look about the issue is www.testconnectivity.microsoft.com

See if you see some certificate errors or config issues during any of the tests there

Hi,

I have noticed that the users can see OOF and free/busy when using OWA webmail, so the issue may be related to autodiscover service.

Please run the below command to check your autodiscover service:

Get-ClientAccessServer | FL Identity,AutodiscoverServiceInternalUri

We can set the autodiscover by running:

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

On problematic client side, please run Test E-mail AutoConfiguration Tool, and collect the Logs tab and Results tab information:

Open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar - Test Email AutoConfiguration. Put your email address - uncheck use guessmart and secure guessmart.

Best Regards,

David

Running the Get-ClientAccessServer | FL Identity,AutodiscoverServiceInternalUri shows me that the 2010 server and both 2013 servers have the same autodiscover URI.  Is this a problem?  Internal DNS points that URL to a load balancer in front of the 2013 servers.

The client test succeeds and I can manually visit the autodisover webpage with IE.

Hi,

Please make the dns to point directly to your 2013 server to test.

I suggest you also try to re-create a new outlook profile.

regards,

David 

• Marked as answer by Winnie LiangMicrosoft contingent staff, Moderator Wednesday, June 10, 2015 3:12 AM
• Unmarked as answer by -jkm- 10 hours 24 minutes ago

Hi,

Please make the dns to point directly to your 2013 server to test.

I suggest you also try to re-create a new outlook profile.

regards,

David 

• Marked as answer by Winnie LiangMicrosoft contingent staff, Moderator Wednesday, June 10, 2015 3:12 AM
• Unmarked as answer by -jkm- Friday, June 26, 2015 9:01 PM

Hi,

Please make the dns to point directly to your 2013 server to test.

I suggest you also try to re-create a new outlook profile.

regards,

David 

• Marked as answer by Winnie LiangMicrosoft contingent staff, Moderator Wednesday, June 10, 2015 3:12 AM
• Unmarked as answer by -jkm- Friday, June 26, 2015 9:01 PM

This ended up being a problem with our Citrix NetScaler's load balancing configuration. The official guide from Citrix for load balancing Exchange 2013 tells you to create content switching policies using this expression: HTTP.REQ.URL.CONTAINS("ews")

However, in order to gain access to the CONTENTS of the EWS virtual directory, you should actually use the following content switching policy expression instead: HTTP.REQ.URL.SET_TEXT_MODE(IGNORECASE).CONTAINS("/EWS") && HTTP.REQ.URL.SET_TEXT_MODE(IGNORECASE).CONTAINS("/EWS/")

With that in place, the OOF, Mailtips, and Free/Busy issues were resolved.

I found the expression in this post: http://discussions.citrix.com/topic/304964-configure-netscaler-with-exchange-2010-similar-to-microsoft-threat-management-gateway/

• Marked as answer by -jkm- 10 hours 24 minutes ago

This ended up being a problem with our Citrix NetScaler's load balancing configuration. The official guide from Citrix for load balancing Exchange 2013 tells you to create content switching policies using this expression: HTTP.REQ.URL.CONTAINS("ews")

However, in order to gain access to the CONTENTS of the EWS virtual directory, you should actually use the following content switching policy expression instead: HTTP.REQ.URL.SET_TEXT_MODE(IGNORECASE).CONTAINS("/EWS") && HTTP.REQ.URL.SET_TEXT_MODE(IGNORECASE).CONTAINS("/EWS/")

With that in place, the OOF, Mailtips, and Free/Busy issues were resolved.

I found the expression in this post: http://discussions.citrix.com/topic/304964-configure-netscaler-with-exchange-2010-similar-to-microsoft-threat-management-gateway/

• Marked as answer by -jkm- Friday, June 26, 2015 9:01 PM

This ended up being a problem with our Citrix NetScaler's load balancing configuration. The official guide from Citrix for load balancing Exchange 2013 tells you to create content switching policies using this expression: HTTP.REQ.URL.CONTAINS("ews")

However, in order to gain access to the CONTENTS of the EWS virtual directory, you should actually use the following content switching policy expression instead: HTTP.REQ.URL.SET_TEXT_MODE(IGNORECASE).CONTAINS("/EWS") && HTTP.REQ.URL.SET_TEXT_MODE(IGNORECASE).CONTAINS("/EWS/")

With that in place, the OOF, Mailtips, and Free/Busy issues were resolved.

I found the expression in this post: http://discussions.citrix.com/topic/304964-configure-netscaler-with-exchange-2010-similar-to-microsoft-threat-management-gateway/

• Marked as answer by -jkm- Friday, June 26, 2015 9:01 PM