Quick Reference. Good for Enterprise to Good Work Transition Guide

Transcription

1 Quick Reference Good for Enterprise to Good Work Transition Guide

2 Published: SWD

3 Contents Good for Enterprise to Good Work transition guide... 4 Key concepts... 4 Steps to transition from Good for Enterprise to Good Work if you require MDM...5 Steps to transition from Good for Enterprise to Good Work if you do not require MDM... 6 Transition prerequisites...6 Planning your installation of Good Dynamics... 6 Planning your installation of the Good Enterprise Mobility Server... 7 Deployment readiness... 7 In Good Control, disable MDM...8 Decommissioning Good for Enterprise...8 Steps to migrate users...9 Activate an Android device on BES Activate an ios device on BES Install Good Work on an Android device if the user has been added to Good Control Install Good Work on an ios device if the user has been added to Good Control...11 Legal notice...12

4 Good for Enterprise to Good Work transition guide 1 This document explains how to plan a transition from Good for Enterprise to Good Work. Key concepts Product Good Dynamics Good Enterprise Mobility Server BES12 Description With the exception of Good for Enterprise, all Good apps now run on the Good Dynamics platform. ISV and custom enterprise apps are also built on the Good Dynamics platform. Good Proxy is the relay server and Good Control is the management console. See the GD Platform Overview for Administrators and Developers for a technical overview of the Good Dynamics platform. Good Enterprise Mobility Server is an application middleware server platform that provides various mobile backend services (MBaaS) from enterprise backends such as Microsoft Exchange, Microsoft Lync, and Microsoft SharePoint. These services are used by Good Work, other Good apps, and ISV apps built with the Good Dynamics SDK. The Good Enterprise Mobility Server delivers these as standardized backend services around push notifications, directory lookups, online presence, and more. BES12 is a multiplatform EMM solution from BlackBerry that provides comprehensive device, application, and content management with integrated security and connectivity. With BES12 you can: Manage the following device types: BlackBerry 10, ios, OS X, Android (including devices that use Android for Work and Samsung KNOX), Windows (including Windows 10 tablets and computers), and BlackBerry OS (version 5.0 to 7.1) Use a simple web-based interface to manage BYOD, COPE, and COBO devices and protect business information Manage complex fleets of devices using comprehensive reporting and dashboards, dynamic filters, and robust search capabilities Keep mobile workers connected with the information that they need 4

5 Steps to transition from Good for Enterprise to Good Work if you require MDM If you require MDM capabilities, it is recommended that you install BES12 and upgrade to Good Control. Step Action Plan the transition. Review the Good Work and Good for Enterprise comparison chart Document the Good for Enterprise policies and device management settings that you want to recreate in BES12. Create a plan to communicate the transition process to users. For resources, see Deployment readiness. Verify that your environment meets the minimum system requirements. For a list of considerations and minimum requirements, see Transition prerequisites and the Integrating BES12 and Good Dynamics content. Set up your new environment. Complete the steps in the Integrating BES12 and Good Dynamics content. Recreate security policies and device management settings from Good for Enterprise in BES12. For details on how to configure policies, profiles, and devices settings in BES12, see the BES12 Administration content. Instruct users to activate Good Work on their devices and then remove Good for Enterprise. For steps to activate an Android device on BES12 and install Good Work, see Activate an Android device in the Integrating BES12 and Good Dynamics content. For steps to activate an ios device on BES12 and install Good Work, see Activate an ios device in the Integrating BES12 and Good Dynamics content. After users install Good Work, they can remove Good for Enterprise from their devices. For instructions, see Install Good Work on users' devices. Decommission Good for Enterprise. For instructions, see Decommissioning Good for Enterprise. 5

6 Steps to transition from Good for Enterprise to Good Work if you do not require MDM If you do not require MDM, you do not have to install BES12. You can upgrade directly to Good Control. Step Action Plan the transition. Review the Good Work and Good for Enterprise comparison chart Document the Good for Enterprise policies that you want to recreate in Good Control. Create a plan to communicate the transition process to users. For resources, see Deployment readiness. Verify that your environment meets the minimum system requirements. For a list of considerations and minimum requirements, see Transition prerequisites. In Good Control, recreate settings for security policies from Good for Enterprise Make sure that MDM is not turned on in Good Control Instruct users to install on their devices and then remove Good for Enterprise. For instructions, see Install Good Work on users' devices. Decommission Good for Enterprise. For instructions, see Decommissioning Good for Enterprise. Transition prerequisites Before you transition from Good Work to Good for Enterprise, you must do the following planning: Planning your installation of Good Dynamics Planning your installation of the Good Enterprise Mobility Server Planning your installation of Good Dynamics When you install Good Dynamics you must set up two servers: Good Proxy and Good Control. For a complete technical overview, see the GD Platform Overview for Administrators and Developers and GD Server Deployment Planning and Installation. 6

