Enterprise Deployment Guide

The current Windows package is an Inno Setup installer (single .exe):

https://corxor.com/download/windows
  → QuickSecure_Setup.exe

An MSI build is not currently provided. If your tooling requires MSI, see "Future improvements" below.

Use the standard Inno Setup silent switches. These are supported on every Inno-built installer:

QuickSecure_Setup.exe ^
  /VERYSILENT ^
  /SUPPRESSMSGBOXES ^
  /NORESTART ^
  /SP- ^
  /LOG="C:\ProgramData\QuickSecure\Logs\install.log"

Exit codes: 0 = success, 3010 = success-with-reboot-required (do not auto-reboot during business hours), other = failure (consult the /LOG file).

Note: /S is NSIS syntax and is not used by Inno Setup. /LICENSE=, /TENANT=, and similar custom parameters are not currently supported by the QuickSecure installer — supply the license via the config seed below instead.

The agent reads its tenant binding and license key from a config seed your deployment tool places before the agent first starts. The agent consults these sources before any user interface and will not prompt the user when a seed is present.

Primary — JSON file:

C:\ProgramData\QuickSecure\quicksecure.config.json

{
  "licenseKey": "QSEC-XXXX-XXXX-XXXX-XXXX",
  "tenantId": "00000000-0000-0000-0000-000000000000",
  "cmsBaseUrl": "https://corxor.com"
}

Fallback — registry:

HKLM\SOFTWARE\Corxor\QuickSecure
    LicenseKey   REG_SZ
    TenantId     REG_SZ
    CmsBaseUrl   REG_SZ

Restrict ACLs on both sources to SYSTEM and Administrators only. Never pass the license key on the installer command line — it would appear in process telemetry, command-line auditing, and SCCM logs.

1. Your deployment tool (GPO, Intune, SCCM, RMM) installs QuickSecure_Setup.exe silently and writes the config seed.
2. The QuickSecure service starts, reads the seed, and calls POST /api/telemetry/endpoints/register with the license key and a stable hardware ID.
3. The server returns a per-device API key. The agent persists it and begins heartbeats every five minutes.
4. The endpoint appears as Active in the Corxor Command Center within one heartbeat cycle.

• Active Directory — Computer-side Group Policy startup script (Inno .exe cannot be deployed via the GPO Software Installation node, which requires MSI).
• Microsoft Intune — Win32 app wrapped with IntuneWinAppUtil, run as System.
• SCCM / MECM — Script Installer deployment type, install for system, hidden, suppress reboot.
• RMM tools (NinjaOne, Datto, ConnectWise, etc.) — Run a wrapper PowerShell script as SYSTEM.

Step-by-step instructions, registry detection rules, troubleshooting, and key-rotation procedures are in the full administrator guide at Admin → Management → Help → Enterprise Deployment (/Admin/Management/Help/EnterpriseDeployment, sign-in required).

All endpoints report to the Corxor Command Center. Administrators can:

• Monitor all endpoints in real time
• Review and approve AI threat decisions
• Configure AutoPilot for automated responses
• Generate compliance reports

The following are on the roadmap and not currently supported by the installer:

• Native installer command-line parameters for license and tenant (e.g. /LICENSE=, /TENANT=) so a wrapper script is not required.
• MSI package for AD GPO Software Installation node compatibility.
• Per-tenant "Generate Deployment Bundle" download in the portal (installer + pre-filled seed + wrapper, as a single .zip).