Dell Client Configuration Toolkit (CCTK) Known Issues - Systems Management - Wiki - Systems Management - Dell Community
Wikis - Title

Dell Client Configuration Toolkit (CCTK) Known Issues

Systems Management

Systems Management
Dell Systems Management Solutions: Dell OpenManage, iDRAC, Repository Manager, Microsoft SCCM, Chassis Managment Controller, and more

Systems Management - Wiki

Dell Client Configuration Toolkit (CCTK) Known Issues

Systems Management - Wiki

If you're encountering issues with the CCTK, review the issues on this page.

User Reported

These issues have been reported by users.

  1. A CCTK SCE crashes when right clicking on it and selecting the Run As option. See this thread for more information.
  2. Calling CCTK from a directory other than the cctk folder causes dynamic loading of HAPI to fail with error "HAPI driver load error". See this thread for more information.
  3. Installing CCTK without the GUI component causes HAPI to not get installed. See this thread for more information.
  4. Using CCTK to detect or enable the signed BIOS feature on OptiPlex 960s causes the OS to lock up. CCTK is unable to detect the signed BIOS feature on the Latitude E6420 and D630. See this thread for more information.
  5. The --propowntag option for CCTK does not work correctly with --valsetuppwd option on the Latitude E5510 and E6510. The BIOS password must be cleared first, then use propowntag without valsetuppwd, and then set the BIOS password back. See this thread for more information. This also affects OptiPlex 790. See this thread for more information.
  6. Some Latitude models may not support the  --controlwlanradio option for controlling WWAN/WLAN radio settings. See this thread for more information.
  7. The CCTK --latitudeon=disable option fails on Latitude on E4310. See this thread for more information.
  8. Various issues have been reported with device boot order with --bootorder and SCE boot order options. See thread 1, thread 2, thread 3.
  9. Setting the asset tag with CCTK on an OptiPlex 790 may not work. See this thread for more information.

Known Issues at Release

These issues are noted in the CCTK readme as of version 2.0.1.

Command Line

  • Currently, the --enabledevice and --disabledevice options may not work in UEFI-enabled systems. These options will work after upgrading to future BIOS releases.
  • If the system is not connected to Internet, Windows 7 does not recognize the digital signature validity of CCTK installation file. Connect the system to Internet and validate the digital signature.
  • To upgrade CCTK 1.0 to any future releases, uninstall CCTK 1.0 and install the current release. For more information, see the "Dell Client Configuration Toolkit User's Guide" available on support.dell.com/manuals or User's Guide Online available with CCTK.
  • While running CCTK, if you get an error message, "BIOS Interface not found.", uninstall HAPI using the hapiuninstall.bat script located under the HAPI folder, and install it again using the hapiinstall.bat script located in the same folder.
  • Do not use the infile or outfile option in the ini file.
  • Read-only options, such as asset, svctag, and so on, do not report if they are used along with the -o option.
  • At present, CCTK supports only single byte characters for asset set operation. If the user has a different locale, change the keyboard layout to English before using the asset option. When you execute cctk.exe on Microsoft Windows XP Professional or Microsoft Windows XP Professional SP2, a blue screen may appear. This is a known Microsoft issue and Microsoft provides a fix for this. For more information, refer to http://www:support.microsoft.com/kb/921337.
  • Following are the known issues on OptiPlex 740:
    • floppy option does not work.
    • usbemu option does not work.
    • asset, minsizeofcontigmem, bioscharacteristics, and completion code may not work.
  • On Precision T3500, CCTK does not report the correct value of the turbomode option. Though the option is enabled, CCTK reports it as disabled.
  • On Latitude XT2, the busratio option does not set the argument max.
  • When you install CCTK on a Linux system, after installing the omilcore rpm, the following message is displayed: "To start all installed services without a reboot, enter the following command: srvadmin-services.sh start.". You can ignore the message and can proceed with the installation of other rpms.
  • CCTK log file does not capture information related to the sub options of commands.
  • On OptiPlex 760, CCTK may allow to set setup and system passwords with number of characters lesser than what BIOS mandates.
  • On Precision M4400, the bootorder option may not display the correct number of boot devices.
  • On OptiPlex 760, if system password is set, BIOS may not allow to set a setup password. CCTK does not provide an error message in such a scenario.
  • When you upgrade CCTK 1.1 to 1.2.1, CCTK contains the previous version of User's Guide along with a link to 1.2.1 User's Guide.


Graphical User Interface

  • On launching CCTK GUI from Optiplex 990 and Latitude D630 (without administrator privileges), the CCTK GUI screen takes some time to appear. This does not hamper the system resources and CCTK will be functional.
  • CCTK GUI supports only printable characters for its text-entry fields. If the BIOS has non-printable characters, the GUI may fail to load and display the following error message: "Unexpected Error at System.Xml.". Ensure that BIOS options like asset and propowntag values do not contain non-printable characters.
  • On successive attempts to invoke the CCTK GUI, the following error message is displayed: "Object reference not set to an instance of an object.". Click 'Continue' to access the GUI.
  • In rare cicumstances, when .NET libraries may not have loaded correctly, exporting SCE gives an error message like "Unexpected Error ". This does not affect the CCTK functionality. Do export again and it will be successful.
0
Comments
  • Any news about the reported issue from Ladewig-Wustl he posted under en.community.dell.com/.../19979685.aspx ?

    He reported that HAPI is not loaded if you call cctk.exe from outside the directory where cctk is located. We're able to reproduce exactly the same behavior (set BIOS settings through a cctk.exe command line in a task sequence under SCCM). Tested with the latest CCTK version 2.0.1.0.