As part of our laptop onboarding process we would like to update the Dell Command configuration so that all laptops have the same settings for BIOS updates etc.
Has anyone done this via autopilot when Dell Command is already installed?
Answer from AngryDog on community.spiceworks.comDell Command updates / settings
Dell Command Update Now Dell Update - No Settings Anymore
Automating Dell Command Update - Securely storing bios password
Dell Command Update - is it needed?
Videos
We have multiple computers, and normally a tech would have to manually install the latest firmware updates on all Dell PCs and Laptops. Is there an easier way to do this?
As part of our laptop onboarding process we would like to update the Dell Command configuration so that all laptops have the same settings for BIOS updates etc.
Has anyone done this via autopilot when Dell Command is already installed?
We’re not yet using Autopilot, but you should be able to do this with the CLI (usually at C:\Program Files (x86)\Dell\CommandUpdate\dcu-cli.exe)
The formatting of the documentation isn’t ideal in my opinion, but you should be able to do most of what you’d want by calling this. https://www.dell.com/support/manuals/en-us/command-update/dellcommandupdate_rg/dell-command-|-update-cli-commands?guid=guid-92619086-5f7c-4a05-bce2-0d560c15e8ed&lang=en-us
EDIT: looks like there’s actually an import/export option under the /configure flag that would probably do just what you need 
I just noticed Dell Command Update has been renamed to Dell Update and there's no longer a settings option for it so we can't disable automatic updates? Maybe this command would still work, but I'm not sure?
REG ADD "HKLM\SOFTWARE\Dell\UpdateService\Clients\CommandUpdate\Preferences\Settings\Schedule" /v "ScheduleMode" /t REG_SZ /d "ManualUpdates" /f
https://imgur.com/a/a3V0HqG
Hi All,
So I'm automating dell command update via a powershell script that installs it, and then pushes dcu-cli.exe commands to set things up how we want them. I can currently get it to use the bios password, but there doesnt seem to be any way of doing it without providing the bios password in clear text in the script.
DCU has an option to generate an encrypted password via your bios password + an encryption key password that you make up, but in order for it to use the encrypted password on the users end it also needs the encryption key. So my script would have an encrypted bios password. Cool. But it will also have the clear text key to decrypt it making the encryption useless? am i missing something here?
The bios password would be stored in a script, thats in an .intunewin package, on our intune instance, but still.