Install the collector on Windows (x64)

Overview

The Windows package installs the AssurIQ collector as a native Windows service, supervised by the Service Control Manager and configured to start automatically on boot.

Download the installer

Generate a one-time enrollment token from the site's collector setup page — this also gives you the exact download link and command for your account.

1. 1
   Open collector setup

   From the site record, choose Add Collector, then Windows (x64).
2. 2
   Generate a token

   Click Generate Token. The token is single-use, short-lived, and only its hash is ever stored by the control plane.
3. 3
   Copy the install command

   Copy the ready-made unattended command, which embeds the token and your control plane URL.

Unattended install

Run the installer from an elevated PowerShell or Command Prompt session.

AssurIQCollectorSetup.exe /quiet ENROLLMENT_TOKEN=<one-time-token> ASSURIQ_URL=<control-plane-url>

The setup extracts the collector binary and configuration to the program data directory, registers the AssurIQCollector Windows service, and starts it. On first start, the service exchanges the enrollment token for a permanent collector credential and immediately discards the token.

Under the hood, first start calls POST /api/v1/collectors/enroll with the token, hostname, OS and version; a successful response returns the collector's auth token and initial scan scopes. See the Collector API v1 reference for the exact request and response shapes.

• Collector API v1 reference
  Request/response shapes for the collector-facing API v1 endpoints: enroll, heartbeat and observations, plus tenant/site binding rules and error codes.
• What the v0.1 collector does today
  A plain list of what the native v0.1 collector supports right now versus what is designed but not yet active, and what the DEV build badge means.

Verify the service

sc query AssurIQCollector

Expected state is RUNNING. In the site's Collectors panel, the new collector should move from Enrollment Pending to Healthy within about 60 seconds, once the first heartbeat is received.

Uninstall

Use Windows Programs and Features, or run the uninstaller silently, then revoke the collector's credential from AssurIQ so it cannot be reused.

AssurIQCollectorSetup.exe /quiet /uninstall

• Uninstall and revoke a collector
  How to retire a collector cleanly: uninstall the host software and revoke its credential so it cannot re-authenticate.

Troubleshooting

If enrollment fails, the installer reports the control-plane error code. Common causes are an expired or already-used token, or blocked outbound connectivity.

• AIQ-ENR-001Enrollment token invalid or already used
  The enrollment token was not recognized, or has already been exchanged for a credential.
• AIQ-ENR-002Enrollment token expired
  Too much time passed between generating the token and completing enrollment.
• AIQ-COL-001Collector offline
  The collector has not sent a heartbeat within the expected interval. Discovery, scans and evidence collection for its sites are paused.

• Enrollment failures
  Symptom-first guide for AIQ-ENR-001 through AIQ-ENR-004: token, expiry, revocation and connectivity failures during enrollment.
• Firewall and egress requirements
  The collector is outbound-only. What to allow, on which ports, and why no inbound rules are ever needed.