Release Notes. BlackBerry Enterprise Mobility Server

Transcription

1 Release Notes BlackBerry Enterprise Mobility Server

2 Published: SWD

3 Contents BEMS (SR1)... 4 Fixed issues... 4 Known issues... 5 BEMS Fixed issues... 9 Known Issues Legal... 13

4 BEMS (SR1) BEMS (SR1) 1 What's new in BEMS version (SR1) This release of BEMS features the following enhancements: Item Persistent group chat Description BEMS now supports persistent chat for users in your Skype for Business and Microsoft Lync Server 2013 environments. You can allow users to create and participate in multi-party chat rooms, including sending and receiving files, using the Skype for Business and Microsoft Lync Server 2013 persistent chat capability in BlackBerry Connect. For more information about this feature, see the BlackBerry Connect Administration content for your environment. Fixed issues When you configured the Connect service and Presence service in the BEMS Dashboard, the Application ID and the Application Endpoint dropdown lists are blank. (FIRST-14273) For more information, visit support.blackberry.com/kb to read article When you performed a non-silent mode installation, upgrade, repair or modify using a response file, the Services screen in the installer was not preloaded with the specified values. (FIRST-14235) After upgrading BEMS, some users did not receive real-time Exchange notifications until BEMS was restarted. The BEMS log files logged the message AWAIT_HEARTBEAT. (FIRST-14194) For more information, visit support.blackberry.com/kb to read article Some ios device users were unable to send encrypted messages to contacts outside of their organization and the following error messages displayed Unable to Encrypt. Unable to find certificates for any recipients. (FIRST-14105) For more information, visit support.blackberry.com/kb to read article When logged in to two devices enabled with persistent chat, users experienced the persistent chat features disappearing on ios devices. (GEMSS-5962) 4

5 BEMS (SR1) When logged in to two devices enabled with persistent chat, users might have experienced the group discussion disappearing from the Chats list on the ios device. (GEMSS-5958) When you changed the instant messaging service from Microsoft Lync Server 2010 to Skype for Business and upgraded BEMS, BEMS continued to detect Microsoft Lync Server 2010 as the instant messaging server. (GEMSS-5955) Note: If you upgrade from a version earlier than BEMS , you must upgrade BEMS before changing the instant messaging service. If BEMS isn t upgraded first, it continues to detect Microsoft Lync Server 2010 as the instant messaging server. For instructions on how to upgrade BEMS and change the instant messaging service, see the Installation Guide for your environment: BEMS in a Good Control and Good Proxy environment. BEMS in a BlackBerry UEM environment. When the environment was enabled with persistent chat, the Good Technology Connect service might have stopped responding with the error message Not enough storage is available to process this command. (GEMSS-5949) Known issues Users using non-ascii characters in their Microsoft Active Directory password cannot authenticate to the Docs share and receive the message Authentication required. (FIRST-14402) Workaround: Update the password to remove the non-ascii characters. For more information, visit support.blackberry.com/kb to read article The BEMS installer fails to validate the service account when one or more dollar symbols ($) are in the password, You receive one of the following error messages; Double dollar sign ($$) at the beginning or end of the password: Invalid User Account/Password. The user name or password is incorrect. Please enter a valid login and password. The login format must be <domain>\<user>. Single dollar sign ($) at the beginning or end of the password: Missing Information. Incomplete Administration Information. Administrator Login and Password are required fields. (FIRST-14394) Workaround: Update the password to remove the dollar sign ($). For more information, visit support.blackberry.com/kb to read article When you try to upgrade BEMS using a service account with a password that includes an Ampersand symbol (&), the upgrade is not successful. (G3SERVER-7487) Workaround: Update the password to remove the ampersand (&) and complete the upgrade. 5

