[Stainless Steele]

I setup transporter to migrate a user over to test it and see how it worked.
My new server is a BES 5.0 on sql2005and my old is 4.41 on sql2000

So I selected the user to migrate...i did not choose any options as far a s groups policies etc.

Went though a check and all that came back good.

it took about 8 mins and it said it migration complete pending

So i still see the user on the old BES as well as the new. Mail says pending on the old server.

So my questions are is this normal? Do I have to manually remove the user from the old server after the migration. What about the delay i'm seeing in getting mail 15+ min after the migration? Am i doing this correctly? Anything else I should be asking/looking @?

has anyone else here used the tool? Have any ideas?

[fadmin]

I used this tool and it works as advertised. Once completed it should delete user from old BES domain. What version of BET did you use? There is the one with MR1 released.

[Stainless Steele]

5.0.0.51 is the version

After it completed did the user get removed from the 4.x server right away? I was monitoring it and I never saw it go away. I waited about 15 min before manually deleteing it.
Did it take you about 5-8min per user to migrate? Did any users report duplicate calender entries?

[fadmin]

It took about 4 minutes to do it all for 5 users. This is what I've done and used:
1. Install BlackBerry Enterprise Server User Administration Tool v5.0.0 Maintenance Release 1 for Microsoft® Exchange from here BlackBerry - Enterprise Server Resource Kit
2. Install BlackBerry Enterprise Transporter v5.0.0 Maintenance Release 1 from here BlackBerry - Enterprise Server Resource Kit

Above to be installed on admin workstation and not on either server. (BRK is not to be run on BES servers.)
I logged on as BESAdmin account to a workstation but you can RunAs Besadmin.
Close all other BB apps.
(Prepare destination server/database with IT policies or move users to a Default IT Policy.)
Run transporter tool.

[MarshBklyn]

I've used the transporter tool to move more than 300 users from 4.1.6 to 5.0. what I've noticed is that there is no problem to install the transporter on the bes server. however, did run into some issues when having the transporter assign the policy.
Instead, transport the user with nothing specified in the transporter tool and they will be moved to the default policy. then after they receive their new service books properly, you can move them to any policy you want.

[fadmin]

Have you moved all of them at once or not and if so, how long it took you to migrate them?

[MarshBklyn]

nooooo never all at once. not that brave. first i moved myself. then a colleague. then rest of IT staff. then the rest. it was all phased.
took about 5-6 minutes to move one person at a time. but with 5 users at once, it processed all 5 at the same time so the average went down to about 1-2 minutes each.
So moving about 20 users at once took about 20 minutes or so.

Again, had issues moving them to a locked down policy specified in the transporter tool. called TSupport and they havent seen that before either. so didnt specify policy in the transporter tool and just moved them to default policy and then in 5.0 moved them to my locked down policy. an extra step, yes, but for 300+ it worked like a charm.