[honza]

Hello,

we have a BES server BES02 which is not working well (602 users) and we want to replace it.

Just Yesterday I made a new BES server BES1 which is working very well soo far.
Now i am planing to move users from BES02 to BES1.
I match the IT policy on both server's and i know I can move them without the error it policy rejected.

However I've tried that on one of my coworkers and his calendar got duplicated and it still says activating... for last 24 hours.

So I am looking for some solution to make it as easy as possible for the users. The best way would be if they wouldn't even know about the move.

So should i first delete them from the BES02 and then add them to the BES1? Or keep them on the BES02 and at the same time add them to the BES1?


I would be happy for any help.

[fadmin]

You did not give us much details such as, what version of BES, SQL version local (MSDE) or remote ful sql, Exchange or ..? or e, one SRP key or two etc.

If you are moving the users from one BES database to another BES database you MUST wipe and reactivate the devices on the new BES.

Why not just set up the second BES to use the same database as the first BES?
If you do that, then you can seamlessly move the users to the new BES, and they probably wouldn't even know that you did it.

Can you give some additional details about your environment?

[rsk]

there are some ways you can merge databases but I wouldn't recommend it especially since you have one blank database.

another option is a knife edge cutover using the current database and srp. This is quick and pretty easy.