Installation and Administration Guide

Transcription

1 Installation and Administration Guide BlackBerry Enterprise Transporter for BlackBerry Enterprise Service 12 Version 12.0

2 Published: SWD

3 Contents What is BES12?... 6 Key features of BES What is the BlackBerry Resource Kit for BES12?...7 What is the BlackBerry Enterprise Transporter for BES12?...8 BlackBerry Enterprise Transporter modes... 8 Options for migrating user accounts... 9 Data that the migration process doesn't move Validation that the BlackBerry Enterprise Transporter performs Global validation User validation System requirements...14 System requirements: BlackBerry Enterprise Transporter...14 Installation considerations Supported environments...15 Unsupported features and environments Required permissions in an IBM Domino environment...21 Replicating IBM Domino databases...21 Installing and configuring the BlackBerry Enterprise Transporter...23 Install the BlackBerry Enterprise Transporter Configure how long the BlackBerry Enterprise Transporter waits for the Microsoft SQL Server to process commands Encrypt the information about database connections in the configuration file...24 Premigration considerations Preparing the source EMM domain for the migration process...26 Preparing the destination BES12 EMM domain for the migration process...27 Preparing the destination BlackBerry Enterprise Server EMM domain for the migration process BlackBerry Enterprise Server compatibility...29 Moving user accounts to a destination BES Moving user accounts to a destination BlackBerry Enterprise Server 5.0 or later Moving user accounts to a destination BlackBerry Enterprise Server to

4 Moving user accounts to a destination BlackBerry Enterprise Server 4.1 to or 4.0 to Moving user accounts to a destination BlackBerry Enterprise Server BlackBerry Device Software compatibility Moving user accounts to a destination BES Moving user accounts to a destination BlackBerry Enterprise Server 5.0 or later Moving user accounts to a destination BlackBerry Enterprise Server to Moving user accounts to a destination BlackBerry Enterprise Server 4.1 to or 4.0 to Moving user accounts to a destination BlackBerry Enterprise Server Moving user accounts from a BlackBerry Enterprise Server Express to a BlackBerry Enterprise Server...37 Moving user accounts from a BlackBerry Enterprise Server or BlackBerry Professional Software to a BlackBerry Enterprise Server Express Configure the BlackBerry Enterprise Transporter to skip certificate validation Preparing to move user accounts Create the manifest file Configure the source and destination database instances...40 Configure the default settings to apply to the user accounts that you migrate Configure the BlackBerry Enterprise Transporter to send notification messages to user accounts...42 Configure how long the BlackBerry Enterprise Transporter tries to open a connection to the source and destination databases...43 Selecting the user accounts to move to the destination EMM domain...44 Live mode: Selecting user accounts to migrate Search for and select user accounts to move...44 Import a file with addresses Add the information for a single user account...45 Bulk mode: Selecting user accounts to migrate Enable bulk mode to select all user accounts that are associated with a source BlackBerry Enterprise Server or BES Configure the default settings to apply to specific user accounts Moving user accounts...48 Preview the migration process...48 Prequisites: Moving user accounts to a different EMM domain Move user accounts to a different EMM domain...49 View the latest BlackBerry Enterprise Transporter log file...49 Running the BlackBerry Enterprise Transporter from the command prompt Preview the migration process using the command prompt... 50

5 Move user accounts to a different EMM domain using the command prompt Return user accounts to the source EMM domain...54 Troubleshooting Configuration errors and warnings The BlackBerry Enterprise Transporter cannot connect to the BlackBerry Administration Service Configuration file error XML Manifest Failed to Load One or more user accounts do not have a Destination Server set...56 Troubleshooting preview errors ERROR: Destination contains servers older than Application error messages...57 User validation error messages User validation warning messages...62 Troubleshooting migration errors...62 User migration failed messages User migration completed with warning messages User migration pending error messages IT policy error messages User account status: Skipped User account status: MigrationSkippedDueToValidationFailure Port information for the BlackBerry Enterprise Transporter...67 Glossary Legal notice...69

6 What is BES12? What is BES12? 1 BES12 is an EMM solution from BlackBerry. EMM solutions help you do the following: Manage mobile devices for your organization to protect business information Keep mobile workers connected with the information that they need Provide administrators with efficient business tools With BES12, you can manage the following device types: BlackBerry 10 BlackBerry OS (version 5.0 to 7.1) ios Android Windows Phone You can manage these devices from a single, simplified UI with industry-leading security. Key features of BES12 Feature Management of many types of devices Single, unified UI Trusted and secure experience Balance of work and personal needs You can manage BlackBerry 10, BlackBerry OS (version 5.0 to 7.1), ios, Android, and Windows Phone devices. You can view all devices in one place and access all management tasks in a single, web-based UI. You can share administrative duties with multiple administrators who can access the management console at the same time. Device controls give you precise management of how devices connect to your network, what capabilities are enabled, and what apps are available. Whether the devices are owned by your organization or your users, you can protect your organization's information. BlackBerry Balance and Secure Work Space technologies are designed to make sure that personal information and work information are kept separate and secure on devices. If the device is lost or the employee leaves the organization, you can delete only work-related information or all information from the device. 6

7 What is the BlackBerry Resource Kit for BES12? What is the BlackBerry Resource Kit for BES12? 2 The BlackBerry Resource Kit is a collection of tools that you can use to manage, monitor, and troubleshoot devices that are associated with BES12. You can download the BlackBerry Resource Kit from The BlackBerry Resource Kit for BES12 includes the following tools: Tool BES12 Log Monitoring Tool BlackBerry Push Initiator Tool BlackBerry Enterprise Transporter for BES12 A command-line tool that you can use to monitor the information that is written to the log files for BES12 components. You can specify actions that you want the tool to perform when it finds specific values, such as text strings. For example, you can configure the tool to run a custom batch file when it finds a specific text string in a log message. An application that you can use to push data to apps installed on BlackBerry 10 devices. For example, you can push mapping information about folders in an organization's network that BlackBerry 10 device users can then access using the BlackBerry Work Drives app without the users needing to configure access to the folders. You can customize the data for group members or individuals. You can create a batch file to specify the mapping information that the BlackBerry Push Initiator Tool uses. You can use a scheduling tool to run the batch file. An application that you can use to migrate user accounts between BlackBerry Enterprise Server domains, and between BES5 version and BES12 domains. The BlackBerry Enterprise Transporter for BES12 has separate installation files and documentation from the other BlackBerry Resource Kit tools. If you are using tools from previous releases of the BlackBerry Resource Kit, visit docs.blackberry.com/brk to see the documentation for the appropriate version of the BlackBerry Resource Kit. 7

