Before installation
Create and publish a configuration file on an HTTPS web server. The URL can be customer-specific, while a generic hosted configuration provides a fallback.
Keep the configuration public but non-sensitive.
The JSON file contains support contact information and trusted links. It must not contain passwords, API keys or other secrets.
Deployment outline
- Download the current application package.
- Publish the customer JSON file and branding assets over HTTPS.
- Run the installation command with the primary configuration URL and, where required, a fallback URL.
- Confirm the icon appears for the signed-in user.
- Open Support Details and verify branding, links and computer information.
Configuration refresh
The application loads configuration at startup and then refreshes periodically. It also rechecks network-dependent information after the primary internal IPv4 address changes.
Remote Desktop Services
One instance runs in each interactive Windows session, allowing every signed-in user to see their own username while sharing the same computer and support configuration.
Detailed command line
The final installer command and scripted deployment examples will be published here with the first packaged release.