Software

We lock all Dell Machines, both laptops and desktops, using a BIOS Lock executable that a previous admin Built, using I believe SCE. He built another executable that is designed to unlock the BIOS so that we can do upgrades. We are finding that the exe file used to unlock the BIOS is failing to unlock it. Every time I attempt to do so, this is what comes up on the remove password txt file. Can anyone discern where I may need to make an adjustment? If desired, I can try to link the raw configuration files for the lock and unlock .exe files.

਍਍[07/12/19 14:41:47] Self Contained Executable(SCE) Execution Start
[07/12/19 14:41:47] Original command line: [omitted]
[07/12/19 14:41:48] SCE EXE Version: 3.1.0.0
[07/12/19 14:41:48] SCE Release: R309560
[07/12/19 14:41:48] User Command: unattended
[07/12/19 14:41:48] SCE Capabilities Value: 471859199 (0x1C1FFFFF)
[07/12/19 14:41:48] SCE Vendor Software Version: 3.1.0
[07/12/19 14:41:48] Local System/Model Compatible with this Package? Yes
[07/12/19 14:41:48] Local System OS Version: 6.2.0.0
[07/12/19 14:41:49] OS Compatible with this Package? Unknown
[07/12/19 14:41:49] Local System OS Language: Unknown
[07/12/19 14:41:49] Language Compatible with this Package? Unknown
[07/12/19 14:41:50] Identified Behavior : unattended
[07/12/19 14:41:51] Temporary payload log file name: C:\ProgramData\dell\drivers\BIOSLockRemovePasswd\SCEA7DB.tmp
[07/12/19 14:41:51] Translated Command Line : applyconfig.bat -l="C:\ProgramData\dell\drivers\BIOSLockRemovePasswd\SCEA7DB.tmp"
[07/12/19 14:41:51] Path : C:\ProgramData\dell\drivers\BIOSLockRemovePasswd
[07/12/19 14:41:51] Identified Behavior : unattended
[07/12/19 14:42:02] Append Vendor Software Log: C:\ProgramData\dell\drivers\BIOSLockRemovePasswd\SCEA7DB.tmp
[07/12/19 14:42:02]
--- Start of Vendor Software Log ---

[07/12/19 14:42:02] ASCII payload log file detected.
[07/12/19 14:42:02] 2019/07/12 14:42:02 cctk -
Option : admsetuplockout

2019/07/12 14:42:02 cctk - The option 'admsetuplockout' is not available or cannot be configured
through this tool.

2019/07/12 14:42:02 cctk -
Option : energystarlogo

2019/07/12 14:42:02 cctk - The option 'energystarlogo' is not available or cannot be configured
through this tool.

2019/07/12 14:42:02 cctk -
Option : numlock

2019/07/12 14:42:02 cctk - The option 'numlock' is not available or cannot be configured
through this tool.

2019/07/12 14:42:02 cctk -
Option : postf12key

2019/07/12 14:42:02 cctk - The option 'postf12key' is not available or cannot be configured
through this tool.

2019/07/12 14:42:02 cctk -
Option : postf2key

2019/07/12 14:42:02 cctk - The option 'postf2key' is not available or cannot be configured
through this tool.

2019/07/12 14:42:02 cctk -
Option : pwdlock

2019/07/12 14:42:02 cctk - The option 'pwdlock' is not available or cannot be configured
through this tool.

2019/07/12 14:42:02 cctk -
Option : usbemunousbboot

2019/07/12 14:42:02 cctk - The option 'usbemunousbboot' is not available or cannot be configured
through this tool.

2019/07/12 14:42:02 cctk -
Option : virtualization

2019/07/12 14:42:02 cctk - The option 'virtualization' is not available or cannot be configured
through this tool.

2019/07/12 14:42:02 cctk -
Option : wakeonlanbootovrd

2019/07/12 14:42:02 cctk - The option 'wakeonlanbootovrd' is not available or cannot be configured
through this tool.

2019/07/12 14:42:02 cctk -

WARNING : Unable to set bootorder for : hdd,floppy,cdrom,embnic,usbdev
2019/07/12 14:42:02 cctk -

WARNING : Unable to disable the devices : floppy,cdrom,embnic,usbdev
2019/07/12 14:42:02 cctk -

WARNING : Unable to enable the devices : hdd

2019/07/12 14:42:02 cctk -  DeviceStatus DeviceNumber     DeviceType    Shortform  DeviceDescription
2019/07/12 14:42:02 cctk -  -------------------------------------------------------------------------
2019/07/12 14:42:02 cctk -  -------------------------------------------------------------------------
2019/07/12 14:42:02 cctk - You can use DeviceNumber or shortform to set the boot order.
2019/07/12 14:42:02 cctk - Example1: cctk bootorder --sequence=2,1,3 --disabledevice=1 --enabledevice=2,3
2019/07/12 14:42:02 cctk - Example2: cctk bootorder --sequence=cdrom,hdd.2,hdd.1 --disabledevice=hdd.2 --enabledevice=cdrom,hdd.1
2019/07/12 14:42:02 cctk - In file operation, same command can write like bootorder=+cdrom,-hdd.2,+hdd.1

*** NOTE: The preceding command on bootorder completed successfully for the non-active boot list.To determine the active boot list, run the following command: cctk bootorder --activebootlist
For more information on the boot lists, consult the help and user documentation.CCTK STATUS CODE : SUCCESS
[07/12/19 14:42:02]
--- End of Vendor Software Log ---

[07/12/19 14:42:02] Get name of the Folder file: [omitted]
[07/12/19 14:42:02] Vendor Software Return Code: 0
[07/12/19 14:42:03] Name of Exit Code: SUCCESS
[07/12/19 14:42:03] Name of Exit Code: SUCCESS
[07/12/19 14:42:03] Exit Code set to: 0 (0x0)
[07/12/19 14:42:03] Result: SUCCESS
[07/12/19 14:42:03] Name of Exit Code: SUCCESS
[07/12/19 14:42:04] Execution terminated at date-time 07/12/19 14:42:04
[07/12/19 14:42:04] ######