7 Planning your installation of the Good Enterprise Mobility Server Your environment may require the advanced services that a Good Enterprise Mobility Server installation provides to Good Work and other Good Dynamics apps. For example, you may require Push Registration, Good Follow-Me, Good Presence, Good Directory Lookup, and Good Docs. For comprehensive guidance on installing Good Enterprise Mobility Server and deploying the services necessary to support Good Work and any other Good apps that you intend to deploy, see the GEMS Deployment Planning Guide, Preinstallation checklist, and GEMS Administration Guide for Administrators. Deployment readiness In addition to properly planning your infrastructure and deployment options, it is critical that you also prepare your internal support teams and the end users themselves for the migration. From a support perspective, there are important differences between the Good for Enterprise and Good Dynamics-Good Enterprise Mobility Server infrastructures differences that may require some level of training on troubleshooting, management, configuration, and user-related tasks, depending on each support team member's skill level and experience. Good Professional Services offers Administrator training for all products. This is especially recommended if your organization is new to Good Dynamics. On the client side, there are also major differences between Good for Enterprise and Good Work apps the way they are used and how they communicate with your enterprise. The following actions are therefore recommended to mitigate risk and maintain a positive user experience before and during the migration process: Familiarize your support teams with the Sleuth articles available in the Good Knowledge Base. These contain triage and troubleshooting steps to take for Good Work and any supporting Good Dynamics apps (Good Connect, Good Access, and so on) you deploy. These KB articles also include the details required by Good technical support if you cannot resolve a particular issue on your own. Providing the issue details, reproduction steps and client/server logs detailed in these articles greatly speeds up the issue resolution process. Provide clear communications to your end users regarding the migration process and what to expect when they move to Good Work. The user adoption kit available from Good includes product quick start guides, sample templates, and guidance on hosting internal promotional events, along with How to videos covering both the basic and advanced features of the Good Work app. Another valuable exercise is to take a selection of pilot users and closely capture their feedback during the pilot process. This will give you insight into the types of questions and issues you can expect when you go live. Understanding your users' tendencies and sensitivities will assist in developing communications and training specifically targeting your user community and support organizations. 7

8 In Good Control, disable MDM 1. In Good Control, under Settings, click Servers > Server Properties. 2. Deselect gc.mdm.enabled. 3. Click Submit. 4. Restart the Good Control services. For instructions, see Start or Restart the GC or GP Service in the Good Control help. Decommissioning Good for Enterprise Good for Enterprise and Good Work can co-exist on the same device. Depending on your organization s mobile device policies, you can allow a transition period for users to become familiar with Good Work while still having access to their and calendar from Good for Enterprise. You can eventually end the transition period using one of the following approaches. Hard Cutoff: You schedule a concrete cutoff date after which end users will no longer be able to access Good for Enterprise. The hard cutoff date is applied and enforced using the Wipe Container option in Good Mobile Control. Notify your users of the impending change through any standard communication channel that your organization uses. Immediately after the cutoff date, users must use Good Work to access the functionality previously provided by Good for Enterprise. Another option is to modify the policy for end users to make Good Work the authentication delegate; once the change goes into effect, users will no longer be able to use Good for Enterprise without downloading and provisioning Good Work. When users download and activate Good Work, they are prompted to create a new password for the new app, where Good for Enterprise and every other Good Dynamics app will use Good Work as the authentication delegate. Soft Cutoff: You let your end users choose when to move to the new platform. You provision them in advance to use Good Work after creating a compliance policy in Good Mobile Control to wipe Good for Enterprise when that device has not connected to the server after a set number of days. User entitlement to Good for Enterprise is then removed from the device. The Good for Enterprise app will still need to be uninstalled by the user. In both cases hard cutoff or soft cutoff you can monitor the adoption of Good Work and the lack of Good for Enterprise usage in the various reports available in Good Mobile Control. You can then proactively remove Good for Enterprise from your users' devices or wait for the migration to happen organically. For guidance on decommissioning the Good Mobile Messaging server, see Chapter 10 in the GFE Administrator's Guide. 8

