- 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
- Install BlackBerry AtHoc
- Install the application server
Install the application server
When you install a standalone application server (where the database is on a separate server), the installer prompts for the
BlackBerry AtHoc
database server to connect to. The AtHoc
installer creates a trusted connection to the database, which uses the current user's domain account. The account must have a sysadmin login in the SQL Server.If a trusted connection cannot be used, you can specify an account for the
AtHoc
installer to use by appending the following parameters to the msiexe command line in the .bat file:- IS_SQLSERVER_AUTHENTICATION=1
- IS_SQLSERVER_USERNAME=sa_account_name
- IS_SQLSERVER_PASSWORD=sa_account_password
- To start the installation by opening an elevated command prompt, navigate to the folder with the .bat file, type the .bat file name, and press Enter to 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, then right-click on cmd.exe and chooseRun as Administrator. If theUser Account Controlwindow appears, clickYesto run the Windows Command Prompt as Administrator.
- On theWelcomescreen, clickNext.
- Accept the Software License Agreement. ClickNext.
- Choose theApplication Servercheck box. ClickNext.
- If using a named instance, manually enter the server name or IP and instance name.
- ClickTest Connection. TheAtHocTest Connection script tests the connection through the ngad account and the SQL databases and it tests a trusted connection that does not include the user ID and password.
- Specify the application server home folder to install theBlackBerry AtHoccomponents. ClickChangeto browse to the location that you want, or clickNextto accept the default location.
- Enter the system URL to accessBlackBerry AtHocClickNext. Use a fully qualified URL.
- Specify the IIS configuration type:
- The type of setup: ChooseEnterprise Setupfor a regular configuration.
- The Web Site Settings for theBlackBerry AtHocweb application installation: Use the default web site or choose a new Web site that you want and provide the associated details.
- ClickInstallto begin the database server installation or clickBackto change the installation settings.
- View the onscreen progress bar to gauge the status of the installation.
- When the installation completes, clickFinishto exit the Setup Wizard.