[nobody7290]

I have 2 BESx 5.0.3 servers. I need to move the users (10) from one to the other (new one). Both servers are in the same AD domain, connected via a VPN link (2MBits/s).
I did setup the new server with a new SRP and License.
Downloded the transporter 5.0.3
created a new configuration, added the database servers for source and destination, verified connectivity ok.
clicked preview to see what could be transferred.
Here, the first problem came up: 2 users (they have a 9900, all user users have no 9900 Devices) would not show up.

Then When I did the live migration to the new server, only 4 users transferred ok, 4 others not.
As it turned out later, also the 4 which seemed to be transferred ok did not receive messages. Also, these useraccount were not deleted from the source server.

So, I went back to a SQL backup, and had to reactivate 3 users.

This was the first time, I used the transporter. I found this program straightforward, and it looks to me, you cant do much wrong.

But I still need to move the users, and next time want to be sucessful.

How about the users which were transferred - should they be deleted automatically on the source server or not ?

Why did it fail ?
In the transporter logs, I only see:
{a.b@domain.com} ITAdmin command status for entryId=49 is: RequestError
(06/27 00:06:10.393):{0x20F0:17} [ERROR] {a.b@domain.com} SWITCH_SERVICE failed

and then it rolls back the move to the new server.

And, why are those 2 users invisible ? It might be coincidence that these have a 9900, but it is the only difference i saw.


Thanks.

[freakinvibe]

Check the Policy log of the new BES. It should give you a hint why the switch failed.

[nobody7290]

Thanks, there is something in the logs, but not much:

[30000] (06/26 23:38:06.708):{0x13FC} {some.user@domain.com, PIN=AAAAAA, UserId=12}RequestHandler::DoDeviceSentProcessing - Message returned as FAILED - could not be delivered to device, Tag=12

I hope(d), the device can also be offline at the moment I do the migration using the transporter ?

I now will make a test with a testuser before trying again.

[freakinvibe]

No, the Blackberry device must be in coverage, otherwise you will get:

SWITCH_SERVICE is still pending, device may be out of coverage
SET_IT_POLICY is still pending, device may be out of coverage

I have sorted users by last contact date and then moved them in batches of 20. That worked quite well.

[nobody7290]

Thanks, this explains some of my problems....

Do you know, if the device is offline, will the migration be successful after it comes back online ?

"SWITCH_SERVICE is still pending, device may be out of coverage
SET_IT_POLICY is still pending, device may be out of coverage"

This suggests that this might be possible.