Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

Exchange 2013 Autodiscover

Posted on 2013-05-31
3
2,756 Views
Last Modified: 2013-07-16
We are trying to get autodicsover to work with Mobile devices and tablets that use Activesync.  Autodiscover is currently working with Outlook clients; however, the settings will not auto provision on Activesync devices.  Unfortunately, I have been unable to find documentation that clearly explains the process.  

Our setup is described below:
The name that clients use to access the system is mail.company.com.  When a user enters their email address and password into the mobile device it doesn't populate any of the settings.  Our email addresses are setup as follows: FirstName.LastName@company.com

I ran through a troubleshooting utility and it looks like Autodiscover is trying to obtain settings from company.com instead of mail.company.com.  Seeing that company.com is our web server it is unable to obtain any settings.  

I have a SRV record in our DNS that points to mail.company.com At first, I was receiving a message stating that there were issues resolving this address I also added an A record into our DNS for autodiscover.company.com.  This corrected the issues resolving the name; however, it still isn't working.  I have gone through the tests on https://www.testexchangeconnectivity.com to determine the steps that are failing.  

I have also tried setting the url by entering the following command:
Set-ActiveSyncVirtualDirectory -Identity "SRVMAIL\Microsoft-Server-ActiveSync (Default Web Site)" -ExternalURL "https://mail.company.com/"


For clarification, our Exchange 2013 system is configured as follows:
1 single Server withe a machine name of srvmail.xxx.local
Clients access the system using a host name of mail.company.com.
We have a wildcard SSL certificate for *company.com. That certificate has been successfully applied to the Exchange 2013 server.
Our Email address format is: FirstName.LastName@company.com
Our AD username format is: First Initial + Last Name.  For example: jsmith

Lastly, I'm wondering if autodiscover will be able to pull the correct username from AD as our user names are comprised of the first initial and last name which doesn't match the email address.  (jsmith)  I assume yes; however, I would like clarification on this if possible.  

Please advise...
0
Comment
Question by:netmaster3620
  • 2
3 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39212253
To answer the easy question - Autodiscover will find everything from just the email address and the password.

Autodiscover with mobile devices is very hit and miss, because it depends on the implementation of ActiveSync by the device supplier.
SRV records I find are not reliable for mobile devices, so I would remove those and switch to autodiscover.example.com A record exclusively. You are using a wildcard certificate so it should work fine.

Autodiscover goes through a number of URLs, one of which is the root of the domain. As long as there isn't a /Autodiscover directory on the root, it should fail and move on to the next one, which will be autodiscover.example.com.

Sort out your DNS to begin with, and check whether there is something in the root. Check it on https://example.com/ - as your web host might be hosting something on SSL.

Simon.
0
 

Author Comment

by:netmaster3620
ID: 39216350
Simon,

Thank you for your response.  With the A Record setup, I tested Autodiscover from the following address:

https://www.testexchangeconnectivity.com

The Autodiscover test completed successfully; however, I noticed that the server name, user name, and domain are not being filled in.  On Android devices, it assumes the username is the same as the email address and it automatically fills in this information.  (For Example: \FirstName.LastName)  On iOS devices it is simply blank.  

Below are the results from the test that I ran on the above mentioned web site.  

ExRCA is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.bristolcc.edu/AutoDiscover/AutoDiscover.xml for user FirstName.LastName@company.com.
       The Autodiscover XML response was successfully retrieved.
       
      Additional Details
       Autodiscover Account Settings
XML response:
<?xml version="1.0"?>
<Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/mobilesync/responseschema/2006">
<Culture>en:us</Culture>
<User>
<DisplayName>UsersLastName, UsersFirstName</DisplayName>
<EMailAddress>FirstName.LastName@company.com</EMailAddress>
</User>
<Action>
<Settings>
<Server>
<Type>MobileSync</Type>
<Url>https://mail.company.com/</Url>
<Name>https://mail.company.com/</Name>
</Server>
</Settings>
</Action>
</Response>
</Autodiscover>
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 39220731
You will find that Autodiscover with mobile devices is very hit and miss, more miss than hit in my experience. That is a fault with the mobile device suppliers and their implementation of ActiveSync.

From memory with Android (I am a Blackberry specialist, so don't do much with Android) the email address is initially populated, then it gets corrected by Autodiscover.

Unfortuantely your best option is to tell users how to do it manually, or at least have those instructions. Autodiscover for ActiveSync is a nice idea, but let down by its implementation.

Simon.
0

Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Following basic email etiquette rules will help you write a professional email and achieve a good, lasting impression with your contacts.
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
In this video we show how to create a Distribution Group in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >>…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

791 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question