Provision Manager
Provision Manager installs Windows on bare-metal devices and reinstalls failed devices, using only an internet connection. Both x64 and ARM64 devices are supported. There are no local deployment servers or images to maintain: the device boots into the CapaOne provisioning environment, and everything else is delivered from the cloud.
You can boot a device into the provisioning environment in two ways:
- PXE network boot — start a temporary PXE server on any managed Windows endpoint on the same subnet as the devices you want to provision.
- USB key — create a bootable USB key for devices where network boot is not available.
After boot, the device shows a QR code. You scan it with a phone, sign in to CapaOne, and assign a provisioning template. Installation then runs unattended.
How a deployment is defined
Section titled “How a deployment is defined”| Component | What it controls |
|---|---|
| Provisioning template | The Windows image (architecture, version, release, edition, language), installation settings, and scripts to run during provisioning. |
| Enrollment configuration | How the device is set up in CapaOne after the operating system is installed. Each template is linked to an enrollment configuration. |
| Provisioning point or USB key | How the target device boots into the provisioning environment. |
The same template works across device models — drivers are resolved per device, so you don’t maintain a separate image per hardware model.
Drivers
Section titled “Drivers”During deployment, Provision Manager automatically installs manufacturer-certified driver packages matched to the device’s hardware model. Dell, HP, Lenovo, and Microsoft devices are supported. Driver management continues after deployment: the Drivers tab tracks and rolls out driver updates across your fleet, and the Dashboard tab shows driver compliance per model.