LICENSEWARE Collector

Download the installer package for your operating system and architecture. Packages never contain an enrollment token — you supply it at install time.

The /d/latest/ links above always resolve to the current release. To pin a specific version, replace latest with the release tag, e.g. https://cdn.licenseware-collector.com/d/v1.2.3/…

If your network requires an HTTP proxy for outbound connections, the collector natively supports standard proxy environment variables for all egress traffic.

Authenticated proxies are supported using the format http://user:password@proxy.corp.com:8080.

Setup

Add the proxy variables to the collector environment file on the target machine. Each line uses KEY=value format.

HTTPS_PROXY=http://proxy.corp.com:8080
NO_PROXY=localhost,127.0.0.1

HTTPS_PROXY=http://proxy.corp.com:8080
NO_PROXY=localhost,127.0.0.1

HTTPS_PROXY=http://proxy.corp.com:8080
NO_PROXY=localhost,127.0.0.1

Applying Changes

After modifying the environment file, restart the collector service for changes to take effect:

Corporate proxies that perform TLS inspection inject their own CA certificate into the chain. The collector must be configured to trust these certificates, otherwise all HTTPS connections will fail.

Custom certificates are appended to the system certificate pool, not replacing it. All standard system CAs remain trusted.

Setup

Add the CA_CERT_PATH variable to the collector environment file, pointing to the PEM file containing your corporate CA certificate(s).

Applying Changes

After modifying the environment file, restart the collector service for changes to take effect:

All communication uses HTTPS with Bearer token authentication.

What You Do

What the Collector Does

The collector writes all logs to standard error. How you access them depends on the operating system and service manager.

Log Level

The verbosity is controlled by the LOG_LEVEL environment variable in the collector environment file. The default is error.

Linux

On systemd-based systems, logs are captured by the journal automatically.

macOS

The launchd service writes both stdout and stderr to a single log file.

Windows

The Windows service itself does not write application logs to a file or to the Windows Event Log. Use the commands below in an Administrator PowerShell to investigate the service: check its state, inspect service start/stop/crash records that Windows itself emits, and capture full application output by running the collector interactively.

Get-WinEvent -FilterHashtable @{
  LogName   = 'System'
  StartTime = (Get-Date).AddDays(-1)
  ProviderName = 'Service Control Manager'
} | Where-Object { $_.Message -match 'licenseware-collector' } |
  Format-List TimeCreated, Id, LevelDisplayName, Message

Get-WinEvent -FilterHashtable @{
  LogName   = 'Application'
  StartTime = (Get-Date).AddDays(-7)
} | Where-Object { $_.Message -match 'LicensewareCollector' } |
  Format-List TimeCreated, ProviderName, Id, LevelDisplayName, Message

Stop-Service licenseware-collector
$env:LOG_LEVEL = 'debug'
licenseware-collector run-once --env-file C:\ProgramData\Licenseware\collector.env *>&1 |
  Tee-Object -FilePath "$env:USERPROFILE\licenseware-collector-debug.log"
Start-Service licenseware-collector

msiexec /i LicensewareCollector.msi /l*v install.log
Get-Content install.log -Tail 200

Get-Content C:\ProgramData\Licenseware\setup.log