Deploying CCTK BIOS setting in K2000
I need to automatically do the BIOS settings while imaging for all machines. I created an exe file for the bios setting using CCTK. In KACE2000, I created an application in pre installation tasks, uploaded the exe file & in command line "call cctk.exe". This task was included in the image.
It does not work. The error says 'The subsystem needed to support the image type is not present'
Answers (3)
The subsystem needed to support the image type is not present means that you are running a 32bit .exe in a 64bit KBE. I also recommend putting cctk in the kbe using kbem, and not just because I wrote it ;)
Corey
Lead L3 Enterprise Solutions Engineer, K2000
If my response was helpful, please rate it!
Comments:
-
I tried adding cctk to kbe using kbem. How do you know cctk is added in your kbe? - work@deploy 11 years ago
-
from the main imaging menu open recovery - command window
you should be at the x:\windows\system32 do a cd\cctk and browse from, there - SMal.tmcc 11 years ago
-
For the error 'The subsystem needed to support the image type is not present', you said I was running a 32bit.exe file in a 64 bit KBE. How do I make a 64bit exe with CCTk toolkit? - work@deploy 11 years ago
-
install the cctk to your tech machine that has WAIK installed. The got-you is you will need 2 tech machines to upload the cctk to both 32 and 64 bit. While the WAIK contains both 32 and 64 the cctk is installed for the os version only on the machine. - SMal.tmcc 11 years ago
-
on a 64 pxe boot you should see x:\cctk\cctk_x86_64\ - SMal.tmcc 11 years ago
Use the KBE manipulator and add the CCTK to your boot environment. You can then preform command calls to the x: drive and make changes that way instead of compiling exe's, much easier, i switched to this method and when you need to change something you edit the command line and are donel.
http://support.dell.com/support/edocs/SOFTWARE/smcctk/1.0/ug/html/cctkugcd.htm
Comments:
-
I have added CCTK to KBEM. How to perform command calls to the X:drive - work@deploy 11 years ago
-
create a batch task on the k2000 and use lines like
(this is for 32bit)
start /wait x:\cctk\x86\cctk.exe --pwdlock=unlocked
start /wait x:\cctk\x86\cctk.exe --setuppwd=Newpassword --valsetuppwd=currentpassword - SMal.tmcc 11 years ago-
on a 64 pxe boot you should see x:\cctk\cctk_x86_64\ - SMal.tmcc 11 years ago
-
I also add the CCTK to my images so I can post cctk changes if needed, then I call it from c:\program files\... instead of x:\cctk\... - SMal.tmcc 11 years ago
-
Success.Thanks - work@deploy 11 years ago
-
another advantage with the cctk also on the images. You can use the k1000 to push changes after imaging - SMal.tmcc 11 years ago
I wouldnt recommend running the CCTK packages as a post install task. Inside the KBE as stated above will be the best way to go. If you need to run one after install I would deploy it using the K1000 and a script. There is an article for this here: http://www.itninja.com/blog/view/dell-bios-manipulation-with-the-k1000-and-dell-cctk
Here is more information about the CCTK: http://en.community.dell.com/techcenter/systems-management/w/wiki/1952.dell-client-configuration-toolkit-cctk.aspx
Comments:
-
We installed the CCTK in all our base images to allow us to change the setup password on the fly. We can push a k1000 script and call the cctk on the local HDD's via script commands. - SMal.tmcc 11 years ago
