KACE Product Support Question

Trigger reboot in a scripted install (preinstall tasks) - Dell KACE K2000

01/12/2016 2124 views
Dear all,

I would like to add a step "reboot computer" in the scripted install (preinstall tasks).
MDT and ConfigMgr have these steps build in, but can't find them in the K2000.

I know we have the ability to mark the checkbox "reboot required" for the postinstall tasks.
But this feature is lacking for the preinstall tasks.

Usage: Rebooting after enabling the TPM using the CCTK.

Thanks in advance!

3 Comments   [ + ] Show comments


  • Hello,

    It is not possible to allow reboot in the pre-installation phase.
    It is possible as a mid-level task.
    One of the possible solution is to create a ''fake'' image deployment or scripted install that does what you need in the pre-installation phase and then forces a reboot (or shutdown) of the KBE environment and then launch the right image deployment.
    Something like that.
    To shutdown/reboot in KBE you just need to create a BAT task with the following command:
    wpeutil shutdown
    wpeutil reboot

    Kind regards,
    Marco - StockTrader
    • you can do a preinstall reboot
  • Hi StockTrader, thanks for the reply. So basically, I'll need 3 Scripted Installs which need to be launched manually every time?
    1. All BIOS related settings + enable TPM + reboot
    2. Activate TPM + reboot
    3. Install OS scripted install + post installations
    • Maybe there is a better way than this one but I do not know for sure.
      If you have the K1000 as well you could run the Dell Client Command Suite (that replaces the CCTK) using a K1000 script. (but you need the K1000 and the machine needs to have an OS + the Kace Agent on it).
      And after you run the script(s) to activate the TPM chip you can proceed with the imaging.
      Kind regards,
      Marco - StockTrader
    • Additional idea..
      The main problem here is that if you reboot in the pre-install stage and then you run the deploy job (scripted install or image deployment again) we do not keep out of the box at what stage you were.
      But you can implement it by yourself with a bit of work..
      In the KBE the drive letter T: is mapped to the \\k2000\petemp share of the K2000.
      It is possible to write there.
      So with a bit of work it may be possible to have everything in the same Scripted Instal / Image
      The idea is to determine the MAC address of the machine (I can provide a simple VBS if needed) and use that value to create a folder in T:
      (e.g.: t:\685b358b0fff)
      Then with a script you can create file there that you can use as markers.
      If you find or not find the files you can decide it the reboot was already done or not and at what stage of your TPM process you are.
      Seems a bit complex but can be done..
      Kind regards,
      Marco - StockTrader
  • I am working on a solution for you using the KBEM that will take care of the steps for you, stayed tuned

All Answers

A preinstall reboot task:

Answered 01/12/2016 by: SMal.tmcc
Red Belt

  • For sure it is possible to reboot (I explained it in my first comment) but then you need to implement a way to keep the track of the stage that you executed otherwise you will enter in a loop.
    Marco - StockTrader
    • Will post a solution using the KBEM shortly
You will need to create 2 special kbe's using the KBEM
Here is the flow of what is going to happen. 
You will pxe boot and choose the special KBE1
It loads and runs your step 1 tasks, deploys KBE2 image to the hdd and restarts.
The machine boots to the local drive loading KBE2 and carries out step 2 tasks and sets the pxe to boot first.
(since you have pxe booted these you can assign a job to be deployed upon pxe boot)
The machine reboots and deploys the assigned job.  in the assigned job use the cctk (mid level) to set hdd to first in boot order.

Create the second KBE first, then create a usb boot stick with KBE.

I then took a working win10 image and kbe booted like I was going to capture it.
1. Open a recovery window
2. Place the usb boot stick in this machine and figure what drive letter is assigned to it.
3. Format the c drive with the /q option
4. Xcopy the contents of the boot stick to the cdrive  (xcopy e:\*.* c: /s /y)
5. from the main menu capture the image of the drive.
6. reboot and test the HDD boot to make sure it boots into the kbe2 env. (note if you boot all the way it will issue the cctk commands and restart)

If the machine fails to boot on it own to the local hdd in step 6 you must correct this and recapture.

Now that the second kbe is captured we will create another kbe to deploy that image automatically.
For the first KBE
Here is a picture I took at Dell World 2015 on how to create an automatic deploy via kbe
* Thanks to Corey Serrins for this information

In your second kbe image set a mid level to restart the machine.

In your final target image create a mid level task to set the boot order back to hdd first

Now that you have this in place set your image to deploy to your target on PXE.

F12 boot the machine and choose the first kbe from the menu and the rest will be hands free.

Answered 01/12/2016 by: SMal.tmcc
Red Belt

  • Hi Smal.tmcc, many thanks for this extended information. Very much appreciated!! Upon first reading it, it looks like a lot of work to simply reboot the computer (eg: MDT & ConfigMgr have a special step which you can use during the deployment.)

    I guess it also won't work (in my situation), since I have these restrictions. If you disagree, feel free to advise:
    - Booting over PXE => I'm deploying UEFI images, so need to use bootable USB stick. Image can't be deployed over PXE using the K2000 (correct me if I'm wrong)
    - CCTK commands: To enable the TPM, I need to set a BIOS Password. We have decided to have a dynamic password based on the serialnumber. So I can't hardcode the password in the CCTK commands in the KBEM since it's different per computer.
    • its not the reboot that is hard it is making it do different things between the steps.
    • For your situation what you can do if you have enough machines that you are doing this on.

      Do same things as above but you will create uefi boot sticks from kbes. still copy the second kbe to the hdd just as uefi instead. In the second kbe commands you will add an additional command to replace the existing boot.wim (xcopy) prior to restart.

      You would create a third kbem just like the 1st one that calls the scripted bat you want to deploy at the end. get the boot.wim from that and place it on the hdd also in step 4 in some subdir. then add the line to the kbe2 that will copy that to c:\sources and overwrite the kbe2 boot.wim file so when that HDD reboots it will boot to the hdd again but load that boot.wim which will start the scripted install for you.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