6 BEMS (SR1) For more information, visit support.blackberry.com/kb to read article When you change the BEMS services, such as run the installer to remove the Mail service and install the Presence service during the same installation, the installer stops responding at 71%. The BEMS log files log the error message Failed to creating the component instance and the installation log files log the error message Failed to install BEMS Presence. (G3SERVER-7468) Workaround: Change the installed BEMS services individually. For example, run the installer to remove only the Mail service. Then, run the installer to install the Presence service. When you install or upgrade to BEMS to 2.6 and you use AlwaysOn availability for multi-subnets, the BEMS login page does not appear and the installation log files log the message Failed to unset Maintenance Mode in database: Unable to connect to the specified Database host. (G3SERVER-7446) Workaround: Add the MultiSubnetFailover flag using the Apache Karaf Web Console. 1. On each computer that hosts BEMS, open the Apache Karaf Web Console. Open a browser window and navigate to instance hostname>:8443/system/console/configmgr. 2. Scroll to and click com.good.server.core.datasource. 3. In the jdbc.url field, add the following property to the end of the connection string: MultiSubnetFailover=true. For example, Jdbc:sqlserver:// <Listener value>;databasename=<database name>;integratedsecurity=true;multisubnetfailover=true;. 4. Click Save. BEMS installation and upgrade becomes corrupt if the uninstall fails because it can't remove the install folder due to locks such as a command prompt open to the installation folder bin directory. (G3SERVER-7392) Note: Close all connections to the installer folder before performing a removal or upgrade of the BEMS instance. The Badge Count might display incorrectly if your environment is running in mixed mode, where one node is running a new version of BEMS and another node is running an older version of BEMS, and Mail settings in the BlackBerry Work app is set to New Mail. (G3SERVER-7102) Note: Running BEMS in a mixed mode is not a recommended configuration. When you analyze logs stored on a shared drive using the BEMS Lookout Tool, you receive an Internal Server Error message. Clicking the timestamp from the Audit logs section doesn't display the logs from the file. (G3SERVER-6871) Workaround: Copy the log files to a local drive and then analyze the log files using the BEMS Lookout Tool. Autodiscover fails for remote accounts when using NTLM authentication for web proxy, in a hybrid Microsoft Exchange environment, and when Enforce cert check is selected. (G3SERVER-6868, G3SERVER-5932) 6

7 BEMS (SR1) When you upgrade from JRE 7 to JRE 8, the certificates (for example, the BlackBerry Control and BlackBerry Proxy certificates) that were imported for JRE 7 are not carried forward to the JRE 8 folder. By default, the cacerts folder is located at C:\Program Files\JAVA1.8.0_<version>\lib\security. (G3SERVER-6808) Workaround: Complete one of the following workarounds: Re-import the certificates again to the JRE 8 folder and start the Good Technology Common Services. Disable SSL Certificate validation when communicating with the Microsoft Exchange Server and LDAP server. 1. In the BlackBerry Enterprise Mobility Server Dashboard, under BlackBerry Services Configuration, click Mail. 2. Click Microsoft Exchange. 3. Under the Autodiscover and Exchange Options section, clear the Enforce SSL Certificate validation when communicating with Microsoft Exchange and LDAP server checkbox. 4. Click Save. 5. Restart the Good Technology Connect service. There is a date and time conversion error when using the BEMS Lookout tool. (G3SERVER-6652) After the Good Technology Connect service is restarted, users might not receive some group discussion invitation notifications. (GEMSS-6219) Workaround: Have the user log out and log back in to BlackBerry Connect. When users upload a file using the BlackBerry Connect app, an unrelated message with the file name as a link appears on the Skype for Business and Lync desktop clients and the link does not work. Users can disregard the first message as a second message with a link that works for the same file and an icon or thumbnail appears immediately following it. (GEMSS-6138) When users upgrade the BlackBerry Connect app from version 2.4 to 2.5 with an active session, the persistent chat feature is not available. (GEMSS-5954) Workaround: Have the user log out and log back in to BlackBerry Connect. When upgrading BEMS 2.4 SR1 ( ) Cisco Jabber to BEMS 2.6 and then configuring Jabber for the Connect service for autodiscovery, the AXL application user name, password, and subdomain are not saved. (GEMSS-5933) Workaround: Restart the Good Technology Common Services after upgrading BEMS. Some users that are enabled for persistent chat and are members of more than 100 rooms don't receive invitations on the desktop client or BlackBerry Connect app when they are added as members to additional rooms. (GEMSS-5886) 7

8 BEMS BEMS What's new in BEMS version This release of BEMS features the following enhancements: Item Persistent group chat (Beta feature) Description BEMS now supports persistent chat for users in your Skype for Business and Microsoft Lync Server 2013 environments. You can allow users to create and participate in multi-party chat rooms using the Skype for Business and Microsoft Lync Server 2013 persistent chat capability in BlackBerry Connect. For more information about this feature, see the BlackBerry Connect Administration content for your environment. Multi-cluster Cisco Unified Communications Manager for IM & Presence BEMS now supports Cisco Unified Communications Manager for IM & Presence in a multicluster environment. This enables users to exchange instant messages and view presence status across multiple IM and Presence Service clusters to support Cisco Jabber chats in BlackBerry Connect. For more information about this feature, see the BEMS Installation and Configuration content for your environment. Autodiscovery service You can enable and disable HTTP Redirection and DNS SRV record lookups for retrieving the Autodiscover URL when discovering users for BlackBerry Work Push Notifications. For more information about this feature, see the BEMS Installation and Configuration content for your environment. Log file compression You can enable log file compression to save space on the hard drive. For more information about this feature, see the BEMS Installation and Configuration content for your environment. BlackBerry Dynamics Launcher enhancement BEMS now verifies the validity of images uploaded for customized BlackBerry Dynamics Launcher icons. For more information about this feature, see the BEMS Installation and Configuration content for your environment. Directory Lookup Service enhancement You can allow users in your environment to search for other users in the GAL using the user's phone number. 8

