Installation and Administration Guide

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

Published: 2014-11-06 SWD-20141106165936643

Contents What is BES12?... 6 Key features of BES12...6 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... 10 Validation that the BlackBerry Enterprise Transporter performs... 11 Global validation... 11 User validation... 12 System requirements...14 System requirements: BlackBerry Enterprise Transporter...14 Installation considerations... 15 Supported environments...15 Unsupported features and environments... 20 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... 23 Configure how long the BlackBerry Enterprise Transporter waits for the Microsoft SQL Server to process commands... 24 Encrypt the information about database connections in the configuration file...24 Premigration considerations... 26 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... 28 BlackBerry Enterprise Server compatibility...29 Moving user accounts to a destination BES12... 29 Moving user accounts to a destination BlackBerry Enterprise Server 5.0 or later... 30 Moving user accounts to a destination BlackBerry Enterprise Server 4.1.4 to 4.1.7... 30

Moving user accounts to a destination BlackBerry Enterprise Server 4.1 to 4.1.3 or 4.0 to 4.0.6...31 Moving user accounts to a destination BlackBerry Enterprise Server 4.0.7...31 BlackBerry Device Software compatibility... 32 Moving user accounts to a destination BES12... 33 Moving user accounts to a destination BlackBerry Enterprise Server 5.0 or later... 33 Moving user accounts to a destination BlackBerry Enterprise Server 4.1.4 to 4.1.7... 34 Moving user accounts to a destination BlackBerry Enterprise Server 4.1 to 4.1.3 or 4.0 to 4.0.6...35 Moving user accounts to a destination BlackBerry Enterprise Server 4.0.7...35 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... 38 Configure the BlackBerry Enterprise Transporter to skip certificate validation... 38 Preparing to move user accounts... 40 Create the manifest file... 40 Configure the source and destination database instances...40 Configure the default settings to apply to the user accounts that you migrate... 41 Configure the BlackBerry Enterprise Transporter to send notification email 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... 44 Search for and select user accounts to move...44 Import a file with email addresses... 45 Add the information for a single user account...45 Bulk mode: Selecting user accounts to migrate... 46 Enable bulk mode to select all user accounts that are associated with a source BlackBerry Enterprise Server or BES12...46 Configure the default settings to apply to specific user accounts... 46 Moving user accounts...48 Preview the migration process...48 Prequisites: Moving user accounts to a different EMM domain... 48 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... 50 Preview the migration process using the command prompt... 50

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

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

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 www.blackberry.com/support/business. 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 5.0.4.10 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

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 5.0.4 and use the BlackBerry Enterprise Transporter to move user accounts to the new BlackBerry Configuration Database. You can also move user accounts from a production domain to a test domain and back. When you run the BlackBerry Enterprise Transporter, users do not need to delete BlackBerry 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 www.blackberry.com/go/serverdocs 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

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

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

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

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 email 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 email 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 4.0.2 and the ITPolicyKeyMapping table does not exist. The device is running BlackBerry OS version 4.3.0. In an IBM Domino environment, the tool performs the following actions: If SkipDominoBBSDReplication is set to True in the EnterpriseTransporter.exe.config file, the tool verifies whether the user s BlackBerry state database already exists on the destination BlackBerry Enterprise Server. Verifies that the user s source BlackBerry state database can be opened on the source BlackBerry Enterprise Server. Verifies whether the user s BlackBerry state database has been marked for deletion in the BlackBerry profiles database on the destination 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

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

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

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

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 email application Any version of Microsoft Exchange that the BlackBerry Enterprise Server supports. Any version of Domino later than 6.5.4 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

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 BES12 5.0.4 BES12 S S 5.0.4 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

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 4.0-4.0.6 4.0.7 4.1-4.1.5 4.1.6-4.1.7 5.0 5.0.1 5.0.2 5.0.3 5.0.4 4.0-4.0.6 NS NS BE BE BE BE BE BE BE 4.0.7 NS NS BE BE S S S S S 4.1-4.1.5 NS NS BE BE BE BE BE BE BE 4.1.6-4.1.7 NS NS BE BE S S S S S 5.0 NS BO NS BO S S S S S 5.0.1 NS BO NS BO S S S S S 5.0.2 NS BO NS BO S S S S S 5.0.3 NS BO NS BO S S S S S 5.0.4 NS BO NS BO S S S S S Related information BlackBerry Enterprise Server compatibility, 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

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 4.0.7 and 4.1.7 BlackBerry Professional Software 4.1.4 BlackBerry Enterprise Server Express 5.0.1 BlackBerry Enterprise Server Express 5.0.2 and later BlackBerry Enterprise Server 4.0-5.0.1 BlackBerry Enterprise Server 5.0.2 and later BlackBerry Enterprise Server Small Business Edition 4.0.7 and 4.1.7 BlackBerry Professional Software 4.1.4 BlackBerry Enterprise Server Express 5.0.1 BlackBerry Enterprise Server Express 5.0.2 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

System requirements BlackBerry Enterprise Server 4.0-5.0.1 BlackBerry Enterprise Server 5.0.2 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 4.3.0 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

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 www.blackberry.com/go/serverdocs 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

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

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 www.blackberry.com/support/business, 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

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

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

Premigration considerations Premigration considerations 6 Preparing the source EMM domain for the migration process For more information about managing the BlackBerry Enterprise Server, visit www.blackberry.com/go/serverdocs to read the documentation for the BlackBerry Enterprise Server. Task 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 email 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 <emailaddress1> <emailaddress2> <emailaddress3> 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

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

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 www.blackberry.com/go/serverdocs 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

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

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 4.1.4 to 4.1.7 If you move user accounts to a destination BlackBerry Enterprise Server that is version 4.1.4 to 4.1.7, consider the following information: Consideration 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