BES12 v12.5 Readme
With BES®12, you can say yes to the kind of productivity you know is possible—with the confidence that comes from industry-leading mobile security.
BES12 allows you to securely manage mobile devices and other endpoints across different operating systems (iOS®, Android™ – including Android™ for Work and Samsung KNOX™ – Windows®, OS X and BlackBerry®) and ownership models (personally owned or corporate liable devices).
Get started today with your BES12 Trial. Manage your mobile workers’ access to apps, data and content, all from a single, easy-to-use console that offers a complete set of IT policies and profiles.
Before you get started
- The image is set up with a default of a Windows® Server 2012 r2. Please see Microsoft TechNet for more information.
- Check for any updates to Windows Server 2012 to ensure you have the latest patches.
To use BES12 v12.5, you will need to activate your installation using signing keys. If you do not already have signing keys for your installation, you can request trial or production keys. You can provision a trial Secure Management Suite yourself simply by starting a BlackBerry Secure Management Suite Free Trial before you continue. You can also purchase production-use keys through the sales, or using your existing purchasing mechanisms.
For users installing the BES12 v12.5 base image
The BES12 v12.5 software is already on your desktop, so you can begin your installation once you receive your keys.
Note: Internet Explorer Enhanced Security Configuration has been disabled on this image in order to provide a seamless view of this README file when you connect to your running image. You can freely re-enable Internet Explorer Enhanced Security using Server Manager on your image.
Server Manager automatic startup has also been disabled on this image. You can safely re-enable Server Manager automatic startup by enabling the Server Manager scheduled task, through the Task Scheduler service, through Control Panel->Administrative Tools. To do this, find the Server Manager node under the Task Scheduler Library, and re-enable the startup task.
For users installing the BES12 v12.5 Dev/Test/Trial image
The image contains BES12 v12.5 and SQL Server 2014 Express with Tools, pre-installed. The installation of BES12 v12.5 is configured to use an instance of SQL Server 2014 Express for its data, named ‘BES’, and the SQL Server is configured with mixed mode security.
The pre-installed image uses several service accounts:
- BES12 Service Account (either local account or domain account, depending on image configuration):
Username: bes12service Password: P2ssw0rd
- SQL Server sa account:
Username: sa Password: P2ssw0rd
BES12 uses a local SQL Express 2014 database for this installation, in the form of a ‘(local)\bes’ instance. As this image is intended only for trial, or development and testing purposes, you are not required to change these credentials, however it is STRONGLY RECOMMEND you change them once installation and configuration is complete.
In order to change service account credentials, you need to update the service account password in Computer Management, or in Active Directory Users and Computers, depending on which option you chose at the image’s first launch.
You will also need to update the individual Windows Services Credentials for BES12. The following is a list of the services to be updated:
- BES12 - BlackBerry Affinity Manager
- BES12 - BlackBerry Dispatcher
- BES - BlackBerry Gatekeeping Service
- BES12 - BlackBerry MDS Connection Service
- BES - BlackBerry Work Connection Notification Service
The BES12 installation does not require the use of mixed-mode security in SQL Server, nor does it require the use of the ‘sa’ login. You can change the security mode and/or disable this login, BUT BE SURE to add your administrative credentials to the SQL Server instance, with administrative rights (sysadmin) BEFORE making these changes, to ensure you have sufficient rights to manage the SQL Server instance going forward.
For more information on configuring Windows Services Credentials, visit Microsoft TechNet