First Boot & License

On first boot, the thin client runs ThinX OS Setup (ThinXOS Setup window) from the ChipPC client (client/licensemanager in the chippcapp sources). You choose how the device is licensed and managed.

Without Xcalibur (standalone / local license)

Select Local — Standalone with local license. The device talks to the ChipPC license server over HTTPS:

• Endpoint: https://license.chippc.com (outbound TCP 443 must be allowed).
• Device identity: serial string ProcessorId-MAC (used for lookup and registration).
• Automatic check: the wizard tries to fetch an existing license for this device.
• Register this PC: registers the device with the license server (extended warranty / support flow).
• License code: enter XXXX-XXXX-XXXX and click Apply to bind a code to this device via the server.

If the server cannot be reached, use a code only when your process allows offline steps; otherwise fix DNS/firewall first.

With Xcalibur (managed)

Select Xcalibur Global — Managed by a central server. Enter your Xcalibur server address (hostname or IP) or use discovery.

• Connect: uses the value in the field. If the field is empty, discovery starts automatically.
• Discover: finds the Xcalibur server on the LAN. The client tries, in order: PSK discovery on https://<IP>:1013/psk-discovery when you typed an IP, then UDP broadcast to port 1012, then a subnet scan on the same /24.
• On success, the management URL is stored as wss://<host>:1013/api/v1/ws (defaults applied when the port/path are omitted).
• The client then activates and waits for license approval from the Xcalibur server.

Open on the network: UDP 1012 (broadcast discovery), TCP 1013 (HTTPS discovery and WSS management, depending on deployment), and 443 to license.chippc.com for standalone licensing.

For pool-based and MAC-based licenses uploaded and assigned in the Xcalibur console, see Licenses (Chapter 3). The first-boot wizard here is the on-device path before the agent is fully enrolled.