If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.
Solved
Exchange 2007 Upgrade to Exchange 2010
Posted on 2014-03-24
I recently upgraded our exchange from 2007. I put exchange 2010 on a new server, I moved all mailboxes to the new server. I have the internal and external settings in all of the services. I have my SSL certificate installed as well as a self-signed certificate. I am ready to decommission the old server. I still have one problem though.
My active sync users can no longer connect. I have tried to do an Exchange connection multiple ways. With the iphones it just hangs on 'verifying' or with the androids it just keeps trying to 'sync'. I am running out of things to try, I have researched and researched.
Does anyone know how to fix this?
Does having both servers still coexisting have anything to do with it?
What do I need to do to completely get rid of the old servers in the domain? (Looks like there is reminisce of an old EX 2003 server as well)
My active sync users can no longer connect. I have tried to do an Exchange connection multiple ways. With the iphones it just hangs on 'verifying' or with the androids it just keeps trying to 'sync'. I am running out of things to try, I have researched and researched.
Does anyone know how to fix this?
Does having both servers still coexisting have anything to do with it?
What do I need to do to completely get rid of the old servers in the domain? (Looks like there is reminisce of an old EX 2003 server as well)
-
2
- +2
6 Comments
Active 2 days ago
What is your autodiscover.domain.com pointing to in your Public DNS? Is it pointing to the public IP of the 2007 server or 2010? Autodiscover needs to point to 2010, as well as the rest of your public DNS records for email except for legacy.domain.com.
Active 2 days ago
Is your router forwarding the activesync requests to the new server? This would usually be done by NATting incoming packets on port 443 to the new server's internal private IP address.
Active 2 days ago
With Activesync, as long as the FQDN specified in the Server section matches the certificate name and resolves in DNS, then Activesync should work.
Presumably the default certificate is not an FQDN that resolves externally in DNS which is why you are getting an issue.
Presumably the default certificate is not an FQDN that resolves externally in DNS which is why you are getting an issue.
Featured Post
The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!
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 Already a member? Login.
Configure external lookups on for external mail flow on Exchange 2013 and Exchange 2016.
Lotus Notes is the most prominent choice of all users due to its advance email management. It provides email features along with contact management, appointments, task, calendar etc. Many users rely on its service to carry out electronic communicati…
This tutorial gives a high-level tour of the interface of Marketo (a marketing automation tool to help businesses track and engage prospective customers and drive them to purchase). You will see the main areas including Marketing Activities, Design …
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online.
The email signature template has been downloaded from:
www.mail-signatures…
Suggested Courses
Course of the Month8 days, 15 hours left to enroll
595 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.