Windows: Windows installation and first access
Use the release package for the target system and deployment role. The installer prepares the required database, cache and Python environment.
Choose the installation role
Run the installer as an administrator. The default root is C:\HQControl; another fixed local drive can be selected if it meets the installer requirements.
- Choose full for a complete host, managed data services and Python on one machine.
- database installs PostgreSQL, TimescaleDB and Redis only. host installs the host and Python and uses prepared data services on the same machine.
- Use dedicated-node only for an IO runtime with a prepared schema and same-machine PostgreSQL / Redis managed outside the installer. It provides no Web, Alarm, Trend or Python runtime. The client profile installs only client trust and access shortcuts.
- Check mode, directory and dependencies before continuing. A mode locked by the installer entry cannot be changed.
Configure Portal and Screen addresses
The default Portal uses HTTPS port 8080 and the separate Screen origin uses HTTPS port 8081. Use the endpoints reported by the installation.
- Choose a host name or IP reachable by every client. Portal and Screen must be different HTTPS origins.
- Permit both endpoints for the intended clients and install the trusted certificate on those clients. PostgreSQL and Redis remain private, not client endpoints.
- Open the Portal and then an actual runtime screen to verify the Screen endpoint. After changing public addresses, restart as indicated and reopen the browser entry.
Check installed services
A complete host contains five runtime services: Web/App, IO, Alarm, Trend and Script.
- Check the five services, database and Redis in System Status, then inspect the current license on the License page.
- Windows service names are HQControl, HQControlIO, HQControlAlarm, HQControlTrend and HQControlScript.
- For unready services, check installation and service logs. Check Device connection and Tag values after configuration.
