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.
The short answer
How do I keep BIOS and drivers current on many PCs?
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.
Workflow
From the outdated version to the verified update
-
1
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.
-
2
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.
-
3
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.
-
4
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.
What is included
The safeguards a remote BIOS update needs
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
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.
FAQ
Frequently asked questions about BIOS and driver updates
Can I install BIOS updates remotely when a BIOS password is set?
What happens to BitLocker during a BIOS update?
What happens when a driver causes problems?
Which vendors are supported?
Does the device restart during working hours?
Do I need the vendor tools on every device?
More tasks
What else fliix Ops takes care of
Each page answers one task from daily Windows work, with the workflow, the limits and the licence.
All solutions →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.