On-Prem Deployment
3 guides
On-Premise - Pre-requisites
For optimal performance of Halo on-premise deployment, use two separate servers for IIS Halo Application Hosting and SQL Server Database Hosting, each meeting specific hardware and OS requirements. Additional components like SQL Server Management Studio and various app installations are required. The servers must have internet access for license validation. Ensure necessary files are downloaded and configured, such as Dotnet Hosting and IIS Rewriter. Any special configurations or issues should be communicated prior to deployment to ensure proper preparation.
On-Premise Deployment - Troubleshooting
The article provides troubleshooting tips for on-premise Halo deployments. It suggests checking API and Auth logs in the Halo WebApp for issues, ensuring proper SQL Server setup with enabled remote connections, appropriate user permissions, and correct server configurations. It advises verifying IIS and network settings, including DNS and Firewall rules. Licensing and TLS protocol issues are also addressed, recommending using TLS 1.2 or higher. Network connectivity checks like pinging and flushing DNS entries are suggested to resolve connectivity issues.
On-Premise Deployment - Windows Authentication
The article discusses using Windows NT Integrated Authentication for connecting the Halo WebApp with the Halo Database. While SQL Authentication is recommended for ease and efficiency, Windows Authentication can also be used but requires additional steps. Key steps include creating a new login in SQL Server Management Studio (SSMS) using Windows Authentication, configuring IIS application pools with the Windows user account, and updating the web app configuration. Testing ensures that Windows Authentication is functioning for the Halo's on-premise instance.