Dell Command | Configure Version 4.12.0 User's Guide

Running Dell Command | Configure displays error messages

If you get the error message Required BIOS interface not found or HAPI load error, then uninstall and reinstall the Hardware Application Programming Interface (HAPI).

Running Dell Command | Configure on 32-bit, 64-bit, and ARM64-bit Windows supported system

Ensure that you are running cctk.exe based on the architecture of the system. If you are running Dell Command | Configure on a 32-bit supported system, browse to the x86 directory in the installation directory, and run Dell Command | Configure commands. If you are running cctk.exe on a 64-bit supported system, then browse to the x86_64 directory and run the Dell Command | Configure commands.

If you are running cctk.exe on an ARM64-bit supported system, then browse to the ARM64 directory and run the Dell Command | Configure commands.

If you are running Dell Command | Configure for 32-bit supported systems on a 64-bit supported system, then an error message is displayed: HAPI Driver Load Error.

If you are running Dell Command | Configure for 64-bit supported systems on a 32-bit supported system, then an error message is displayed: Not a valid Win32 application.

If you are running Dell Command | Configure for ARM64-bit supported systems on a 64-bit or 32-bit supported system, then an error message is displayed. The error message has the wording The specified executable is not a valid application for this OS platform.

Running Dell Command | Configure on Windows 7, Windows 8, Windows 8.1, or Windows 10 when user account control is enabled

To run Dell Command | Configure on systems running Windows 7 or later with User Account Control (UAC) enabled, right-click the Dell Command | Configure Command Prompt and select Run as administrator.

Running Dell Command | Configure on Linux

When you install Dell Command | Configure on a system running the Linux operating system, the entry, modprobe dcdbas, is added in the /etc/rc.modules file. After uninstalling Dell Command | Configure , the entry is not removed.

TPM activation

Trusted Platform Module (TPM) is an industry standard cryptographic module that provides attestation, integrity metrics and reporting, and a secure key hierarchy. Client systems use TPM to verify if the state of the system has changed between two boot cycles.

To activate and check the TPM activation:

1. If not set, set the BIOS password on the system. Type:

   cctk --setuppwd=<new-BIOS-password>

2. If not enabled, enable TPM by typing the following command:

   cctk --tpm=on

3. Reboot the system.
4. To activate TPM, type the following command:

   cctk --tpmactivation=activate --valsetuppwd=<Setuppwd>

5. Reboot the system without interruption till the operating system loads.
6. To check the status of TPM, type:

   cctk --tpmactivation

The status is displayed as activate.

SCE failing to run on Windows Preinstallation Environment (Windows PE)

The SCE generated using the Export option on the user interface is failing to run on Windows PE. To configure BIOS using SCE, on the target system running the Windows PE operating systems:

1. On systems running the Windows operating systems, extract the contents of SCE to a folder using the following command:

   SCE.exe /s /e=<folder_path_to_extract_SCE> 

   NOTE:For more information about using the command, use /h switch.
2. Copy the extracted contents to an accessible location on the system.
3. From the location of the extracted contents, run the following command to apply the configuration:

   applyconfig.bat /logfile <A valid and existing folder with write permission>\<A valid file name>

For example, applyconfig.bat /logfile C:\log.txt

To apply the configuration on a system, where setup or system password has been set, run the following command: applyconfig.bat /logfile <A valid and existing folder with write permission>\<A valid file name> "--valsetuppwd= <setup password>"

Example 1: applyconfig.bat /logfile C:\log.txt "--valsetuppwd=password"

Example 2: applyconfig.bat /logfile C:\log.txt "--valsyspwd=password"