NOTE: Dell Command | Configure 4.0 or later requires platforms supporting WMI-ACPI BIOS. The complete functionalities of Dell Command | Configure is available for the supported platforms, refer the Supported Platforms for more information.
NOTE: Ensure SMM Security Mitigation BIOS Feature is Disabled on applicable platforms running Linux operating systems. Dell Command | Configure on Linux operating systems will not work as intended if SMM Security Mitigation BIOS feature is Enabled.
NOTE: Dell Command | Configure 4.1 or later Supported Features Nomenclature (Names along with its Configuration Possible Value Names) have been refreshed across CLI and GUI. Dell Command | Configure even though is Backward Compatible for the Older Nomenclature, it is highly advisable to migrate/create Scripts to start using these Newer Features Nomenclature.
View the complete list of the Newer and the Older Nomenclature here
For the limited functionalities on non WMI-ACPI complaint platforms, see Windows SMM Security Mitigations Table Compliance section in Dell Command | Configure User's guide.
Dell Command | Configure is a packaged software application that provides configuration capability to business client platforms.
This product consists of a Command Line Interface (CLI) and Graphical User Interface (GUI) to configure various BIOS features. Dell Command | Configure supports following Windows and Linux operating systems: Windows 7, Windows 8, Windows 8.1, and Windows 10, Windows Pre-installation Environment (Windows PE), Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, and Ubuntu Desktop 16.04.
This is the 4.1 version of Dell Command | Configure.
Fixes in the Release
Fix: Dell Command | Configure sets an unknown password for the BIOS issue has been resolved
Description: While running the following command cctk.exe --setuppwd --valsetuppwd=abcd1234, Dell Command | Configure displays Only validation option. No actions will be performed. Password is set successfully message issue has been resolved now.
Fix: Local package takes few seconds to load for the first time issue has been resolvedDescription: Once you launch the GUI Application for the first time, the local system package takes few seconds to load. As a result of that, the application takes few seconds to display the data grid. This delay is not observed during the next cycle onwards issue has been resolved now.
Fix: GUI Application takes few seconds to exit if closed immediately after launch issue has been resolvedDescription: Once you launch the GUI Application and close it immediately, the closure is delayed by few seconds. This happens for the first time and is not observed during the next cycle onwards issue has been resolved now.
Fix: Issue in validating the feature for non enum types has been resolved
New in the Release
– GUI launch time has been improved
– SCE execution time has been improved
– Configuration read and write time using command line has been improved
Dell Command | Configure 4.0
Dell Command | Configure 3.3
Dell Command | Configure 3.2
Dell Command | Configure 3.1.2
Dell Command | Configure 3.1
Dell Command | Configure 3.0
1. Activating the TPM with Dell Command | Configure
2. Setting the BIOS defaults using Dell Command | Configure
use a space character to clear the password. For command-line usage, the HAPI driver needs to be installed. It won't work with just the files present.
How do I get support for this tool? My problem is needing to change UEFI boot order. I would like to ensure the computer boots to the hard disk -- and am having trouble because the hard disk is sometimes UEFI.1 and sometimes the NICIPv4 and NICIIPv6 show up ahead of the disk in the boot order so the NIC IPv4 is UEFI.1 and the Hard Drive is UEFI.3--- can I send a command to only boot from the hard disk? And not the NIC and not a bootable USB device? The UEFI boot order stuff is really hard and confusing compared to legacy boot order.
The only fix for making the hard drive boot first that I've found is to disable all the other options.
UEFI likes to name the hard drive dynamically by vendor ID or as "Windows Boot Manager" which is associated with a unique GUID ID (I've seen it list multiple entries for Windows Boot Manager before). Thus it's not something it'll let you set ahead of time. Perhaps there is a fix that can be implemented in CCTK but it might not be possible with the UEFI architecture.
13" XPS 9350 and 15" XPS 9550 have options that are not configurable with DCC 3.1 that need to be enabled to allow for PXE booting from an USB-C dongle. In the BIOS, the settings are under:
Settings -> System Configuration -> USB/Thunderbolt Configuration -> Thunderbolt Boot Support
Settings -> System Configuration -> USB/Thunderbolt Configuration -> Enable Thunderbolt (and PCIe behind TBT) Pre-boot
I assume this is because Thunderbolt 3 is so new.
Deos it support Dell Latitude E5270?
Yes, it does support the E5270.
Could you please confirm that the packages created with Dell Command Configure 3.1 are compatible with the model Dell E7470. I didn't find in the documentation the list of the supported product.
I'm trying to push this out to all of our laptops in our env, but I receive an error when I run this on my laptop. I'm trying to configure the setting to Disable Wifi when docked.
Thanks - Josh
The option "controlwwanradio" is not available or cannot be configured through this tool.
Hello, i have a problem to set bios settings with enabled bios Password. if i start the .exe with --valsetuppwd=ABCD123 the command line is translated to --valsetuppwd=abcd123
so the Software say the Password is wrong.
if i set the bios to lower case everthing works.
here the log:
[11/25/16 08:50:03] Self Contained Executable(SCE) Execution Start
[11/25/16 08:50:03] Original command line: GB-Standard-V6.exe --valsetuppwd=ABCD123
[11/25/16 08:50:03] SCE EXE Version: 220.127.116.11
[11/25/16 08:50:03] SCE Release: R309560
[11/25/16 08:50:03] User Command: unattended
[11/25/16 08:50:03] SCE Capabilities Value: 471859199 (0x1C1FFFFF)
[11/25/16 08:50:03] SCE Vendor Software Version: 3.1.0
[11/25/16 08:50:03] Local System/Model Compatible with this Package? Yes
[11/25/16 08:50:03] Local System OS Version: 18.104.22.168
[11/25/16 08:50:03] OS Compatible with this Package? Unknown
[11/25/16 08:50:03] Local System OS Language: Unknown
[11/25/16 08:50:03] Language Compatible with this Package? Unknown
[11/25/16 08:50:03] User Parameter: valsetuppwd
[11/25/16 08:50:06] Identified Behavior : unattended
[11/25/16 08:50:06] Temporary payload log file name: C:\ProgramData\dell\drivers\GB-Standard-V6\SCE757A.tmp
[11/25/16 08:50:06] Translated Command Line : applyconfig.bat -l="C:\ProgramData\dell\drivers\GB-Standard-V6\SCE757A.tmp" "--valsetuppwd=abcd123"
[11/25/16 08:50:06] Path : C:\ProgramData\dell\drivers\GB-Standard-V6
[11/25/16 08:50:14] Append Vendor Software Log: C:\ProgramData\dell\drivers\GB-Standard-V6\SCE757A.tmp
--- Start of Vendor Software Log ---
[11/25/16 08:50:14] ASCII payload log file detected.
[11/25/16 08:50:14] 2016/11/25 08:50:11 cctk -
Option : optimus
2016/11/25 08:50:11 cctk - The option 'optimus' is not available or cannot be configured
through this tool.
2016/11/25 08:50:11 cctk -
Option : switchablegraphics
2016/11/25 08:50:11 cctk - The option 'switchablegraphics' is not available or cannot be configured
2016/11/25 08:50:11 cctk - The setup password supplied is incorrect. Please try again.
CCTK STATUS CODE : FAILURE
--- End of Vendor Software Log ---
[11/25/16 08:50:14] Get name of the Folder file: C:\Temp
[11/25/16 08:50:14] Vendor Software Return Code: 0
[11/25/16 08:50:14] Name of Exit Code: SUCCESS
[11/25/16 08:50:14] Exit Code set to: 0 (0x0)
[11/25/16 08:50:14] Result: SUCCESS
[11/25/16 08:50:14] Execution terminated at date-time 11/25/16 08:50:14
[11/25/16 08:50:14] ######
Thanks for help
After selecting my options to enable WoL in Command | Configure v3.1.2, I get the following error when I click the Export .EXE button: "Dell Command Configure has stopped working, a problem caused the program to stop working correctly. Please close the program."
In Event Viewer, I see the following:
Application Error, Event ID 1000
Faulting application name: cctkgui.exe, version: 22.214.171.124, time stamp: 0x5790c20c
Faulting module name: KERNELBASE.dll, version: 10.0.10240.17113, time stamp: 0x57cf93c8
Exception code: 0xe0434352
Fault offset: 0x000000000002a1c8
Faulting process id: 0x1e5c
Faulting application start time: 0x01d25bc0b4e064c5
Faulting application path: C:\Program Files (x86)\Dell\Command Configure\cctkgui.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: bd5c7fc2-eda1-46c1-b9c6-3664022da27a
Faulting package full name:
Faulting package-relative application ID:
.NET Runtime error, Event ID 1026
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
at System.Windows.DependencyObject.SetValue(System.Windows.DependencyProperty, System.Object)
at CCTK.App.ShowWindowAlertText(System.String, System.Windows.MessageBoxButton, System.Windows.MessageBoxImage, Int32)
at CCTK.App.ShowWindowAlert(System.String, System.Windows.MessageBoxButton, System.Windows.MessageBoxImage, Int32)
at CCTK.App.HandleRecoverableError(System.Exception, System.String)
at Dell.CCTK.BusinessLogic.CCCTKOperations.ExportSCE(System.String, CCTK.DataClasses.ConfigInfo, System.String, System.String, System.String, Dell.CCTK.BusinessLogic.SelectFileViewModes, Boolean, System.Object ByRef)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
I had the same problem when I was using v3.1.0 as well. I uninstalled that, rebooted, and installed 3.1.2 afterwards. Same issue.
I have a Dell OptiPlex 3010
Windows 10 Enterprise 2015 LTSB (64-bit)
Intel i3 3220 3.3GHz CPU
I googled the error and saw that this same problem was occurring on Dell XPS models so I followed their instructions and updated the BIOS. My BIOS is now at version A17 but same issue.
Any ideas what could be causing this?
Thank you very much for your help!
FYI, in case anyone is reading the comments; there is a new version available:
Version 3.2.0, A00
Release date 23 Dec 2016
<ADMIN NOTE: Broken link has been removed from this post by Dell>
Integration Suite version 4.2 cannot import a configuration package create by Dell Command Configure 3.2. Will this be fixed soon?
No problem to create (with my own process) a WinPE10 x64 with a working CCTK 3.2
However with WinPE10 x32, CCTK 3.2 is not working (with my own process to make the PE and also with the Dell proces cctk_x86_winpe_10.bat)
When I type cctk, it return nothing, no message, no error, nothing...
Any idea on how to create a working WinPE10 with CCTK 3.2 ?
KriKri it's not just WINPE 10. The same thing happens to me in WINPE 5 with just the X86 version. Broken :(