8 What is the BlackBerry Enterprise Transporter for BES12? What is the BlackBerry Enterprise Transporter for BES12? 3 You can use the BlackBerry Enterprise Transporter to move user accounts from one EMM domain to a different EMM domain. A BES12 domain consists of a BES12 database and any BES12 components that are associated with it. A BlackBerry Enterprise Server 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 installs BES12 and you want to migrate users from BES5 to BES12. You can also migrate users with devices that run BlackBerry OS (version 5.0 to 7.1) from BES12 back to BES5. You can also use the BlackBerry Enterprise Transporter when your organization upgrades from an earlier version of the BlackBerry Enterprise Server to a more recent version, or if you need to move user accounts between existing EMM domains. For example, if you want to upgrade your organization's BlackBerry Enterprise Server to version 5.0.4, you can create a new EMM domain for version 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 OS device data or reactivate their devices. After the migration process completes, the destination BES12 or BES5 instance 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 (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 about the available migration options between BlackBerry Enterprise Server EMM domains, visit to read the BlackBerry Enterprise Server Upgrade Guide. For more information about upgrading from BES5 to BES12, visit docs.blackberry.com/bes12 to read the BlackBerry Enterprise Service 12 Planning Guide. 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 EMM domain to a different destination EMM 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 or BES12 to a destination BlackBerry Enterprise Server or BES12 in a different EMM domain. Both the source and destination instances must be running and must use a different SRP ID. Live mode is the default mode of the BlackBerry Enterprise Transporter. 8

9 What is the BlackBerry Enterprise Transporter for BES12? 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 or BES12 to a destination BlackBerry Enterprise Server or BES12. The source and destination instances must not be running, except for the BlackBerry Administration Service and the IBM Domino services on the destination BlackBerry Enterprise Server (if applicable). In 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 Enterprise Server or BES12 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 change the IT policy, software configuration, and group assignments using the BlackBerry Administration Service or BES12 management console 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 Move one or more user accounts at a time If your organization's environment includes more than one EMM domain, and you want to move select user accounts from one EMM domain to another, you can use the tool in live mode. For example, you can use this option if you maintain multiple EMM domains for different groups in the organization, and you want to move users over to the EMM domain for a different group, or if you install a new BES5 or BES12 environment as a new EMM 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 EMM 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 BES12. 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 Enterprise Server or BES12 must process the 9

10 What is the BlackBerry Enterprise Transporter for BES12? Option 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 BlackBerry Enterprise Server or BES12 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 doesn't move Data User accounts that are not BlackBerryenabled Administrative role assignment Group data Software configurations The BlackBerry Enterprise Transporter doesn't move user accounts that are not BlackBerry-enabled (for example, administrator accounts that cannot be assigned a device). If you move user accounts from BES5 to a different BES5, or you move user accounts between BES5 and BES12, the migration process doesn't move the administrative roles that are assigned to the user accounts. You can manually assign 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 BES5 or BES12. The migration process doesn't migrate groups or any of the data associated with groups. Instead, you can create a group on the destination BlackBerry Enterprise Server or BES12 and specify it as the group that you want to assign user accounts to during the migration process. The migration process doesn't migrate software configurations, including BlackBerry MDS Runtime app data. You can create a software configuration on the destination BlackBerry Enterprise Server or BES12 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. User accounts migrated to BES12 are assigned the BlackBerry OS Default IT policy. Before you start the migration process, you can select the IT policies on the 10

11 What is the BlackBerry Enterprise Transporter for BES12? Data destination BlackBerry Enterprise Server or BES12 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 or BES12 and then assign the user accounts to the group. Note: If you move user accounts to a destination BES5 or BES12, there might be a delay before the destination server applies the selected IT policies or groupassigned 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. The BlackBerry MDS Integration Service has been deprecated as of BlackBerry Enterprise Server 5.0 SP3. BlackBerry Browser configuration settings Synchronized public contacts and databases, and additional private contact folders The migration process does not migrate the BlackBerry Browser configuration settings on the device that is associated with a user account. 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. 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 BES12 or the BlackBerry Administration Service is installed in the destination EMM domain. Sends a test command to verify that BES12 or the BlackBerry Administration Service is available and can respond. Verifies that the required API and web services are installed on the computer that hosts BES12 or the BlackBerry Administration Service. 11

12 What is the BlackBerry Enterprise Transporter for BES12? 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 and destination EMM domain. The default location of the EnterpriseTransporter.exe.config file is <drive>:\program Files (x86)\blackberry\blackberry Resource Kit for BlackBerry Enterprise Service 12\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\<username> \AppData\Roaming\BlackBerry\BlackBerry Enterprise Transporter). 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 address. Verifies that the user account exists in the source EMM domain. If the destination is a BlackBerry Enterprise Server EMM domain, verifies that the user account does not already exist. If the destination is a BES12 EMM domain, verifies that if an account with the same address already exists, the account has no BlackBerry OS devices associated with it. The account may have other devices associated with it. Verifies whether it can preserve the user ID that is associated with the user's BlackBerry OS device. Verifies that an IT policy can be applied to the user's device. This verification might not be possible in any of the following scenarios: The device is running an unspecified version of the BlackBerry OS. The device is running BlackBerry OS version and the ITPolicyKeyMapping table does not exist. The device is running BlackBerry OS version 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 or BES12. 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)\blackberry\blackberry Resource Kit for BlackBerry Enterprise Service 12\BlackBerry Enterprise Transporter. If your computer's operating system uses 12

13 What is the BlackBerry Enterprise Transporter for BES12? 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\<username> \AppData\Roaming\BlackBerry\BlackBerry Enterprise Transporter). 13

