Exchange 2010 to 2013 migration with BES12 in place
 

Dear All,

We are migrating our Exchange 2010 to Exchange 2013 server. We have BES12.5.1 working with Exchange 2010. What is the best practice or steps so that we have no disconnection of the users at the mobile devices. We have Z10 and IPhones activated on the BES server.

thank you

Re: Exchange 2010 to 2013 migration with BES12 in place
 

As Z10 and iPhones are using ActiveSync, you just have to create a new mail profile pointing to the new Exchange 2013 server. Once you have migrated the user to the new Exchange, assign the new mail profile to him.

If you have Exchange gatekeeping enabled, make sure the BESAdmin user is moved to Exchange 2013 and has the necessary rights for gatekeeping.

Re: Exchange 2010 to 2013 migration with BES12 in place
 

thank you very much. Does this require a new activation? we hope to find a solution that is transparent for to the users.

thank you

Re: Exchange 2010 to 2013 migration with BES12 in place
 

No re-activation is needed. Just assign the new mail profile to the user. This will remove the old account and add the new one without the need for any user action.

Of course, try this on a test user/test device first.

Re: Exchange 2010 to 2013 migration with BES12 in place
 

thank you very much. the iOS profile was assigned and worked normally. The problem is with the Blackberry profile! when assigning the new profile, the device is activated but when reaching the authentication part, the following happens:

if the password is incorrect, the Z10 gives: your login information for account() has changed or is incorrect....

if the password is correct, the z10 gives: your account activesync() cannot be authenticated with your service provider. pleased make sure that the account settings are correct!

any idea?

thanks

Re: Exchange 2010 to 2013 migration with BES12 in place
 

You have to test ActiveSync functionality with your new Exchange 2013 servers. Details can be found in this KB article:

How to test Microsoft ActiveSync connectivity