I really need some help deploying the dell CCTK configuration file to workstations using the k1000. Here's what I have:

  • The latest K1000 version and the latest agent version (as of 10/06/11)
  • I have already figured out how to deploy the Dell CCTK client to workstations using the Distribution>managed installation section of K1000
  • I have installed Dell CCTK version 2.0.1 on my PC and created a multi-platform bios file (enabling WOL)
  • I exported those settings as a .cctk
  • I deployed the CCTK client using the kbox to a machine
  • I can't figure how to deploy the configuration file
The user's guide for the Dell CCTK says to deploy the configuration file just type cctk -i <filename> so I tried using the "issue a DOS command" script in the Scripts section of the K1000 with the following settings:
  • Enabled = yes
  • Deploying to just the one PC that I know has the Dell CCTK client installed
  • Run as: domain administrator (credentials entered correctly)
  • Task1 = I tried this 2 different ways:
  • 1) Launch “SYS\cmd.exe” with params “"C:\Program Files\Dell\CCTK\X86\cctk.exe" -i \\share\folder\config.cctk
  • 2) Run the batch file...Batch file:="C:\Program Files\Dell\CCTK\X86\cctk.exe" -i \\share\folder\config.cctk
Both of these ways did not work. I set an alert on the script to tell me when it's running and that worked but then the script would do nothing on the machine. The Run Now Status on the K1000 would say:
  • Pushed 1/1
  • Completed 0/1
  • And in the Run Now Detail, next to the name of the computer it's supposed to be running on, it always displays a question mark and a "status pending" message. I don't see any other logs or anything. But it does display all this in the Run Now Detail as well:

  • Start Time:Oct 06 2011 11:28:21 AM
    Script Name:Configure Bios after CCTK install
    Total Machines:1
    Pushed Machines:1 (100%)
    Push Successes:1 (100%)
    Push Failures:0 (0%)
    Completed Machines:0 (0%)
    Running Machines:1 (100%)
    Successes:0 (0%)
    Failures:0 (0%)
  • But when I check the BIOS of that machine, no changes have been made.
So, can anyone point me in the right direction or show me what I'm doing wrong? I really appreciate it.

Thank you.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


we actually do this with the K2000 as a post install but, this will still work. Zip up your CCTK directory with it's executables and the output you want is for an .ini file, do this by exporting the configuration. Add this as a dependency to a new script and add a task to launch an application.

in the Directory field use $(KACE_DEPENDENCY_DIR)

in the File field use cctk.exe

for parameters we use the following:

-i multiplatform_xp_bios_201107251116.ini -l "c:\documents and settings\all users\Dell\bios_config_xp.out"

this calls an ini file located in the zip file and outputs the results to "c:\documents and settings\all users\Dell\bios_config_xp.out".

No installation required on target machines, and if you make it an online script you can use admin credentials.
Answered 10/10/2011 by: craig.thatcher
Orange Belt

  • could you let me know how you did it as post install in K2000?
Please log in to comment
no installation of the dell cctk? How is that?
Answered 10/11/2011 by: lefttunknown
Orange Belt

Please log in to comment
We had to install the CCTK to get it to work with the K1000. We called the program directly via a bat file in a script, and that seemed to work. We only modified a couple of settings in the bios settings:


Launch “C:\UpdateBIOS.cmd” with params

batchfile contents:

"C:\Program Files\Dell\CCTK\x86\cctk.exe" bootorder --enabledevice=hdd --disabledevice=usbdev --valsetuppwd=*******
Answered 10/11/2011 by: ms01ak
Tenth Degree Black Belt

Please log in to comment
ORIGINAL: lefttunknown

no installation of the dell cctk? How is that?

simply packaging the resources works since it is a command line utility. you can delete the contents after you finish deploying.
Answered 10/12/2011 by: craig.thatcher
Orange Belt

Please log in to comment

Here's what I did to run the CCTK without having to install it on all of my computers, yet still letting me change the BIOS settings.

Here's my script that I use in KACE:



  1. Verify that “HKLM\SOFTWARE\Kace!BIOSupdated” is equal to “YES”.

On Success

  1. Log “BIOS has been updated already, nothing to do.” to “output”.


  1. Unzip “$(KACE_DEPENDENCY_DIR)\desktop_autoon.zip” to “$(KACE_DEPENDENCY_DIR)”.
  2. Launch “$(KACE_DEPENDENCY_DIR)\desktop_autoon\cctk.exe” with params “-i desktop_wol_pxe_enable_lowpower_disable_autoon3am.ini”.
  3. Set “HKLM\SOFTWARE\Kace!BIOSupdatedByKACE” to “YES”.

On Remediation Success

  1. Log “Successfully updated BIOS - enabled Wake-On-LAN and PXE, disabled Low Power (S5), and set AutoOn to 3am.” to “output”.

On Remediation Failure

  1. Log “FAILED to update BIOS - enabling Wake-On-LAN and PXE, disabling Low Power (S5), and set AutoOn to 3am.” to “output”.
I attached the file "desktop_autoon.zip" to the dependency directory (in this script) and the contents of that zip file structure looks like this:

1.    desktop_autoon.zip file structure

a.    Folder inside it called "desktop_autoon"

                                         i.    Inside desktop_autoon folder are the following files: cctk.exe, cctk_x86_WinPE.bat, cctk_x86_WinPE_3.bat, desktop_wol_pxe_enable_lowpower_disable_autoon3am.ini, mxml1.dll, pci.ids", and a folder called "HAPI".

a.    The files inside HAPI folder are: dcdbas32.cat, dcdbas32.inf, dcdbas32.sys, dchapi32.dll, dchbas32.dll, dchcfg32.exe, dchipm32.dll, dcmdev32.exe, HAPIInstall.bat, hapint.exe, HAPIUninstall.bat.




Answered 01/22/2013 by: jwaltersnsm
Purple Belt

  • FYI: The "desktop_wol_pxe_enable_lowpower_disable_autoon3am.ini" is the file that I created using the CCTK tool. The rest of the above files are from the program that I installed on my computer.
Please log in to comment