• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 138
  • Last Modified:

IPhones and IPads not connected to Exchange 2013

Hello All -

Fresh install of Windows 2013 within Exchange 2013 SP 1 w/ 3rd party SAN certs applied.  We created the Autodiscovery both externally and internally and Windows phones and Outlook 2013 clients have no issues Automatically discovering and configuring the Outlook client.

However,  Apple OS devices cannot connect even if we manually try to configure them - We tried both the native Exchange client as well as the Outlook 2013 client available within the Appstore with no luck.  

Any ideas on what we should be looking at would be greatly appreciated!  - Zoo
0
zookeepa1
Asked:
zookeepa1
1 Solution
 
suriyaehnopCommented:
If this happen to all user? Does the mailbox's activesync feature enable?
Could you run test connectivity to verify the activesync.

https://testconnectivity.microsoft.com/
0
 
zookeepa1Author Commented:
Passed with warnings...

      The Microsoft Connectivity Analyzer is testing Exchange ActiveSync.
The warning
The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://DOMAIN.com:443/Autodiscover/Autodiscover.xml for user t@DOMAIN.com.
       The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.
       
      Additional Details
       
A redirect response was received, but only HTTPS redirect URLs are supported in response to a POST request. The URL that was received was http://www.DOMAIN.com/Autodiscover/Autodiscover.xml.

THOUGHTS?
0
 
Tom Jacob ChirayilSystems EngineerCommented:
Did you create an 'A' record for Autodiscover?
The SRV record mechanism does not still support iPhones and android phones. The A record should point to the client access server. Also, if you have a load balancer in front of CAS, please check the Load balancer documentation and make sure it is configured appropriately for ActiveSync.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
zookeepa1Author Commented:
Hi tomjacobchirayil -

An A record was created.  This customer does not have a load balance and this is a single on premise installation.

Any other ideas?

Thanks,
Zoo
0
 
hecgomrecCommented:
I suspect you created the record with the ISP to match the autodiscover.domain.com.

This was ok, but accordingly to your message/question, it looks like the virtual directory is getting redirected to an http instead of staying on https.

Check your IIS for redirections on the virtual directory and while you are at it make sure you have the right authentication selected.
0
 
zookeepa1Author Commented:
Hmm...Based on the IIS comment I just noticed I did not have a external FQDN defined for autodiscover.  Rookie mistake - need to check if this corrected the issue.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now