14 System requirements System requirements 4 System requirements: BlackBerry Enterprise Transporter Item BlackBerry Enterprise Transporter version Operating system Requirement Use the latest available version of the BlackBerry Enterprise Transporter, regardless of the versions of the source and destination EMM domains. 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 and the destination BlackBerry Enterprise Server or BES12 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 BES12 to use Triple DES and AES, this 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 BlackBerry Administration Service or BES12 management console In the source and destination BlackBerry Administration Service or BES12 management console, create an administrator account that you can use to view BlackBerry Enterprise Server or BES12 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. 14

15 System requirements Item BlackBerry Enterprise Server or BES12 APIs and web services EMM domain Requirement Before you use the BlackBerry Enterprise Transporter for the first time, log in to the destination BlackBerry Administration Service or BES12 management console and verify that you can create a user account, assign a device to the user account, and activate the device. The BlackBerry Enterprise Transporter uses the BlackBerry Administration API and the admin web services (AdminWS) for optional user assignment. If the destination EMM 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, on page 26 Installation considerations Supported environments Item BlackBerry Enterprise Server versions Environment 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 BES12 BlackBerry Enterprise Transporter compatibility matrix for the BlackBerry Enterprise Server for Microsoft Exchange and the BlackBerry Enterprise Server for IBM Domino 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 and destination BlackBerry Enterprise Server or BES12. For more information, see the premigration considerations. 15

16 System requirements Item BlackBerry Enterprise Server Express Database server (source and destination) Environment The BlackBerry Enterprise Transporter does not support the use of bulk mode when moving user accounts to or from the BlackBerry Enterprise Server Express. The BlackBerry Enterprise Transporter supports the following database servers (32-bit or 64-bit): Microsoft SQL Server 2014 Microsoft SQL Server 2012 Microsoft SQL Server 2008 R2 Express Microsoft SQL Server 2008 Express SP1 Microsoft SQL Server 2008 R2 The following database servers have not been tested and are not officially supported: 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 mail server IBM Domino mail server Novell GroupWise mail server User application Any version of Microsoft Exchange that the BlackBerry Enterprise Server supports. Any version of Domino later than that the BlackBerry Enterprise Server supports. Any version of Novell GroupWise that the BlackBerry Enterprise Server supports. The BlackBerry Enterprise Transporter supports the following versions of IBM Notes: 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 BlackBerry Device Software For more information about BlackBerry Device Software compatibility, see BlackBerry Device Software compatibility. Related information Premigration considerations, on page 26 16

17 System requirements BlackBerry Enterprise Transporter compatibility matrix for BES12 The following table displays the migration paths that the BlackBerry Enterprise Transporter supports. Based on the version of the source BlackBerry Enterprise Server or BES12 and the destination BlackBerry Enterprise Server or BES12, there might be important conditions that you must be aware of. Read the premigration considerations section before you try to migrate user accounts. Previous versions of the BlackBerry Enterprise Transporter tool cannot migrate users to BES12. Do not try to migrate with an older version of the tool. Designation Abbreviation Supported S The migration path has been tested and is supported for moving users from the source to the destination EMM domain, and for moving users back to the source EMM domain for troubleshooting purposes. Back Out Only BO The migration path is supported only for troubleshooting purposes. 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 Source server BES BES12 S S S S Related information BlackBerry Enterprise Server compatibility, on page 29 BlackBerry Device Software compatibility, on page 32 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 and 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. 17

18 System requirements Designation Abbreviation Supported S The migration path has been tested and is supported for moving users from the source to the destination EMM domain, and for moving users back to the source EMM Domain for troubleshooting purposes. Back Out Only BO The migration path is supported only for troubleshooting purposes. 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 Source server NS NS BE BE BE BE BE BE BE NS NS BE BE S S S S S NS NS BE BE BE BE BE BE BE NS NS BE BE S S S S S 5.0 NS BO NS BO S S S S S NS BO NS BO S S S S S NS BO NS BO S S S S S NS BO NS BO S S S S S NS BO NS BO S S S S S Related information BlackBerry Enterprise Server compatibility, on page 29 BlackBerry Device Software compatibility, on page 32 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. 18

19 System requirements 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. Designation Abbreviation Supported S The migration path has been tested and is supported for moving users from the source to the destination EMM domain, and for moving users back to the source EMM domain for troubleshooting purposes. Back Out Only BO The migration path is supported only for troubleshooting purposes. 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 Source server BlackBerry Enterprise Server Small Business Edition and BlackBerry Professional Software BlackBerry Enterprise Server Express BlackBerry Enterprise Server Express and later BlackBerry Enterprise Server BlackBerry Enterprise Server and later BlackBerry Enterprise Server Small Business Edition and BlackBerry Professional Software BlackBerry Enterprise Server Express BlackBerry Enterprise Server Express and later NS NS BE S NS* NS* NS NS BE S NS NS NS NS BE BE BE BE BO BO BE BE BE S 19

20 System requirements BlackBerry Enterprise Server BlackBerry Enterprise Server and later Destination server NS NS NS NS See appropriate matrix NS NS NS BO See appropriate matrix 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, on page 29 BlackBerry Device Software compatibility, on page 32 Moving user accounts from a BlackBerry Enterprise Server Express to a BlackBerry Enterprise Server, on page 37 Moving user accounts from a BlackBerry Enterprise Server or BlackBerry Professional Software to a BlackBerry Enterprise Server Express, on page 38 Unsupported features and environments For more information about BlackBerry Enterprise Transporter compatibility, see Supported environments. Item EMM domains Environment The BlackBerry Enterprise Transporter does not support the following EMM domains: BlackBerry Device Service Universal Device Service BlackBerry Device Software IBM DB2 UDB Mail server environment The BlackBerry Enterprise Transporter does not support BlackBerry Device Software versions that are earlier than version 4.0; version is supported with conditions. The BlackBerry Enterprise Transporter does not support DB2 UDB. The BlackBerry Enterprise Transporter does not support migrating users from one mail server environment to a different environment (for example, migrating users from an IBM Domino environment to a Microsoft Exchange environment). Microsoft Office 365 The BlackBerry Enterprise Transporter does not support Microsoft Office 365. Novell GroupWise The BlackBerry Enterprise Transporter does not support Novell GroupWise. 20

