# Driver Management

> Monitor and update drivers on enrolled Windows endpoints after provisioning, without reimaging.

Source: https://docs.capaone.com/capaone/provision-manager/driver-management/  
Product: CapaOne — a separate CapaSystems product; do not apply this page to any other.

Provision Manager includes automatic driver management for enrolled Windows endpoints. After a
device is provisioned, CapaOne continues to monitor its drivers and can push updates as new
versions become available — without requiring a reimaging or manual intervention.

Driver management status is available in two places:

- **Windows → Provisioning → Dashboard** — chart-based overview of driver compliance across the
  fleet.
- **Windows → Provisioning → Drivers** — a list view showing all driver stats per endpoint,
  useful for finding specific devices or sorting by status.

## Driver compliance

The **Driver Compliance** chart shows the current driver health across your fleet in three
categories:

- **Driver Up-to-Date** — all managed drivers on the device are at the latest available version.
- **Driver Updates Available** — one or more drivers have a newer version that has not yet been
  applied.
- **Not Supported** — the device model is not in CapaOne's driver catalog. See [Supported
  devices](#supported-devices) below.

The **Driver Updates Available** chart breaks down which specific driver categories have pending
updates. Use this to understand whether outstanding updates are for a single driver type (e.g.,
chipset) or spread across multiple categories.

## Supported devices

CapaOne maintains a hardware model catalog that determines which devices can receive automatic
driver updates. The **Driver Supported Devices** chart shows how your fleet splits between
supported and unsupported models.

To see exactly which models are supported, click the **Supported Models** button on the
Provisioning Dashboard.

**Virtual machines** always appear as unsupported — driver management is intended for physical
hardware, since VMs use virtual device drivers managed by the hypervisor.

If you have physical devices showing as unsupported, their hardware model is not yet in CapaOne's
catalog. In that case, driver updates must be handled manually or through other tooling for those
devices.

## Driver update categories

Driver updates are grouped by category (chipset, network, display, storage, etc.). The **Driver
Update Categories** chart gives a breakdown of which categories have pending updates across the
fleet.

This is useful for prioritising remediation — a pending network driver update, for example, is
generally more urgent than an optional utility driver.

## In-progress and failed updates

Two additional charts track the live state of driver update operations:

- **Driver Updates in Progress** — updates currently being applied. This is typically only
  populated during active update cycles.
- **Driver Updates Failed** — updates that did not apply successfully. Failed driver updates
  should be investigated — check whether the device is online, whether the driver package is
  compatible with the OS version, and whether the failure is isolated or affecting multiple
  devices.

## Good to know

- **Driver management is automatic for supported models** — once a device is enrolled and its
  model is in the catalog, CapaOne handles driver updates without additional configuration.
- **Unsupported devices still benefit from provisioning** — a device that cannot receive automatic
  driver updates can still be provisioned using a template. It will simply show as unsupported in
  the driver compliance view.
- **Driver updates happen independently of OS provisioning** — after the initial provisioning,
  driver updates continue on an ongoing basis as new versions are published to the catalog.
- **Check the History tab** (Windows → Provisioning → History) if you need a log of past driver
  update activity for a specific device.