For a current Microsoft Configuration Manager (formerly SCCM) environment, use the native Third-Party Software Update Catalogs feature with Dell’s Business Client catalog. Microsoft has treated SCUP integration with Configuration Manager as unsupported since January 31, 2024 (Microsoft documentation). Keep SCUP only for maintaining an existing legacy process. For tighter control over BitLocker, BIOS passwords, reboots, or remote devices, package Dell Command | Update as a Configuration Manager application instead.
Choose the deployment method
| Method | Status | Best fit | Principal limitation |
|---|---|---|---|
| Native Dell third-party catalog | Recommended | Software-update groups, maintenance windows, staged collections and compliance reporting | Less control over custom BIOS-password and BitLocker logic |
| SCUP | Legacy; Configuration Manager integration unsupported since January 31, 2024 | Existing historical environments that cannot yet be migrated | Unsupported integration and difficult troubleshooting |
| Dell Command | Update (DCU) | Supported alternative | Explicit BIOS/firmware selection, BitLocker suspension, password handling and remote clients | Requires application packaging, detection, logging and return-code design |
| Direct Dell BIOS package | Specialized | Task sequences or tightly controlled model-specific deployments | High packaging and model-management burden |
BIOS updates flash motherboard firmware. Firmware updates can target docks, Thunderbolt controllers, storage controllers, network adapters and other components. Drivers are Windows software, while Dell Command | Update and SupportAssist are applications. Dell’s catalog can contain all of these categories, so do not publish the entire catalog when the campaign is intended to update BIOS only.
As an Amazon Associate I earn from qualifying purchases.
Prerequisites and safety checks
- A healthy, supported Configuration Manager current-branch hierarchy with an active Software Update Point (SUP) and WSUS integration.
- Internet access from the top-level SUP to Microsoft, Dell catalog and Dell content locations over HTTPS/TCP 443, including any proxy configuration.
- Enough free space in the SUP’s
WSUSContentdirectory. Microsoft lists this storage and Internet access as prerequisites (third-party update requirements). - A custom client setting that enables third-party software updates, plus trusted WSUS-signing and catalog certificates.
- Dell commercial client models covered by the catalog and a representative pilot collection.
- Escrowed BitLocker recovery keys, an AC-power requirement for laptops, a BIOS-password strategy, maintenance windows and user notification.
- A recovery plan: retain Dell release notes, logs and a way to reach devices that fail before Windows starts.
Enable third-party software updates
- In the Configuration Manager console, open Administration and select Client Settings.
- Edit an existing custom client setting or create one; avoid changing Default Client Settings globally for the pilot.
- Select Software Updates, set Enable third-party software updates to Yes, and deploy the setting to a small Dell test collection.
- Confirm the WSUS signing certificate is installed in each pilot client’s Trusted Publishers store before approving BIOS updates. Microsoft documents this workflow at Third-party software updates.
Subscribe to Dell’s native catalog
- Go to Software Library > Software Updates > Third-Party Software Update Catalogs.
- Find Dell in the partner-catalog list and choose Subscribe to Catalog.
- Review and approve the catalog certificate. Partner catalogs are registered in Configuration Manager; a custom catalog would instead require an HTTPS URL and digitally signed updates.
- Choose supported synchronization categories and a schedule. Dell documentation uses names such as Dell Business Client Catalog, Dell Client Catalog, Dell SCUP Catalog and Dell 3rd Party Update Catalog for the same general catalog family (Dell Update Strategies). The catalog covers BIOS, firmware, drivers and Dell applications (Dell catalog information).
Synchronize metadata, then publish only approved content
These are separate operations:
- Synchronization imports update metadata and applicability rules into WSUS and Configuration Manager. Clients use that metadata to determine whether a model and current version match.
- Publishing downloads and signs the selected update content. The binaries are stored in the SUP’s WSUS content directory before they can be placed in a deployment package.
For supported version-3 catalogs, Configuration Manager can perform a scan-only synchronization (metadata without binaries) or automatically stage content for selected categories. Start narrowly:
- Limit products or model families to those in the campaign.
- Select BIOS and, where explicitly planned, firmware categories.
- Filter by security or critical severity when the catalog supplies those classifications.
- Approve exact release versions after reviewing Dell release notes and prerequisites.
- Exclude drivers and applications unless they are intentionally part of the change.
Create and stage a deployment
- Open Software Library > Software Updates > All Software Updates and search for the approved Dell BIOS or firmware titles.
- Check each title’s model applicability, release version, severity and reboot information.
- Select the updates and choose Add to Software Update Group. Use a separate group for each campaign or model family.
- Download the group’s content, create or select a deployment package, and distribute it to the required distribution points.
- Deploy first to a collection such as
Dell BIOS - Pilot. After validation, useDell BIOS - Early Production,Dell BIOS - Broad Productionand anExceptioncollection for holds and failures. - Configure maintenance windows and user notifications so the restart can occur with the laptop on AC power. Expand rings only after verifying firmware versions and recovery behavior.
Do not assume one deployment safely covers every Dell model. Applicability metadata can prevent an incorrect package from installing, but a package can still fail because of a BIOS password, power state, prerequisite sequence or pending reboot.
#1 Best Overall
- Vibrant Visuals: Enjoy vivid, accurate colors with up to 300 nits brightness on a spacious 15" display featuring a sleek 3‑sided narrow bezel.
- AI Productivity: Boost efficiency with Intel Core Ultra processors and NPU‑powered AI features designed to keep multitasking smooth and responsive.
- Smarter Shortcuts: Use the dedicated Copilot key for instant access to your AI assistant, helping you organize, search, and work faster every day.
- Eye Comfort: Dell ComfortView reduces blue‑light emissions to help keep your eyes comfortable during extended viewing.
- Ergonomic Angle: Lifted hinges enhance typing comfort and support better airflow, helping your system run smoothly.
Reboots, AC power and BitLocker
A BIOS update may stage in Windows and finish during a pre-boot firmware phase. A deployment can defer the restart, but it cannot complete the firmware flash without the required reboot. A laptop that is not connected to AC power may postpone or reject the operation. Never terminate the updater or power off a device during the firmware phase.
Catalog-driven behavior depends on the individual Dell package and installer. With Dell Command | Update, administrators can explicitly control BitLocker handling. In current 5.x documentation, -autoSuspendBitLocker suspends BitLocker for a BIOS update and allows it to be re-enabled after the update and reboot; when disabled, BIOS updates may be skipped while other updates continue (Dell Command | Update CLI reference).
- Verify BitLocker is enabled as expected and that the recovery key is escrowed before deployment.
- Suspend protection only for the minimum period and test with TPM and Secure Boot enabled.
- Do not claim that a generic catalog deployment automatically suspends BitLocker; verify the exact package behavior.
Dell’s guides cover BIOS updates with BitLocker enabled and the suspension option (user guide PDF and BitLocker guidance).
BIOS-password handling
A system password can make an otherwise applicable update fail. Dell Command | Update exports do not contain the BIOS password, so it must be supplied separately through an approved secret-management design (Dell password guidance).
Rank #2
- Effortlessly chic. Always efficient. Finish your to-do list in no time with the Dell 15, built for everyday computing with 13th Gen Intel Core i7-1355U processor
- Designed for easy learning: Energy-efficient batteries and Express Charge support extend your focus and productivity.
- Stay connected to what you love: Spend more screen time on the things you enjoy with Dell ComfortView software that helps reduce harmful blue light emissions to keep your eyes comfortable over extended viewing times.
- Type with ease: Write and calculate quickly with roomy keypads, separate numeric keypad and calculator hotkey.
- Ergonomic support: Keep your wrists comfortable with lifted hinges that provide an ergonomic typing angle.
Never put a clear-text password in a Configuration Manager command line, batch file, package source or readable log. Dell documents an encrypted-password workflow; syntax varies by installed DCU version:
dcu-cli.exe /generateEncryptedPassword -encryptionKey="MyEncryptionKey01" -password="The Local System BIOS Password" -outputPath="C:Temp"
dcu-cli.exe /applyUpdates -encryptionKey="MyEncryptionKey01" -encryptedPassword="ENCRYPTED_VALUE"Protect the encryption key and encrypted value, restrict access to the package and logs, and test password-protected and password-free device collections separately.
Use Dell Command | Update when you need finer control
Package DCU as a Configuration Manager application when catalog behavior is insufficient, when devices are frequently off the corporate network, or when BIOS-password, BitLocker and reboot logic must be explicit. Dell documents /scan as identifying updates applicable to the current system and /applyUpdates as applying them (CLI documentation).
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11dcu-cli.exe /scan -updateType=bios,firmware -outputLog="C:ProgramDataDellBIOSScan.log"
dcu-cli.exe /applyUpdates -updateType=bios,firmware -silent -reboot=disable -outputLog="C:ProgramDataDellBIOSApply.log"These examples target Dell Command | Update 5.x syntax. Validate every option against the installed major version; older guides and versions differ. Common options include -updateType=bios,firmware, -silent, -outputLog, -reboot, -autoSuspendBitLocker, -encryptedPassword, -encryptedPasswordFile, -encryptionKey and -forceupdate.
Rank #3
- 256 GB SSD of storage.
- Multitasking is easy with 16GB of RAM
- Equipped with a blazing fast Core i5 2.00 GHz processor.
A production application should include:
- Detection for the installed DCU version and Dell-manufactured hardware.
- Operating-system architecture and supported-model requirements.
- Preflight checks for AC power, BitLocker state and pending reboot.
- Secure password retrieval, if required.
- Known log paths, explicit return-code mapping and a reboot policy controlled by Configuration Manager.
- Update-type restrictions so an emergency BIOS campaign does not unexpectedly install drivers or applications.
Verify the firmware result
Compliance may remain pending until the firmware phase and final reboot finish, followed by hardware inventory or a software-update evaluation cycle. Confirm the actual BIOS version with Windows inventory:
Get-CimInstance Win32_BIOS |
Select-Object Manufacturer, SMBIOSBIOSVersion, ReleaseDateCompare the returned version with the exact Dell model’s approved catalog entry or support page. Review Configuration Manager software-update logs, DCU logs (for application deployments), restart state, and Dell pre-boot messages.
Troubleshooting common failures
SCUP updates do not appear or publish
SCUP/Configuration Manager integration is unsupported after January 31, 2024. Missing WSUS signing certificates, metadata-only legacy updates or incomplete synchronization can also prevent publication. Migrate to the native catalog or DCU rather than building a new SCUP dependency (SCUP status).
Content download fails
Check SUP Internet and proxy access, TCP 443, Dell content URLs, certificate trust and free space in WSUSContent. A successful metadata sync does not prove that binaries were downloaded.
Rank #4
- Edge-to-edge clarity: Enjoy crisp, expansive visuals on a 16" screen with up to FHD+ and a 16:10 aspect ratio—delivering a wide, immersive viewing experience.
- All-day comfort: Dell ComfortView Plus helps reduce harmful blue light emissions while preserving true-to-life color, keeping your eyes comfortable even during prolonged screen time.
- Ready for business: Flip between effortless productivity and captivating entertainment on a large, immersive screen powered by Intel Core 7-150U processor and graphics.
- Built for virtual connection: Bring your connections to life with an up-to FHD camera, designed with wide dynamic range and temporal noise reduction to deliver crisp, sharp images, no matter the lighting conditions.
- Adaptive thermals: Built-in technology allows your PC to sense when it's on a stable surface and adjusts its power and thermals to run more efficiently.
The update is applicable but installation fails
Check the BIOS password, AC connection, BitLocker state, model and prerequisite sequence, pending reboot and whether another firmware operation is already staged.
BitLocker requests recovery
Common causes include missing suspension, an unexpected restart, or TPM/Secure Boot changes. Confirm recovery-key escrow and test the exact package on each major hardware family before widening deployment.
Configuration Manager reports success but BIOS is unchanged
The update may be waiting for reboot, may have been rejected during pre-boot, may be superseded, or compliance may not have refreshed. Check the BIOS inventory command above and the device’s restart and firmware logs.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteLegacy SCUP procedure (maintenance only)
Older environments historically installed and configured SCUP, imported or subscribed to Dell’s catalog, imported metadata, published selected updates to WSUS, synchronized Configuration Manager with WSUS, and then deployed the updates through software-update groups. Microsoft no longer supports this SCUP integration path from January 31, 2024. Do not mix metadata-only SCUP updates with the native third-party update service casually; plan a controlled migration and republish updates through the supported catalog workflow.
Best Value
- Effortlessly chic. Always efficient. Finish your to-do list in no time with the Dell 15, built for everyday computing with Intel processors.
- Designed for easy learning: Energy-efficient batteries and Express Charge support extend your focus and productivity.
- Stay connected to what you love: Spend more screen time on the things you enjoy with Dell ComfortView software that helps reduce harmful blue light emissions to keep your eyes comfortable over extended viewing times.
- Type with ease: Write and calculate quickly with roomy keypads, separate numeric keypad and calculator hotkey.
- Ergonomic support: Keep your wrists comfortable with lifted hinges that provide an ergonomic typing angle.
Operational practices that reduce risk
- Deploy by model family and use pilot, early-production and broad-production rings.
- Start with BIOS-only or firmware-only campaigns; do not combine drivers and applications until the process is proven.
- Require AC power and schedule restarts inside maintenance windows.
- Keep BitLocker recovery keys escrowed and retain deployment and firmware logs.
- Review Dell release notes and prerequisites before approving each version.
- Revalidate commands, detection rules and return codes whenever Dell Command | Update changes major version.
- Use an exception collection for devices with password, power, encryption or hardware issues instead of repeatedly retrying them in the broad deployment.
Frequently Asked Questions
Is SCUP still supported for Dell BIOS updates in Configuration Manager?
No. Microsoft documents SCUP integration with Configuration Manager as unsupported beginning January 31, 2024. Use the native Dell third-party catalog or Dell Command | Update instead.
Can a Dell BIOS update be installed without a restart?
You can sometimes defer the restart, but the firmware flash normally completes only during the required reboot and pre-boot phase. Do not promise a no-restart BIOS deployment.
Why did an applicable Dell update fail on some computers?
Typical causes are a BIOS password, missing AC power, BitLocker handling, model-specific prerequisites, another pending firmware update or an incomplete reboot cycle.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