21 System requirements Related information Supported environments, on page 15 Troubleshooting preview errors, on page 56 Troubleshooting migration errors, on page 62 Premigration considerations, on page 26 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 EMM domain and the destination EMM domain that you require as an administrator of the BlackBerry Enterprise Server for IBM Domino. For more information, visit to read the BlackBerry Enterprise Server Installation Guide and the BlackBerry Enterprise Server Administration Guide. Permission Resource Notes.ini file You must configure read and write permissions in the notes.ini file. BlackBerry Enterprise Server Installation Guide Section: System requirements: BlackBerry Enterprise Server 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, ã). 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)\blackberry\blackberry Resource Kit for BlackBerry Enterprise Service 12\BlackBerry Enterprise Transporter. If your computer's operating system uses UAC and does not permit you to change the configuration file at this location, open the 21

22 System requirements virtualized copy of the EnterpriseTransporter.exe.config file in the application data folder for the current user (for example, <drive>\users\<username>\appdata\roaming\blackberry\blackberry Enterprise Transporter). 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 EMM domain before you begin the migration process. If you migrate a user account without replicating the user s BlackBerry state database in the destination EMM 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. 22

23 Installing and configuring the BlackBerry Enterprise Transporter Installing and configuring the BlackBerry Enterprise Transporter 5 Install 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 or BES12 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 and navigate to the Business Support Resources and Downloads area for the BlackBerry Enterprise Server Resource Kit and download the latest installation package. 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. 23

24 Installing and configuring the BlackBerry Enterprise Transporter 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 or BES12, 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, 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)\blackberry \BlackBerry Resource Kit for BlackBerry Enterprise Service 12\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 change 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\<username>\appdata\roaming\blackberry\blackberry Enterprise Transporter). 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. Encrypt the information about database connections in the configuration file When you configure the source and destination BlackBerry Configuration Database or BES12 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 or BES12 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 change the configuration file to encrypt the information that it contains about database connections. 24

25 Installing and configuring the BlackBerry Enterprise Transporter 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)\blackberry \BlackBerry Resource Kit for BlackBerry Enterprise Service 12\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 change 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\<username>\appdata\roaming\blackberry\blackberry Enterprise Transporter). 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. 25

26 Premigration considerations Premigration considerations 6 Preparing the source EMM domain for the migration process For more information about managing the BlackBerry Enterprise Server, visit to read the documentation for the BlackBerry Enterprise Server. Task Delete all unused user accounts. In an IBM Domino environment, remove the associated BlackBerry state databases. Back up the BlackBerry Configuration Database. Create a list of the software configurations and applications that you want to duplicate in the destination EMM domain. Create a list of the IT policies, policy rules, and default settings that you want to duplicate in the destination EMM domain. You require BES12 BlackBerry OS licenses to use BlackBerry OS version 5.0 to 7.1 devices in a BES12 domain. If you want the BlackBerry Enterprise Transporter to import a list of the user accounts to migrate, collect the list of user addresses in a flat, CR-delimited text file. Verify that the text file uses the following format: Resource BlackBerry Enterprise Server Administration Guide BlackBerry Enterprise Server Upgrade Guide BlackBerry Enterprise Server Administration Guide BlackBerry Enterprise Server Administration Guide BlackBerry Enterprise Service 12 Licensing Guide < address1> < address2> < address3> Create a list of the administrative roles that you want to duplicate and assign in the destination EMM domain. If you set up replication for the BlackBerry Configuration Database, stop the replication process. BlackBerry Enterprise Server Administration Guide 26

27 Premigration considerations Task Notify users that applications on BlackBerry OS devices that use a data connection through the BlackBerry MDS Connection Service might experience a service interruption until the user account is migrated and reactivated. Resource Preparing the destination BES12 EMM domain for the migration process For more information about managing BES12, visit docs.blackberry.com/bes12 to read the BES12 documentation. Task If you plan to move user mailboxes to the destination EMM domain, as a best practice, consider moving the user mailboxes before you migrate user accounts. Resource Install BES12. BlackBerry Enterprise Service 12 Installation Guide In the destination BES12 administrative console, create the groups, IT policies, roles, and software configurations that you want to duplicate from the source EMM domain. BlackBerry Enterprise Service 12 Administration Guide If you enable bulk mode and configure custom default settings (IT policies, software configurations, and groups) to apply to individual user accounts, the destination BES12 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 BES12 management console 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 BES12 database. BlackBerry Enterprise Service 12 Configuration Guide In an IBM Domino environment, you can copy the BlackBerry state databases and BlackBerry profiles databases from the source BlackBerry Enterprise Server instances to the destination BES12. You can perform this task if you do not want the BlackBerry Enterprise Transporter to replicate the databases during the migration process. IBM Domino documentation 27

28 Premigration considerations Task If you plan to use the BlackBerry Enterprise Transporter in bulk mode, in a Microsoft Exchange environment, configure the destinationbes12 to use the same instance names (ServerConfig.ServiceName) and SRP IDs as the source instances. Resource In an IBM Domino environment, configure the destination BES12 instances to use the same SRP IDs as the source BlackBerry Enterprise Server instances. Notify users that applications on their BlackBerry OS devices that use a data connection through the BlackBerry MDS Connection Service might experience a service interruption until the user account is migrated and reactivated. Preparing the destination BlackBerry Enterprise Server EMM domain for the migration process For more information about managing the BlackBerry Enterprise Server, visit to read the BlackBerry Enterprise Server documentation. Task If you plan to move user mailboxes to the destination EMM 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 Enterprise Server instances. Resource BlackBerry Enterprise Server 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 EMM 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. 28

29 Premigration considerations Task Resource 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. In an IBM Domino environment, you can copy the BlackBerry state databases 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 environment, configure the destination BlackBerry Enterprise Server instances to use the same instance names (ServerConfig.ServiceName) and SRP IDs as the source instances. BlackBerry Enterprise Server Upgrade Guide IBM Domino documentation 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 OS devices that use a data connection through the BlackBerry MDS Connection Service might experience a service interruption until the user account is migrated and reactivated. BlackBerry Enterprise Server compatibility Moving user accounts to a destination BES12 If the version of the source BlackBerry Enterprise Server is earlier than version 5.0 SP4 MR10, consider the following information: Consideration The BlackBerry Enterprise Transporter for BES12 supports migration from Upgrade the source BlackBerry Enterprise Server to version 5.0 SP4 MR10. 29

