Set up a Proxmox host

One USB for your compatible computers

The ComputerUse boot image detects the computer it starts on: CPU, installed RAM, network and eligible internal disks. It is not tied to a ThinkCentre or one disk serial. Use a 64-bit Intel or AMD computer with virtualization enabled, at least 8 GB RAM, an internal disk of at least 64 GiB and wired Internet access. A 256 GB or larger SSD is recommended for the initial desktops. ARM computers and Apple Silicon are not supported.

Every rental host runs Proxmox VE. ComputerUse manages that host privately; a customer will receive a Linux or Windows virtual desktop inside it. The initial dedicated product reserves one physical host for one customer VM. The previous Windows installers are retired.

1. Make or reuse the boot USB

Get the image from the download page. Check the published SHA-256 checksum, then use your operating system's disk-image writer to write the ISO to an identified USB of at least 8 GB. Writing the image replaces that USB's contents. Copying the ISO file onto a normal USB folder does not make it bootable.

Once written, reuse the same USB on each compatible machine. The image contains no company password, partner pairing code or administrator private key. It obtains a unique worker credential after authenticated enrollment during setup.

The current company-option-1 USB does not need rewriting for the latest website sign-in or fast desktop connection improvements. Website updates arrive when you load the site. Installed host software and desktop connections are managed separately after enrollment; the USB does not pull new code from GitHub automatically.

2. Prepare and boot the target computer

Back up files you need from the selected internal disk. Connect Ethernet, a keyboard and display. Enable CPU virtualization in firmware. On a ThinkCentre, restart and tap F1, enable Intel Virtualization Technology, then save with F10. Detailed firmware instructions.

Insert the prepared USB, power on and tap F12 on the ThinkCentre. Select the SanDisk USB, preferably its UEFI entry. Other brands use their own boot-menu key. Select ComputerUse - detect hardware and install Proxmox. The computer must boot from the USB; plugging it in while Windows is running does not start installation.

3. Choose ownership and the exact disk

The setup displays detected hardware and eligible internal disks with model, serial and capacity. USB drives and mounted disks are excluded from installation targets. A single eligible internal disk is selected automatically. If there is more than one, enter the intended disk number; an empty choice will not select one.

Choose 1 — Erase the displayed disk and install a company host, then enter the company enrollment password or an operator-issued private enrollment code. Company installation proceeds without a separate typed erase phrase. Choose 2 for a partner host, enter the host ID from your account and its private one-use pairing code. An unknown or missing host ID directs you to sign up first. A host ID alone cannot authorize enrollment.

The selected internal disk will be erased, including its operating system, applications, files and recovery partitions. Review the displayed target before choosing company option 1. That choice authorizes erasure once authentication and the hardware checks pass. Partner option 2 retains its assessment consent and typed disk confirmation, such as ERASE /dev/sda. The installer rechecks disk identity before installation. Do not use this process on a host with an active customer rental.

4. Let installation finish

Setup authenticates enrollment, installs Proxmox and prepares the worker's private management connection. When installation finishes, the computer powers off. Remove the USB, then power the computer on again. Keep Ethernet connected and allow several minutes for first boot and reporting.

Both company ThinkCentres have now completed installation, with KVM, automatic reporting and authenticated private management verified. A separate virtual-machine rehearsal also verified the installation and reconnect after reboot. Installation time varies with the disk and USB; there is no fixed completion-time guarantee.

5. Find the installed computer

Company computers appear in Operations. Partner computers appear under the host ID in the host dashboard. Setup creates a hardware-derived name beginning cu-. It reports physical RAM into the appropriate 8 GB or 16 GB hardware bucket. Larger hardware is detected, but the current product catalog has those two tiers.

Proxmox needs memory for itself. Physical RAM is not the guest's full RAM allowance; final guest allocations must be measured and disclosed. The 8 GB Standard tier includes 80 GB of guest storage and the 16 GB Creator tier includes 150 GB, including the guest operating system. A 128 GB SSD is a compact Standard-host option only when its installed guest storage pool can fully back the 80 GiB disk with room for metadata and maintenance; check actual free capacity before provisioning. Storage reporting uses Proxmox's guest storage pool. Health reports run automatically, with small periodic network probes. Partner qualification starts on the final Proxmox installation, with a 24-hour preliminary view and a 48-hour assessment.

Each host opens an outbound, authenticated SSH connection to the ComputerUse server. Host management is reached through a restricted loopback-only forwarding endpoint with pinned SSH identities. No public port forwarding on the host router is needed. Root passwords and host credentials are never customer API keys.

6. Activate the desktop after enrollment

A newly online host appears in Operations before it has a usable desktop. The current USB installs Proxmox, reporting and private management. Creating an isolated Linux VM, assigning it to an account, installing desktop controls and configuring the fast connection still require server-side activation. This work uses the private management connection; you do not need to reinstall Proxmox or boot the USB again.

Both existing company ThinkCentres have completed owner desktop activation. The 8 GiB host gives its guest 6 GiB RAM and four vCPUs; the 16 GiB host gives its guest 12 GiB RAM and six vCPUs. New Standard desktops on 8 GiB hosts receive 80 GiB of disk; Creator desktops receive 150 GiB. Both existing owner pilots retain their already-provisioned 150 GiB disks. Open Your computers after signing in to the assigned account.

The direct connection is currently configured for approved owner devices on the local network. New hosts and new owner workstation addresses need their own configuration. Other connections can use the HTTPS fallback with greater latency. An online host does not automatically inherit another host's direct connection settings.

7. Verify before offering rentals

Installation and an online status do not make a computer available for purchase. Fresh customer VM creation, resource limits, desktop actions, tenant network isolation, credential revocation, clean deletion/reset, power recovery and payment reconciliation must pass before rental stock is enabled. End-to-end Boardly desktop sessions are also pending.

Central management does not require putting every partner's remote PC into the same Proxmox cluster. Independently managed nodes can connect to one control plane. Use stable network addressing and maintain router DHCP reservations for addresses assigned during installation. See enterprise deployment and customer virtual desktops.

Recovery or retirement

If enrollment fails, installation stops and displays the error. An exit prompt belongs to the stopped installer; it restarts the USB and does not confirm erasure. Note the error immediately above that prompt. If using the original 10 September USB, rewrite it with the updated image to get the simplified company setup. If a new host does not report after first boot, keep it powered on with Ethernet connected and provide its displayed cu- name to support. Reinstalling creates a new enrollment; an operator must reconcile the old record. Do not wipe a live rental to repair telemetry.

Drain allocations, settle customer retention choices, verify cleanup, revoke the node credential and remove inventory before retiring a host. The old Windows reporter can be preserved until the new Proxmox record is reconciled to the same owner.

Proxmox hardware requirements · Proxmox automated installation.