Solved

Active sync not working on Exchange 2013 Server

Posted on 2015-01-21
4
78 Views
Last Modified: 2015-01-29
Hi

I currently migrating my current users from Exchange 2010 to Exchange 2013 ,in the migration I still need my users to connect their phones/devices with ActiveSync on Exchange 2013 Server. The OWA address works like a charm on Exchange 2013 but can't get my users to connect with the public ip of the new Exchange 2013 Server ,Please advice what I can do

Thanks
SD
0
Comment
Question by:Dirkie Laubscher
[X]
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
  • 2
4 Comments
 
LVL 3

Expert Comment

by:Sudhir Bidye
ID: 40561485
Run activesync manual test and inform us about the error. Based on the error anyone can suggest the troubleshooting steps.

-Check if it is not working for single user or all users.
-Check in  inherited permission are enabled for the users.
- is your AD domain and smtp domain same? i.e is your internal domain abc.com and smtp domain abc.com or abc.local and xyz.com. If your internal domain abc.com and external domain xyz.com then you will have to add addtioinal upn suffix in AD for xyz.com and set primary upn for all the users to xyz.com. this wont affect domain login but will be helpful in accessing activesync using autodiscover.
0
 

Author Comment

by:Dirkie Laubscher
ID: 40561673
Hi  I did run the test utility from Microsoft site please see attached error message ,do I need to change the DNS pointer or create a new certificate for this. Also if I need to create a new certificate how do I do this in Exchange 2013

Thanks
SD
C--Users-DirkieL-Desktop-exchange2013ate
0
 
LVL 20

Accepted Solution

by:
Satya Pathak earned 500 total points
ID: 40561759
0
 
LVL 3

Expert Comment

by:Sudhir Bidye
ID: 40563881
Your external host name seems to be owa.abc.co.za whereas your certificate seems to have owa-Exchange.abc.com.

If you are already using a valid thrid party certificate then check what is the name you have in your third party certificate and change the Exchange url's accordingly.
If you do not have a valid third party certificate then purchase a valid third party certificate according to the url's you need.
0

Featured Post

Moving data to the cloud? Find out if you’re ready

Before moving to the cloud, it is important to carefully define your db needs, plan for the migration & understand prod. environment. This wp explains how to define what you need from a cloud provider, plan for the migration & what putting a cloud solution into practice entails.

Question has a verified solution.

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

As tax season makes its return, so does the increase in cyber crime and tax refund phishing that comes with it
This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
To show how to create a transport rule 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 Mail Flow >> Rules tab.:  To cr…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
Suggested Courses

617 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