BlackBerry Enterprise Transporter Installation and Administration

Transcription

BlackBerry Enterprise Transporter Installation and Administration
BlackBerry Enterprise Transporter
Version: 5.0
Service Pack: 4
Installation and
Administration Guide
BlackBerry Enterprise Server
Resource Kit
Published: 2013-12-06
SWD-20131206103351031
Contents
1
BlackBerry Enterprise Transporter.................................................................................................... 6
BlackBerry Enterprise Transporter modes............................................................................................................................ 6
Options for migrating user accounts..................................................................................................................................... 7
Data that the migration process does not move.....................................................................................................................8
Validation that the BlackBerry Enterprise Transporter performs.......................................................................................... 10
Global validation..........................................................................................................................................................10
User validation............................................................................................................................................................ 10
What's new in BlackBerry Enterprise Transporter 5.0.4...................................................................................................... 11
2
System requirements......................................................................................................................12
System requirements: BlackBerry Enterprise Transporter................................................................................................... 12
Installation considerations..................................................................................................................................................13
Supported environments............................................................................................................................................. 14
Unsupported features and environments..................................................................................................................... 19
Required permissions in an IBM Domino environment................................................................................................. 20
Replicating IBM Domino databases............................................................................................................................. 21
3
Installing or upgrading the BlackBerry Enterprise Transporter......................................................... 22
Install or upgrade the BlackBerry Enterprise Transporter.................................................................................................... 22
4
Configuring the BlackBerry Enterprise Transporter..........................................................................23
Configure how long the BlackBerry Enterprise Transporter waits for the Microsoft SQL Server to process commands........... 23
Encrypt the information about database connections in the BlackBerry Enterprise Transporter configuration file.................24
Configure the BlackBerry Enterprise Transporter to skip certificate validation..................................................................... 25
5
Preparing the source MDM domain for the migration process.......................................................... 26
6
Preparing the destination MDM domain for the migration process................................................... 28
7
Premigration considerations........................................................................................................... 30
BlackBerry Enterprise Server compatibility......................................................................................................................... 30
Moving user accounts to a destination BlackBerry Enterprise Server 5.0 or later........................................................... 30
Moving user accounts to a destination BlackBerry Enterprise Server 4.1.4 to 4.1.7.......................................................30
Moving user accounts to a destination BlackBerry Enterprise Server 4.1 to 4.1.3..........................................................31
Moving user accounts to a destination BlackBerry Enterprise Server 4.0.7................................................................... 33
Moving user accounts to a destination BlackBerry Enterprise Server 4.0 to 4.0.6..........................................................34
BlackBerry Device Software compatibility...........................................................................................................................35
Moving user accounts to a destination BlackBerry Enterprise Server 5.0 or later........................................................... 35
Moving user accounts to a destination BlackBerry Enterprise Server 4.1.4 to 4.1.7.......................................................36
Moving user accounts to a destination BlackBerry Enterprise Server 4.1 to 4.1.3..........................................................38
Moving user accounts to a destination BlackBerry Enterprise Server 4.0.7................................................................... 39
Moving user accounts to a destination BlackBerry Enterprise Server 4.0 to 4.0.6..........................................................40
Moving user accounts from a BlackBerry Enterprise Server Express to a BlackBerry Enterprise Server.................................42
Moving user accounts from a BlackBerry Enterprise Server or BlackBerry Professional Software to a BlackBerry
Enterprise Server Express...................................................................................................................................................43
8
Preparing to move user accounts.................................................................................................... 44
Create the manifest file...................................................................................................................................................... 44
Configure the source and destination instances of the BlackBerry Configuration Database.................................................. 44
Configure the default settings to apply to the user accounts that you migrate...................................................................... 45
Configure the BlackBerry Enterprise Transporter to send notification email messages to user accounts...............................47
Configure how long the BlackBerry Enterprise Transporter tries to open a connection to the source BlackBerry
Configuration Database and the destination BlackBerry Configuration Database.................................................................47
9
Selecting the user accounts to move to the destination MDM domain ............................................. 49
Live mode: Selecting user accounts to migrate................................................................................................................... 49
Search for and select user accounts to move............................................................................................................... 49
Import a file with email addresses................................................................................................................................ 50
Add the information for a single user account.............................................................................................................. 50
Bulk mode: Selecting user accounts to migrate...................................................................................................................51
Enable bulk mode to select all user accounts that are associated with a source BlackBerry Enterprise Server............... 51
Configure the default settings to apply to specific user accounts......................................................................................... 52
10
Moving user accounts..................................................................................................................... 54
Preview the migration process............................................................................................................................................54
Move user accounts to a different MDM domain................................................................................................................. 54
View the latest BlackBerry Enterprise Transporter log file....................................................................................................55
11
Running the BlackBerry Enterprise Transporter from the command prompt.....................................57
Preview the migration process using the command prompt.................................................................................................57
Move user accounts to a different MDM domain using the command prompt...................................................................... 59
12
Return user accounts to the source MDM domain........................................................................... 61
13
Troubleshooting............................................................................................................................. 62
Configuration errors and warnings...................................................................................................................................... 62
The BlackBerry Enterprise Transporter cannot connect to the BlackBerry Administration Service.................................62
Configuration file error.................................................................................................................................................62
XML Manifest Failed to Load........................................................................................................................................63
Destination 5.0 server found but unable to find BUA installation...................................................................................63
One or more user accounts do not have a Destination Server set.................................................................................. 64
Troubleshooting preview errors.......................................................................................................................................... 64
ERROR: Destination contains servers older than 5.0.................................................................................................... 64
Application error messages......................................................................................................................................... 64
User validation error messages.................................................................................................................................... 66
User validation warning messages............................................................................................................................... 69
Troubleshooting migration errors........................................................................................................................................70
User migration failed messages................................................................................................................................... 70
User migration completed with warning messages....................................................................................................... 71
User migration pending error messages.......................................................................................................................72
IT policy error messages.............................................................................................................................................. 73
User account status: Skipped...................................................................................................................................... 74
User account status: MigrationSkippedDueToValidationFailure....................................................................................74
14
Port information for the BlackBerry Enterprise Server Resource Kit tools..........................................75
Port information for tools that connect to the BlackBerry Configuration Database................................................................75
Port information for tools that connect to the BlackBerry Administration Service, BlackBerry Administration API, and
BlackBerry Web Services................................................................................................................................................... 76
Port information for the BlackBerry System Log Monitoring and Reporting Tool................................................................... 77
Port information for the BlackBerry Message Receipt Confirmation Tool............................................................................. 77
15
Glossary......................................................................................................................................... 78
16
Legal notice ................................................................................................................................... 79
Installation and Administration Guide
BlackBerry Enterprise
Transporter
BlackBerry Enterprise Transporter
1
You can use the BlackBerry Enterprise Transporter to move user accounts from one MDM domain to a different MDM
domain. An MDM domain consists of a BlackBerry Configuration Database and any BlackBerry Enterprise Server
components that are associated with it.
You can use the BlackBerry Enterprise Transporter when your organization upgrades the BlackBerry Enterprise Server and
you want to move users to a new MDM domain, or if you need to move user accounts between existing MDM domains. For
example, if you want to upgrade your organization's BlackBerry Enterprise Server from version 5.0.1 to version 5.0.4, you
can create a new MDM domain version 5.0.4 and use the BlackBerry Enterprise Transporter to move user accounts to the
new BlackBerry Configuration Database. You can also move user accounts from a production domain to a test domain and
back.
When you run the BlackBerry Enterprise Transporter, users do not need to delete BlackBerry device data or reactivate their
devices. After the migration process completes, the destination BlackBerry Enterprise Server resends the service book to
devices over the wireless network, device activation starts, and the synchronization of organizer data and calendar
information starts.
Note that the BlackBerry Enterprise Transporter does not move server settings to the destination BlackBerry Enterprise
Server (for example, the software configurations or IT policies that are assigned to user accounts). Prior to using the tool,
evaluate the available migration options. For more information on the available migration options, visit
www.blackberry.com/go/serverdocs to read the BlackBerry Enterprise Server Upgrade Guide.
Related information
Supported environments, 14
Unsupported features and environments, 19
BlackBerry Enterprise Transporter modes
You can run the BlackBerry Enterprise Transporter in live mode or in bulk mode to move user accounts from a source MDM
domain to a different destination MDM domain.
Live mode
Running the BlackBerry Enterprise Transporter in live mode refers to migrating one or more user accounts from a source
BlackBerry Enterprise Server to a destination BlackBerry Enterprise Server in a different MDM domain. Both the source
6
Installation and Administration Guide
BlackBerry Enterprise Transporter
and destination BlackBerry Enterprise Server must be running. The destination BlackBerry Enterprise Server must use a
different SRP ID than the source BlackBerry Enterprise Server.
Live mode is the default mode of the BlackBerry Enterprise Transporter.
When using live mode, the tool monitors organizer data synchronization, calendar synchronization, and the delivery of IT
administration commands (such as Resend IT Policy or Switch Service) to verify that the migration process completed
successfully.
Bulk mode
Running the BlackBerry Enterprise Transporter in bulk mode refers to migrating all of the user accounts from a source
BlackBerry Enterprise Server to a destination BlackBerry Enterprise Server. The source and destination instances must not
be running, except for the BlackBerry Administration Service and the IBM Domino services (where applicable) on the
destination BlackBerry Enterprise Server.
In a Microsoft Exchange or Novell GroupWise environment, you must configure the destination BlackBerry Enterprise
Server instances to use the same instance names (ServerConfig.ServiceName) and SRP IDs as the source BlackBerry
Enterprise Server instances. In an IBM Domino environment, you must configure the destination BlackBerry Enterprise
Server instances to use the same SRP IDs as the source BlackBerry Enterprise Server instances.
When using bulk mode, the tool does not monitor IT administration commands (such as Resend IT Policy or Switch Service)
to verify that the migration process completed successfully.
If you enable bulk mode and configure custom default settings to apply to individual user accounts (the IT policies,
software configurations, and groups to assign to user accounts), the destination BlackBerry Administration Service must
process the different settings for each user account. As a result, the migration process might take longer than expected to
complete.
If you enable bulk mode, it is a best practice to configure a single default setting to apply to all user accounts. You can
modify the IT policy, software configuration, and group assignments using the BlackBerry Administration Service after the
migration is complete. If you want to assign custom default settings to individual user accounts as part of the migration
process, it is a best practice to use live mode.
Options for migrating user accounts
Option
Description
Move one or more user accounts at a
time
If your organization's environment includes more than one MDM domain, and
you want to move select user accounts from one MDM domain to another, you
can use the tool in live mode.
For example, you can use this option if you maintain multiple MDM domains for
different groups in the organization, and you want to move users over to the
7
Installation and Administration Guide
Option
BlackBerry Enterprise Transporter
Description
MDM domain for a different group, or if you install a new BlackBerry Enterprise
Server environment as a new MDM domain, and you want to move users to the
new production environment.
Move all user accounts on a
BlackBerry Enterprise Server
If you want to move all of the user accounts on a BlackBerry Enterprise Server to
a new MDM domain, you can use the tool in bulk mode.
For example, you can use this option to upgrade your organization's
environment in phases to the latest version of the BlackBerry Enterprise Server.
If you enable bulk mode and configure custom default settings to apply to
individual user accounts (the IT policies, software configurations, and groups to
assign to user accounts), the destination BlackBerry Administration Service
must process the different settings for each user account. As a result, the
migration process might take longer than expected to complete.
If you enable bulk mode, it is a best practice to configure a single default setting
to apply to all user accounts. You can modify the IT policy, software
configuration, and group assignments using the BlackBerry Administration
Service after the migration is complete. If you want to assign custom default
settings to individual user accounts as part of the migration process, it is a best
practice to use live mode.
Data that the migration process does not
move
Data
Description
User accounts that are not BlackBerry- The BlackBerry Enterprise Transporter does not move user accounts that are
enabled
not BlackBerry-enabled (for example, administrator accounts that cannot be
assigned a device).
Administrative role assignment
8
If you move user accounts from a BlackBerry Enterprise Server 5.0 or later to a
different BlackBerry Enterprise Server 5.0 or later, the migration process does
not move the administrative roles that are assigned to the user accounts. You
can manually assign the administrative roles to the user accounts after the
migration process completes, or you can create groups for user accounts and
assign roles to the groups in the destination BlackBerry Enterprise Server.
Installation and Administration Guide
BlackBerry Enterprise Transporter
Data
Description
Group data
The migration process does not migrate groups or any of the data associated
with groups. Instead, you can create a group on the destination BlackBerry
Enterprise Server and specify it as the group that you want to assign user
accounts to during the migration process.
Software configurations
The migration process does not migrate software configurations, including
BlackBerry MDS Runtime application data.
You can create a software configuration on the destination BlackBerry
Enterprise Server and specify it as the software configuration that you want to
assign to user accounts during the migration process.
IT policy data
By default, the user accounts that you move to a destination BlackBerry
Enterprise Server are assigned the Default IT policy after the migration process
completes. Before you start the migration process, you can select the IT policies
on the destination BlackBerry Enterprise Server that you want to apply to the
user accounts after the migration process completes. Alternatively, before a
migration, you can assign an IT policy to a group in the destination BlackBerry
Enterprise Server and then assign the user accounts to the group.
Note: If you move user accounts to a destination BlackBerry Enterprise Server
5.0 or later, there might be a delay before the destination BlackBerry Enterprise
Server applies the selected IT policies or group-assigned IT policies to devices.
During this delay, the Default IT policy is applied to the devices.
BlackBerry MDS Integration Service
data
The migration process does not migrate any data associated with the BlackBerry
MDS Integration Service. For more information about the BlackBerry MDS
Integration Service, visit www.blackberry.com/go/serverdocs to read the
BlackBerry Enterprise Server Feature and Technical Overview.
Note that the BlackBerry MDS Integration Service has been deprecated as of
BlackBerry Enterprise Server 5.0 SP3.
BlackBerry Browser configuration
settings
The migration process does not migrate the BlackBerry Browser configuration
settings on the device that is associated with a user account.
Synchronized public contacts and
databases, and additional private
contact folders
The migration process does not migrate public contact folders and databases
that you have not published globally on the destination BlackBerry
Administration Service. The BlackBerry Enterprise Transporter does not publish
public contact folders and databases.
In a Microsoft Exchange environment, synchronized public contacts and
additional private contact folders can be moved only to a BlackBerry Enterprise
Server that is version 5.0 SP1 or later.
9
Installation and Administration Guide
BlackBerry Enterprise Transporter
Validation that the BlackBerry Enterprise
Transporter performs
Global validation
The BlackBerry Enterprise Transporter performs the following actions before it begins the migration process:
•
Verifies that the BlackBerry Administration Service is installed in the destination MDM domain.
•
Sends a test BlackBerry Administration Service command to verify that the BlackBerry Administration Service is
available and can respond.
•
Verifies that the required API and web services are installed on the computer that hosts the BlackBerry Administration
Service. For more information about the required API and web services, see System requirements: BlackBerry
Enterprise Transporter.
In an IBM Domino environment, the tool verifies whether skipDominoBBSDReplication and skipDominoBBSDValidation are
set to True in the EnterpriseTransporter.exe.config file to determine how to validate. It then performs the following actions:
•
Verifies that IBM Notes is installed on the computer that hosts the BlackBerry Enterprise Transporter
•
If skipDominoBBSDReplication and skipDominoBBSDValidation are not present or are set to False, verifies that the
selected IBM Notes user.id can open the BlackBerry profiles databases in both the source MDM domain and the
destination MDM domain.
The default location of the EnterpriseTransporter.exe.config file is <drive>:\Program Files (x86)\Research In Motion
\BlackBerry Enterprise Server Resource Kit\BlackBerry Enterprise Transporter. If your computer's operating system uses
UAC and does not permit you to modify the configuration file at this location, open the virtualized copy of the
EnterpriseTransporter.exe.config file in the application data folder for the current user (for example, <drive>\Users
\<user_name>\AppData\Local\VirtualStore\Program Files (x86)\Research In Motion\BlackBerry Enterprise Server Resource
Kit).
User validation
The BlackBerry Enterprise Transporter performs the following validation before it migrates a user account:
•
Verifies that the user account is associated with a valid email address.
•
Verifies that the user account exists in the source MDM domain.
•
Verifies that the user account does not already exist in the destination MDM domain.
10
Installation and Administration Guide
BlackBerry Enterprise Transporter
•
Verifies whether it can preserve the user ID that is associated with the user's BlackBerry device.
•
Verifies that an IT policy can be applied to the user's device. Tthis verification might not be possible in any of the
following scenarios:
•
The device is running an unspecified version of the BlackBerry Device Software
•
The device is running BlackBerry Device Software 4.0.2 and the ITPolicyKeyMapping table does not exist.
•
The device is running BlackBerry Device Software 4.3.0.
In an IBM Domino environment, the tool performs the following actions:
•
If SkipDominoBBSDReplication is set to True in the EnterpriseTransporter.exe.config file, the tool verifies whether the
user’s BlackBerry state database already exists on the destination BlackBerry Enterprise Server.
•
Verifies that the user’s source BlackBerry state database can be opened on the source BlackBerry Enterprise Server.
•
Verifies whether the user’s BlackBerry state database has been marked for deletion in the BlackBerry profiles database
on the destination BlackBerry Enterprise Server.
•
Verifies whether a duplicate BlackBerry state database exists on the destination BlackBerry Enterprise Server.
The default location of the EnterpriseTransporter.exe.config file is <drive>:\Program Files (x86)\Research In Motion
\BlackBerry Enterprise Server Resource Kit\BlackBerry Enterprise Transporter. If your computer's operating system uses
UAC and does not permit you to modify the configuration file at this location, open the virtualized copy of the
EnterpriseTransporter.exe.config file in the application data folder for the current user (for example, <drive>\Users
\<user_name>\AppData\Local\VirtualStore\Program Files (x86)\Research In Motion\BlackBerry Enterprise Server Resource
Kit).
What's new in BlackBerry Enterprise
Transporter 5.0.4
Feature
Description
Online help
Help buttons in the BlackBerry Enterprise Transporter now direct you to the
BlackBerry Enterprise Transporter online help and context-sensitive help topics.
11
Installation and Administration Guide
System requirements
System requirements
2
System requirements: BlackBerry
Enterprise Transporter
Note: You can use the BlackBerry Enterprise Transporter to move user accounts to a destination BlackBerry Enterprise
Server in a different MDM domain, but the tool does not migrate server settings to the destination BlackBerry Enterprise
Server. Prior to using the tool, evaluate the available migration options. For more information about the available migration
options, visit www.blackberry.com/go/serverdocs to read the BlackBerry Enterprise Server Upgrade Guide.
Item
Requirement
BlackBerry Enterprise
Transporter version
Use the latest available version of the BlackBerry Enterprise Transporter, regardless of
the version of the source BlackBerry Enterprise Server and destination BlackBerry
Enterprise Server.
Operating system
Any of the following operating systems:
•
Windows 7
•
Windows Server 2008 R2
•
Windows Server 2008
•
Windows Vista
•
Windows Server 2003 SP1 or later
•
Windows XP Professional SP2
Microsoft .NET Framework
•
Microsoft .NET Framework 2.0 or later
Encryption algorithm
•
Triple DES, AES, or both Triple DES and AES
Configure the source BlackBerry Enterprise Server and the destination BlackBerry
Enterprise Server to use the same option for the encryption algorithm.
For example, if you configure the source BlackBerry Enterprise Server to use Triple
DES and the destination BlackBerry Enterprise Server to use Triple DES and AES, this
12
Installation and Administration Guide
Item
System requirements
Requirement
configuration is not supported for user migration. You must configure both the source
and the destination to use Triple DES and AES.
Administrator permissions for the In the source and destination BlackBerry Administration Service, create an
BlackBerry Administration
administrator account that you can use to view BlackBerry Enterprise Server
Service
instances, and to create and manage groups, user accounts, IT policies, and software
configurations. These permissions are typically associated with a security
administrator role or enterprise administrator role.
BlackBerry Enterprise Server
Before you use the BlackBerry Enterprise Transporter for the first time, log in to the
destination BlackBerry Administration Service and verify that you can create a user
account, assign a device to the user account, and activate the device.
APIs and web services
The BlackBerry Enterprise Transporter uses the BlackBerry Administration API and
the admin web services (AdminWS) to migrate user accounts and user configuration
settings. If the destination BlackBerry Enterprise Server is 4.0.x, 4.1.x, or 5.0.1 or
later, the required components are installed automatically with the BlackBerry
Enterprise Server.
If the destination BlackBerry Enterprise Server is 5.0, you must install the BlackBerry
Enterprise Server User Administration Tool on the computer that hosts the destination
BlackBerry Administration Service. The BlackBerry Enterprise Server User
Administration Tool provides the components that the BlackBerry Enterprise
Transporter requires.
For more information about installing the BlackBerry Enterprise Server User
Administration Tool, visit www.blackberry.com/go/serverdocs to read the BlackBerry
Enterprise Server Resource Kit Installation Guide.
MDM domain
If the destination MDM domain includes a BlackBerry Enterprise Server 5.0.x, all
BlackBerry Enterprise Server instances must be 5.0.x or later.
Screen resolution
•
Minimum 1024 x 768
Related information
Premigration considerations, 30
Installation considerations
13
Installation and Administration Guide
System requirements
Supported environments
Item
Environment
BlackBerry Enterprise Server
versions
For information about the supported versions of the source and destination
BlackBerry Enterprise Server, see the appropriate compatibility matrix:
•
BlackBerry Enterprise Transporter compatibility matrix for the BlackBerry
Enterprise Server for Microsoft Exchange and the BlackBerry Enterprise Server for
IBM Lotus Domino
•
BlackBerry Enterprise Transporter compatibility matrix for the BlackBerry
Enterprise Server for Novell GroupWise
•
BlackBerry Enterprise Transporter compatibility matrix for the BlackBerry
Enterprise Server Express, BlackBerry Professional Software, and BlackBerry
Enterprise Server Small Business Edition
Known issues might apply depending on the versions of the source BlackBerry
Enterprise Server and the destination BlackBerry Enterprise Server. For more
information, see the premigration considerations.
BlackBerry Enterprise Server
Express
The BlackBerry Enterprise Transporter does not support the use of bulk mode when
moving user accounts from a source BlackBerry Enterprise Server Express, or to a
destination BlackBerry Enterprise Server Express.
Database server (source and
destination)
The BlackBerry Enterprise Transporter supports the following database servers (32-bit
or 64-bit):
•
Microsoft SQL Server 2012
•
Microsoft SQL Server 2008 R2 Express
•
Microsoft SQL Server 2008 Express SP1
•
Microsoft SQL Server 2008 R2
•
Microsoft SQL Server 2008 SP2 or SP1
•
Microsoft SQL Server 2005 Express SP3
•
Microsoft SQL Server 2005 SP3 or SP2
The BlackBerry Enterprise Transporter might function correctly with versions of
Microsoft SQL Server that are not listed, but the tool has not been tested with and
does not officially support other versions.
Microsoft Exchange messaging
server
14
Any version of Microsoft Exchange that the BlackBerry Enterprise Server supports.
Installation and Administration Guide
System requirements
Item
Environment
IBM Domino messaging server
Any version of Domino that the BlackBerry Enterprise Server supports, and that is
version 6.5.4 or later.
Novell GroupWise messaging
server
Any version of Novell GroupWise that the BlackBerry Enterprise Server supports.
User email application
The BlackBerry Enterprise Transporter supports the following versions of IBM Notes:
BlackBerry Device Software
•
Notes 7.0 (to support encrypted message display when the user.id file is stored in
BlackBerry Desktop Manager 4.1)
•
Notes 8.0.x
•
Notes 8.5.x
For more information about BlackBerry Device Software compatibility, see BlackBerry
Device Software compatibility.
Related information
Premigration considerations, 30
BlackBerry Enterprise Transporter compatibility matrix for the BlackBerry
Enterprise Server for Microsoft Exchange and the BlackBerry Enterprise
Server for IBM Domino
The following table displays the migration paths that the BlackBerry Enterprise Transporter supports.
Note: Based on the version and the type of the source BlackBerry Enterprise Server and the destination BlackBerry
Enterprise Server, there might be important conditions that you must be aware of. Read the premigration considerations
section before you try to migrate user accounts.
Table 1: Legend
Designation
Abbreviation
Description
Supported
S
The migration path has been tested and is supported for moving users
from the source server to the destination server, and for moving users
back from the destination server to the source server for troubleshooting
purposes only.
Back Out Only
BO
The migration path is supported for troubleshooting purposes only.
Best Effort
BE
The migration path has not been tested and is not officially supported.
Not Supported
NS
The migration path is not supported due to compatibility issues.
15
Installation and Administration Guide
System requirements
Destination server
4.0 4.0.6
4.0.7
4.1 4.1.5
4.1.6 4.1.7
5.0
5.0.1
5.0.2
5.0.3
5.0.4
Sour 4.0 ce 4.0.6
serv
er 4.0.7
NS
NS
BE
BE
BE
BE
BE
BE
BE
NS
NS
BE
BE
S
S
S
S
S
4.1 4.1.5
NS
NS
BE
BE
BE
BE
BE
BE
BE
4.1.6 4.1.7
NS
NS
BE
BE
S
S
S
S
S
5.0
NS
BO
NS
BO
S
S
S
S
S
5.0.1
NS
BO
NS
BO
S
S
S
S
S
5.0.2
NS
BO
NS
BO
S
S
S
S
S
5.0.3
NS
BO
NS
BO
S
S
S
S
S
5.0.4
NS
BO
NS
BO
S
S
S
S
S
Related information
BlackBerry Enterprise Server compatibility, 30
BlackBerry Device Software compatibility, 35
BlackBerry Enterprise Transporter compatibility matrix for the BlackBerry
Enterprise Server for Novell GroupWise
The following table displays the migration paths that the BlackBerry Enterprise Transporter supports.
Note: Based on the version and the type of the source BlackBerry Enterprise Server and the destination BlackBerry
Enterprise Server, there might be important conditions that you must be aware of. Read the premigration considerations
section before you try to migrate user accounts.
Table 2: Legend
Designation
Abbreviation
Description
Supported
S
The migration path has been tested and is supported for moving users
from the source server to the destination server, and for moving users
back from the destination server to the source server for troubleshooting
purposes only.
16
Installation and Administration Guide
System requirements
Designation
Abbreviation
Description
Back Out Only
BO
The migration path is supported for troubleshooting purposes only.
Best Effort
BE
The migration path has not been tested and is not officially supported.
Not Supported
NS
The migration path is not supported due to compatibility issues.
Destination server
4.0 - 4.0.6
4.0.7
4.1 - 4.1.4
4.1.6 - 4.1.7
5.0.1
5.0.4
Source 4.0 - 4.0.6
server
4.0.7
NS
NS
BE
BE
BE
BE
NS
NS
BE
BE
S
S
4.1 - 4.1.4
NS
NS
BE
BE
BE
BE
4.1.6 - 4.1.7
NS
NS
BE
BE
S
S
5.0.1
NS
BO
NS
BO
S
S
5.0.4
NS
BO
NS
BO
S
S
Related information
BlackBerry Enterprise Server compatibility, 30
BlackBerry Device Software compatibility, 35
BlackBerry Enterprise Transporter compatibility matrix for the BlackBerry
Enterprise Server Express, BlackBerry Professional Software, and
BlackBerry Enterprise Server Small Business Edition
The following table displays the migration paths that the BlackBerry Enterprise Transporter supports.
The BlackBerry Enterprise Transporter does not support bulk mode when moving user accounts from a BlackBerry
Enterprise Server Express to a destination BlackBerry Enterprise Server. The BlackBerry Enterprise Transporter does not
support bulk mode when moving user accounts to a BlackBerry Enterprise Server Express.
Note: Based on the version and the type of the source and destination server, there might be important conditions that you
must be aware of. Read the premigration considerations section before you try to migrate user accounts.
17
Installation and Administration Guide
System requirements
Table 3: Legend
Designation
Abbreviation
Description
Supported
S
The migration path has been tested and is supported for moving users
from the source server to the destination server, and for moving users
back from the destination server to the source server for troubleshooting
purposes only.
Back Out Only
BO
The migration path is supported for troubleshooting purposes only.
Best Effort
BE
The migration path has not been tested and is not officially supported.
Not Supported
NS
The migration path is not supported due to compatibility issues.
Destination server
BlackBerry
Enterprise
Server Small
Business
Edition 4.0.7
and 4.1.7
BlackBerry
BlackBerry
Professional
Enterprise
Software 4.1.4 Server Express
5.0.1
BlackBerry
Enterprise
Server Express
5.0.2 and later
BlackBerry
Enterprise
Server 4.0 5.0.1
BlackBerry
Enterprise
Server 5.0.2
and later
NS
NS
BE
S
NS*
NS*
BlackBerry
NS
Professional
Software 4.1.4
NS
BE
S
NS
NS
BlackBerry
NS
Enterprise
Server Express
5.0.1
NS
BE
BE
BE
BE
BlackBerry
BO
Enterprise
Server Express
5.0.2 and later
BO
BE
BE
BE
S
Sourc BlackBerry
e
Enterprise
server Server Small
Business
Edition 4.0.7
and 4.1.7
18
Installation and Administration Guide
System requirements
Destination server
BlackBerry
Enterprise
Server 4.0 5.0.1
NS
NS
NS
NS
See
appropriate
matrix
See
appropriate
matrix
BlackBerry
Enterprise
Server 5.0.2
and later
NS
NS
NS
BO
See
appropriate
matrix
See
appropriate
matrix
*To move user accounts from the source server, you must install an upgrade key to upgrade the source server to the
BlackBerry Enterprise Server.
Related information
BlackBerry Enterprise Server compatibility, 30
BlackBerry Device Software compatibility, 35
Moving user accounts from a BlackBerry Enterprise Server Express to a BlackBerry Enterprise Server, 42
Moving user accounts from a BlackBerry Enterprise Server or BlackBerry Professional Software to a BlackBerry Enterprise
Server Express, 43
Unsupported features and environments
For more information about BlackBerry Enterprise Transporter compatibility, see Supported environments.
Item
Environment
MDM domains
The BlackBerry Enterprise Transporter does not support the following MDM domains:
•
BlackBerry Device Service
•
Universal Device Service
Messaging server environment
The BlackBerry Enterprise Transporter does not support migrating users from one
messaging server environment to a different environment (for example, migrating
users from an IBM Domino environment to a Microsoft Exchange environment).
BlackBerry Device Software
The BlackBerry Enterprise Transporter does not support BlackBerry Device Software
versions that are earlier than version 4.0; version 4.3.0 is supported with conditions.
IBM DB2 UDB
The BlackBerry Enterprise Transporter does not support DB2 UDB.
Related information
Supported environments, 14
19
Installation and Administration Guide
System requirements
BlackBerry Enterprise Transporter compatibility matrix for the BlackBerry Enterprise Server for Microsoft Exchange and
the BlackBerry Enterprise Server for IBM Domino, 15
BlackBerry Enterprise Transporter compatibility matrix for the BlackBerry Enterprise Server for Novell GroupWise, 16
BlackBerry Enterprise Transporter compatibility matrix for the BlackBerry Enterprise Server Express, BlackBerry
Professional Software, and BlackBerry Enterprise Server Small Business Edition, 17
Troubleshooting preview errors, 64
Troubleshooting migration errors, 70
Premigration considerations, 30
Required permissions in an IBM Domino environment
To run the BlackBerry Enterprise Transporter in an IBM Domino environment, you require the same permissions in the
source MDM domain and the destination MDM domain that you require as an administrator of the BlackBerry Enterprise
Server for IBM Domino.
For more information, visit www.blackberry.com/go/serverdocs to read the BlackBerry Enterprise Server Installation Guide
and the BlackBerry Enterprise Server Administration Guide.
Permission
Description
Resource
Notes.ini file
You must configure read and write permissions in the
notes.ini file.
BlackBerry Enterprise Server
Installation Guide
•
IBM Notes user.id file
The BlackBerry Enterprise Transporter uses the IBM Notes —
user ID of the administrator to perform IBM Notes
operations, in the same way that the BlackBerry Enterprise
Server uses a server ID to perform IBM Notes operations.
The BlackBerry Enterprise Transporter prompts for the
user ID and password before it runs a migration preview.
The IBM Notes user ID must be a member of the
LocalDomainServers group. The BlackBerry Enterprise
Transporter might not be able to use the user ID if the user
ID file name (username.id), stored in the notes.ini file,
contains accented characters (for example, ã).
20
Section: System
requirements:
BlackBerry Enterprise
Server
Installation and Administration Guide
System requirements
Replicating IBM Domino databases
Before you begin the migration process, you must verify the setting for skipDominoBBSDReplication in the configuration
file for the BlackBerry Enterprise Transporter (EnterpriseTransporter.exe.config). By default, the file is located at <drive>:
\Program Files (x86)\Research In Motion\BlackBerry Enterprise Server Resource Kit\BlackBerry Enterprise Transporter. If
your computer's operating system uses UAC and does not permit you to modify the configuration file at this location, open
the virtualized copy of the EnterpriseTransporter.exe.config file in the application data folder for the current user (for
example, <drive>\Users\<user_name>\AppData\Local\VirtualStore\Program Files (x86)\Research In Motion\BlackBerry
Enterprise Server Resource Kit).
Perform one of the following actions:
•
If skipDominoBBSDReplication is not set to True, do not replicate the IBM Domino databases before you run the
BlackBerry Enterprise Transporter. The BlackBerry Enterprise Transporter performs a database replication before it
migrates user accounts.
•
If skipDominoBBSDReplication is set to True, you must replicate the BlackBerry state database for each user account
in the destination MDM domain before you begin the migration process. If you migrate a user account without
replicating the user’s BlackBerry state database in the destination MDM domain, all information for the user account is
lost, and you must remove the user account from the BlackBerry Enterprise Server, delete all data on the device that is
associated with the user account, add the user account again to the BlackBerry Enterprise Server, and reactivate the
device.
21
Installation and Administration Guide
Installing or upgrading the BlackBerry Enterprise Transporter
Installing or upgrading the
BlackBerry Enterprise
Transporter
3
Install or upgrade the BlackBerry Enterprise
Transporter
Before you begin:
• Verify that the computer you want to use has access to the database servers that host the source BlackBerry
Configuration Database and the destination BlackBerry Configuration Database.
•
On the computer where you plan to install the BlackBerry Enterprise Transporter, create a folder to store the
installation files.
•
In a browser, visit www.blackberry.com/support/downloads, and navigate to the Downloads area for the BlackBerry
Enterprise Server Resource Kit to download the latest installation package for the tools (brk<version>.exe).
•
Complete the download instructions on the website.
•
Double-click brk<version>.exe. Extract the contents of the installation package to the folder you created.
1.
In the installation folder that you created, double-click brk-bbenterprisetransporter<version>.msi.
2.
Click Next.
3.
In the drop-down list, click the country or region in which you are located.
4.
Read the license agreement. Select I accept the terms in the License Agreement.
5.
Click Next.
6.
If necessary, click Change to specify the installation file path for the tool.
7.
Click Next.
8.
Click Install.
9.
Click Finish.
22
Installation and Administration Guide
Configuring the BlackBerry Enterprise Transporter
Configuring the BlackBerry
Enterprise Transporter
4
Configure how long the BlackBerry
Enterprise Transporter waits for the
Microsoft SQL Server to process commands
When you try to move user accounts to a destination BlackBerry Enterprise Server, the BlackBerry Enterprise Transporter
sends commands to the Microsoft SQL Server to process. By default, the BlackBerry Enterprise Transporter waits for a
timeout period of 30 seconds for the Microsoft SQL Server to process a command and return a response. If the timeout
period expires and the BlackBerry Enterprise Transporter has not received a response, the BlackBerry Enterprise
Transporter stops waiting for a response and considers the command to be failed.
You can configure how long you want the BlackBerry Enterprise Transporter to wait for the Microsoft SQL Server to process
a command and return a response. You can change the timeout period to any value between 30 and 300 seconds.
1.
On the computer that hosts the BlackBerry Enterprise Transporter, navigate to <drive>:\Program Files
(x86)\Research In Motion\BlackBerry Enterprise Server Resource Kit\BlackBerry Enterprise Transporter.
2.
In a text editor, open the EnterpriseTransporter.exe.config file.
If your computer's operating system uses UAC and does not permit you to modify the configuration file at this
location, open the virtualized copy of the EnterpriseTransporter.exe.config file in the application data folder for the
current user (for example, <drive>\Users\<user_name>\AppData\Local\VirtualStore\Program Files (x86)\Research In
Motion\BlackBerry Enterprise Server Resource Kit).
3.
In the <appSettings> section, type the following information: <add key="sqlCommandTimeout"
value="<timeout_value>"/>, where <timeout_value> is the number of seconds that you want the tool to wait for the
Microsoft SQL Server to process commands and return responses.
4.
Save and close the EnterpriseTransporter.exe.config file.
After you finish: Restart the BlackBerry Enterprise Transporter.
23
Installation and Administration Guide
Configuring the BlackBerry Enterprise Transporter
Encrypt the information about database
connections in the BlackBerry Enterprise
Transporter configuration file
When you configure the source BlackBerry Configuration Database and the destination BlackBerry Configuration Database
in the BlackBerry Enterprise Transporter, information about the database connections is stored in the BlackBerry
Enterprise Transporter configuration file (EnterpriseTransporter.exe.config). If you select Microsoft SQL Server
Authentication for a BlackBerry Configuration Database, the password information is stored in the configuration file in plain
text (the password is not stored if you choose Windows authentication). You can modify the configuration file to encrypt the
information that it contains about database connections.
Note: If you encrypt the information about database connections in the BlackBerry Enterprise Transporter configuration
file and you copy or move the configuration file to a different computer, you cannot decrypt the information about database
connections on the new computer.
1.
On the computer that hosts the BlackBerry Enterprise Transporter, navigate to <drive>:\Program Files
(x86)\Research In Motion\BlackBerry Enterprise Server Resource Kit\BlackBerry Enterprise Transporter.
2.
In a text editor, open the EnterpriseTransporter.exe.config file.
If your computer's operating system uses UAC and does not permit you to modify the configuration file at this
location, open the virtualized copy of the EnterpriseTransporter.exe.config file in the application data folder for the
current user (for example, <drive>\Users\<user_name>\AppData\Local\VirtualStore\Program Files (x86)\Research In
Motion\BlackBerry Enterprise Server Resource Kit).
3.
In the <appSettings> section, type the following: <add key="encryptConnectionStrings" value="true"/>.
4.
Save and close the EnterpriseTransporter.exe.config file.
After you finish: Restart the BlackBerry Enterprise Transporter.
24
Installation and Administration Guide
Configuring the BlackBerry Enterprise Transporter
Configure the BlackBerry Enterprise
Transporter to skip certificate validation
When the BlackBerry Enterprise Transporter 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.
1.
On the computer that hosts the BlackBerry Enterprise Transporter, navigate to <drive>:\Program Files
(x86)\Research In Motion\BlackBerry Enterprise Server Resource Kit\BlackBerry Enterprise Transporter.
2.
In a text editor, open the EnterpriseTransporter.exe.config file.
If your computer's operating system uses UAC and does not permit you to modify the configuration file at this
location, open the virtualized copy of the EnterpriseTransporter.exe.config file in the application data folder for the
current user (for example, <drive>\Users\<user_name>\AppData\Local\VirtualStore\Program Files (x86)\Research In
Motion\BlackBerry Enterprise Server Resource Kit).
3.
In the <appSettings> section, type the following: <add key="certValidationExcludedHosts" value="<server>"/>,
where <server> is the FQDN or IP address of the computer that hosts the BlackBerry Administration Service. If you
want to specify multiple computers, separate each FQDN or IP address using a comma ( , ) or semi-colon ( ; ).
Example: <add key="certValidationExcludedHosts" value="server1.testnet.company.net;192.0.2.124"/>
4.
Save and close the EnterpriseTransporter.exe.config file.
After you finish: Restart the BlackBerry Enterprise Transporter.
25
Installation and Administration Guide
Preparing the source MDM domain for the migration process
Preparing the source MDM
domain for the migration
process
5
For more information about managing the BlackBerry Enterprise Server, visit www.blackberry.com/go/serverdocs to read
the documentation for the BlackBerry Enterprise Server.
Task
Resource
Delete all unused user accounts.
BlackBerry Enterprise Server
Administration Guide
In an IBM Domino environment, remove the associated BlackBerry state
databases.
Back up the BlackBerry Configuration Database.
BlackBerry Enterprise Server Upgrade
Guide
Create a list of the software configurations and applications that you want to
duplicate in the destination MDM domain.
BlackBerry Enterprise Server
Administration Guide
Create a list of the IT policies, policy rules, and default settings that you want to
duplicate in the destination MDM domain.
BlackBerry Enterprise Server
Administration Guide
Create a list of the SRP information and BlackBerry Enterprise Server CAL keys
that you want to duplicate in the destination MDM domain.
BlackBerry Enterprise Server
Administration Guide
If you want the BlackBerry Enterprise Transporter to import a list of the user
accounts to migrate, collect the list of user email addresses in a flat, CRdelimited text file. Verify that the text file uses the following format:
—
<emailaddress1>
<emailaddress2>
<emailaddress3>
Create a list of the administrator roles that you want to duplicate and assign in
the destination MDM domain.
BlackBerry Enterprise Server
Administration Guide
If you set up replication for the BlackBerry Configuration Database, stop the
replication process.
—
26
Installation and Administration Guide
Task
Preparing the source MDM domain for the migration process
Resource
Notify users that applications on the BlackBerry device that use a data
—
connection through the BlackBerry MDS Connection Service might experience a
service interruption until the user account is migrated and reactivated.
27
Installation and Administration Guide
Preparing the destination MDM domain for the migration process
Preparing the destination MDM
domain for the migration
process
6
For more information about managing the BlackBerry Enterprise Server, visit www.blackberry.com/go/serverdocs to read
the documentation the BlackBerry Enterprise Server.
Task
Resource
If you plan to move user mailboxes to the destination MDM domain, as a best
—
practice, consider moving the user mailboxes before you migrate user accounts.
Install a new BlackBerry Configuration Database, and install the new BlackBerry BlackBerry Enterprise Server
Enterprise Server instances.
Installation Guide
During the installation process, if the BlackBerry Enterprise Server instances
use the same SRP information as the source instances, do not verify the SRP
credentials, and do not start any BlackBerry Enterprise Server services except
for the BlackBerry Administration Service services.
In the destination BlackBerry Administration Service, create the groups, IT
policies, roles, and software configurations that you want to duplicate from the
source MDM domain.
BlackBerry Enterprise Server
Administration Guide
If you enable bulk mode and configure custom default settings to apply to
individual user accounts (the IT policies, software configurations, and groups to
assign to user accounts), the destination BlackBerry Administration Service
must process the different settings for each user account. As a result, the
migration process might take longer than expected to complete.
If you enable bulk mode, it is a best practice to configure a single default setting
to apply to all user accounts. You can modify the IT policy, software
configuration, and group assignments using the BlackBerry Administration
Service after the migration is complete. If you want to assign custom default
settings to individual user accounts as part of the migration process, it is a best
practice to use live mode.
Back up the BlackBerry Configuration Database.
28
BlackBerry Enterprise Server Upgrade
Guide
Installation and Administration Guide
Preparing the destination MDM domain for the migration process
Task
Resource
In an IBM Domino environment, you can copy the BlackBerry state databases
IBM Domino documentation
and BlackBerry profiles databases from the source BlackBerry Enterprise Server
instances to the destination BlackBerry Enterprise Server instances. You can
perform this task if you do not want the BlackBerry Enterprise Transporter to
replicate the databases during the migration process.
If you plan to use the BlackBerry Enterprise Transporter in bulk mode, in a
—
Microsoft Exchange or Novell GroupWise environment, configure the destination
BlackBerry Enterprise Server instances to use the same instance names
(ServerConfig.ServiceName) and SRP IDs as the source instances.
In an IBM Domino environment, configure the destination BlackBerry Enterprise
Server instances to use the same SRP IDs as the source BlackBerry Enterprise
Server instances.
Notify users that applications on the BlackBerry device that use a data
—
connection through the BlackBerry MDS Connection Service might experience a
service interruption until the user account is migrated and reactivated.
29
Installation and Administration Guide
Premigration considerations
Premigration considerations
7
BlackBerry Enterprise Server compatibility
Moving user accounts to a destination BlackBerry
Enterprise Server 5.0 or later
If the version of the source BlackBerry Enterprise Server for Microsoft Exchange is earlier than version 5.0, consider the
following information:
Consideration
Description
The BlackBerry Enterprise Transporter
might require more time than expected
to move user accounts to the
destination BlackBerry Enterprise
Server for Microsoft Exchange.
In specific circumstances, if the version of the source BlackBerry Enterprise
Server for Microsoft Exchange is earlier than version 4.1 SP6 MR5, the
BlackBerry Enterprise Transporter might require more time than expected to
move user accounts to the destination MDM domain. Before you try to move the
user accounts, upgrade the source BlackBerry Enterprise Server for Microsoft
Exchange to version 4.1 SP6 MR5 or later.
Moving user accounts to a destination BlackBerry
Enterprise Server 4.1.4 to 4.1.7
If you move user accounts to a destination BlackBerry Enterprise Server that is version 4.1.4 to 4.1.7, consider the
following information:
Consideration
Description
Issues might occur if the user ID of a
user account already exists on the
destination BlackBerry Enterprise
Server.
If the user ID of a user account on the source BlackBerry Enterprise Server is the
same as a user ID on the destination BlackBerry Enterprise Server, the user's
BlackBerry device might not work as expected after you migrate the account.
Before you move the user account, delete the user account from the source
30
Installation and Administration Guide
Consideration
Premigration considerations
Description
BlackBerry Enterprise Server, add it to the BlackBerry Enterprise Server again,
and activate the BlackBerry device.
If the source BlackBerry Enterprise Server is 5.0 or later, consider the following information:
Consideration
Description
Duplicate contact list entries might
appear on BlackBerry devices.
If organizer data synchronization is turned on for user accounts, and you try to
move the user accounts to a destination BlackBerry Enterprise Server for IBM
Domino, duplicate contact list entries might appear on devices. Permanently
delete the data on the devices and activate the devices again.
If the version of the source BlackBerry Enterprise Server for Microsoft Exchange is earlier than 5.0, consider the following
information:
Consideration
Description
The BlackBerry Enterprise Transporter
might require more time than expected
to move user accounts to the
destination BlackBerry Enterprise
Server for Microsoft Exchange.
In specific circumstances, if the version of the source BlackBerry Enterprise
Server for Microsoft Exchange is earlier than version 4.1 SP6 MR5, the
BlackBerry Enterprise Transporter might require more time than expected to
move user accounts to the destination MDM domain. Before you try to move the
user accounts, upgrade the source BlackBerry Enterprise Server for Microsoft
Exchange to version 4.1 SP6 MR5 or later.
If your organization's environment uses the BlackBerry Enterprise Server for Novell GroupWise, consider the following
information:
Consideration
Description
The BlackBerry Enterprise Transporter Upgrade the destination BlackBerry Enterprise Server to a version that the
does not support the version of the
BlackBerry Enterprise Transporter supports.
destination BlackBerry Enterprise
Server.
Moving user accounts to a destination BlackBerry
Enterprise Server 4.1 to 4.1.3
If you move user accounts to a destination BlackBerry Enterprise Server that is version 4.1 to 4.1 SP3, consider the
following information:
31
Installation and Administration Guide
Consideration
Premigration considerations
Description
The BlackBerry Enterprise Transporter Upgrade the destination BlackBerry Enterprise Server to a version that the
does not support the version of the
BlackBerry Enterprise Transporter supports.
destination BlackBerry Enterprise
Server.
Issues might occur if the user ID of a
user account already exists on the
destination BlackBerry Enterprise
Server.
If the user ID of a user account on the source BlackBerry Enterprise Server is the
same as a user ID on the destination BlackBerry Enterprise Server, the user's
BlackBerry device might not work as expected after you migrate the account.
Before you move the user account, delete the user account from the source
BlackBerry Enterprise Server, add it to the BlackBerry Enterprise Server again,
and activate the BlackBerry device.
If the source BlackBerry Enterprise Server is 5.0 or later, consider the following information:
Consideration
Description
Duplicate contact list entries might
appear on BlackBerry devices.
If organizer data synchronization is turned on for user accounts, and you try to
move the user accounts to a destination BlackBerry Enterprise Server for IBM
Domino, duplicate contact list entries might appear on devices. Permanently
delete the data on the devices and activate the devices again.
The BlackBerry Enterprise Transporter Upgrade the destination BlackBerry Enterprise Server to a version that the
does not support the version of the
BlackBerry Enterprise Transporter supports.
destination BlackBerry Enterprise
Server.
If the version of the source BlackBerry Enterprise Server for Microsoft Exchange is earlier than 5.0, consider the following
information:
Consideration
Description
The BlackBerry Enterprise Transporter
might require more time than expected
to move user accounts to the
destination BlackBerry Enterprise
Server for Microsoft Exchange.
In specific circumstances, if the version of the source BlackBerry Enterprise
Server for Microsoft Exchange is earlier than version 4.1 SP6 MR5, the
BlackBerry Enterprise Transporter might require more time than expected to
move user accounts to the destination MDM domain. Before you try to move the
user accounts, upgrade the source BlackBerry Enterprise Server for Microsoft
Exchange to version 4.1 SP6 MR5 or later.
32
Installation and Administration Guide
Premigration considerations
Moving user accounts to a destination BlackBerry
Enterprise Server 4.0.7
If you move user accounts to a destination BlackBerry Enterprise Server that is version 4.0.7, consider the following
information:
Consideration
Description
Issues might occur if the user ID of a
user account already exists on the
destination BlackBerry Enterprise
Server.
If the user ID of a user account on the source BlackBerry Enterprise Server is the
same as a user ID on the destination BlackBerry Enterprise Server, the user's
BlackBerry device might not work as expected after you migrate the account.
Before you move the user account, delete the user account from the source
BlackBerry Enterprise Server, add it to the BlackBerry Enterprise Server again,
and activate the BlackBerry device.
If the source BlackBerry Enterprise Server is 5.0 or later, consider the following information:
Consideration
Description
Duplicate contact list entries might
appear on BlackBerry devices.
If organizer data synchronization is turned on for user accounts, and you try to
move the user accounts to a destination BlackBerry Enterprise Server for IBM
Domino, duplicate contact list entries might appear on devices. Permanently
delete the data on the devices and activate the devices again.
If the version of the source BlackBerry Enterprise Server for Microsoft Exchange is earlier than 5.0, consider the following
information:
Consideration
Description
The BlackBerry Enterprise Transporter
might require more time than expected
to move user accounts to the
destination BlackBerry Enterprise
Server for Microsoft Exchange.
In specific circumstances, if the version of the source BlackBerry Enterprise
Server for Microsoft Exchange is earlier than version 4.1 SP6 MR5, the
BlackBerry Enterprise Transporter might require more time than expected to
move user accounts to the destination MDM domain. Before you try to move the
user accounts, upgrade the source BlackBerry Enterprise Server for Microsoft
Exchange to version 4.1 SP6 MR5 or later.
If your organization's environment uses the BlackBerry Enterprise Server for Novell GroupWise, consider the following
information:
Consideration
Description
The BlackBerry Enterprise Transporter Upgrade the destination BlackBerry Enterprise Server to a version that the
does not support the version of the
BlackBerry Enterprise Transporter supports.
33
Installation and Administration Guide
Consideration
Premigration considerations
Description
destination BlackBerry Enterprise
Server.
Moving user accounts to a destination BlackBerry
Enterprise Server 4.0 to 4.0.6
If you move user accounts to a destination BlackBerry Enterprise Server that is 4.0 to 4.0.6, consider the following
information:
Consideration
Description
The BlackBerry Enterprise Transporter Upgrade the destination BlackBerry Enterprise Server to a version that the
does not support the version of the
BlackBerry Enterprise Transporter supports.
destination BlackBerry Enterprise
Server.
Issues might occur if the user ID of a
user account already exists on the
destination BlackBerry Enterprise
Server.
If the user ID of a user account on the source BlackBerry Enterprise Server is the
same as a user ID on the destination BlackBerry Enterprise Server, the user's
BlackBerry device might not work as expected after you migrate the account.
Before you move the user account, delete the user account from the source
BlackBerry Enterprise Server, add it to the BlackBerry Enterprise Server again,
and activate the BlackBerry device.
If the source BlackBerry Enterprise Server is 5.0 or later, consider the following information:
Consideration
Description
Duplicate contact list entries might
appear on BlackBerry devices.
If organizer data synchronization is turned on for user accounts, and you try to
move the user accounts to a destination BlackBerry Enterprise Server for IBM
Domino, duplicate contact list entries might appear on devices. Permanently
delete the data on the devices and activate the devices again.
If the version of the source BlackBerry Enterprise Server for Microsoft Exchange is earlier than 5.0, consider the following
information:
Consideration
Description
The BlackBerry Enterprise Transporter In specific circumstances, if the version of the source BlackBerry Enterprise
might require more time than expected Server for Microsoft Exchange is earlier than version 4.1 SP6 MR5, the
to move user accounts to the
BlackBerry Enterprise Transporter might require more time than expected to
move user accounts to the destination MDM domain. Before you try to move the
34
Installation and Administration Guide
Premigration considerations
Consideration
Description
destination BlackBerry Enterprise
Server for Microsoft Exchange.
user accounts, upgrade the source BlackBerry Enterprise Server for Microsoft
Exchange to version 4.1 SP6 MR5 or later.
BlackBerry Device Software compatibility
Moving user accounts to a destination BlackBerry
Enterprise Server 5.0 or later
If you move user accounts to a destination BlackBerry Enterprise Server that is 5.0 or later, consider the following
information:
Consideration
Description
The BlackBerry Enterprise Transporter Upgrade all BlackBerry Enterprise Server instances in the destination MDM
does not support a destination MDM
domain to 5.0 or later.
domain that contains both BlackBerry
Enterprise Server 5.0 or later and a
version of the BlackBerry Enterprise
Server that is earlier than 5.0.
If BlackBerry devices use BlackBerry Device Software 4.3.0, consider the following information:
Consideration
Description
IT policies might not be applied to
BlackBerry devices.
After you move user accounts to the destination BlackBerry Enterprise Server,
the IT policies on the destination BlackBerry Enterprise Server might not be
applied to devices. Before you move the user accounts, update the BlackBerry
Device Software on devices to version 4.5.0 or later. You can also run the
BlackBerry Enterprise Transporter with the Ignore Warnings check box selected,
and activate the user accounts again on the destination BlackBerry Enterprise
Server if the IT policy is not applied to the devices. You are not required to
permanently delete the data on the devices before you activate the user
accounts again.
If devices use BlackBerry Device Software 4.0.2 to 4.2.2, and your organization's environment uses the BlackBerry
Enterprise Server for Novell GroupWise, consider the following information:
35
Installation and Administration Guide
Consideration
Premigration considerations
Description
The BlackBerry Enterprise Transporter Upgrade the destination BlackBerry Enterprise Server to a version that the
does not support the version of the
BlackBerry Enterprise Transporter supports.
destination BlackBerry Enterprise
Server.
If devices use BlackBerry Device Software 4.0.0 to 4.0.1, consider the following information:
Consideration
Description
IT policies might not be applied to
BlackBerry devices.
If the destination BlackBerry Configuration Database does not contain the
optional ITPolicyKeyMapping table, the IT policies on the destination BlackBerry
Enterprise Server are not applied to devices after you move the user accounts.
Before you move the user accounts, update the BlackBerry Device Software on
devices to 4.0.2 or later, or add the ITPolicyKeyMapping table to the destination
BlackBerry Configuration Database. You can also run the BlackBerry Enterprise
Transporter with the Ignore Warnings check box selected, and activate the user
accounts again on the destination BlackBerry Enterprise Server if the IT policy is
not applied to the devices. You are not required to permanently delete the data
on the devices before you activate the user accounts again.
Moving user accounts to a destination BlackBerry
Enterprise Server 4.1.4 to 4.1.7
If you move user accounts to a destination BlackBerry Enterprise Server that is 4.1.4 to 4.1.7, consider the following
information:
Consideration
Description
Issues might occur if the user ID of a
user account already exists on the
destination BlackBerry Enterprise
Server.
If the user ID of a user account on the source BlackBerry Enterprise Server is the
same as a user ID on the destination BlackBerry Enterprise Server, the user's
BlackBerry device might not work as expected after you migrate the account.
Before you move the user account, delete the user account from the source
BlackBerry Enterprise Server, add it to the BlackBerry Enterprise Server again,
and activate the BlackBerry device.
If BlackBerry devices use BlackBerry Device Software version 4.5.0 or later or version 5.0 or later, and your organization's
environment uses the BlackBerry Enterprise Server for IBM Domino, consider the following information:
36
Installation and Administration Guide
Premigration considerations
Consideration
Description
Duplicate contact list entries might
appear on BlackBerry devices.
If organizer data synchronization is turned on for user accounts, and you try to
move the user accounts to a destination BlackBerry Enterprise Server for IBM
Domino, duplicate contact list entries might appear on devices. Permanently
delete the data on the devices and activate the devices again.
If BlackBerry devices use BlackBerry Device Software 4.3.0, consider the following information:
Consideration
Description
IT policies might not be applied to
BlackBerry devices.
After you move user accounts to the destination BlackBerry Enterprise Server,
the IT policies on the destination BlackBerry Enterprise Server might not be
applied to devices. Before you move the user accounts, update the BlackBerry
Device Software on devices to version 4.5.0 or later. You can also run the
BlackBerry Enterprise Transporter with the Ignore Warnings check box selected,
and activate the user accounts again on the destination BlackBerry Enterprise
Server if the IT policy is not applied to the devices. You are not required to
permanently delete the data on the devices before you activate the user
accounts again.
If BlackBerry devices use BlackBerry Device Software 4.0.0 to 4.0.1, consider the following information:
Consideration
Description
IT policies might not be applied to
BlackBerry devices.
If the destination BlackBerry Configuration Database does not contain the
optional ITPolicyKeyMapping table, the IT policies on the destination BlackBerry
Enterprise Server are not applied to devices after you move the user accounts.
Before you move the user accounts, update the BlackBerry Device Software on
devices to 4.0.2 or later, or add the ITPolicyKeyMapping table to the destination
BlackBerry Configuration Database. You can also run the BlackBerry Enterprise
Transporter with the Ignore Warnings check box selected, and activate the user
accounts again on the destination BlackBerry Enterprise Server if the IT policy is
not applied to the devices. You are not required to permanently delete the data
on the devices before you activate the user accounts again.
If your organization's environment uses the BlackBerry Enterprise Server for Novell GroupWise, consider the following
information:
Consideration
Description
The BlackBerry Enterprise Transporter Upgrade the destination BlackBerry Enterprise Server to a version that the
does not support the version of the
BlackBerry Enterprise Transporter supports.
destination BlackBerry Enterprise
Server.
37
Installation and Administration Guide
Premigration considerations
Moving user accounts to a destination BlackBerry
Enterprise Server 4.1 to 4.1.3
If you move user accounts to a destination BlackBerry Enterprise Server that is 4.1 to 4.1.3, consider the following
information:
Consideration
Description
The BlackBerry Enterprise Transporter Upgrade the destination BlackBerry Enterprise Server to a version that the
does not support the version of the
BlackBerry Enterprise Transporter supports.
destination BlackBerry Enterprise
Server.
Issues might occur if the user ID of a
user account already exists on the
destination BlackBerry Enterprise
Server.
If the user ID of a user account on the source BlackBerry Enterprise Server is the
same as a user ID on the destination BlackBerry Enterprise Server, the user's
BlackBerry device might not work as expected after you migrate the account.
Before you move the user account, delete the user account from the source
BlackBerry Enterprise Server, add it to the BlackBerry Enterprise Server again,
and activate the BlackBerry device.
If BlackBerry devices use BlackBerry Device Software version 4.5.0 or later or version 5.0 or later, and your organization's
environment uses the BlackBerry Enterprise Server for IBM Domino, consider the following information:
Consideration
Description
Duplicate contact list entries might
appear on BlackBerry devices.
If organizer data synchronization is turned on for user accounts, and you try to
move the user accounts to a destination BlackBerry Enterprise Server for IBM
Domino, duplicate contact list entries might appear on devices. Permanently
delete the data on the devices and activate the devices again.
If devices use BlackBerry Device Software 4.3.0, consider the following information:
Consideration
Description
IT policies might not be applied to
BlackBerry devices.
After you move user accounts to the destination BlackBerry Enterprise Server,
the IT policies on the destination BlackBerry Enterprise Server might not be
applied to devices. Before you move the user accounts, update the BlackBerry
Device Software on devices to version 4.5.0 or later. You can also run the
BlackBerry Enterprise Transporter with the Ignore Warnings check box selected,
and activate the user accounts again on the destination BlackBerry Enterprise
Server if the IT policy is not applied to the devices. You are not required to
permanently delete the data on the devices before you activate the user
accounts again.
38
Installation and Administration Guide
Premigration considerations
If devices use BlackBerry Device Software 4.0.0 to 4.0.1, consider the following information:
Consideration
Description
IT policies might not be applied to
BlackBerry devices.
If the destination BlackBerry Configuration Database does not contain the
optional ITPolicyKeyMapping table, the IT policies on the destination BlackBerry
Enterprise Server are not applied to devices after you move the user accounts.
Before you move the user accounts, update the BlackBerry Device Software on
devices to 4.0.2 or later, or add the ITPolicyKeyMapping table to the destination
BlackBerry Configuration Database. You can also run the BlackBerry Enterprise
Transporter with the Ignore Warnings check box selected, and activate the user
accounts again on the destination BlackBerry Enterprise Server if the IT policy is
not applied to the devices. You are not required to permanently delete the data
on the devices before you activate the user accounts again.
Moving user accounts to a destination BlackBerry
Enterprise Server 4.0.7
If you move user accounts to a destination BlackBerry Enterprise Server 4.0.7, consider the following information:
Consideration
Description
Issues might occur if the user ID of a
user account already exists on the
destination BlackBerry Enterprise
Server.
If the user ID of a user account on the source BlackBerry Enterprise Server is the
same as a user ID on the destination BlackBerry Enterprise Server, the user's
BlackBerry device might not work as expected after you migrate the account.
Before you move the user account, delete the user account from the source
BlackBerry Enterprise Server, add it to the BlackBerry Enterprise Server again,
and activate the BlackBerry device.
If devices use BlackBerry Device Software 4.5.0 or later or 5.0 or later, and your organization's environment uses the
BlackBerry Enterprise Server for IBM Domino, consider the following information:
Consideration
Description
Duplicate contact list entries might
appear on BlackBerry devices.
If organizer data synchronization is turned on for user accounts, and you try to
move the user accounts to a destination BlackBerry Enterprise Server for IBM
Domino, duplicate contact list entries might appear on devices. Permanently
delete the data on the devices and activate the devices again.
If devices use BlackBerry Device Software 4.3.0, consider the following information:
39
Installation and Administration Guide
Premigration considerations
Consideration
Description
IT policies might not be applied to
BlackBerry devices.
After you move user accounts to the destination BlackBerry Enterprise Server,
the IT policies on the destination BlackBerry Enterprise Server might not be
applied to devices. Before you move the user accounts, update the BlackBerry
Device Software on devices to version 4.5.0 or later. You can also run the
BlackBerry Enterprise Transporter with the Ignore Warnings check box selected,
and activate the user accounts again on the destination BlackBerry Enterprise
Server if the IT policy is not applied to the devices. You are not required to
permanently delete the data on the devices before you activate the user
accounts again.
If devices use BlackBerry Device Software 4.0.0 to 4.0.1, consider the following information:
Consideration
Description
IT policies might not be applied to
BlackBerry devices.
If the destination BlackBerry Configuration Database does not contain the
optional ITPolicyKeyMapping table, the IT policies on the destination BlackBerry
Enterprise Server are not applied to devices after you move the user accounts.
Before you move the user accounts, update the BlackBerry Device Software on
devices to 4.0.2 or later, or add the ITPolicyKeyMapping table to the destination
BlackBerry Configuration Database. You can also run the BlackBerry Enterprise
Transporter with the Ignore Warnings check box selected, and activate the user
accounts again on the destination BlackBerry Enterprise Server if the IT policy is
not applied to the devices. You are not required to permanently delete the data
on the devices before you activate the user accounts again.
If your organization's environment uses the BlackBerry Enterprise Server for Novell GroupWise, consider the following
information:
Consideration
Description
The BlackBerry Enterprise Transporter Upgrade the destination BlackBerry Enterprise Server to a version that the
does not support the version of the
BlackBerry Enterprise Transporter supports.
destination BlackBerry Enterprise
Server.
Moving user accounts to a destination BlackBerry
Enterprise Server 4.0 to 4.0.6
If you move user accounts to a destination BlackBerry Enterprise Server that is 4.0 to 4.0.6, consider the following
information:
40
Installation and Administration Guide
Consideration
Premigration considerations
Description
The BlackBerry Enterprise Transporter Upgrade the destination BlackBerry Enterprise Server to a version that the
does not support the version of the
BlackBerry Enterprise Transporter supports.
destination BlackBerry Enterprise
Server.
Issues might occur if the user ID of a
user account already exists on the
destination BlackBerry Enterprise
Server.
If the user ID of a user account on the source BlackBerry Enterprise Server is the
same as a user ID on the destination BlackBerry Enterprise Server, the user's
BlackBerry device might not work as expected after you migrate the account.
Before you move the user account, delete the user account from the source
BlackBerry Enterprise Server, add it to the BlackBerry Enterprise Server again,
and activate the BlackBerry device.
If devices use BlackBerry Device Software 4.5.0 or later or 5.0 or later, and your organization's environment uses the
BlackBerry Enterprise Server for IBM Domino, consider the following information:
Consideration
Description
Duplicate contact list entries might
appear on BlackBerry devices.
If organizer data synchronization is turned on for user accounts, and you try to
move the user accounts to a destination BlackBerry Enterprise Server for IBM
Domino, duplicate contact list entries might appear on devices. Permanently
delete the data on the devices and activate the devices again.
If devices use BlackBerry Device Software 4.3.0, consider the following information:
Consideration
Description
IT policies might not be applied to
BlackBerry devices.
After you move user accounts to the destination BlackBerry Enterprise Server,
the IT policies on the destination BlackBerry Enterprise Server might not be
applied to devices. Before you move the user accounts, update the BlackBerry
Device Software on devices to version 4.5.0 or later. You can also run the
BlackBerry Enterprise Transporter with the Ignore Warnings check box selected,
and activate the user accounts again on the destination BlackBerry Enterprise
Server if the IT policy is not applied to the devices. You are not required to
permanently delete the data on the devices before you activate the user
accounts again.
If devices use BlackBerry Device Software 4.0.0 to 4.0.1, consider the following information:
Consideration
Description
IT policies might not be applied to
BlackBerry devices.
If the destination BlackBerry Configuration Database does not contain the
optional ITPolicyKeyMapping table, the IT policies on the destination BlackBerry
Enterprise Server are not applied to devices after you move the user accounts.
Before you move the user accounts, update the BlackBerry Device Software on
41
Installation and Administration Guide
Consideration
Premigration considerations
Description
devices to 4.0.2 or later, or add the ITPolicyKeyMapping table to the destination
BlackBerry Configuration Database. You can also run the BlackBerry Enterprise
Transporter with the Ignore Warnings check box selected, and activate the user
accounts again on the destination BlackBerry Enterprise Server if the IT policy is
not applied to the devices. You are not required to permanently delete the data
on the devices before you activate the user accounts again.
Moving user accounts from a BlackBerry
Enterprise Server Express to a BlackBerry
Enterprise Server
Consideration
Description
The BlackBerry Enterprise Transporter The BlackBerry Enterprise Transporter does not support the use of bulk mode
does not support bulk mode when
when moving user accounts from a source BlackBerry Enterprise Server Express
moving user accounts from a
to a destination BlackBerry Enterprise Server.
BlackBerry Enterprise Server Express
to a destination BlackBerry Enterprise
Server.
User accounts with BlackBerry devices
that have been activated using the
BlackBerry Internet Service cannot be
moved to a destination BlackBerry
Enterprise Server.
42
If a user account is associated with a device that was provisioned using the
BlackBerry Internet Service, you cannot move the user account from the source
BlackBerry Enterprise Server Express to the destination BlackBerry Enterprise
Server. The BlackBerry Enterprise Server does not support devices that are
provisioned using the BlackBerry Internet Service.
Installation and Administration Guide
Premigration considerations
Moving user accounts from a BlackBerry
Enterprise Server or BlackBerry
Professional Software to a BlackBerry
Enterprise Server Express
Consideration
Description
The BlackBerry Enterprise Transporter
does not support bulk mode when
moving user accounts from a
BlackBerry Enterprise Server or
BlackBerry Professional Software to a
BlackBerry Enterprise Server Express.
The BlackBerry Enterprise Transporter does not support the use of bulk mode
when moving user accounts from a source BlackBerry Enterprise Server or
BlackBerry Professional Software to a destination BlackBerry Enterprise Server
Express.
By default, the BlackBerry Enterprise
Transporter cannot connect to the
BlackBerry Administration Service of a
BlackBerry Enterprise Server Express.
As a result, the BlackBerry Enterprise
Transporter can move user accounts,
but you cannot assign IT policies or
software configurations to the user
accounts when they are moved, and
you cannot assign the user accounts to
groups when they are moved.
The BlackBerry Enterprise Transporter tries to connect to the BlackBerry
Administration Service of the destination server using port 443, the default port
connection for the BlackBerry Administration Service of the BlackBerry
Enterprise Server. The BlackBerry Administration Service of the BlackBerry
Enterprise Server Express uses port 3443 by default.
If you want to move user accounts to a destination BlackBerry Enterprise Server
Express and assign IT policies, software configurations, and groups to the user
accounts, you must add the following text to the appSettings section of the
EnterpriseTransporter.exe.config file: <add key="basUrl"
value="<BlackBerry_Administration_Server_URL>:
<BlackBerry_Administration_Service_port>"/>
Do not specify http or https for the BlackBerry Administration Service web
address (for example, <add key="basUrl" value="bas.test.org.net:3443"/>).
43
Installation and Administration Guide
Preparing to move user accounts
Preparing to move user
accounts
8
Create the manifest file
The manifest file contains information about the MDM domain instances, default settings, and user accounts that the
BlackBerry Enterprise Transporter requires to run the migration process. The information that you configure in the tool is
saved to the manifest file and used to complete the migration process.
1.
On the computer that hosts the BlackBerry Enterprise Transporter, on the taskbar, click Start > All Programs >
BlackBerry Enterprise Server Resource Kit > BlackBerry Enterprise Transporter > BlackBerry Enterprise
Transporter.
2.
In the Step 1: User Manifest section, click New.
3.
Type a file name.
4.
Click Save.
After you finish: Configure the source and destination instances of the BlackBerry Configuration Database.
Configure the source and destination
instances of the BlackBerry Configuration
Database
To configure the tool for the migration process, you must specify information about the source BlackBerry Configuration
Database and the destination BlackBerry Configuration Database.
Before you begin: Create a manifest file or open a saved manifest file.
1.
44
In the BlackBerry Enterprise Transporter, in the Step 2: BlackBerry Databases section, in the Source Domain
section, click Configure.
Installation and Administration Guide
2.
Preparing to move user accounts
In the Label drop-down list, perform one of the following actions:
•
To configure the information for the source BlackBerry Configuration Database for the first time, click <new>.
•
To choose an existing source BlackBerry Configuration Database, click the appropriate label name.
3.
In the Edit/New section, in the Label field, type a label for the source BlackBerry Configuration Database.
4.
In the SQL Server field, type the FQDN or IP address of the Microsoft SQL Server that hosts the source BlackBerry
Configuration Database.
5.
In the Authentication drop-down list, perform one of the following actions:
•
To use database authentication to access the source BlackBerry Configuration Database, click SQL Server
Authentication. In the User Name and Password fields, type the login information for the database administrator
account that you want the tool to use to access the source BlackBerry Configuration Database.
•
To use Windows authentication to access the source BlackBerry Configuration Database using the login
information of the current database administrator account, click Windows NT Authentication (Current User).
•
To use Windows authentication to access the source BlackBerry Configuration Database using the login
information of a different database administrator account, click Windows NT Authentication (Specify User). In
the User Name and Password fields, type the login information for the database administrator account. The
domain of the specified administrator account must trust the current domain that hosts the BlackBerry Enterprise
Transporter.
If you click Windows NT Authentication (Specify User), the Authentication drop-down list changes to Windows NT
Authentication (Current User) when you open the Configure Database window again.
6.
In the Database field, type the name of the source BlackBerry Configuration Database (for example, BESMgmt).
7.
Click Test Connection.
8.
Click OK.
9.
In the Step 2: BlackBerry Databases section, in the Destination Domain section, click Configure.
10. Repeat steps 2 to 8, specifying the information for the destination BlackBerry Configuration Database.
After you finish: Configure the default settings to apply to the user accounts that you migrate.
Configure the default settings to apply to the
user accounts that you migrate
Before you select the user accounts that you want to migrate, you can configure the default settings for the destination
BlackBerry Enterprise Server, group, IT policy, and software configuration that you want to apply to the user accounts that
you move to the destination MDM domain. Alternatively, you can select the user accounts that you want to move and then
apply different settings to specific user accounts; for more information, see Configure the default settings to apply to
specific user accounts.
45
Installation and Administration Guide
Preparing to move user accounts
If you enable bulk mode and configure custom default settings to apply to individual user accounts, the destination
BlackBerry Administration Service must process the different settings for each user account. As a result, the migration
process might take longer than expected to complete. If you enable bulk mode, it is a best practice to configure a single
default setting to apply to all user accounts. You can modify the IT policy, software configuration, and group assignments
using the BlackBerry Administration Service after the migration is complete. If you want to assign custom default settings
to individual user accounts as part of the migration process, it is a best practice to use live mode.
Before you begin:
• In the destination MDM domain, create the group, IT policy, and software configuration that you want to apply to the
user accounts.
•
Configure the source and destination instances of the BlackBerry Configuration Database.
1.
In the BlackBerry Enterprise Transporter, in the Step 3: Manifest Configuration section, in the Summary section,
click Details.
2.
In the Default Destination Assignments section, in the drop-down lists, click the BlackBerry Enterprise Server, group,
IT policy, and software configuration that you want to apply to the user accounts by default during the migration
process.
3.
Select the Use current defaults for all new entries check box.
4.
Click Done.
To apply different default settings to specific user accounts, clear the Use current defaults for all new entries check box
and see Configure the default settings to apply to specific user accounts.
Using the BlackBerry Enterprise Transporter, you can apply software configurations and IT policies directly to user
accounts. You can also assign user accounts to groups that are associated with existing software configurations and IT
policies. The BlackBerry Administration Service uses preconfigured rules that give priority to user-assigned software
configurations and IT policies over the software configurations and IT policies that you assign to groups. If you want the
group-assigned software configurations and IT policies to take precedence, remove the user-assigned software
configurations and IT policies from the user accounts. For more information about reconciliation rules, see the BlackBerry
Enterprise Server Administration Guide.
Note: If you move user accounts to a destination BlackBerry Enterprise Server 5.0 or later, there might be a delay before
the destination BlackBerry Enterprise Server applies the selected IT policy or group-assigned IT policies to devices. During
this delay, the Default IT policy is applied to the devices.
After you finish: Select the user accounts that you want to move to the destination MDM domain.
46
Installation and Administration Guide
Preparing to move user accounts
Configure the BlackBerry Enterprise
Transporter to send notification email
messages to user accounts
You can configure the BlackBerry Enterprise Transporter to send a notification message to user accounts after the
BlackBerry Enterprise Transporter moves the user accounts to a destination BlackBerry Enterprise Server. You cannot
send a notification message to user accounts when you use the tool in bulk mode.
1.
On the Config menu, click Email Configuration.
2.
In the Email option section, select the Enable check box.
3.
In the SMTP Server Configuration section, type the information for the host SMTP server.
4.
In the Email section, type the information for the notification message.
5.
Click OK.
After you finish: To turn off notification messages, clear the Enable check box.
Configure how long the BlackBerry
Enterprise Transporter tries to open a
connection to the source BlackBerry
Configuration Database and the destination
BlackBerry Configuration Database
When you try to move user accounts, the BlackBerry Enterprise Transporter tries to open a connection to the Microsoft SQL
Server that is used by the source BlackBerry Enterprise Server and the Microsoft SQL Server that is used by the destination
BlackBerry Enterprise Server. By default, the tool tries to open a connection to a Microsoft SQL Server for a timeout period
of 15 seconds, the default value for establishing Microsoft SQL connections. If the timeout period expires and a connection
is not established, the tool stops trying to connect to the Microsoft SQL Server.
47
Installation and Administration Guide
Preparing to move user accounts
You can configure how long you want the tool to try to open a connection to a Microsoft SQL Server.
Before you begin: Create the manifest file and configure the source and destination instances of the BlackBerry
Configuration Database.
1.
On the computer that hosts the BlackBerry Enterprise Transporter, navigate to the EnterpriseTransporter.exe.config
configuration file. By default, the file is located at <drive>:\Program Files (x86)\Research In Motion\BlackBerry
Enterprise Server Resource Kit\BlackBerry Enterprise Transporter. If your computer's operating system uses UAC
and does not permit you to modify the configuration file at this location, open the virtualized copy of the
EnterpriseTransporter.exe.config file in the application data folder for the current user (for example, <drive>\Users
\<user_name>\AppData\Local\VirtualStore\Program Files (x86)\Research In Motion\BlackBerry Enterprise Server
Resource Kit)
2.
In a text editor, open the EnterpriseTransporter.exe.config file.
3.
In the <connectionStrings> section, locate the connection strings for the source BlackBerry Configuration Database
and the destination BlackBerry Configuration Database.
4.
At the end of each connection string (connectionString), after Password=<password> for connections using SQL
authentication or after Integrated Security=<value> for connections using NT authentication, type the following
information: ;Connection Timeout=<timeout_value>, where <timeout_value> is a value in seconds.
For example:
<add name="Label 1"
providerName="System.Data.SqlClient"
connectionString="Data Source=Computer1;Initial Catalog=Database1;User
Id=User1;Password=Password1;Connection Timeout=50" />
5.
Save and close the EnterpriseTransporter.exe.config file.
After you finish: Restart the BlackBerry Enterprise Transporter.
Related information
Create the manifest file, 44
Configure the source and destination instances of the BlackBerry Configuration Database, 44
48
Installation and Administration Guide
Selecting the user accounts to move to the destination MDM domain
Selecting the user accounts to
move to the destination MDM
domain
9
You can select the user accounts that you want to migrate using any of the following methods:
•
Search for and select the user accounts that are associated with a specific MDM domain, BlackBerry Enterprise Server,
group, or IT policy.
•
Specify the email addresses of each user account.
•
Import a CR-delimited, flat text file that contains the email addresses of the user accounts.
•
If you want to run the tool in bulk mode, select a source BlackBerry Enterprise Server; the tool will migrate all of the
users associated with that BlackBerry Enterprise Server.
Live mode: Selecting user accounts to
migrate
Search for and select user accounts to move
You can search for and select user accounts that are associated with a specific MDM domain, BlackBerry Enterprise
Server, group, or IT policy.
Before you begin: Configure the source and destination instances of the BlackBerry Configuration Database.
1.
In the BlackBerry Enterprise Transporter, in the Step 3: Manifest Configuration section, in the Summary section,
click Details.
2.
Click Find Users.
3.
Perform one of the following actions:
49
Installation and Administration Guide
Selecting the user accounts to move to the destination MDM domain
•
To search for user accounts at the global level, select the BlackBerry Domain option.
•
To search for user accounts that are associated with a specific BlackBerry Enterprise Server, select the Server
option. In the drop-down list, click a BlackBerry Enterprise Server.
•
To search for user accounts that are associated with a specific group, select the Group option. In the drop-down
list, click a group.
•
To search for user accounts that are associated with a specific IT policy, select the IT Policy option. In the dropdown list, click an IT policy.
4.
Click Find. To filter the list of available users, type the user name.
5.
Add the user accounts that you want to move.
6.
Click Done.
After you finish: To remove a user account from the list, highlight the user account information and press DELETE.
Import a file with email addresses
Before you begin:
• Configure the source and destination instances of the BlackBerry Configuration Database.
•
Create a CR-delimited flat text file that contains the email addresses of the user accounts that you want to move. Verify
that the user accounts are associated with the source MDM domain.
1.
In the BlackBerry Enterprise Transporter, in the Step 3: Manifest Configuration section, in the Summary section,
click Details.
2.
Click Import Users.
3.
Navigate to the file that contains the list of email addresses.
4.
Click Open.
5.
Click OK.
6.
Click Done.
Add the information for a single user account
You can add the information for a single user account without searching the source BlackBerry Configuration Database for
the information.
Before you begin: Configure the source and destination instances of the BlackBerry Configuration Database.
1.
50
In the BlackBerry Enterprise Transporter, in the Step 3: Manifest Configuration section, in the Summary section,
click Details.
Installation and Administration Guide
Selecting the user accounts to move to the destination MDM domain
2.
In the Email column, double-click the empty cell and type the email address for the user account.
3.
In the Dest Server column, in the drop-down list, click the BlackBerry Enterprise Server that you want to associate
the user account with.
4.
Click Done.
Bulk mode: Selecting user accounts to
migrate
Enable bulk mode to select all user accounts that are
associated with a source BlackBerry Enterprise Server
To move all user accounts that are associated with a source BlackBerry Enterprise Server, you can enable bulk mode. For
more information about bulk mode, see BlackBerry Enterprise Transporter modes.
If you enable bulk mode and configure custom default settings to apply to individual user accounts, the destination
BlackBerry Administration Service must process the different settings for each user account. As a result, the migration
process might take longer than expected to complete. If you enable bulk mode, it is a best practice to configure a single
default setting to apply to all user accounts. You can modify the IT policy, software configuration, and group assignments
using the BlackBerry Administration Service after the migration is complete. If you want to assign custom default settings
to individual user accounts as part of the migration process, it is a best practice to use live mode.
Before you begin: Configure the source and destination instances of the BlackBerry Configuration Database.
1.
In the BlackBerry Enterprise Transporter, in the Step 3: Manifest Configuration section, select the Bulk Server Mode
check box.
2.
In the Summary section, click Details.
3.
In the Bulk Mode section, in the Source Server drop-down list, click the BlackBerry Enterprise Server that the user
accounts you want to move are associated with.
4.
Click Done.
51
Installation and Administration Guide
Selecting the user accounts to move to the destination MDM domain
Configure the default settings to apply to
specific user accounts
After you select the user accounts that you want to move to the destination MDM domain, you can apply different settings
for the destination BlackBerry Enterprise Server, group, IT policy, and software configuration to the user accounts that you
want to move.
If you enable bulk mode and configure custom default settings to apply to individual user accounts, the destination
BlackBerry Administration Service must process the different settings for each user account. As a result, the migration
process might take longer than expected to complete. If you enable bulk mode, it is a best practice to configure a single
default setting to apply to all user accounts. You can modify the IT policy, software configuration, and group assignments
using the BlackBerry Administration Service after the migration is complete. If you want to assign custom default settings
to individual user accounts as part of the migration process, it is a best practice to use live mode.
Before you begin:
• In the destination MDM domain, create the groups, IT policies, and software configurations that you want to apply to
the user accounts.
•
Configure the source and destination instances of the BlackBerry Configuration Database.
•
Before you select the user accounts that you want to move to the destination MDM domain, in the Step 3: Manifest
Configuration section, in the Summary section, click Details. Clear the Use current defaults for all new entries check
box.
•
Select the user accounts that you want to move to the destination MDM domain.
1.
In the BlackBerry Enterprise Transporter, in the Step 3: Manifest Configuration section, in the Summary section,
click Details.
2.
In the Default Destination Assignments section, click the BlackBerry Enterprise Server, group, IT policy, and
software configuration that you want to apply to the user accounts.
3.
Perform one of the following actions:
•
To apply the selected default settings to specific user accounts, select the user accounts. Click Apply to selected.
•
To apply the selected default settings to all user accounts that do not have values for the default settings
specified, click Apply to blank cells.
•
To specify the default settings for a specific user account, configure the values for the Dest Server, Dest Group,
Dest Policy, and Dest SW Config drop-down lists for the user account.
4.
If necessary, repeat steps 2 and 3 to apply different default settings to specific user accounts.
5.
Click Done.
52
Installation and Administration Guide
Selecting the user accounts to move to the destination MDM domain
Using the BlackBerry Enterprise Transporter, you can apply software configurations and IT policies directly to user
accounts. You can also assign user accounts to groups that are associated with existing software configurations and IT
policies. The BlackBerry Administration Service uses preconfigured rules that give priority to user-assigned software
configurations and IT policies over the software configurations and IT policies that you assign to groups. If you want the
group-assigned software configurations and IT policies to take precedence, remove the user-assigned software
configurations and IT policies from the user accounts. For more information about reconciliation rules, see the BlackBerry
Enterprise Server Administration Guide.
Note: If you move user accounts to a destination BlackBerry Enterprise Server 5.0 or later, there might be a delay before
the destination BlackBerry Enterprise Server applies the selected IT policies or group-assigned IT policies to devices.
During this delay, the Default IT policy is applied to the devices.
Related information
Configure the default settings to apply to the user accounts that you migrate, 45
Selecting the user accounts to move to the destination MDM domain, 49
53
Installation and Administration Guide
Moving user accounts
Moving user accounts
10
Preview the migration process
Before you begin the migration process, you can preview the migration to help identify potential issues.
Before you begin: Select the user accounts that you want to move.
1.
In the BlackBerry Enterprise Transporter, in the Step 4: Preview section, click Preview.
2.
On the Report tab, check for warning messages.
3.
Resolve any issues. For more information about potential issues, see Troubleshooting preview errors and
Troubleshooting migration errors.
After you finish: To stop the preview, in the Step 4: Preview section, click Abort.
Move user accounts to a different MDM
domain
To stop the migration process at any time, in the Step 5: Migration section, click Abort. When you click Abort, the
BlackBerry Enterprise Transporter stops after it migrates the batch of user accounts that it is currently processing.
Before you begin:
• Before you use the BlackBerry Enterprise Transporter for the first time, log in to the BlackBerry Administration Service
of the destination MDM domain and verify that you can create a user account, assign a BlackBerry device to the user
account, and activate the device.
•
Preview the migration process and resolve any issues that are identified.
•
Verify that only one instance of the tool is running at a time.
•
If you plan to move the mailboxes that are associated with user accounts, move the mailboxes before you migrate the
user accounts.
•
Move the user accounts when the associated devices are on, and are in a wireless coverage area.
54
Installation and Administration Guide
Moving user accounts
•
To move the WLAN data for user accounts, verify that both the source MDM domain and the destination MDM domain
are version 4.1.2 or later. WLAN configurations must be the same on both the source and destination domain. If the
WLAN configurations are not the same, the user accounts are moved with the WLAN settings from the source domain.
•
Verify that the destination BlackBerry Administration Service is running. If the destination BlackBerry Administration
Service is not running while you are moving user accounts, the default assignments for groups, IT policies, and software
configurations might not be applied.
1.
In the BlackBerry Enterprise Transporter, in the Step 3: Manifest Configuration section, perform any of the following
actions:
•
If you want the destination BlackBerry Enterprise Server to synchronize the organizer data for user accounts
immediately after the migration process completes, select the Trigger SlowSync check box.
If you plan to migrate a large number of users, this action might have an unexpected performance impact on your
organization's messaging server and BlackBerry Enterprise Server environment. It is a best practice to use this
option when you move user accounts during low usage periods. If you do not select this option, the destination
BlackBerry Enterprise Server synchronizes the organizer data for the user accounts at a regularly scheduled
interval.
•
To move the WLAN data for user accounts, select the Migrate WLAN check box.
2.
In the Step 5: Migration section, if you want to ignore validation warning messages, select the Ignore Warnings check
box.
3.
In the Step 5: Migration section, click Migrate.
4.
On the Console tab, view the success and warning messages.
To copy all the success and warning messages to the clipboard, on the Edit menu, click Copy Console to Clipboard.
After you finish: To verify that the migration process completed successfully, search for the user accounts in the
destination BlackBerry Administration Service. Verify that the user accounts are assigned to the correct BlackBerry
Enterprise Server, group, IT policy, and software configuration.
Note: If you move user accounts to a destination BlackBerry Enterprise Server 5.0 or later, there might be a delay before
the destination BlackBerry Enterprise Server applies the selected IT policies or group-assigned IT policies to devices.
During this delay, the Default IT policy is applied to the devices.
View the latest BlackBerry Enterprise
Transporter log file
You can view the latest BlackBerry Enterprise Transporter log file to verify that user accounts were migrated or to
troubleshoot migration issues.
55
Installation and Administration Guide
Moving user accounts
In the BlackBerry Enterprise Transporter, on the Help menu, click View Log.
By default, the log files are located at <drive>:\Users\<user_name>\AppData\Roaming\Research In Motion\BlackBerry
Enterprise Transporter\Logs.
56
Installation and Administration Guide
Running the BlackBerry Enterprise Transporter from the command prompt
Running the BlackBerry
Enterprise Transporter from the
command prompt
11
You can preview or run a user migration using the command prompt. It is a best practice to configure the manifest file that
is required for migration using the BlackBerry Enterprise Transporter UI. You can then reference the manifest file when you
type the commands to run the BlackBerry Enterprise Transporter from the command prompt.
Preview the migration process using the
command prompt
Before you begin: Create and configure a manifest file. You can create and configure a manifest file using the sample
manifest file that is included in the BlackBerry Enterprise Transporter installation files, or by using the BlackBerry
Enterprise Transporter user interface. It is a best practice to create and configure the manifest file using the user interface.
1.
On the computer that hosts the BlackBerry Enterprise Transporter, at the command prompt, navigate to <drive>:/
Program Files (x86)/Research in Motion/BlackBerry Resource Kit/BlackBerry Enterprise Transporter <version>.
2.
Type enterprisetransporter /console /preview and any of the following parameters:
Item
Description
/basauthtype <type>
This parameter specifies which of the following options the tool uses to
authenticate with the BlackBerry Administration Service:
•
ad_auth: use Microsoft Active Directory authentication; you must also specify
the /basdomain parameter.
•
bas_auth: use BlackBerry Administration Service authentication; you must
also specify the /basusername and /baspassword parameters.
•
mailbox_auth: use mailbox authentication (IBM Domino environment only)
If you do not specify an authentication type, by default, the tool uses BlackBerry
Administration Service authentication (bas_auth).
57
Installation and Administration Guide
Running the BlackBerry Enterprise Transporter from the command prompt
Item
Description
/basdomain <domain>
This parameter specifies the Microsoft Active Directory domain for the BlackBerry
Administration Service.
Use this parameter when you specify /basauthtype ad_auth.
/basusername <user_name>
This parameter specifies the user name of the administrator account that the tool
uses to authenticate with the BlackBerry Administration Service when it uses
BlackBerry Administration Service authentication.
Use this parameter when you specify /basauthtype bas_auth.
If you use this parameter, you must also specify /baspassword <password>.
/baspassword <password>
This parameter specifies the password of the administrator account that the tool
uses to authenticate with the BlackBerry Administration Service when it uses
BlackBerry Administration Service authentication.
Use this parameter when you specify /basauthtype bas_auth.
If you use this parameter, you must also specify a value for the /basusername
parameter.
/dominoid <drive>:<file_path>
This parameter specifies the path to the user.id file.
This parameter is required in a BlackBerry Enterprise Server for IBM Domino
environment only.
/dominopassword <password>
This parameter specifies the password that the BlackBerry Enterprise Transporter
uses for the user.id file.
This parameter is required in a BlackBerry Enterprise Server for IBM Domino
environment only.
/manifestPath
<drive>:<file_path>
This parameter specifies the path to the manifest file. If you do not specify a path,
the tool uses the manifest.xml file that is in the folder that the tool is installed in. If
the file path contains spaces, enclose the file path in quotation marks ( " " ).
Example: Preview the migration process using BlackBerry Administration Service authentication
enterprisetransporter /console /preview /basauthtype bas_auth /basusername admin /baspassword password /
manifestPath "C:\Users\besadmin\Desktop\ET manifest files"
Example: Preview the migration process using Active Directory authentication
enterprisetransporter /console /preview /basauthtype ad_auth /basdomain domain1.testnet.net /manifestPath
"C:\Users\besadmin\Desktop\ET manifest files"
After you finish: In a Microsoft Exchange messaging environment, to stop the preview migration process, press CTRL
+BREAK. To shut down the BlackBerry Enterprise Transporter, press CTRL+C.
58
Installation and Administration Guide
Running the BlackBerry Enterprise Transporter from the command prompt
Move user accounts to a different MDM
domain using the command prompt
Before you begin: Create and configure a manifest file. You can create and configure a manifest file using the sample
manifest file that is included in the BlackBerry Enterprise Transporter installation files, or by using the BlackBerry
Enterprise Transporter user interface. It is a best practice to create and configure the manifest file using the user interface.
1.
On the computer that hosts the BlackBerry Enterprise Transporter, at the command prompt, navigate to <drive>:/
Program Files (x86)/Research in Motion/BlackBerry Resource Kit/BlackBerry Enterprise Transporter <version>.
2.
Type enterprisetransporter /console /execute and any of the following optional parameters:
Item
Description
/basauthtype <type>
This parameter specifies which of the following options the tool uses to
authenticate with the BlackBerry Administration Service:
•
ad_auth: use Microsoft Active Directory authentication; you must also specify
the /basdomain parameter.
•
bas_auth: use BlackBerry Administration Service authentication; you must
also specify the /basusername and /baspassword parameters.
•
mailbox_auth: use mailbox authentication (IBM Domino environment only)
If you do not specify an authentication type, by default, the tool uses BlackBerry
Administration Service authentication (bas_auth).
/basdomain <domain>
This parameter specifies the Microsoft Active Directory domain for the BlackBerry
Administration Service.
Use this parameter when you specify /basauthtype ad_auth.
/basusername <user_name>
This parameter specifies the user name of the administrator account that the tool
uses to authenticate with the BlackBerry Administration Service when it uses
BlackBerry Administration Service authentication.
Use this parameter when you specify /basauthtype bas_auth.
If you use this parameter, you must also specify /baspassword <password>.
/baspassword <password>
This parameter specifies the password of the administrator account that the tool
uses to authenticate with the BlackBerry Administration Service when it uses
BlackBerry Administration Service authentication.
Use this parameter when you specify /basauthtype bas_auth.
59
Installation and Administration Guide
Item
Running the BlackBerry Enterprise Transporter from the command prompt
Description
If you use this parameter, you must also specify a value for the /basusername
parameter.
/dominoid <drive>:<file_path>
This parameter specifies the path to the user.id file.
This parameter is required in a BlackBerry Enterprise Server for IBM Domino
environment only.
/dominopassword <password>
This parameter specifies the password that the BlackBerry Enterprise Transporter
uses for the user.id file.
This parameter is required in a BlackBerry Enterprise Server for IBM Domino
environment only.
/manifestPath
<drive>:<file_path>
This parameter specifies the path to the manifest file. If you do not specify a path,
the tool uses the manifest.xml file that is in the folder that the tool is installed in. If
the file path contains spaces, enclose the file path in quotation marks ( " " ).
Example: Preview the migration process using BlackBerry Administration Service authentication
enterprisetransporter /console /execute /basauthtype bas_auth /basusername admin /baspassword password /
manifestPath "C:\Users\besadmin\Desktop\ET manifest files"
Example: Preview the migration process using Active Directory authentication
enterprisetransporter /console /execute /basauthtype ad_auth /basdomain domain1.testnet.net /manifestPath
"C:\Users\besadmin\Desktop\ET manifest files"
After you finish: In a Microsoft Exchange messaging environment, to abort the migration process, press CTRL+BREAK. To
shut down the BlackBerry Enterprise Transporter, press CTRL+C.
To verify that the migration process completed, search for the user accounts in the destination BlackBerry Administration
Service. Verify that the user accounts are assigned to the correct BlackBerry Enterprise Server instance, group, IT policy,
and software configuration.
Note: If you move user accounts to a destination BlackBerry Enterprise Server 5.0 or later, there might be a delay before
the destination BlackBerry Enterprise Server applies the selected IT policies or group-assigned IT policies to devices.
During this delay, the Default IT policy is applied to the devices.
60
Installation and Administration Guide
Return user accounts to the source MDM domain
Return user accounts to the
source MDM domain
12
To return user accounts to the source MDM domain, you must run the migration process a second time. You must set the
former destination MDM domain as the source domain, and the former source MDM domain as the destination domain.
Before you begin: Back up the source BlackBerry Configuration Database and destination BlackBerry Configuration
Database.
1.
In the BlackBerry Enterprise Transporter, in the Step 2: BlackBerry Databases section, in the Source Domain
section, click Configure.
2.
In the Label drop-down list, click the label for the former destination BlackBerry Configuration Database.
3.
Click OK.
4.
In the Step 2: BlackBerry Databases section, in the Destination Domain section, click Configure.
5.
In the Label drop-down list, click the label for the former source BlackBerry Configuration Database.
6.
Click OK.
7.
In the Step 3: Manifest Configuration section, in the Summary section, click Details.
8.
Change the list of user accounts to the user accounts that you want to return to the source BlackBerry Configuration
Database.
9.
Click Done.
10. Preview the migration process. Resolve any issues.
11. Move the user accounts.
61
Installation and Administration Guide
Troubleshooting
Troubleshooting
13
Configuration errors and warnings
The BlackBerry Enterprise Transporter cannot connect
to the BlackBerry Administration Service
Possible cause
If you configured to use a proxy server by default, the BlackBerry Enterprise Transporter might not be able to connect to
the BlackBerry Administration Service.
Possible solution
To configure the BlackBerry Enterprise Transporter to override the proxy server that you configured, in the
EnterpriseTransporter.exe.config file, add the following text inside the <configuration> tags:
<system.net>
<defaultProxy>
<proxy usesystemdefault = "false" />
</defaultProxy>
</system.net>
Configuration file error
Description
This message appears when the BlackBerry Enterprise Transporter configuration file (EnterpriseTransporter.exe.config)
contains invalid information.
Possible solution
Try performing the following actions:
•
62
Read the additional information that is displayed with the error message to determine the problem.
Installation and Administration Guide
•
Troubleshooting
Use the sample configuration file located in the BlackBerry Enterprise Transporter installation files to try to identify the
issue with the configuration file that you are using.
XML Manifest Failed to Load
Description
This message appears when the BlackBerry Enterprise Transporter cannot load the manifest file that you specified.
Possible solution
Try performing one of the following actions:
•
Verify that the manifest file is in the location that you specified.
•
Create and configure a new manifest file.
Destination 5.0 server found but unable to find BUA
installation
Description
This message appears when you try to move user accounts to a destination BlackBerry Enterprise Server 5.0 and the
BlackBerry Enterprise Transporter cannot detect the BlackBerry Enterprise Server User Administration Tool. The
BlackBerry Enterprise Transporter uses the BlackBerry Enterprise Server User Administration Tool to assign default
settings for groups, IT policies, and software configurations to the user accounts that you want to move to the destination
BlackBerry Enterprise Server.
Possible solution
Install a compatible version of the BlackBerry Enterprise Server User Administration Tool on the computer that hosts the
BlackBerry Enterprise Transporter. The BlackBerry Enterprise Server User Administration Tool is not required if the
destination BlackBerry Enterprise Server is 5.0 SP1 or later.
63
Installation and Administration Guide
Troubleshooting
One or more user accounts do not have a Destination
Server set
Description
This message appears if you did not select a destination BlackBerry Enterprise Server for one or more user accounts in the
User Manifest Configuration window.
Possible solution
For more information about configuring the settings for user accounts that you want to move, see Configure the default
settings that apply to specific user accounts.
Troubleshooting preview errors
ERROR: Destination contains servers older than 5.0
Description
This message appears if BlackBerry Enterprise Server 5.0.x and an earlier version of the BlackBerry Enterprise Server are
both present in the destination MDM domain.
Possible solution
Upgrade all BlackBerry Enterprise Server instances in the destination MDM domain to 5.0 or later, and then run the
BlackBerry Enterprise Transporter.
Application error messages
Failed to initialize <source/destination> database connection
Description
This message appears when the BlackBerry Enterprise Transporter cannot connect to the specified database, or the
database is not a valid BlackBerry Configuration Database.
64
Installation and Administration Guide
Troubleshooting
Possible solution
Try performing the following actions:
•
Verify that the server that hosts the BlackBerry Configuration Database is running and that the BlackBerry
Configuration Database is running.
•
Verify that the information that you specified for the BlackBerry Configuration Database is correct.
•
Verify that the authentication credentials that you specified are correct, and that the account you configured the tool to
use has the required database permissions.
No users found in manifest, shutting down
Description
This message appears when the BlackBerry Enterprise Transporter finds no user accounts to move.
Possible solution
Try performing one of the following actions:
•
If you are running the BlackBerry Enterprise Transporter in live mode (you did not select the Bulk Server Mode check
box), check the manifest file to verify that one or more user accounts are defined in the Users section. By default, the
manifest file is located at <drive>:\Users\<user_name>\AppData\Roaming\Research In Motion\BlackBerry Enterprise
Transporter\Manifests.
•
If you are running the BlackBerry Enterprise Transporter in bulk mode (you selected the Bulk Server Mode check box),
verify the names of the database servers that host the BlackBerry Configuration Database in the source MDM domain
and the destination MDM domain, and verify that the names and server information are configured correctly in the
manifest file. By default, the manifest file is located at <drive>:\Users\<user_name>\AppData\Roaming\Research In
Motion\BlackBerry Enterprise Transporter\Manifests.
Manifest Validation Error
Description
This message appears when the manifest file does not conform to the manifest.xsd schema.
Possible solution
Determine the line or element of the schema error and correct it. You can compare the manifest file to the sample manifest
file that is included in the BlackBerry Enterprise Transporter installation files. By default, the manifest file is located at
<drive>:\Users\<user_name>\AppData\Roaming\Research In Motion\BlackBerry Enterprise Transporter\Manifests.
65
Installation and Administration Guide
Troubleshooting
User validation error messages
No users have been activated on destination server - user may lose some
device functionality
Description
This message appears when you try to move user accounts to a destination BlackBerry Enterprise Server that has never
had user accounts added to it, and has never had BlackBerry devices activated.
Possible solution
Perform one of the following actions:
•
Use the BlackBerry Administration Service to activate the user accounts again.
•
Use the BlackBerry Administration Service to remove the user accounts from the BlackBerry Enterprise Server, then
create and activate a test user account. Try migrating user accounts to the destination BlackBerry Enterprise Server
again.
Destination server does not support the current encryption scheme
Description
This message appears when the destination BlackBerry Enterprise Server does not support the encryption scheme that is
used by the source BlackBerry Enterprise Server. For example, the source BlackBerry Enterprise Server uses Triple DES
and the destination BlackBerry Enterprise Server uses Triple DES and AES.
Possible solution
Configure the source BlackBerry Enterprise Server and the destination BlackBerry Enterprise Server to use the same
encryption algorithm and try to move the user accounts again.
User not found in source
Description
This message appears when the BlackBerry Enterprise Transporter cannot find a user record in the source MDM domain
with the email address that is specified in the manifest file.
Possible solution
Try performing the following actions:
66
Installation and Administration Guide
Troubleshooting
•
Verify that the source MDM domain and the email address of the user account are correct in the manifest file. By
default, the manifest file is located at <drive>:\Users\<user_name>\AppData\Roaming\Research In Motion\BlackBerry
Enterprise Transporter\Manifests.
•
Verify that the user account exists on one of the BlackBerry Enterprise Server instances in the source MDM domain.
User already exists in destination
Description
This message appears when the BlackBerry Enterprise Transporter finds that a user account already exists in the
destination MDM domain with the email address of a user account that is specified in the manifest file.
Possible solution
Try performing the following actions:
•
Verify that the destination MDM domain is correct in the manifest file. By default, the manifest file is located at <drive>:
\Users\<user_name>\AppData\Roaming\Research In Motion\BlackBerry Enterprise Transporter\Manifests.
•
Verify that the email address of the user account is typed correctly in the manifest file.
SrcRoutingInfo is null or empty
Description
This message appears when there is no routing information for the user account in the source BlackBerry Configuration
Database. The user account might not be active. The user's BlackBerry device might not have been updated with the
destination routing information during the migration process.
Possible solution
Try performing the following actions:
•
Activate the user account on the source BlackBerry Enterprise Server again, then try to move the user account to the
destination BlackBerry Enterprise Server.
•
Run the BlackBerry Enterprise Transporter with the Ignore warnings option selected and activate the user account on
the destination BlackBerry Enterprise Server after the migration process completes. You do not need to delete all of the
data on the device before you try to activate the user account.
The UserId cannot be preserved
Description
This message appears when the BlackBerry Enterprise Transporter cannot preserve the user ID that the BlackBerry
Enterprise Server sends to the BlackBerry device because the user ID is already in use in the destination MDM domain. The
user ID must be preserved so that the device can work correctly.
67
Installation and Administration Guide
Troubleshooting
This message appears only if the BlackBerry Enterprise Server instances in the destination MDM domain are not version
5.0 and later.
Possible solution
Manually remove, re-add, and reactivate the user accounts on the source BlackBerry Enterprise Server to generate a new
user ID, then try to migrate the user account again.
<email_address> Skipping WLAN configuration due to empty
WLANBaseConfigSet: ConfigName
Description
This message appears when the BlackBerry Enterprise Transporter does not move the WLAN information for a user
account because the WLAN base configuration set is empty.
Possible solution
After the migration process completes, configure the WLAN base configuration set on the destination BlackBerry
Enterprise Server using the BlackBerry Administration Service.
<email_address> Unable to parse device version string: "Version found in
database"
Description
This message appears when the BlackBerry Enterprise Transporter cannot process the version of the BlackBerry Device
Software that is associated with a user account in the BlackBerry Configuration Database. The BlackBerry Device Software
version might not exist in the BlackBerry Configuration Database.
Possible solution
Move the user account to the destination BlackBerry Enterprise Server with the Ignore Warnings option selected.
<email_address> Failed to load UserConfig row for user
Description
This message appears when the BlackBerry Enterprise Transporter cannot load the user account information from the
UserConfig table in the source BlackBerry Configuration Database.
Possible solution
To determine the cause of the issue, check the BlackBerry Enterprise Transporter log file for Microsoft SQL Server errors. If
possible, correct the problem and try to move the user account again.
68
Installation and Administration Guide
Troubleshooting
<email_address> Failed to load PIM Sync data for user
Description
This message appears when the BlackBerry Enterprise Transporter cannot load the user account information from the
organizer synchronization tables in the source BlackBerry Configuration Database.
Possible solution
Check the BlackBerry Enterprise Transporter log file for Microsoft SQL Server errors to identify which tables in the
BlackBerry Configuration Database were affected. If possible, correct the problem and try to move the user account again.
<email_address> Incomplete SWITCH_SERVICE command data
Description
This message appears when the BlackBerry Enterprise Transporter cannot queue a switch service command for the user
account.
Possible solution
Try performing the following actions:
•
Review the BlackBerry Messaging Agent log file for the destination BlackBerry Enterprise Server to determine why the
BlackBerry Enterprise Server did not queue a switch service command automatically.
•
Verify that the routing information for the user account on the source and destination server is not blank or null, and
that the configuration ID for the user account on the destination server is greater than 0.
User account status: Skipped
On the Report tab, this status message appears for user accounts that were previously moved to the destination BlackBerry
Enterprise Server.
User validation warning messages
Invalid PIN
Description
This message appears when the user account has an invalid, null, or 0 PIN, which indicates that the user account is not
active. The BlackBerry Enterprise Transporter can move the user account, but IT administration commands do not
complete, and you must activate the user account after the migration to the destination BlackBerry Enterprise Server.
69
Installation and Administration Guide
Troubleshooting
Possible solution
Try performing one of the following actions:
•
Activate the user account on the source BlackBerry Enterprise Server, then retry the migration.
•
Run the migration process with Ignore warnings selected. Then activate the user account on the destination
BlackBerry Enterprise Server after the migration process completes.
User status on the source BlackBerry Enterprise Server instance is not
"Running"
Description
The status of the user account on the source BlackBerry Enterprise Server indicates that the user account is not currently
active.
Possible solution
Try performing one of the following actions:
•
Activate the user account on the source BlackBerry Enterprise Server, then retry the migration.
•
Run the migration process with Ignore warnings selected, then activate the user account on the destination BlackBerry
Enterprise Server after the migration process completes. You do not need to delete the data on the device that is
associated with the user account.
Troubleshooting migration errors
When you troubleshoot migration issues, you can review the migration job history in the BlackBerry Enterprise Transporter
log file.
User migration failed messages
VALIDATION / FAILED
Description
This message appears when the BlackBerry Enterprise Transporter cannot validate the user account.
Possible solution
See User validation error messages and User validation warning messages.
70
Installation and Administration Guide
Troubleshooting
MIGRATION / FAILED
Description
This message appears when the BlackBerry Enterprise Transporter cannot add the data for the user account to the
destination BlackBerry Configuration Database.
Possible solution
Try performing the following actions:
•
Check the log file for the BlackBerry Enterprise Transporter for details about the error. By default, the log files are
located at <drive>:\Users\<user_name>\AppData\Roaming\Research In Motion\BlackBerry Enterprise Transporter
\Logs.
•
Verify that the destination BlackBerry Configuration Database is online.
•
Verify that you have the required permissions to insert records into the destination BlackBerry Configuration Database.
SWITCH_SERVICE / FAILED
Description
This message appears when the destination BlackBerry Policy Service reports an error after it tries to send the Switch
Service command to the BlackBerry device.
Possible solution
Check the log file for the BlackBerry Policy Service to determine the cause of the error. By default, the log files for the
BlackBerry Policy Service are located at <drive>:\Program Files (x86)\Research In Motion\BlackBerry Enterprise Server
\Logs on the computer that hosts the BlackBerry Policy Service.
Check the device's event log to determine the cause of the error. For more information about accessing the event log, visit
www.blackberry.com/go/kbhelp to read KB29215.
User migration completed with warning messages
SET_IT_POLICY / FAILED
Description
This message appears when the IT policy sent from the destination BlackBerry Enterprise Server is not successfully applied
to the BlackBerry device after the migration process completes.
71
Installation and Administration Guide
Troubleshooting
Possible solution
Try performing the following actions:
•
Manually resend the IT policy from the destination BlackBerry Enterprise Server.
•
If you still cannot apply the IT policy, reactivate the device on the destination BlackBerry Enterprise Server. You do not
need to delete the data from the device.
•
If you still cannot apply the IT policy, delete the data from the device. Reactivate the device on the destination
BlackBerry Enterprise Server.
Any other task / FAILED or NOT_STARTED
Description
This message appears if some other task failed but did not stop the migration process.
Possible solution
Check the BlackBerry Enterprise Transporter log file for details. By default, the log files are located at <drive>:\Users
\<user_name>\AppData\Roaming\Research In Motion\BlackBerry Enterprise Transporter\Logs.
User migration pending error messages
SWITCH_SERVICE or SET_IT_POLICY / PENDING
Description
These messages appear when the BlackBerry Policy Service sends the Switch Service command or the Set IT Policy
command to the BlackBerry device, but the command does not complete. The device might be turned off, outside of a
wireless coverage area, or inactive.
Possible solution
Verify that the device is turned on and in a wireless coverage area. Use the BlackBerry Administration Service to reactivate
the device and send the IT administration commands again.
72
Installation and Administration Guide
Troubleshooting
IT policy error messages
Last IT Policy Command Failed or Pending
Description
These messages appear when the last Set IT Policy command that the source BlackBerry Enterprise Server sent to the
BlackBerry device failed or is still in progress. If you migrate the user account in this state, an IT administration command
that is sent from the destination BlackBerry Enterprise Server might fail.
Possible solution
Try performing one of the following actions:
•
Wait for the source Set IT Policy command to complete, or resend the Set IT Policy command if the previous command
failed.
•
Run the migration process with Ignore warnings selected. If the migration process completes and the the IT
administration command fails, use the BlackBerry Administration Service to activate the user account. You do not need
to delete the data on the device.
IT Policy might not be applied successfully to a BlackBerry device
Description
This message appears when the BlackBerry Enterprise Transporter detects a condition where the destination BlackBerry
Enterprise Server might not be able to apply a new IT policy to the BlackBerry device that is associated with a user account.
This can happen if the BlackBerry Device Software is earlier than version 4.0.2 and the destination BlackBerry
Configuration Database does not contain the optional ITPolicyKeyMapping table.
Possible solution
Try performing the following actions:
•
If possible, upgrade the BlackBerry Device Software to version 4.0.2.x or later.
•
Add the ITPolicyKeyMapping table to the destination BlackBerry Configuration Database before you try to migrate a
user account if the BlackBerry Device Software is earlier than version 4.0.2.
•
If the Set IT Policy command fails, run the BlackBerry Enterprise Transporter with Ignore warnings selected. Then
reactivate the user account on the destination BlackBerry Enterprise Server after the migration process completes. You
do not need to delete the data on the device.
73
Installation and Administration Guide
Troubleshooting
User account status: Skipped
On the Report tab, this status message appears for user accounts that were previously moved to the destination BlackBerry
Enterprise Server.
User account status:
MigrationSkippedDueToValidationFailure
Description
On the Report tab, this status message appears for user accounts that were not moved to the destination BlackBerry
Enterprise Server because the BlackBerry Enterprise Transporter could not validate the user accounts.
Possible solution
Use the information that appears on the Report tab to resolve the issue.
74
Installation and Administration Guide
Port information for the BlackBerry Enterprise Server Resource Kit tools
Port information for the
BlackBerry Enterprise Server
Resource Kit tools
14
Port information for tools that connect to
the BlackBerry Configuration Database
Tool
Connection type
Default port number
BlackBerry Application Reporting Tool
TCP
1433
BlackBerry Domain Administration History Reporting Tool
TCP
1433
BlackBerry Enterprise Transporter
TCP
1433
BlackBerry IT Policy Import and Export Tool
TCP
1433
BlackBerry Message Receipt Confirmation Tool
TCP
1433
75
Installation and Administration Guide
Port information for the BlackBerry Enterprise Server Resource Kit tools
Port information for tools that connect to
the BlackBerry Administration Service,
BlackBerry Administration API, and
BlackBerry Web Services
Tool
Connection type
Default port number
BlackBerry Enterprise Server User Administration Tool
TCP
•
BlackBerry Enterprise
Server: 443
•
BlackBerry Enterprise
Server Express: 8443
•
BlackBerry Enterprise
Server: 443
•
BlackBerry Enterprise
Server Express: 8443
•
BlackBerry Enterprise
Server: 443
•
BlackBerry Enterprise
Server Express: 8443
BlackBerry Enterprise Transporter
BlackBerry Directory Sync Tool
76
TCP
TCP
Installation and Administration Guide
Port information for the BlackBerry Enterprise Server Resource Kit tools
Port information for the BlackBerry System
Log Monitoring and Reporting Tool
Action
Connection type
Default port number
Listens for packets
UDP
514
Sends messages over SMTP
TCP
25
Port information for the BlackBerry
Message Receipt Confirmation Tool
Action
Connection type
Default port number
Sends messages
MAPI
125
77
Installation and Administration Guide
Glossary
Glossary
15
AES
Advanced Encryption Standard
API
application programming interface
CAL
A BlackBerry Client Access License (BlackBerry CAL) limits how many users you can add to a
BlackBerry Enterprise Server.
CR
carriage return
DES
Data Encryption Standard
FQDN
fully qualified domain name
IBM DB2 UDB
IBM DB2 Universal Database
IP
Internet Protocol
IP address
An Internet Protocol (IP) address is an identification number that each computer or mobile
device uses when it sends or receives information over a network, such as the Internet. This
identification number identifies the specific computer or mobile device on the network.
MDM domain
An MDM domain consists of a BlackBerry database and any BlackBerry services or components
that are associated with it. An MDM domain can refer to any of the following environments:
•
BlackBerry Enterprise Server domain: A BlackBerry Configuration Database and any
BlackBerry Enterprise Server components that are associated with it
•
BlackBerry Enterprise Server Express domain: A BlackBerry Configuration Database and any
BlackBerry Enterprise Server Express components that are associated with it
•
BlackBerry Device Service domain: A BlackBerry Configuration Database and any
BlackBerry Device Service components that are associated with it
•
Universal Device Service domain: A Management Database and any Universal Device
Service components that are associated with it
SRP
Server Routing Protocol
Triple DES
Triple Data Encryption Standard
WLAN
wireless local area network
78
Installation and Administration Guide
Legal notice
Legal notice
16
©2013 BlackBerry. All rights reserved. BlackBerry® and related trademarks, names, and logos are the property of
BlackBerry Limited and are registered and/or used in the U.S. and countries around the world.
IBM, DB2, Domino, Lotus, and Notes are trademarks of International Business Machines Corporation. Microsoft, Active
Directory, SQL Server, Windows, and Windows Server are trademarks of Microsoft Corporation. All other trademarks are the
property of their respective owners.
This documentation including all documentation incorporated by reference herein such as documentation provided or
made available at www.blackberry.com/go/docs is provided or made accessible "AS IS" and "AS AVAILABLE" and without
condition, endorsement, guarantee, representation, or warranty of any kind by BlackBerry Limited and its affiliated
companies ("BlackBerry") and BlackBerry assumes no responsibility for any typographical, technical, or other
inaccuracies, errors, or omissions in this documentation. In order to protect BlackBerry proprietary and confidential
information and/or trade secrets, this documentation may describe some aspects of BlackBerry technology in generalized
terms. BlackBerry reserves the right to periodically change information that is contained in this documentation; however,
BlackBerry makes no commitment to provide any such changes, updates, enhancements, or other additions to this
documentation to you in a timely manner or at all.
This documentation might contain references to third-party sources of information, hardware or software, products or
services including components and content such as content protected by copyright and/or third-party websites
(collectively the "Third Party Products and Services"). BlackBerry does not control, and is not responsible for, any Third
Party Products and Services including, without limitation the content, accuracy, copyright compliance, compatibility,
performance, trustworthiness, legality, decency, links, or any other aspect of Third Party Products and Services. The
inclusion of a reference to Third Party Products and Services in this documentation does not imply endorsement by
BlackBerry of the Third Party Products and Services or the third party in any way.
EXCEPT TO THE EXTENT SPECIFICALLY PROHIBITED BY APPLICABLE LAW IN YOUR JURISDICTION, ALL CONDITIONS,
ENDORSEMENTS, GUARANTEES, REPRESENTATIONS, OR WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING WITHOUT LIMITATION, ANY CONDITIONS, ENDORSEMENTS, GUARANTEES, REPRESENTATIONS OR
WARRANTIES OF DURABILITY, FITNESS FOR A PARTICULAR PURPOSE OR USE, MERCHANTABILITY, MERCHANTABLE
QUALITY, NON-INFRINGEMENT, SATISFACTORY QUALITY, OR TITLE, OR ARISING FROM A STATUTE OR CUSTOM OR A
COURSE OF DEALING OR USAGE OF TRADE, OR RELATED TO THE DOCUMENTATION OR ITS USE, OR PERFORMANCE
OR NON-PERFORMANCE OF ANY SOFTWARE, HARDWARE, SERVICE, OR ANY THIRD PARTY PRODUCTS AND SERVICES
REFERENCED HEREIN, ARE HEREBY EXCLUDED. YOU MAY ALSO HAVE OTHER RIGHTS THAT VARY BY STATE OR
PROVINCE. SOME JURISDICTIONS MAY NOT ALLOW THE EXCLUSION OR LIMITATION OF IMPLIED WARRANTIES AND
CONDITIONS. TO THE EXTENT PERMITTED BY LAW, ANY IMPLIED WARRANTIES OR CONDITIONS RELATING TO THE
DOCUMENTATION TO THE EXTENT THEY CANNOT BE EXCLUDED AS SET OUT ABOVE, BUT CAN BE LIMITED, ARE
HEREBY LIMITED TO NINETY (90) DAYS FROM THE DATE YOU FIRST ACQUIRED THE DOCUMENTATION OR THE ITEM
THAT IS THE SUBJECT OF THE CLAIM.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW IN YOUR JURISDICTION, IN NO EVENT SHALL
BLACKBERRY BE LIABLE FOR ANY TYPE OF DAMAGES RELATED TO THIS DOCUMENTATION OR ITS USE, OR
79
Installation and Administration Guide
Legal notice
PERFORMANCE OR NON-PERFORMANCE OF ANY SOFTWARE, HARDWARE, SERVICE, OR ANY THIRD PARTY
PRODUCTS AND SERVICES REFERENCED HEREIN INCLUDING WITHOUT LIMITATION ANY OF THE FOLLOWING
DAMAGES: DIRECT, CONSEQUENTIAL, EXEMPLARY, INCIDENTAL, INDIRECT, SPECIAL, PUNITIVE, OR AGGRAVATED
DAMAGES, DAMAGES FOR LOSS OF PROFITS OR REVENUES, FAILURE TO REALIZE ANY EXPECTED SAVINGS,
BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, LOSS OF BUSINESS OPPORTUNITY, OR CORRUPTION
OR LOSS OF DATA, FAILURES TO TRANSMIT OR RECEIVE ANY DATA, PROBLEMS ASSOCIATED WITH ANY
APPLICATIONS USED IN CONJUNCTION WITH BLACKBERRY PRODUCTS OR SERVICES, DOWNTIME COSTS, LOSS OF
THE USE OF BLACKBERRY PRODUCTS OR SERVICES OR ANY PORTION THEREOF OR OF ANY AIRTIME SERVICES, COST
OF SUBSTITUTE GOODS, COSTS OF COVER, FACILITIES OR SERVICES, COST OF CAPITAL, OR OTHER SIMILAR
PECUNIARY LOSSES, WHETHER OR NOT SUCH DAMAGES WERE FORESEEN OR UNFORESEEN, AND EVEN IF
BLACKBERRY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW IN YOUR JURISDICTION, BLACKBERRY SHALL HAVE NO
OTHER OBLIGATION, DUTY, OR LIABILITY WHATSOEVER IN CONTRACT, TORT, OR OTHERWISE TO YOU INCLUDING
ANY LIABILITY FOR NEGLIGENCE OR STRICT LIABILITY.
THE LIMITATIONS, EXCLUSIONS, AND DISCLAIMERS HEREIN SHALL APPLY: (A) IRRESPECTIVE OF THE NATURE OF
THE CAUSE OF ACTION, DEMAND, OR ACTION BY YOU INCLUDING BUT NOT LIMITED TO BREACH OF CONTRACT,
NEGLIGENCE, TORT, STRICT LIABILITY OR ANY OTHER LEGAL THEORY AND SHALL SURVIVE A FUNDAMENTAL
BREACH OR BREACHES OR THE FAILURE OF THE ESSENTIAL PURPOSE OF THIS AGREEMENT OR OF ANY REMEDY
CONTAINED HEREIN; AND (B) TO BLACKBERRY AND ITS AFFILIATED COMPANIES, THEIR SUCCESSORS, ASSIGNS,
AGENTS, SUPPLIERS (INCLUDING AIRTIME SERVICE PROVIDERS), AUTHORIZED BLACKBERRY DISTRIBUTORS (ALSO
INCLUDING AIRTIME SERVICE PROVIDERS) AND THEIR RESPECTIVE DIRECTORS, EMPLOYEES, AND INDEPENDENT
CONTRACTORS.
IN ADDITION TO THE LIMITATIONS AND EXCLUSIONS SET OUT ABOVE, IN NO EVENT SHALL ANY DIRECTOR,
EMPLOYEE, AGENT, DISTRIBUTOR, SUPPLIER, INDEPENDENT CONTRACTOR OF BLACKBERRY OR ANY AFFILIATES OF
BLACKBERRY HAVE ANY LIABILITY ARISING FROM OR RELATED TO THE DOCUMENTATION.
Prior to subscribing for, installing, or using any Third Party Products and Services, it is your responsibility to ensure that
your airtime service provider has agreed to support all of their features. Some airtime service providers might not offer
Internet browsing functionality with a subscription to the BlackBerry® Internet Service. Check with your service provider for
availability, roaming arrangements, service plans and features. Installation or use of Third Party Products and Services with
BlackBerry's products and services may require one or more patent, trademark, copyright, or other licenses in order to
avoid infringement or violation of third party rights. You are solely responsible for determining whether to use Third Party
Products and Services and if any third party licenses are required to do so. If required you are responsible for acquiring
them. You should not install or use Third Party Products and Services until all necessary licenses have been acquired. Any
Third Party Products and Services that are provided with BlackBerry's products and services are provided as a
convenience to you and are provided "AS IS" with no express or implied conditions, endorsements, guarantees,
representations, or warranties of any kind by BlackBerry and BlackBerry assumes no liability whatsoever, in relation
thereto. Your use of Third Party Products and Services shall be governed by and subject to you agreeing to the terms of
separate licenses and other agreements applicable thereto with third parties, except to the extent expressly covered by a
license or other agreement with BlackBerry.
Certain features outlined in this documentation require a minimum version of BlackBerry Enterprise Server, BlackBerry
Desktop Software, and/or BlackBerry Device Software.
80
Installation and Administration Guide
Legal notice
The terms of use of any BlackBerry product or service are set out in a separate license or other agreement with BlackBerry
applicable thereto. NOTHING IN THIS DOCUMENTATION IS INTENDED TO SUPERSEDE ANY EXPRESS WRITTEN
AGREEMENTS OR WARRANTIES PROVIDED BY BLACKBERRY FOR PORTIONS OF ANY BLACKBERRY PRODUCT OR
SERVICE OTHER THAN THIS DOCUMENTATION.
Certain features outlined in this documentation might require additional development or Third Party Products and Services
for access to corporate applications.
BlackBerry Limited
2200 University Avenue East
Waterloo, Ontario
Canada N2K 0A7
BlackBerry UK Limited
200 Bath Road
Slough, Berkshire SL1 3XE
United Kingdom
Published in Canada
81