Maintenance
Release Notes
BES12
Version 12.1 MR1
Published: 2015-04-08
SWD-20150408081254749
Contents
Fixed issues......................................................................................................................4
Known issues................................................................................................................... 6
Legal notice......................................................................................................................9
Fixed issues
Fixed issues
1
Installation and upgrade fixed issues
After you upgraded the BlackBerry Router it did not start automatically. (JI 913933)
You could not log in to BES12 if you used an SRP authentication key that began with the letter "T". (JI 898373)
When you were installing BES12 version 12.1 on a Windows 2012 server, if the Remote Access feature did not install correctly,
the BES12 software also failed to install. (JI 895875)
Management console fixed issues
If you deleted a BES12 group that had a matching BES5 role mapping in the database, the role was deleted instead of the
group. (JI 913574)
No matter the number of days that you set the expiry date for the enterprise activation password to be, in the discovery service
the expiry date displayed as 2 days. (JI 898814)
In some circumstances, you could not log in to the management console from the same computer where BES12 was installed.
(JI 898385)
When you edited a user's name, you could not add a slash (/), for example Chepesky/Mike. (JI 898378)
If you sent the Delete Only Work Data command to a device that uses Secure Work Space, the work data was not deleted from
the device. (JI 898369)
User and device management fixed issues
You might not have been able to activate Windows Phone devices. (JI 916780)
You might not have been able to activate BlackBerry 10 devices. (JI 899010)
iOS devices did not receive notifications. (JI 898375)
4
Fixed issues
BlackBerry Work Connect Notification Service fixed issues
The BlackBerry Work Connect Notification Service might have permitted a man in the middle to force the use of EXPORT level
ciphers to weaken the long-term key that the SSL server used. (JI 898371, JI 898955)
OpenSSL vulnerabilities existed in the version of Apache Tomcat that the BlackBerry Work Connect Notification Service used.
(JI 898364)
Log file fixed issues
The BlackBerry MDS Connection Service MDAT_web log file could become very large. (JI 898856)
5
Known issues
Known issues
2
Installation and upgrade known issues
When you upgrade from BES5 to BES12, the Microsoft Active Directory connection for BES5 is migrated automatically. This
connection supports all devices that connect to this directory. You do not have to create a Microsoft Active Directory connection
to this directory.
When you are preparing for a migration from one BES12 version 12.1 instance to another BES12 version 12.1 instance and one
of the BES12 Core instances in the source domain is not running, when you are filling in the fields in the Settings > Migration >
Configuration page on the target BES12 version 12.1 instance, an error message appears. (JI 878744)
Workaround: Before performing a migration ensure that all of the BES12 Core instances in the source domain are running.
If you migrate BlackBerry 10 devices from a BES10 server that has gatekeeping enabled to BES12, if the global Exchange
ActiveSync gatekeeping policy is set to block devices unless the devices are being managed, after the migration completes the
BlackBerry 10 devices do not synchronize with the email server. (JI 845628)
Workaround: In the BES12 management console, on the Exchange Gatekeeping page, if the device appears as allowed but the
Exchange server’s gatekeeping displays as blocked, changing the device’s status from Allowed to Blocked and then back to
Allowed forces the gatekeeping policy to synchronize with the BES12 server and allows the device to connect.
When you are migrating devices from BES10 to BES12, the CPU might reach 100%. (JI 808263)
Workaround: Perform these steps on all BES10 servers in your environment.
1.
Navigate to C:\Program Files (x86)\Research In Motion\BlackBerry Enterprise Service 10\EMWS\webapps\mdm\WEB-INF
\classes.
2.
In the PBMS.properties file, change the following settings:
•
pollTime=12
•
maximumRequestsPerMinute=2
3.
Restart the Enterprise Management Web Service.
4.
After device migration is complete, change the PBMS.properties file settings back to their original parameters and restart
the Enterprise Management Web Service.
After you upgrade from BES5 to BES12, if the BlackBerry Administration Service stops, when you restart the BlackBerry
Administration Service and log in to the console, the login screen keeps reloading. (JI 788051)
Workaround: Log out from BES12 and then after the BlackBerry Administration Service is running, log back in to BES12.
6
Known issues
After you upgrade from BES5 to BES12, if you use the Enterprise Transporter tool to move multiple users, when you click User
Summary > Advanced Settings you cannot assign anything to the users. (JI 787042)
User and device management known issues
If a device is out of compliance, in the Settings > About > Work Space screen on the device, a message might display that states
that the device is in compliance. (JI 880405)
After you activate a Windows Phone device, when you view the device report and export it to a .csv file, the .csv file shows data
while the device report does not. (JI 869624)
Management console known issues
You cannot activate a user’s device if the user has a username that begins with zero (0). (JI 879829)
Workaround: Use the email address to activate the device.
The OID shortcuts that are supported in the SCEP Subject field are “C,L,ST,O,OU,CN”. If any other shortcuts are used (either
directly or indirectly when an injection variable is replaced with its real value), then the dotted number format for the OID should
be used. For example, for “DC” which equals “Domain Component”, use “0.9.2342.19200300.100.1.25” which is the OID for
the short cut “DC”. (JI 879366)
If one of your organization’s Microsoft Active Directory users has a comma in their common name (for example, Chepesky,
Mike), the issued certificate will contain an invalid user DN (for example, for BlackBerry devices the name displays as Chepesky
\\\Mike, and for iOS devices the name displays as Chepesky). Any attempts to validate the CN fail. (JI 879213)
If you create a local user and do not enter an email address or a console password, when you try to edit the user you cannot
enter a console password. (JI 877986)
Workaround: Add an email address for the user, click Save, edit the user again, and enter a console password.
Secure Work Space for iOS and Android devices does not support SCEP, however some of the SCEP help tips refer to Secure
Work Space. (JI 876690)
When you use Mozilla Firefox to access the management console, if you specify an incorrect package ID when you create an
app lock mode profile for an Android device, after you click Save you cannot access the package ID field to enter a correct ID.
(JI 873858)
Workaround: Click on another tab and then click on the Policies and Profiles tab and create the app lock mode profile again.
The Company directory page might not display if validating all of the directory connections takes longer than 30 seconds. (JI
871164)
Workaround: Limit the number of directory connections that you create.
7
Known issues
When you create an Apple VPP account, if you use an apostrophe (') in the friendly name field, when you click on any app to
view the license usage information, the information does not display and you are redirected to the Apps tab. (JI 867927)
Workaround: Do not use an apostrophe when you create an Apple VPP account.
When you enable single sign-on for multiple Microsoft Active Directory connections, if the Microsoft Active Directory accounts
use the same passwords single sign-on does not work. (JI 853807)
Workaround: Do not use the same password on multiple directory connections.
On the dashboard, if you set the Device activations section to display a pie chart and no devices have been activated, the pie
chart displays as gray and no legend is available to explain the chart. (JI 841934)
On the dashboard, the Devices by carrier area does not include Windows Phone devices. (JI 813089)
In a BES12 and BES5 integrated environment, if you delete a BlackBerry OS user from the BlackBerry Administration Service
without selecting the "Delete the user and remove the BlackBerry information from the user’s mail system" option, and then
you add the same user to BES12 and activate a BlackBerry OS device for the user, the BlackBerry OS device information does
not display in the BES12 management console.
If you have assigned a user certificate to a user and then edit the user certificate profile to remove the assigned certificate and
add a different certificate, the new certificate is not shown in the management console and is not sent to the device. (JI
807990)
If your organization's environment contains BES5 and BES12, when you create users in BES5 and then you view the Directory
synchronization report in BES12, the users display in both the “User information update on BES12” and “User removal from
BES12” sections. (JI 795407)
The bwcn.log and local_host_access.log files are not stored in the same location. (JI 792988)
If the database is not accessible, no log files for the BES12 Core are created. (JI 758247)
BlackBerry Resource Kit known issues
If you use the BlackBerry Enterprise TransporterEnterprise Transporter tool to move users from a BES5 database that has been
upgraded to BES12, you cannot fully manage the users. (JI 798529)
8
Legal notice
Legal notice
3
©2015 BlackBerry. All rights reserved. BlackBerry® and related trademarks, names, and logos are the property of BlackBerry
Limited and are registered and/or used in the U.S. and countries around the world.
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. Apple and Safari are trademarks of Apple Inc. Android is a trademark of Google Inc. Mozilla and Firefox are
trademarks of Mozilla Foundation. Microsoft, Active Directory, ActiveSync, SQL Server, Windows, Windows Phone and Windows
Server are trademarks of Microsoft Corporation. All other trademarks are the property of their respective owners.
This documentation including all documentation incorporated by reference herein such as documentation provided or made
available 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, NONINFRINGEMENT, 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 NONPERFORMANCE OF ANY SOFTWARE, HARDWARE, SERVICE, OR ANY THIRD PARTY PRODUCTS AND SERVICES
REFERENCED HEREIN, ARE HEREBY EXCLUDED. YOU MAY ALSO HAVE OTHER RIGHTS THAT VARY BY STATE OR
PROVINCE. SOME JURISDICTIONS MAY NOT ALLOW THE EXCLUSION OR LIMITATION OF IMPLIED WARRANTIES AND
CONDITIONS. TO THE EXTENT PERMITTED BY LAW, ANY IMPLIED WARRANTIES OR CONDITIONS RELATING TO THE
DOCUMENTATION TO THE EXTENT THEY CANNOT BE EXCLUDED AS SET OUT ABOVE, BUT CAN BE LIMITED, ARE HEREBY
LIMITED TO NINETY (90) DAYS FROM THE DATE YOU FIRST ACQUIRED THE DOCUMENTATION OR THE ITEM THAT IS THE
SUBJECT OF THE CLAIM.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW IN YOUR JURISDICTION, IN NO EVENT SHALL BLACKBERRY
BE LIABLE FOR ANY TYPE OF DAMAGES RELATED TO THIS DOCUMENTATION OR ITS USE, OR PERFORMANCE OR NON-
9
Legal notice
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.
10
Legal notice
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
11