9 BEMS Item Description For more information about this feature, see the BEMS Installation and Configuration content for your environment. Synchronization API (For developers) The BEMS Synchronization API provides a service between BlackBerry Dynamics apps and third-party applications and BEMS for users to receive notifications when specific Uniform Resource Identifiers (URIs) such as bookmarks are not synchronized between the user s devices. For more information about this API, see the API Reference guides for your environment. Contact groups API (For developers) The BEMS contact groups API allows BlackBerry Work app and third-party applications to display the user's personal distribution lists. For more information about this API, see the API Reference guides for your environment. Fixed issues Some environments might have experienced increased memory usage in the LSASS process on BEMS instances running only the Mail service. (FIRST-14055) Some BlackBerry Connect for Android app users experienced the presence status change from "Away" to "Available mobile" automatically. (FIRST-13910) When you analyzed log files using the BEMS Lookout Tool and the BEMS name did not match, including case sensitivity, to the log file name in the config.cfg file, the BEMS Lookout Tool did not include the log file in the analysis. (FIRST-13807, G3SERVER-7273) After configuring content connectors on the BlackBerry Workspaces console, some environments experienced increased memory usage in the LSASS process. (FIRST-13824) Some users might have experienced not receiving BlackBerry Work Push Notifications. (FIRST-13798) In some environments when Kerberos constrained delegation (KCD) was configured for the BlackBerry Docs service, the Good Technology Common Services restarted automatically and generated dump files. (FIRST-13577) Some users might have experienced the contact list disappearing in BlackBerry Connect. (FIRST-13537, GEMSS-5262) Users with an underscore (_) in their SIP address were unable to log in to the BlackBerry Connect app. (FIRST-13528) 9

10 BEMS Users that specified the Set 'Away' after setting in the BlackBerry Connect app and then closed the app, retained the presence status from before the app was closed. (FIRST-13129) When you downloaded the BEMS SSL certificate using a Safari browser, you received an error message that the SSL certificate was not downloaded. (G3SERVER-7088) Resolution: Upgrade to Safari version When you tried uploading a customized icon for the BlackBerry Dynamics Launcher, if the file name had a space in it the file would not upload. (G3SERVER-6654) When the BlackBerry Connect app went into background and users created a new group and added a contact to the group using the desktop client, the contact did not synchronize to the BlackBerry Connect app when the app returned to the foreground. (GEMSS-3436) When users in a high availability environment sent messages from their BlackBerry Connect app to a contact and a BEMS instance was taken offline, the recipient user saw the notification in their BlackBerry Connect app, but the message didn't display immediately. (GEMSS-3398) Known Issues When you try to upgrade BEMS using a service account with a password that includes an ampersand symbol (&), the upgrade is not successful. (G3SERVER-7487) Workaround: Update the password to remove the ampersand (&) and complete the upgrade. When you change the BEMS services, such as run the installer to remove the Mail service and install the Presence service during the same installation, the installer stops responding at 71%. The BEMS log files log the error message Failed to creating the component instance and the installation log files log the error message Failed to install BEMS Presence. (G3SERVER-7468) Workaround: Change the installed BEMS services individually. For example, run the installer to remove only the Mail service. Then, run the installer to install the Presence service. When you install or upgrade to BEMS to 2.6 and you use AlwaysOn availability for multi-subnets, the BEMS login page does not appear and the installation log files log the message Failed to unset Maintenance Mode in database: Unable to connect to the specified Database host. (G3SERVER-7446) Workaround: Add the MultiSubnetFailover flag using the Apache Karaf Web Console. 1. On each computer that hosts BEMS, open the Apache Karaf Web Console. Open a browser window and navigate to instance hostname>:8443/system/console/configmgr. 2. Scroll to and click com.good.server.core.datasource. 3. In the jdbc.url field, add the following property to the end of the connection string: MultiSubnetFailover=true. 10

