# BIOS and Driver Updates for HP, Dell and Lenovo | fliix Ops

> Deploy BIOS and driver updates for HP, Dell and Lenovo centrally: vendor catalog, pilot phase, rollback, maintenance windows. Hosted in Germany.

Canonical HTML: https://www.fliix-ops.com/solutions/bios-and-driver-updates

## Hero

BIOS and driver updates

**Deploy BIOS and driver updates for HP, Dell and Lenovo centrally**

fliix Ops compares the BIOS and drivers of every Windows device with the vendor catalog and installs newer versions remotely: on one device, on many, or in a maintenance window.

- Packages straight from the vendor, with checksum
- Pilot phase before the wide rollout
- Driver rollback for 30 days

## Answer

The short answer

**How do I keep BIOS and drivers current on many PCs?**

### Paragraphs

- The fliix Ops agent reports the model, BIOS version and installed drivers of every device. fliix Ops matches them against the catalogs of HP, Dell and Lenovo and shows every device with a newer version as a finding. From there you install the update on one device, as a bulk action, or as a maintenance window step.
- You do not need HP Image Assistant, Dell Command Update and Lenovo System Update side by side, nor a package repository of your own. The agent downloads only from the vendor, checks checksum and signature, and installs silently.
- Because a BIOS update cannot be undone, every new BIOS file goes to pilot devices first. If it fails there too often, fliix Ops blocks it for all further devices.

## Steps

Workflow

**From the outdated version to the verified update**

**Detect**

Every HP, Dell or Lenovo device with a newer BIOS or driver in the vendor catalog appears as a finding, with the installed and the available version.

**Check in the pilot**

Devices tagged "Pilot" receive a new package first. A driver is released after seven days without errors and one successful installation.

**Roll out**

Install on one device, as a bulk action on many, or let the maintenance window install the released packages, at most ten drivers per window.

**Verify**

After the installation the agent checks the device. If a driver fails the check, the agent rolls it back itself. For a BIOS, fliix Ops compares the version after the restart.

## Capabilities

What is included

**The safeguards a remote BIOS update needs**

- BIOS only from the vendor catalog: the newest version with checksum, silent installation and download from the vendor.
- If the BIOS has an administrator password, you store it in fliix Ops. It is verified on the device before an update starts.
- If the system drive is encrypted, the agent suspends BitLocker for the update. The stored recovery key is a precondition.
- Starts only on mains power, with the battery at least half full and 2 GB of free disk space.
- The BIOS is prepared and installed at the next restart. Signed-in users are asked: now, in an hour or tonight. If nobody is signed in, the device restarts right away. In a maintenance window, the window's restart rule applies.
- Before each driver the agent backs up the current driver and, where Windows allows it, creates a restore point.
- After a network driver the agent checks for ten minutes that the device stays reachable and rolls back otherwise.
- "Restore previous driver" is available for 30 days.
- Recommended drivers from Windows Update can be rolled out as well, optional ones only on a single device.

## Limits

Limits

**What fliix Ops deliberately does not do**

- BIOS updates are available for clients from HP, Dell and Lenovo. Servers and virtual machines get no BIOS through fliix Ops.
- Not every package from the vendor catalog is installed. Packages without a checksum or silent installation, and packages that would restart the device on their own, remain links to the vendor.
- For Intel, AMD, NVIDIA and Fujitsu, fliix Ops shows the link to the vendor but does not install.
- For models without a vendor catalog, such as consumer devices or self-built PCs, fliix Ops looks up BIOS and drivers on the vendor pages and shows the verified link. Nothing is installed there.
- A BIOS that Windows Update offers is reported but not installed through it.
- A BIOS update cannot be reverted. The BIOS step in the maintenance window is therefore off by default and installs at most one BIOS per run.
- A driver update never triggers a restart by itself.

## Licence

Licence

**Which licence includes this?**

Findings for outdated BIOS versions and drivers and their installation are part of the Windows Agents Full licence. Windows Agents Lite includes neither.

### Links

#### Links

View pricing

#### Links

All Windows capabilities

## Faq

FAQ

**Frequently asked questions about BIOS and driver updates**

**Q:** Can I install BIOS updates remotely when a BIOS password is set?

Yes. You store the BIOS administrator password in fliix Ops and it is verified on the device. The agent passes it only to the vendor's update program, never to a log. The update programs from Dell and Lenovo accept it only on their command line; while the update runs, a signed-in user can see it there. If a password is set but not stored and verified, no BIOS update starts.

**Q:** What happens to BitLocker during a BIOS update?

The agent suspends BitLocker for two restarts so the device does not ask for the recovery key after the update. With an encrypted system drive, the update starts only if the recovery key is stored in fliix Ops.

**Q:** What happens when a driver causes problems?

The agent checks the device after the installation and rolls the driver back itself when the check fails. In addition you can restore the previous driver for 30 days. A package that stands out in the pilot does not reach the wide rollout.

**Q:** Which vendors are supported?

fliix Ops installs for HP, Dell and Lenovo devices from the vendor catalog. For chips from Intel, AMD and NVIDIA and for Fujitsu devices it shows the link to the vendor. Recommended drivers from Windows Update can be rolled out for any vendor.

**Q:** Does the device restart during working hours?

Not without asking, as long as someone is signed in. Drivers do not trigger a restart. A BIOS is prepared and installed at the next restart: signed-in users decide whether that happens now, in an hour or in the evening. If nobody is signed in, the device restarts right away. In a maintenance window, the restart rule you set for the window applies.

**Q:** Do I need the vendor tools on every device?

No. The fliix Ops agent downloads the packages from the vendor itself and installs them silently. A package repository or distribution server of your own is not needed.

## Cta

**Keep BIOS and drivers current without walking from desk to desk**

In the demo you see the findings, the pilot phase and an update in a maintenance window on real devices.
