Exchange 2013 - 2 active sync Vdir

Hello!

We have started a migration from Exchange 2010 to 2013. In our 2010 we had an extra active sync vdir that we configured for certificate based auth, this also has a separate FWDN on the EAS URL. We also have Airwatch that configures our Ipads with the servername on the url. We did the same configuration in Exchange 2013, 2 vdir for active sync. One for our phones that connects using username and password, and one Vdir with certificate based auth.

We moved our users to 2013 and it looked like even the ipad was working against the new server. However, suddenly they reconfigured them self with server FQDN used by our phones. This caused our Ipads to stop sync when the got the servername from our Vdir for our phones. Is there a way to prevent this, I dont want our Ipads to use autodiscover, I need to have the connect with the server name configured by airwatch.

UC

September 1st, 2015 2:52pm

It depends on how AirWatch works.

If it depends on Autodiscover, you could change the ActiveSync virtual directory's URLs to a hostname that isn't published in DNS, and enter that name in the AirWatch server's hosts file or otherwise configure AirWatch to associate that name with the appropriate IP address.

If it doesn't use Autodiscover, just change the URLs in the ActiveSync virtual directory to $Null.

Think about it a little if you have multiple servers because you'll want to configure it so that it doesn't break proxy or redirection as needed in your environment.

Free Windows Admin Tool Kit Click here and download it now
September 1st, 2015 10:24pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics