Patching Dell Command Specific Firmware and Drivers
Automox does not patch firmware, BIOS, or hardware driver updates natively. On Dell hardware you can still deploy these through Automox by using a Worklet to invoke Dell Command Update, which is Dell's own update utility. This article covers what that requires and the pitfalls to check before deploying it broadly.
Prerequisite: Dell Command Update must already be installed
This is the single most common reason this approach does not work. A Worklet runs Dell Command Update, it does not install it. The utility has to already be present on every target device, otherwise the Worklet has nothing to invoke and the run does not produce the expected updates.
Before deploying, confirm Dell Command Update is installed across the target group, and have the Worklet check for the executable and exit cleanly when it is missing, so that devices without it are visibly skipped rather than silently failing.
The community Worklet
A community-contributed Worklet is available for this purpose: Run Dell Command Driver Updates (Windows). Its stated purpose is to run Dell Command on a device to update to the latest drivers, and to apply firmware updates where it finds them.
Worklets shared on the Automox Community are contributed examples rather than Automox features. They are a starting point, they sit outside the scope of Automox Support, and you should expect to review and adapt one to your environment. Test on a small group before deploying to production.
For Automox-maintained templates rather than community contributions, see Policy Catalog Overview and Usage.
Test the Worklet the way Automox will run it
A Dell Command Update command that works when you run it yourself can appear to do nothing when the same code runs through a Worklet. This happens because Worklets do not run in your interactive session. Automox executes script content in a 32-bit context as the System account, which changes how processes are launched and which paths resolve.
Validate the remediation code under those same conditions before concluding the utility or the Worklet is at fault. See How to Test a PowerShell Script Locally for Worklets for how to reproduce the Automox execution context locally.
If the Worklet launches a separate process rather than running the update inline, confirm that process actually starts and that its exit status is captured, since a launch that fails silently looks identical to a Worklet that ran successfully and found nothing to do.
Keeping Dell Command Update itself up to date
Keeping the utility current is a separate task from using it. Dell has renamed this application in the past, and when a vendor changes a product name the older installed title does not necessarily upgrade into the newly named one through normal third-party patching. Devices can sit on an older version indefinitely while the console shows the newer title as supported.
If you have devices that are not moving to the current version, deploy the current installer directly with a Worklet or a Required Software policy rather than waiting for it to be picked up as an update. Check the version actually installed on a sample device rather than relying on the software list alone.
Reporting
Firmware, BIOS, and driver updates applied this way are not tracked as patches and do not appear in patch reporting. The record of what ran is the Worklet's output in the policy activity log, so write the Worklet to print each item and its result explicitly. For more detail on this limitation and the other available approaches, see Can Automox Patch Driver or Firmware/Hardware Updates?