- 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
- Advanced server configuration
- Configure IIS processor affinity
Configure IIS processor affinity
On multi-CPU servers, application pools can be configured to establish affinity between worker processes and an individual processor to more efficiently use CPU caches. This configuration also isolates applications such that if one application causes a CPU to stop responding, other CPU’s continue to function normally. Processor affinity is used in conjunction with the processor affinity mask setting to specify CPUs.
- Create a .vbs file named affinity.vbs, copy the following data, and save it in your temp folder.set appPoolObj=GetObject("IIS://localhost/W3svc/AppPools/DefaultAppPool") ' Set the properties. Enable processor affinity for processors 0,1,2,3: appPoolObj.Put "SMPAffinitized", TRUE appPoolObj.Put "SMPProcessorAffinityMask", &HFF ' Save the property changes in the metabase: appPoolObj.SetInfo WScript.Echo "After: " & appPoolObj.SMPAffinitized & ", " & appPoolObj.SMPProcessorAffinityMask
- Change the value ofSMPProcessorAffinityMaskinaffinity.vbsto reflect the number of cores available.The value for SMPProcessorAffinityMask must be entered as hexadecimal.
- Complete any of the following tasks:TaskStepsSpecify specific cores to use.Create the value as binary (each core is represented by 1 bit) and then transformed into a hexadecimal. The easiest way to do this is to use a Windows scientific calculator.For example, eight cores in binary would be represented as 11111111.Specify to use only the first four cores. For example, all cores in the same chip for a quad-core)Select 00001111 or 11110000 (if dual-quad.)Specify to use every other core.
- Enter10101010(or01010101) in a Windows scientific calculator in binary data (Bin) and clickHexto see the equivalent value in hexadecimal (&AA or &55).
- Stop IIS and run theaffinity.vbsfile in a command prompt. (cscript affinity.vbs)You should see the mask change to the correct decimal value for the hexadecimal value that was used. If you are not sure what the decimal value should be, check the Windows calculator.
- Reset the IIS.
- Open the Performance Monitor (perfmon) performance tab to verify that the correct core combination is used.