30 Premigration considerations Consideration BlackBerry Enterprise Server version 5.0 SP4 MR10. Domains without BES12 (source or destination) can be of a range of BES5 versions. 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 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 EMM 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 to If you move user accounts to a destination BlackBerry Enterprise Server that is version to 4.1.7, consider the following information: Consideration 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: 30

31 Premigration considerations Consideration 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 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 EMM 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 to or 4.0 to If you try to move user accounts to a destination BlackBerry Enterprise Server that is 4.1 to or 4.0 to 4.0.6, consider the following information: Consideration The BlackBerry Enterprise Transporter does not support the version of the destination BlackBerry Enterprise Server. Upgrade the destination BlackBerry Enterprise Server to a version that the BlackBerry Enterprise Transporter supports. Moving user accounts to a destination BlackBerry Enterprise Server If you move user accounts to a destination BlackBerry Enterprise Server that is version 4.0.7, consider the following information: 31

32 Premigration considerations Consideration 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 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 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 EMM 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 The BlackBerry Enterprise Transporter does not support the version of the destination BlackBerry Enterprise Server. Upgrade the destination BlackBerry Enterprise Server to a version that the BlackBerry Enterprise Transporter supports. BlackBerry Device Software compatibility 32

33 Premigration considerations Moving user accounts to a destination BES12 If you move user accounts to a destination BES12, consider the following information: Consideration BES12 supports BlackBerry OS devices version 5.0 to 7.1 Upgrade BlackBerry OS devices with BlackBerry Device Software earlier than version 5.0. 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 The BlackBerry Enterprise Transporter does not support a destination EMM 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. Upgrade all BlackBerry Enterprise Server instances in the destination EMM domain to 5.0 or later. If BlackBerry devices use BlackBerry Device Software 4.3.0, consider the following information: Consideration IT policies might not be applied to BlackBerry OS 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 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 to 4.0.1, consider the following information: Consideration IT policies might not be applied to BlackBerry OS devices. If the destination BlackBerry Configuration Database does not contain the optional ITPolicyKeyMapping table, the IT policies on the destination BlackBerry Enterprise 33

34 Premigration considerations Consideration 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 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 to If you move user accounts to a destination BlackBerry Enterprise Server that is to 4.1.7, consider the following information: Consideration 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 OS 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 OS device. If BlackBerry devices use BlackBerry Device Software version 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 Duplicate contact list entries might appear on BlackBerry OS 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 OS devices use BlackBerry Device Software 4.3.0, consider the following information: Consideration IT policies might not be applied to BlackBerry OS 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 34

35 Premigration considerations Consideration devices. Before you move the user accounts, update the BlackBerry Device Software on devices to version 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 to 4.0.1, consider the following information: Consideration IT policies might not be applied to BlackBerry OS 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 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 to or 4.0 to If you try to move user accounts to a destination BlackBerry Enterprise Server that is 4.1 to or 4.0 to 4.0.6, consider the following information: Consideration The BlackBerry Enterprise Transporter does not support the version of the destination BlackBerry Enterprise Server. Upgrade the destination BlackBerry Enterprise Server to a version that the BlackBerry Enterprise Transporter supports. Moving user accounts to a destination BlackBerry Enterprise Server If you move user accounts to a destination BlackBerry Enterprise Server 4.0.7, consider the following information: 35

36 Premigration considerations Consideration 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 OS 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 OS device. If devices use BlackBerry Device Software 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 Duplicate contact list entries might appear on BlackBerry OS 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 IT policies might not be applied to BlackBerry OS 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 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 to 4.0.1, consider the following information: Consideration IT policies might not be applied to BlackBerry OS 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 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 36

37 Premigration considerations Consideration 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 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. User accounts with BlackBerry devices that have been activated using the BlackBerry Internet Service cannot be moved to a destination BlackBerry Enterprise Server. The BlackBerry Enterprise Transporter does not support the use of bulk mode when moving user accounts from a source BlackBerry Enterprise Server Express to a destination BlackBerry Enterprise Server. 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. 37

38 Premigration considerations Moving user accounts from a BlackBerry Enterprise Server or BlackBerry Professional Software to a BlackBerry Enterprise Server Express Consideration 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"/>). Configure the BlackBerry Enterprise Transporter to skip certificate validation When the BlackBerry Enterprise Transporter connects to the BlackBerry Administration Service or to BES12, it verifies that the FQDN that it reads from the BlackBerry Configuration Database or the BES12 database matches the SSL certificate of the BlackBerry Administration Service. You can configure the tool to skip this verification process for specific servers. 38

39 Premigration considerations 1. On the computer that hosts the BlackBerry Enterprise Transporter, navigate to <drive>:\program Files (x86)\blackberry \BlackBerry Resource Kit for BlackBerry Enterprise Service 12\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 change 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\<username>\appdata\roaming\blackberry\blackberry Enterprise Transporter). 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 or BES12. If you want to specify multiple computers, separate each FQDN or IP address using a comma (,) or semicolon (;). Example: <add key="certvalidationexcludedhosts" value="server1.testnet.company.net; "/> 4. Save and close the EnterpriseTransporter.exe.config file. After you finish: Restart the BlackBerry Enterprise Transporter. 39

40 Preparing to move user accounts Preparing to move user accounts 7 Create the manifest file The manifest file contains information about the EMM 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 or BES12 database. Configure the source and destination database instances To configure the tool for the migration process, you must specify information about the source and destination BlackBerry Configuration Database or BES12 database. Before you begin: Create a manifest file or open a saved manifest file. 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, perform one of the following actions: To configure the information for the source BlackBerry Configuration Database or BES12 database for the first time, click <new>. To choose an existing source database, click the appropriate label name. 3. In the Edit/New section, in the Label field, type a label for the source database. 4. In the SQL Server field, type the FQDN or IP address of the Microsoft SQL Server that hosts the source database. 5. In the Authentication drop-down list, perform one of the following actions: 40

