08-18-2009 12:58 PM
08-18-2009 03:08 PM
I started seeing this today as well. I was just about to post the issue and saw yours. I am in the same exact situation as you. We're going from 4.1.6 to 5.0. I migrated myself and one other user last week without issue. Yesterday I migrated my manager and today I migrated another manager and they were seeing the issue you described below. Like you said, everything seems to work fine and communication is good between the device and the BES server, and BAS shows these users to be ok, but the enterprise activation icon stays on their home screen until the phone is rebooted. I haven't found anything on this yet but when I do a mass migration for the rest of the company I don't want to have to ask everyone to reboot their phone. I haven't changed anything on the BES server between the two migrations where I didn't see this issue and the two were I did so I'm not sure why now I am seeing this. I don't think it has anything to do with the model of the phone either because I have the same model as the two people who had this issue (Bold 9000)
Anyone else seen this and found a fix?
08-18-2009 03:27 PM
Before launching the migration did you check the box for Trigger SlowSync? I did not. What I am reading is that this the same process that occurs during an enterprise activation. If it is not selected it will start the sync process after the move. I'm wondering if checking this will change anything? Also, how long have you waited before rebooting one of the devices in order to get the enterprise activation icon to disappear?
My boss noticed the icon around 7:30pm EST yesterday and when I got in this morning it was still on his home screen. He then rebooted his device and it went away.
08-18-2009 03:45 PM
Yes, I always select the Trigger SlowSync with the move. One of my user restarted his BB device about 2 hours after his account been moved. Another user restarted a hour after his move but it took a few hours before the icon disappeared. I'm going to open a ticket with Blackberry support and see if they have seen this.
08-19-2009 09:38 AM
08-27-2009 08:46 AM
12-01-2009 08:47 AM
Am experiencing same problem. Transporter migrations from BES 4.1.6 to new BES 5 server w/ new BlackBerry domain and BESMgmt database.
Have migrated about 20 accounts so far and at least 2 rebooted. One in the middle of a phone call. The two devices so far have been a 8310 and 8900. Altough we also have 9000, 8100 and 8220's OS on the devices vary.
Call logged with RIM but just a vague "its to do with different IT policies", even though we only have 3 policies that have been replicated to the new server and not all devices are rebooting.
If anyone has a better answer please post.
Also if there is a way I can find out up-front which devices might reboot. Or after migration which devices rebooted.