KACE Product Support

We've been using the command line version of the CCTK with decent success. From the gui export your settings as an .ini file and running it like so.

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

This takes the ini file and outputs it to the location above the new 5.2 agent for logging, you can execute with "Run As" and get things moving.

Can you share your script? Screenshots of settings and the script are helpful.

It's a real simple Offline script. the only thing I changed between DCCU and CCTK was the actual file; I even kept the same filename.

EDIT: I forgot to mention, the log also shows:
C:\Program Files\KACE\KBOX\\packages\kbots\61\CoNP-Dell-BIOS.exe: process exited with code: -1073741819

I haven't used the CCTK to upgrade the BIOS, only to change BIOS settings. To use it, I had to install the .MSI, then I could run command line options.

Did you install the .MSI? Could that be the cause of an SCE error, that an expected service does not exist? Sande

I know my description in the screenshot said "update," but I'm only using it to push out settings. I'm not sure why I'd need to install the full CCTK onto every system, since on my technician install of the kit I get the option to create an EXE. Said EXE changes the BIOS settings without a problem when I manually run it on my test sytem, but gives me the SCE error running via script.

Jon- maybe I'm not seeing it, but can you post the actual script? All I see is the top of the page, the bottom is the script. Online scripts can run as a specified user; it might be permissions?

You're right, I guess I cropped out too much of the image so it would fit. I customized the BIOS as needed on CCTK on my computer, then exported a configuration .exe, which I uploaded to Kace. I had my original DCCU script configured just like this one launching the exe and it worked great. Do you think I'd be better off using a batch file?


Verify that the file “$(KACE_DEPENDENCY_DIR)\CoNP-Dell-BIOS.exe” exists Finish[/align][/align]
On Success Launch “$(KACE_DEPENDENCY_DIR)\CoNP-Dell-BIOS.exe” with params “”.
Finish[/align][/align]

EDIT: I rewrote the script to run the configuration file via a batch script, but I still get the SCE error, and no changes are made.

What OS & Architecture?
Can you run this script on another OS/Architecture? Can you run this script on another model of PC?
Just trying to rule things out or see if maybe we're running up against a know bug or something.

Chris,
My workstation with CCTK installed is an Optiplex 745 (small form) running Win7 x86. The script runs through Kace on my system without errors, but it also has the full CCTK installed.
Most of our systems, including what I'm testing on, are running WinXP x86. I was originally testing the script on my Latitude D820, but just attempted to run it on some Optiplex 745s (desktop). On all 5 Optiplex systems it gave a memory error:
Application popup: CoNP-Dell-BIOS.exe - Application Error : The instruction at "0x006c44bc" referenced memory at "0x00000000". The memory could not be "read".

I installed CCTK 2.01 on my laptop and attempted to push the configuration exe to it, but I still got the SCE error. When I manually ran the exe that had been downloaded via the script, it ran without problems.

I may have come up with the cause, but not the solution yet. If I'm logged onto a system as a local admin, I can run the program without problems, but it does not run for non-admin users. If I'm logged on as a non admin and try to Run As an admin, I get the SCE error. So, apparently, you can't do a run as of SCE in WinXP. I sent the problem on the Dell tech support to see if they have any ideas. This is probably an issue for those organizations that use SCCM, as well.

ORIGINAL: craig.thatcher

We've been using the command line version of the CCTK with decent success. From the gui export your settings as an .ini file and running it like so.

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

This takes the ini file and outputs it to the location above the new 5.2 agent for logging, you can execute with "Run As" and get things moving.

---------------
Thank you, Craig! I thought the exe option would work like it did with DCCU, but obviously it doesn't. I went through the GUI again and exported the ini file. After I zipped and uploaded the x86 folder as a dependency, I was able to run the configuration as a script through Kace. Thanks again!

Hi Jon,

I'm new to KACE and this utility. I have exported my settings as an inf file, but not sure what script to use to get KACE to run it. Do you have a sample script that you use it get it running?

Using Craig's instructions as a guide, I zipped the "C:\Program Files\Dell\CCTK\X86" folder (x86_64 would probably work as well) and uploaded the new zip with my ini as dependencies. This may be more than necessary, but I found that without including the x86 folder, there were some dependent files missing. I then created the below offline KScript, setting it to run while logged off at the next checkin.:


Verify
1. Unzip “$(KACE_DEPENDENCY_DIR)\CoNP-Dell-BIOS.zip” to “$(KACE_DEPENDENCY_DIR)”.

On Success

1. Launch “$(KACE_DEPENDENCY_DIR)\cctk.exe” with params “-i Config-BIOS.ini -l BIOS_configured.txt”.
2. Upload “$(KACE_DEPENDENCY_DIR)\BIOS_configured.txt” to the server.
I've had mixed results with the boot device order, but all of the other changes I made appeared to apply without a problem. Best of luck to you!