41 Preparing to move user accounts To use database authentication to access the source 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 database. To use Windows authentication to access the source 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 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 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 or BES12 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 or BES12, group, IT policy, and software configuration that you want to apply to the user accounts that you move to the destination EMM 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. If you enable bulk mode and configure custom default settings to apply to individual user accounts, the destination BlackBerry Administration Service or BES12 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 or BES12 management console 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 EMM domain, create the group, IT policy, and software configuration that you want to apply to the user accounts. 41

42 Preparing to move user accounts Configure the source and destination instances of the BlackBerry Configuration Database or BES12 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 or BES12 instance, 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 BES5 or BES12, there might be a delay before the selected IT policy or groupassigned IT policy is sent 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 EMM domain. Configure the BlackBerry Enterprise Transporter to send notification 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 or BES12. You cannot send a notification message to user accounts when you use the tool in bulk mode. 1. On the Config menu, click Configuration. 2. In the 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 section, type the information for the notification message. 5. Click OK. After you finish: To turn off notification messages, clear the Enable check box. 42

43 Preparing to move user accounts Configure how long the BlackBerry Enterprise Transporter tries to open a connection to the source and destination databases When you try to move user accounts, the BlackBerry Enterprise Transporter tries to open a connection to the Microsoft SQL Server to the source EMM domain and the Microsoft SQL Server that the destination EMM domain uses. By default, the tool tries to open a connection to a Microsoft SQL Server for a timeout period of 15 seconds, which is 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. 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 or BES12 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)\blackberry\blackberry Resource Kit for BlackBerry Enterprise Service 12\BlackBerry Enterprise Transporter. If your computer's operating system uses UAC and does not permit you to change 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 \<username>\appdata\roaming\blackberry\blackberry Enterprise Transporter) 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 or BES12 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, on page 40 Configure the source and destination database instances, on page 40 43

44 Selecting the user accounts to move to the destination EMM domain Selecting the user accounts to move to the destination EMM domain 8 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 EMM domain, BlackBerry Enterprise Server instance or BES12 instance, group, or IT policy. Specify the addresses of each user account. Import a CR-delimited, flat text file that contains the addresses of the user accounts. If you want to run the tool in bulk mode, select a source BlackBerry Enterprise Server instance or BES12 instance; the tool will migrate all of the users associated with that instance. 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 EMM domain, BlackBerry Enterprise Server instance or BES12 instance, group, or IT policy. Before you begin: Configure the source and destination instances of the BlackBerry Configuration Database or BES12 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: 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 or BES12 instance, select the Server option. In the drop-down list, click a BlackBerry Enterprise Server or BES12. 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. 44

45 Selecting the user accounts to move to the destination EMM domain 4. Click Find. To filter the list of available users, type the username. 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 addresses Before you begin: Configure the source and destination instances of the BlackBerry Configuration Database or BES12 database. Create a CR-delimited flat text file that contains the addresses of the user accounts that you want to move. Verify that the user accounts are associated with the source EMM 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 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 or BES12 database for the information. Before you begin: Configure the source and destination instances of the BlackBerry Configuration Database or BES12 database. 1. In the BlackBerry Enterprise Transporter, in the Step 3: Manifest Configuration section, in the Summary section, click Details. 2. In the column, double-click the empty cell and type the address for the user account. 3. In the Dest Server column, in the drop-down list, click the BlackBerry Enterprise Server or BES12 instance that you want to associate the user account with. 4. Click Done. 45

46 Selecting the user accounts to move to the destination EMM domain Bulk mode: Selecting user accounts to migrate Enable bulk mode to select all user accounts that are associated with a source BlackBerry Enterprise Server or BES12 To move all user accounts that are associated with a source BlackBerry Enterprise Server or BES12, 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 or BES12 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 or BES 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. Configure the default settings to apply to specific user accounts After you select the user accounts that you want to move to the destination EMM domain, you can apply different settings for the destination BlackBerry Enterprise Server or BES12 instance, 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 or BES12 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 46

47 Selecting the user accounts to move to the destination EMM domain Administration Service or BES12 administration console 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 EMM 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 or BES12 database. Before you select the user accounts that you want to move to the destination EMM 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 EMM 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 or BES12 instance, 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. 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 and BES12 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 or BlackBerry Enterprise Service 12 Administration Guide. Note: If you move user accounts to a destination BES5 or BES12, 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, on page 41 Selecting the user accounts to move to the destination EMM domain, on page 44 47

48 Moving user accounts Moving user accounts 9 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. Prequisites: Moving user accounts to a different EMM domain Before you use the BlackBerry Enterprise Transporter for the first time, log in to the BlackBerry Administration Service or BES12 management console of the destination EMM domain and verify that you can create a user account, assign a BlackBerry OS 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. To move the Wi-Fi profile data for user accounts, verify that both the source and destination EMM domains are version or later. Wi-Fi profile configurations must be the same on both the source and destination domains. If the Wi-Fi profile configurations are not the same, the user accounts are moved with the Wi-Fi profile settings from the source domain. Verify that the destination BlackBerry Administration Service or BES12 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. 48

49 Moving user accounts Move user accounts to a different EMM 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. 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 or BES12 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 mail 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 or BES12 synchronizes the organizer data for the user accounts at a regularly scheduled interval. To move the Wi-Fi profile 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 or BES12 management console. Verify that the user accounts are assigned to the correct BlackBerry Enterprise Server or BES12 instance, group, IT policy, and software configuration. Note: If you move user accounts to a destination BES5 or BES12, there might be a delay before the selected IT policies or group-assigned IT policies are sent 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. In the BlackBerry Enterprise Transporter, on the Help menu, click View Log. By default, the log files are located at <drive>:\users\<username>\appdata\roaming\blackberry\blackberry Enterprise Transporter\Logs. 49

50 Running the BlackBerry Enterprise Transporter from the command prompt Running the BlackBerry Enterprise Transporter from the command prompt 10 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)/blackberry/blackberry Resource Kit/BlackBerry Enterprise Transporter <version>. 2. Type enterprisetransporter /console /preview and any of the following parameters: Parameter /basauthtype <type> This parameter specifies which of the following options the tool uses to authenticate with the BlackBerry Administration Service or BES12: ad_auth: Use Microsoft Active Directory authentication. You must also specify the /basdomain parameter. bas_auth: Use BlackBerry Administration Service or BES12 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 or BES12. Use this parameter when you specify /basauthtype ad_auth. 50

