- Getting started
- System components and configuration
- BlackBerry AtHoc account requirements
- Install BlackBerry AtHoc
- Upgrade BlackBerry AtHoc
- Postinstallation or upgrade configuration
- Set antivirus file exclusions for database log and tempDB files
- IIS postinstallation checklist
- Application pool configuration tables
- Table 1: Application pool configuration
- Table 2: Application Pool - Web application associations for the AtHoc website - Enterprise configuration
- Table 3: AtHoc services application pool configuration
- Table 4: Application pools - web application association for AtHoc services web site
- IIS handler mappings
- Verification checklist
- Application pool configuration tables
- (Optional) Enable message termination
- (Optional) Enable and enforce the TLS 1.2 protocol
- (Optional) Configure the application server for Windows authentication
- (Optional) Configure client certificates on the application server
- (Optional) Set the SSL client certificate
- (Optional) Install certificates for cloud delivery services
- (Optional) Configure new access card formats for operator auto-login
- (Optional) Enable FIPS on each application server
- (Optional) Archive and MAS export service account requirements
- Configure .NET framework to use a web proxy
- (Optional) Restore the XML files for duplicated devices
- (Optional) Set up error pages for Self Service throttling
- (Optional) Set up error pages for Self Service throttling
- Advanced server configuration
- IIS 8.5 Security Technology Implementation Guide
- Server STIG
- IISW-SV-000103: Enable log file and Event Tracing windows
- IISW-SV-000107: Sufficient web server log records for location of web server events
- IISW-SV-000108: Sufficient web server log records for source of web server events
- IISW-SV-000110: Sufficient web server log records to establish the outcome of web server events
- IISW-SV-000111: Sufficient web server log records to establish identity
- IISW-SV-000112: Web server must use Event Tracing for Windows logging option
- IISW-SV-000120: Samples, examples, and tutuorials must be removed from production server
- IISW-SV-000124: Web server must have MIMEs that invoke OS shell programs disabled
- IISW-SV-000146: Web server must not impede ability to write log record content to an audit log
- IISW-SV-000153: Web server must maintain the confidentiality of controlled information during transmission
- IISW-SV-000154: Web server must maintain the confidentiality of controlled information during transmission
- Application STIG
- IISW-SI-000206: Enable log file and Event Tracing windows
- IISW-SI-000209: Sufficient website log records to establish identity
- IISW-SI-000210: Sufficient website log records to establish identity
- IISW-SI-000211: Website must use Event Tracing for Windows logging option
- IISW-SI-000214: Website must have MIMEs that invoke OS shell programs disabled
- IISW-SI-000228: Non-ASCII characters in URLs must be prohibited
- Server STIG
- Verifying BlackBerry AtHoc is operational
- Appendix A: Troubleshooting
- Appendix B: Organization duplicator object management
- BlackBerry AtHoc Customer Support Portal
- Legal notice
- BlackBerry Docs
- BlackBerry AtHoc
- BlackBerry AtHoc 7.9
- Installation and Configuration Guide
- Upgrade BlackBerry AtHoc
- Application server upgrade
Application server upgrade
During an upgrade, run the
AtHoc
installer (MSI) on the application server. The MSI uses a Windows authentication connection to SQL Server. Your server or domain login must have a login in SQL Server, and that login must be a sysadmin. See the note below if Windows authentication is not possible and you must use SQL Server authentication.If a trusted connection cannot be used, you can specify a specific account for the
AtHoc
Installer to use during the upgrade by appending the following parameters to the msiexec command line in the .bat file:- IS_SQLSERVER_AUTHENTICATION=1
- IS_SQLSERVER_USERNAME=sa_account_name
- IS_SQLSERVER_PASSWORD=sa_account_password
If you update the application and database servers on separate servers, you must run the
AtHoc
Installer (MSI) once on each application server. After all application servers have been upgraded, run the installer again on one of the application servers. You must upgrade all application servers before you upgrade the database server.
- Open an elevated command prompt, navigate to the folder with the .bat file, type the .bat file name, and pressEnterto run it. The .bat file name follows the naming convention "BlackBerry_AtHoc_7.9.x.x_build.bat."The .bat file distributed with the MSI generates a log file of the installer actions. The log file, ATHOC_yyyy_mm_dd_hh_mm_AM|PM.log, is created in the root of C:.
- To open an elevated command prompt, locate cmd.exe in the program search, right-click on cmd.exe, and chooseRun as Administrator. If theUser Account Controlwindow appears, clickYesto run the Windows Command Prompt as Administrator.)"
- In theWelcomescreen, clickNext.
- Accept the Software License Agreement. ClickNext.
- Agree to the upgrade prompt.
- Select theApplication Servercheck box. ClickNext.
- If any prerequisites are missing, the installer will display a message that lists them. ClickOKon the message to stop the upgrade. Install the prerequisites and run the MSI again.For detailed information about the prerequisites, see Requirements: Application server installation.
- ClickInstall.