Exchange 2003 2010 CoExistence

Posted on 2014-12-04
Last Modified: 2015-05-27
I am in the coexistence phase of my Exchange 2003 to 2010 migration and everything is going well. I have reached a point where I have to create a new user. The user must be created on the legacy exchange server, due to third party applications that are not ready. Everything works perfectly, except for activesync. I cannot get a new user's (existing users are fine) iphone to retrieve mail from the legacy server. It configures on the device and verifys that everthing is fine, but it will not retreive or send mail or connect to anything. I also created a test user, and the same thing happens.

Is this expected behaviour at this phase does anyone know?
Question by:AntExpert
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
  • 6
  • 3
LVL 19

Expert Comment

ID: 40480633
What url did you use to configure the activesync for legacy users. The legacy url or the primary url which is pointing to Exchange 2010.

Author Comment

ID: 40480646
Just want to reiterate the question.  All legacy user mobile devices are working fine. This only occurs if I create a brand new user, and point them to the legacy exchange server. If I point the brand new user to the exchange 2010 server, active sync works.

When I test using the Microsoft Connectivity Analyzer, the newley create accounts fails? Does it seems like a permission issue?
LVL 19

Expert Comment

ID: 40480755
Are you able to login to OWA. In Exchange 2003 the mailbox is not created until a email is delivered to the mailbox. Are you able to see the mailbox in Exchange 2003 console? What is the failed error message?
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!


Author Comment

ID: 40480806
Yes, I if I did not have to provide him an iPhone, I would not have known there were issues. Outlook email is up and working.

Owa is working internally and externally.

It almost seems as if there is some ActiveSync Permission missing somewhere. When I check the 2003 server, there are http status code [409] error codes.

How is it even possible that 79 other legacy accounts work fine and pass the connectivity analyzer, but new accounts do not?
LVL 19

Expert Comment

ID: 40480938
Please send the error message in connectivity analyzer.

Author Comment

ID: 40481683
I attached the results with personal information replaced.
LVL 11

Expert Comment

ID: 40482878
I have spend at least 10 min to try to understand your scenario and still have doubts, but here I go:

When you create a user in 2003 and make his mailbox in 2003 you have to activate ActiveSync manually, this setting is not by default as it is in 2010. (if you have only 2003 in place)

Having a user mailbox in 2010 will render it access impossible from a 2007 or 2003 server.  If your 2003 server is still in charge for the access (main CAS) you will not be able to access. If users still authenticate using the 2003 they can't open mailboxes on the new server.

You mentioned "pointing" if you have both servers as CAS within the organization don't expect a server to authenticate the user and get the mailbox from another server you're not authenticated.

You should have your 2010 as your main CAS within and from outside your organization. Created a name space for your 2003 users so they will get redirected and 2010 will get proxied as normal regardless where the mailbox is located the 2010 will be able to open it.

Read more here:

Author Comment

ID: 40482953
Currently, the 2010 server is the main CAS with legacy name space created for the 2003 exchange server. Everything is currently working for 79 users with various smart phones, from inside or outside the organization,  OWA, Autodiscovery, rpc/http are all working without a hitch. I can't understand it either.

My plan at this point is to get all 3rd  party systems working with the new  2010 exchange server. As long as I create all new users with mailboxes on the 2010 server, everything works fine.

Thank you for the time you spent trying to solve this!

Accepted Solution

AntExpert earned 0 total points
ID: 40791939
i was unable to resolve this problem. The only solution that worked for me, was to create all new users on the Exchange 2010 server and get everything migrated ASAP.

Author Closing Comment

ID: 40797902
I was able to work through this issue on my own.

Featured Post

Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

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

This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

726 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