51 Running the BlackBerry Enterprise Transporter from the command prompt Parameter /basusername <username> This parameter specifies the username of the administrator account that the tool uses to authenticate with the BlackBerry Administration Service or BES12 when it uses BlackBerry Administration Service or BES12 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 or BES12 when it uses BlackBerry Administration Service or BES12 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. 51

52 Running the BlackBerry Enterprise Transporter from the command prompt Move user accounts to a different EMM 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)/blackberry/blackberry Resource Kit/BlackBerry Enterprise Transporter <version>. 2. Type enterprisetransporter /console /execute and any of the following optional parameters: Parameter /basauthtype <type> This parameter specifies which of the following options the tool uses to authenticate with the BlackBerry Administration Service or BES12: ad_auth: Use Microsoft Active Directory authentication. You must also specify the /basdomain parameter. bas_auth: Use BlackBerry Administration Service or BES12 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 or BES12 authentication (bas_auth). /basdomain <domain> This parameter specifies the Microsoft Active Directory domain for the BlackBerry Administration Service or BES12. Use this parameter when you specify /basauthtype ad_auth. /basusername <username> This parameter specifies the username of the administrator account that the tool uses to authenticate with the BlackBerry Administration Service or BES12 when it uses BlackBerry Administration Service or BES12 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 or BES12 when it uses BlackBerry Administration Service or BES12 authentication. Use this parameter when you specify /basauthtype bas_auth. 52

53 Running the BlackBerry Enterprise Transporter from the command prompt Parameter 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 cancel 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 or BES12 management console. Verify that the user accounts are assigned to the correct BlackBerry Enterprise Server instance or BlackBerry Enterprise Service instance, group, IT policy, and software configuration. Note: If you move user accounts to a destination BES5 or BES12, there might be a delay before the selected IT policies or group-assigned IT policies are sent to devices. During this delay, the Default IT policy is applied to the devices. 53

54 Return user accounts to the source EMM domain Return user accounts to the source EMM domain 11 To return user accounts to the source EMM domain, you must run the migration process a second time. You must set the former destination EMM domain as the source domain, and the former source EMM domain as the destination domain. Before you begin: Back up the source and destination BlackBerry Configuration Database or BES12 databases. 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 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 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 database. 9. Click Done. 10. Preview the migration process. Resolve any issues. 11. Move the user accounts. 54

55 Troubleshooting Troubleshooting 12 Configuration errors and warnings The BlackBerry Enterprise Transporter cannot connect to the BlackBerry Administration Service Possible cause If you configured Internet Explorer to use a proxy server by default, the BlackBerry Enterprise Transporter might not be able to connect to the BlackBerry Administration Service or BES12. 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 This message appears when the BlackBerry Enterprise Transporter configuration file (EnterpriseTransporter.exe.config) contains invalid information. Possible solution Try performing the following actions: Read the additional information that is displayed with the error message to determine the problem. 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. 55

56 Troubleshooting XML Manifest Failed to Load 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. One or more user accounts do not have a Destination Server set This message appears if you did not select a destination BlackBerry Enterprise Server or BES12 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 to apply to specific user accounts. Troubleshooting preview errors ERROR: Destination contains servers older than 5.0 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 EMM domain. Possible solution Upgrade all BlackBerry Enterprise Server instances in the destination EMM domain to 5.0 or later, and then run the BlackBerry Enterprise Transporter. 56

57 Troubleshooting Application error messages Failed to initialize <source/destination> database connection This message appears when the BlackBerry Enterprise Transporter cannot connect to the specified database, or the database is not a valid BlackBerry Configuration Database or BES12 database. Possible solution Try performing the following actions: Verify that the server that hosts the BlackBerry Configuration Database or BES12 database is running and that the database is running. Verify that the information that you specified for the 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 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, 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 \<username>\appdata\roaming\blackberry\blackberry Enterprise Transporter\Manifests. If you are running the BlackBerry Enterprise Transporter in bulk mode, verify the names of the database servers that host the BlackBerry Configuration Database or BES12 database in the source and destination EMM domains, 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\<username>\appdata\roaming\blackberry\blackberry Enterprise Transporter\Manifests. Manifest Validation Error This message appears when the manifest file does not conform to the manifest.xsd schema. 57

58 Troubleshooting 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\<username>\AppData\Roaming\BlackBerry\BlackBerry Enterprise Transporter\Manifests. User validation error messages No users have been activated on destination server - user may lose some device functionality 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 devices activated. Possible solution Perform one of the following actions: Use the BlackBerry Administration Service or BES12 to activate the user accounts again. Use the BlackBerry Administration Service or BES12 to remove user accounts from the BlackBerry Enterprise Server or BES12, then create and activate a test user account. Try migrating user accounts to the destination BlackBerry Enterprise Server or BES12 database again. Destination server does not support the current encryption scheme This message appears when the destination BlackBerry Enterprise Server or BES12 does not support the encryption scheme that is used by the source BlackBerry Enterprise Server or BES12. 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 and destination BlackBerry Enterprise Server or BES12 to use the same encryption algorithm and try to move the user accounts again. 58

59 Troubleshooting User not found in source This message appears when the BlackBerry Enterprise Transporter cannot find a user record in the source EMM domain with the address that is specified in the manifest file. Possible solution Try performing the following actions: Verify that the source EMM domain and the address of the user account are correct in the manifest file. By default, the manifest file is located at <drive>:\users\<username>\appdata\roaming\blackberry\blackberry Enterprise Transporter\Manifests. Verify that the user account exists in the source EMM domain. User already exists in destination This message appears when the BlackBerry Enterprise Transporter finds that a user account already exists in the destination EMM domain with the address of a user account that is specified in the manifest file. Possible solution Try performing the following actions: Verify that the destination EMM domain is correct in the manifest file. By default, the manifest file is located at <drive>:\users\<username>\appdata\roaming\blackberry\blackberry Enterprise Transporter\Manifests. Verify that the address of the user account is typed correctly in the manifest file. SrcRoutingInfo is null or empty This message appears when there is no routing information for the user account in the source BlackBerry Configuration Database or BES12 database. The user account might not be active. The user's BlackBerry OS 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 or BES12 again, then try to move the user account to the destination BlackBerry Enterprise Server or BES12. 59

