AA-in-CA
asked on
ActiveSync "migration" when migrating from Exchange 2007 to 2013: supported or no?
My customer is migrating from SBS 2008, and a large number of their staff use ActiveSync-enabled devices (iOS and Android) to access their Exchange 2007 mailboxes. We plan to migrate them to Exchange 2013, and the mailbox store is small enough that a coexistence deployment shouldn't be necessary (in other words, we're going to move everyone's mailboxes more or less at once).
Will ActiveSync devices gracefully/seamlessly reconnect to user mailboxes on the new server, like Outlook does? Or will we need each and every user to redo their ActiveSync profiles on their devices?
Will ActiveSync devices gracefully/seamlessly reconnect to user mailboxes on the new server, like Outlook does? Or will we need each and every user to redo their ActiveSync profiles on their devices?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you, Will and Vincent, that's incredibly helpful.
MS Partner support has been telling me that they "recommend" redoing the ActiveSync device profiles for users whose mailboxes get migrated to the new server. They're not giving me a lot of detail as to why, just that it can be problematic. We can redo them, but it'd be physically impossible to redo profiles on 75 iPads/iPhones/Androids all at once without inconveniencing our users (we don't have an MDM platform to help us with this). Which leads to my next question, about simply sidestepping that issue by doing a phased migration with 2007/2013 coexistence...
In a coexistence scenario, where Exchange 2013 proxies requests for mailboxes living on the 2007 server to that server, will ActiveSync still behave normally for users still on the old server? In other words, if user John has his mailbox moved to 2013, we need to redo his ActiveSync profile. But if user Anna has her mailbox on the 2007 server, we don't need to redo hers yet, correct? If that's the case, we can migrate batches of 5-10 mailboxes at a time, and schedule the corresponding users to give us their smartphones/tablets for reconfiguration, in an orderly way.
MS Partner support has been telling me that they "recommend" redoing the ActiveSync device profiles for users whose mailboxes get migrated to the new server. They're not giving me a lot of detail as to why, just that it can be problematic. We can redo them, but it'd be physically impossible to redo profiles on 75 iPads/iPhones/Androids all at once without inconveniencing our users (we don't have an MDM platform to help us with this). Which leads to my next question, about simply sidestepping that issue by doing a phased migration with 2007/2013 coexistence...
In a coexistence scenario, where Exchange 2013 proxies requests for mailboxes living on the 2007 server to that server, will ActiveSync still behave normally for users still on the old server? In other words, if user John has his mailbox moved to 2013, we need to redo his ActiveSync profile. But if user Anna has her mailbox on the 2007 server, we don't need to redo hers yet, correct? If that's the case, we can migrate batches of 5-10 mailboxes at a time, and schedule the corresponding users to give us their smartphones/tablets for reconfiguration, in an orderly way.
ASKER
Frosty, Autodiscover is where it gets tricky. The prior admin never configured it properly/fully, so whenever existing staff buy new phones, or a new hire comes in, a tech has to manually 'point' the phone at the external address for mailbox access, Mail.OurDomain.Org. Once the phone/tablet is pointed at Mail.OurDomain.Org, setting up the user's mailbox access proceeds normally,
If I'm not mistaken, resolving this issue is as simple as creating a CNAME record with our external DNS provider, pointing Autodiscover.OurDomain.Org