11 BEMS For example, Jdbc:sqlserver:// <Listener value>;databasename=<database name>;integratedsecurity=true;multisubnetfailover=true;. 4. Click Save. BEMS installation and upgrade becomes corrupt if the uninstall fails because it can't remove the install folder due to locks such as a command prompt open to the installation folder bin directory. (G3SERVER-7392) Note: Close all connections to the installer folder before performing a removal or upgrade of the BEMS instance. The Badge Count might display incorrectly if your environment is running in mixed mode, where one node is running a new version of BEMS and another node is running an older version of BEMS, and Mail settings in the BlackBerry Work app is set to New Mail. (G3SERVER-7102) Note: Running BEMS in a mixed mode is not a recommended configuration. When you analyze logs stored on a shared drive using the BEMS Lookout Tool, you receive an Internal Server Error message. Clicking the timestamp from the Audit logs section doesn't display the logs from the file. (G3SERVER-6871) Workaround: Copy the log files to a local drive and then analyze the log files using the BEMS Lookout Tool. Autodiscover fails for remote accounts when using NTLM authentication for web proxy, in a hybrid Microsoft Exchange environment, and when Enforce cert check is selected. (G3SERVER-6868, G3SERVER-5932) When you upgrade from JRE 7 to JRE 8, the certificates (for example, the BlackBerry Control and BlackBerry Proxy certificates) that were imported for JRE 7 are not carried forward to the JRE 8 folder. By default, the cacerts folder is located at C:\Program Files\JAVA1.8.0_<version>\lib\security. (G3SERVER-6808) Workaround: Complete one of the following workarounds: Re-import the certificates again to the JRE 8 folder and start the Good Technology Common Services. Disable SSL Certificate validation when communicating with the Microsoft Exchange Server and LDAP server. 1. In the BlackBerry Enterprise Mobility Server Dashboard, under BlackBerry Services Configuration, click Mail. 2. Click Microsoft Exchange. 3. Under the Autodiscover and Exchange Options section, clear the Enforce SSL Certificate validation when communicating with Microsoft Exchange and LDAP server checkbox. 4. Click Save. 5. Restart the Good Technology Connect service. There is a date and time conversion error when using the BEMS Lookout tool. (G3SERVER-6652) When logged in to two devices enabled with persistent chat, users might experience the persistent chat features disappearing on the ios device. (GEMSS-5962) 11

12 BEMS Workaround: Have the user log out and log back in to BlackBerry Connect. When logged in to two devices enabled with persistent chat, users might experience the group discussion disappearing from the Chats list on the ios device. (GEMSS-5958) Workaround: Have the user log out and log back in to BlackBerry Connect. When you change the instant messaging service from Microsoft Lync Server 2010 to Skype for Business and BEMS to version 2.6, you must upgrade BEMS before changing the instant messaging service. If BEMS isn t upgraded first, it continues to detect Microsoft Lync Server 2010 as the instant messaging server. (GEMSS-5955) For instructions on how to upgrade BEMS and change the instant messaging service, see the Installation Guide for your environment: BEMS in a Good Control and Good Proxy environment. BEMS in a BlackBerry UEM environment. When users upgrade the BlackBerry Connect app from version 2.4 to 2.5 with an active session, the persistent chat feature is not available. (GEMSS-5954) Workaround: Have the user log out and log back in to BlackBerry Connect. When the environment is enabled with persistent chat, the Good Technology Connect service might stop responding with the error message Not enough storage is available to process this command. (GEMSS-5949) When upgrading BEMS 2.4 SR1 ( ) Cisco Jabber to BEMS 2.6 and then configuring Jabber for the Connect service for autodiscovery, the AXL application user name, password, and subdomain are not saved. (GEMSS-5933) Workaround: Restart the Good Technology Common Services after upgrading BEMS. Some users that are enabled for persistent chat and are members of more than 100 rooms don't receive invitations on the desktop client or BlackBerry Connect app when they are added as members to additional rooms. (GEMSS-5886) BlackBerry Presence still appears in the dashboard after the server is modified to remove the BlackBerry Connect and BlackBerry Presence services. (GEMSS-5012) 12

13 Legal Legal BlackBerry Limited. Trademarks, including but not limited to BLACKBERRY, BBM, BES, EMBLEM Design, ATHOC, MOVIRTU and SECUSMART 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. Apache is a trademark of The Apache Software Foundation. Android is a trademark of Google Inc. Cisco and Cisco Jabber are trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. 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. JRE is a trademark of Oracle and/or its affiliates. Kerberos is a trademark of the Massachusetts Institute of Technology. Microsoft, Active Directory, SharePoint, and Skype are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Safari is a trademark of Apple Inc. 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. 13

14 Legal 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. 14

15 Legal 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 15