CICB deployment options
- Signed EXE or MSI installation for supported Windows endpoints.
- Silent or managed deployment through organization-approved endpoint tooling.
- Preconfigured Client connection settings when the customer protects the configuration and associated credentials.
- Standard Connected or Air-Gapped Isolated LAN operation.
Standard Connected updates
Current connected releases use the signed CICB AppUpdater launched from the Client or Server Check Update action. The installed app_updater/AppUpdater.exe must pass Windows trust validation for the expected ARKSOFT INC publisher before launch. The updater selects a release installer, records its SHA-256, validates available digest and Authenticode evidence, stops CICB processes when required, and starts the installer.
Air-Gapped Isolated LAN updates
The Air-gap release excludes AppUpdater. Transfer an approved local EXE or MSI through the organization’s offline process and validate it with install-airgap-update.ps1, an independently supplied expected SHA-256 digest, and the ARKSOFT INC publisher signature.
Post-installation verification
Verify version, signatures, required dependencies, configuration, services or startup tasks, listener, Client connectivity, display behavior, and Air-gap exclusions as applicable. Retain evidence for the customer change-control and authorization process.
The legacy Updater.ps1 and shared-drive hot-copy workflow is retired.