Since I deployed the Dell Command Update (DCU) version 5.5, I've noticed some strange behavior in the logs. The command I see is: `C:Program FilesDellCommandUpdatedcu-cli.exe /configure -biosPassword="xxxxxxx"`, but it's returning a non-zero result and is blocked because it's managed by the administrator. Interestingly, our BIOS isn't managed by Group Policy (GPO), and I couldn't find any reference to managing BIOS passwords via the Dell ADMX files. I didn't have this issue in previous versions, so I'm curious if anyone else has experienced this issue?
2 Answers
Could it be that someone added that command in the User GPO logon script? I remember back in the day, you could set a BIOS password without needing elevated permissions, but I think that changed around DCU 4.x.
We actually use the ADMX files and run that command at set intervals. You might want to check this Dell support page for more info: [Dell Support on BIOS Password Issue](https://www.dell.com/support/kbdoc/en-us/000187573/bios-password-is-not-included-in-the-exported-configuration-of-dell-command-update). It might shed some light on your situation.
What exactly is the encryption key that I need to provide? I can run the command manually without issue like this: `C:Program FilesDellCommandUpdatedcu-cli.exe /configure -biosPassword="xxxxxxx"`. Just trying to clarify.