BlackBerry Enterprise Transporter fixed issues

When the BlackBerry Enterprise Transporter 5.0 SP4 connects to the BlackBerry Administration Service, it verifies that the FQDN that it reads from the BlackBerry Configuration Database matches the SSL certificate of the BlackBerry Administration Service. You can configure the tool to skip this verification process for specific servers. For more information, visit www.blackberry.com/go/serverdocs to read the BlackBerry Enterprise Transporter Installation and Administration Guide.

When using a previous version of the BlackBerry Enterprise Transporter in a Novell GroupWise environment, the tool did not migrate user accounts without a unique MessageUID. (DT 5693736)

In the BlackBerry Enterprise Transporter 5.0 SP4, this issue is resolved.

If you used the BlackBerry Enterprise Transporter to move user accounts from a source BlackBerry Enterprise Server that is version 5.0 SPx to a destination BlackBerry Enterprise Server 4.1 SPx, a UserMigrationHandler exception error might have occurred. As a result, the user account was not migrated, and the tool might not have been able to roll the user back to the source BlackBerry Enterprise Server. (DT 5032373)

In the BlackBerry Enterprise Transporter 5.0 SP4, this issue is resolved.

In previous versions of the BlackBerry Enterprise Transporter, if you moved user accounts with VoIP configurations from BlackBerry Enterprise Server 4.1 SPx to BlackBerry Enterprise Server 5.0 SP3 or later using live mode, the migration might not have completed successfully. The BlackBerry Enterprise Server 5.0 SP3 and later does not support VoIP profiles. (DT 5026409)

In the BlackBerry Enterprise Transporter 5.0 SP4, the tool does not migrate VoIP configurations.

When using a previous version of the BlackBerry Enterprise Transporter in a Novell GroupWise environment, if a user changed a recurring calendar item after you migrated the user account from BlackBerry Enterprise Server 4.1 SPx to BlackBerry Enterprise Server 5.0 SPx, multiple instances of the calendar item might have appeared in the user's calendar. (DT 3575478)

In the BlackBerry Enterprise Transporter 5.0 SP4, this issue is resolved.

When using a previous version of the BlackBerry Enterprise Transporter in a Novell GroupWise environment, if a user changed a recurring calendar item after you migrated the user account from BlackBerry Enterprise Server 4.1 SPx to BlackBerry Enterprise Server 5.0 SPx, the update might not have synchronized to the user's device. (DT 3575463)

In the BlackBerry Enterprise Transporter 5.0 SP4, this issue is resolved.

In the BlackBerry Enterprise Transporter 5.0 SP3, if you moved user accounts from BlackBerry Enterprise Server 4.1 SPx to BlackBerry Enterprise Server 5.0 or later, a few days after the migration process completed, contact information might have disappeared from the contact list on each user's device. (DT 2077524)

In the BlackBerry Enterprise Transporter 5.0 SP4, this issue is resolved.

In a Novell GroupWise environment, if you moved a user account from a BlackBerry Enterprise Server 4.1 SP7 to a BlackBerry Enterprise Server 5.0 SPx, or from a BlackBerry Enterprise Server 5.0 SP1 to a BlackBerry Enterprise Server 5.0 SP4, the following issues occured: (DT 1837472)
  • If you tried to change the user's default configuration settings in the BlackBerry Administration Service, the following error message appeared: "The request cannot be completed."
  • The user’s PIN did not appear in lookup results in the destination domain. Other device users in the destination domain could not search for the user by the user’s PIN.

In the BlackBerry Enterprise Transporter 5.0 SP4 MR5, these issues are resolved.

In previous versions of the BlackBerry Enterprise Transporter, in the Find Users window, localized group names might have appeared in the Groups drop-down list. (DT 1025165)

In the BlackBerry Enterprise Transporter 5.0 SP4, this issue is resolved.

In previous versions of the BlackBerry Enterprise Transporter, if the BlackBerry Administration Service of the destination BlackBerry Enterprise Server stopped running while you were moving user accounts in live mode, the default assignments for groups, IT policies, and software configurations were not applied to the user accounts. (DT 1019239)

The BlackBerry Enterprise Transporter 5.0 SP4 stops the migration process if a set number of operations using the BlackBerry Administration Service fail.

In previous versions of the BlackBerry Enterprise Transporter, if an SQL exception occurred due to a SQL deadlock while the BlackBerry Enterprise Transporter was moving a user account, the BlackBerry Enterprise Transporter might not have moved the user account. (DT 1018860)

In the BlackBerry Enterprise Transporter 5.0 SP4, this issue is resolved.

In the BlackBerry Enterprise Transporter 5.0 SP3, if you tried to move a user account from the source BlackBerry Enterprise Server and a user account already existed on the destination BlackBerry Enterprise Server with the same first name, last name, and displayname, but a different email address, you could not move the user account. (DT 995375)

In the BlackBerry Enterprise Transporter 5.0 SP4, this issue is resolved.

In the BlackBerry Enterprise Transporter 5.0 SP3, if the SkipDominoBBSDReplication and SkipDominoBBSDValidation parameters were set to true in the BlackBerry Enterprise Transporter configuration file (EnterpriseTransporter.exe), after a migration process completed successfully, an IBM Notes exception might have appeared and the BlackBerry Enterprise Transporter might have shut down. (DT 958526)

In the BlackBerry Enterprise Transporter 5.0 SP4, this issue is resolved.

In previous versions of the BlackBerry Enterprise Transporter, if you tried to move user accounts to a new BlackBerry Enterprise Server using bulk mode, and some of the user accounts had null values in the email address field in the BlackBerry Configuration Database, you could not move the user accounts. (DT 757027)

In the BlackBerry Enterprise Transporter 5.0 SP4, when using bulk mode, the tool ignores all user accounts with a blank email address.



Was this information helpful? Send us your comments.