Deploying Dell BIOS Updates using the Application Model

Deploying Dell BIOS Updates Using the Application Model in SCCM

Updating Dell BIOS versions as part of an SCCM OS deployment task sequence — rather than manually, machine by machine — keeps firmware consistent across your fleet and folds neatly into the same imaging process you’re already running. How it works: The general approach uses the Application Model rather than a plain Package: package the Dell BIOS update executable as an Application with a detection method (checking the currently installed BIOS version, typically via WMI against Win32_BIOS), and a silent install command line using the flash utility’s own quiet switches (Dell’s BIOS update executables typically support something like /s for silent operation, though exact switches vary by utility generation). Add this Application as a step in your task sequence, usually right after the OS image is applied and drivers are injected, so the BIOS update runs as part of the same automated build rather than as a separate manual step afterward. Because Dell’s BIOS flash utility switches and packaging have changed across different tool generations, confirm the exact silent-install syntax for the specific Dell BIOS update executable you’re deploying against Dell’s own documentation before building this into a production task sequence.

Beyond the Classic Application Model (Updated for 2026)

The Application Model approach above is still a valid, commonly-documented method, and current Dell BIOS packages are typically wrapped around Dell Command | Update’s command-line tool (dcu-cli.exe), which handles both detection and the actual flash. Current Dell Command | Update is on its 5.x release line, with the same broad shape of switches as earlier versions (an /applyUpdates-style silent update pass alongside a separate configuration/detection mode) — always pull the exact current switch syntax from Dell’s own Command | Update documentation for the version you’re packaging, since the specifics have shifted across releases. Dell and Microsoft have also both been pushing BIOS management toward Intune-native paths more recently: Dell Command | Endpoint Configure for Microsoft Intune (DCECMI) handles BIOS configuration directly, and Microsoft’s own Intune BIOS configuration policy now covers some of this ground natively for Intune-managed fleets. Dell has additionally introduced Dell Client Device Manager (DCDM) as a newer management option alongside DCU. None of this makes the SCCM Application Model approach wrong — it’s still current on Configuration Manager 2603 — but it’s worth knowing the landscape has broadened if you’re choosing a deployment mechanism today rather than maintaining an existing one.

Resources

• Deploying Dell BIOS Updates using the Application Model
• OSD
• guide
• ConfigMgr OSD Boot Image Problems with Dell Machines
• Browse our Windows Admin Toolkit picks on Amazon