60 Troubleshooting Run the BlackBerry Enterprise Transporter with the Ignore warnings option selected and activate the user account on the destination BlackBerry Enterprise Server or BES12 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 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 EMM domain. The user ID must be preserved so that the device can work correctly. This message appears only if the BlackBerry Enterprise Server instances in the destination EMM domain are not version 5.0 or 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. < _address> Skipping WLAN configuration due to empty WLANBaseConfigSet: ConfigName This message appears when the BlackBerry Enterprise Transporter does not move the Wi-Fi profile information for a user account because the Wi-Fi profile base configuration set is empty. Possible solution After the migration process completes, configure the Wi-Fi profile base configuration on the destination BlackBerry Enterprise Server using the BlackBerry Administration Service. < _address> Unable to parse device version string: "Version found in database" 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 or BES12 database. The BlackBerry Device Software version might not exist in the database. Possible solution Move the user account to the destination BlackBerry Enterprise Server with the Ignore Warnings option selected. 60

61 Troubleshooting < _address> Failed to load UserConfig row for user This message appears when the BlackBerry Enterprise Transporter cannot load the user account information from the UserConfig table in the source BlackBerry Configuration Database or BES12 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. < _address> Failed to load PIM Sync data for user 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 or BES12 database. Possible solution Check the BlackBerry Enterprise Transporter log file for Microsoft SQL Server errors to identify which tables in the database were affected. If possible, correct the problem and try to move the user account again. < _address> Incomplete SWITCH_SERVICE command data 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 or BES12. 61

62 Troubleshooting User validation warning messages Invalid PIN 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 or BES12. 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 or BES12 after the migration process completes. User status on the source BlackBerry Enterprise Server instance is not "Running" The status of the user account on the source BlackBerry Enterprise Server or BES12 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 or BES12, then retry the migration. Run the migration process with Ignore warnings selected, then activate the user account on the destination BlackBerry Enterprise Server or BES12 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. 62

63 Troubleshooting User migration failed messages VALIDATION / FAILED 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. MIGRATION / FAILED This message appears when the BlackBerry Enterprise Transporter cannot add the data for the user account to the destination BlackBerry Configuration Database or BES12 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\<username>\appdata\roaming\blackberry\blackberry Enterprise Transporter\Logs. Verify that the destination database is online. Verify that you have the required permissions to insert records into the destination database. SWITCH_SERVICE / FAILED This message appears when the destination BlackBerry Policy Service or BES12 reports an error after it tries to send the Switch Service command to the BlackBerry OS device. Possible solution Check the log file for the BlackBerry Policy Service or BES12 to determine the cause of the error. By default, the log files are located at <drive>:\program Files (x86)\blackberry\blackberry Enterprise Server\Logs on the computer that hosts the BlackBerry Policy Service or BES12. Check the device's event log to determine the cause of the error. For more information about accessing the event log, visit to read KB

64 Troubleshooting User migration completed with warning messages SET_IT_POLICY / FAILED This message appears when the IT policy sent from the destination BlackBerry Enterprise Server or BES12 is not successfully applied to the BlackBerry OS device after the migration process completes. Possible solution Try performing the following actions: Manually resend the IT policy from the destination BlackBerry Enterprise Server or BES12. If you still cannot apply the IT policy, reactivate the device on the destination BlackBerry Enterprise Server or BES12. 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 or BES12. Any other task / FAILED or NOT_STARTED This message appears if some other task did not complete 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 \<username>\appdata\roaming\blackberry\blackberry Enterprise Transporter\Logs. User migration pending error messages SWITCH_SERVICE or SET_IT_POLICY / PENDING These messages appear when the BlackBerry Enterprise Server or BES12 sends the Switch Service command or the Set IT Policy command to the BlackBerry OS device, but the command does not complete. The device might be turned off, outside of a wireless coverage area, or inactive. 64

65 Troubleshooting Possible solution Verify that the device is turned on and in a wireless coverage area. Use the BlackBerry Administration Service or BES12 management console to reactivate the device and send the IT administration commands again. IT policy error messages Last IT Policy Command Failed or Pending These messages appear when the last Set IT Policy command that the source BlackBerry Enterprise Server or BES12 sent to the BlackBerry OS 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 or BES12 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 IT administration command fails, use the BlackBerry Administration Service or BES12 management console 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 This message appears when the BlackBerry Enterprise Transporter detects a condition where the destination BlackBerry Enterprise Server or BES12 might not be able to apply a new IT policy to the BlackBerry OS device that is associated with a user account. This can happen if the BlackBerry Device Software is earlier than version 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 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

66 Troubleshooting 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. 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 or BES12. User account status: MigrationSkippedDueToValidationFailure On the Report tab, this status message appears for user accounts that were not moved to the destination BlackBerry Enterprise Server or BES12 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. 66

67 Port information for the BlackBerry Enterprise Transporter Port information for the BlackBerry Enterprise Transporter 13 Connection Connection type Default port number BES12 database TCP 1433 BES12 TCP 443 BlackBerry Configuration Database TCP 1433 BlackBerry Enterprise Server TCP 443 BlackBerry Enterprise Server Express TCP

68 Glossary Glossary 14 AES API Advanced Encryption Standard application programming interface BES5 BlackBerry Enterprise Server 5 CAL CR DES EMM EMM domain A BlackBerry Client Access License (BlackBerry CAL) limits how many users you can add to a BlackBerry Enterprise Server. carriage return Data Encryption Standard Enterprise Mobility Management An EMM domain consists of a BlackBerry database and any BlackBerry services or components that are associated with it. An EMM domain can refer to any of the following environments: BES12 domain: A BES12 database and any BES12 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 BlackBerry Enterprise Server: A BlackBerry Configuration Database and any BlackBerry Enterprise Server components that are associated with it FQDN IBM DB2 UDB IP IP address SRP Triple DES UAC WLAN fully qualified domain name IBM DB2 Universal Database Internet Protocol 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. Server Routing Protocol Triple Data Encryption Standard User Account Control wireless local area network 68

69 Legal notice Legal notice 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 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 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, 69

70 Legal notice 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. 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. 70

71 Legal notice 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 71