9 Steps to migrate users Step Action In the Good for Enterprise client, turn off Contact Sync. On the device, remove the MDM profile. The Good for Enterprise client closes. If the user has been added to BES12, complete one of the following steps: Activate an Android device on BES12 Activate an ios device on BES12 If the user has been added to Good Control, complete one of the following steps: Install Good Work on an Android device if the user has been added to Good Control Install Good Work on an ios device if the user has been added to Good Control In Good Work, turn on Contact Sync. Activate an Android device on BES12 Send the following activation instructions to the device user. 1. On the device, install the BES12 Client. You can download the BES12 Client from Google Play. 2. On the device, tap BES12 Client. 3. Read the license agreement and tap I Agree. 4. Type your work address and tap Next. 5. If necessary, type the server address and tap Next. You can find the server address in the activation message you received or in BES12 Self-Service. 6. Confirm that the certificate details displayed on the device are accurate, and tap Accept. If your administrator sent you the certificate details separately, you can compare the information displayed with the information you received. 7. Type your activation password and tap Activate My Device. 8. Tap Next. 9. Depending on your security settings, you may be prompted to create a screen unlock option. 10. Tap Activate. 9

10 Good Dynamics will be configured on the device and, if your administrator has assigned you any apps, you will be prompted to install them. Activate an ios device on BES12 Send the following activation instructions to the device user. 1. On the device, install the Good for BES12 app. You can download Good for BES12 from the App Store. 2. On the device, tap Good for BES Read the license agreement and tap I Agree. 4. Type your work address and tap Go. 5. If necessary, type the server address and tap Go. You can find the server address in the activation message you received or in BES12 Self-Service. 6. Confirm that the certificate details displayed on the device are accurate, and tap Accept. If your administrator sent you the certificate details separately, you can compare the information displayed with the information you received. 7. Type your activation password and tap Activate My Device. 8. Tap Install to install the required certificate. 9. Good Dynamics will be configured on the device. If you are prompted to enter the password for your account or the passcode for your device, follow the instructions on the screen. 10. If your administrator has assigned you any apps, you will be prompted to install them. Install Good Work on an Android device if the user has been added to Good Control After users are added to Good Control, they receive an message with activation instructions. Included in the is the 15-digit access key that the user must enter to activate the app. Send the following activation instructions to the device user. 1. On your device, click the link to Google Play included in your invitation or get the app from Google Play. 2. Accept the Good Work device access requirements. 3. Tap Accept. 4. After the installation completes, tap Open. 5. Enter your address and your access key, and tap Go. 6. When secure communications have been established, set your application password and click Go. 7. Enter your corporate account password and tap Next. 8. Tap the Good Launcher to begin using the app. 10

11 Install Good Work on an ios device if the user has been added to Good Control After users are added to Good Control, they receive an message with activation instructions. Included in the is the 15-digit access key that the user must enter to activate the app. Send the following activation instructions to the device user. 1. On your device, tap the link to the App Store included in your invitation or get Good Work from the App Store. 2. After the installation completes, tap Open. 3. Enter your address and your access key, then tap Go. Or, if another Good Dynamics app like Good Access is a delegated authenticator, you can use its access key for Easy Activation. 4. When secure communications have been established, set your application password and tap Go. 5. Enable Touch ID by sliding its control to the On position (green). 6. Enter your corporate account password and tap Next. 7. If Kerberos authentication is enabled, you are prompted to also enter your domain each time to you log on to a new session in Good Work. 8. Tap the Good Launcher to begin using the app. 11

12 Legal notice Legal notice BlackBerry Limited. Trademarks, including but not limited to BLACKBERRY, BES, EMBLEM Design, GOOD, GOOD WORK, LOCK Design, MANYME, MOVIRTU, SECUSMART, SECUSMART & Design, SECUSUITE, SECUVOICE, VIRTUAL SIM PLATFORM, WATCHDOX and WORKLIFE are the trademarks or registered trademarks of BlackBerry Limited, its subsidiaries and/or affiliates, used under license, and the exclusive rights to such trademarks are expressly reserved. All other trademarks are the property of their respective owners. Android is a trademark of Google Inc. ios is a trademark of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries. ios is used under license by Apple Inc. OS X is a trademark of Apple Inc. Samsung KNOX and KNOX are trademarks of Samsung Electronics Co., Ltd. Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.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 on the BlackBerry website 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. 12

13 Legal notice 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, 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. 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. 13

14 Legal notice BlackBerry Enterprise Software incorporates certain third-party software. The license and copyright information associated with this software is available at 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 14