KACE Product Support Question

Pairing Automated Deployments & Get/Set Computer Name?

03/14/2016 1403 views
Good day ITNinja,

I am doing some testing with both Automated Deployments, and the Get/Set Computer name options in Kace.

I see how the Get/Set works, and it appears to work fine.
I also see how the Automated Deployments work, and they appear to work fine as well.

So I tried to do an AD with an image that has Get/Set as Pre and Mid level tasks. The target PC is right next to me, so it failed on image, because it couldn't set a name.

But in a scenario such as I'm sitting on the beach and get a call that a machine is compromised and I need to reimage it, how can I configure an Automated Deployment that does one of two things:

1. Gets the existing PC name, reimages it, and applies the same name back on? (Useful for redeploying the same machine and role.)
2. Allows me to only set the name and have it apply during the image process? (Useful for simply refreshing an image and giving a name.)

Additionally, if an AD requires booting to the NIC, how can I set a target computer which otherwise boots from the HDD to boot from the NIC this one time?


-- Ray

Answer Summary:
0 Comments   [ + ] Show comments


Answer Chosen by the Author

I have a keepname and entername deployment for my images

the get set computer name task will take care of the naming.  Create a pre-install app task with the GetComputerName_x64.exe and for parameter call


and it will collect the name

create a second pre-install task using the same file but with (prompt for computerrname)

GetComputerName_x64.exe /dialog

and it will prompt for the name to be input.

create a set mid level task to apply either one using


if you have a k1000 you can use it to push out a script to use the Command Configure to change the bios boot order to PXE first and reboot.  The machine will boot to the k2, image and as mid task use the CC to change thje boot order back
Answered 03/14/2016 by: SMal.tmcc
Red Belt

  • I'm interested in using the Command | Configure utility but am having a hard time finding applicable documentation on how to integrate this product into my workflow alongside my K1000/K2000.

    If I understand what I've read so far, I can include CMD/CFG either in an image as a post-installation task or (potentially) as a Managed Distribution that I can push out to my Windows clients.

    Then, I can create custom settings packages that I guess I can send out to individual computers?

    Is that the gist? The documentation I'm reading is not as clear as I'd like. Any links you can drop?
    • I install on all my clients and include in all my kbe's by using the KBEM to add it. It has a command line exe you can call to make changes with.

All Answers

the command line pdf can be found here:

here is my k1 script to set pxe to boot

then as a mid task you call the cctk.exe and change the boot order back to hdd first

x:\command_configure\amdx64\cctk.exe bootorder --sequence=hdd.1,hdd.2,usbdev,cdrom.embnic --valsetuppwd=password@1
Answered 03/15/2016 by: SMal.tmcc
Red Belt

  • sorry posted the x86 script but gave you the x64 mid task call. you will get the idea though
    • I appreciate the info and link. If you haven't gathered, I'm still green as a Kace admin, so trying to tie this in a challenge for me.

      So if I understand this correctly, this is a script that you run against the target PC. It will flip the boot-order and restart the computer.

      PC boots to NIC and if I have an automated deployment set for the target PC, it will connect to Kace and automatically pull the image I have selected.

      At which point does the midtask to revert the boot order take place?
      • the image will be deployed to the machine and still in winpe mode (mid level). about to reboot to run post sysprep and post tasks yet. So that way it will boot like normal and finish all its post tasks. to run as a mid level task requires you to add the cctk to the KBE

        To create a mid or post application task you can install the Command Configure to a machine zip up either the x86 or x86_64 files (cctk.exe, mxml1.dll and pci.ids files) then call the cctk as an application task, this is another way to save having to install in your kbe's and images.
  • Progress so far:

    I have a Managed Installation and a Post-Install task to install Command | Configure. It leaves a desktop shortcut that I want to remove (and have to find out how), but it's there.

    I created a Run Now script that calls cctk.exe, changes the boot order, and restarts the machine. (Thank you)

    I then created an Automated Deployment, based on MAC address that pushes out my image on Next Boot.

    One concern: In the process of reverting from NIC boot to HDD boot, I copied my original script, reversed the parameters, and exported it to the K2000 as a Post-Install task. It is not available as a mid-level task, so I'm not sure if I did something wrong, or if it will still work as a Post-Install task.

    Regardless, I'm testing now. Ran the script against my target machine, it executed and restarted, it booted to NIC and my Automated Deployment is underway.

    I will post an update at the end on whether the post-install task to revert to HDD boot executes properly or not.
    • when you create the post application task choose Runtime Environment:
      K2000 Boot Environment (Windows) and it will create it as a mid level task
      • the only real downfall as a post task is it will cause a boot delay in your post tasks till the pxe menu times out prior to it running and rebooting
      • Replying to your second comment, it actually failed as a post-install task.

        I created it as you suggested, it is now an available mid-level task, and I will be testing that next.
      • did you zip the files and attach to your task?
      • For the Command Client? Not yet. This is just testing right now. Fine tuning will likely involve that.
    • if you added the command configure to your KBE using the KBEM it is only available at mid level (x drive) once the deployment reboots from mid to start the post the x files go away. for post you would have to install the C|C to you image prior to sysprep and call it from the c: drive. or zip and include them as an application task attachment and call it from the task
      • I see what's happening now. The full C|C software won't install until (and as) post-installation, but the script to change the boot happens in mid, and there's no cctk.exe there yet to execute the command.

        Oddly, Kace indicated the process executed normally, but it is still booting to NIC for each restart as it goes through the imaging tasks, so definitely not working.

        OK. You mentioned three files earlier:

        I just need to push these three files onto the client PC, default location or otherwise, just as long as I reference the right location when calling them?

        Like C:\Dell CC, for example
      • you can create an application task and attach those in a zip and all you need to do is call the exe with no path since application tasks use their file content directory as a working directory. so zip and attach and for parameters use "cctk.exe bootorder --sequence=hdd.1,hdd.2,usbdev,cdrom.embnic"
      • for mid level what I did was install the C|C on my tech station and use the KBEM which has an option to add the C|C to the KBE (x:\command_configure\amdx64) that way it is always available in my WinPE's
  • Little hump I'm experiencing...

    I created a zip/compressed file that contains cctk, mxml1, and pci.ids and am working on a script to push the zip, unzip it, run cctk.exe with parameters to NIC boot, and then restart the computer to initiate the network boot.

    The script includes my zip file as a dependency and then under Verify are two steps:

    1. Launch $(KACE_DEPENDENCY_DIR)\cctk.exe” with params “bootorder --sequence=embnic,hdd.1,hdd.2,usbdev,cdrom”.

    2. Launch “C:\WINDOWS\SYSTEM32\shutdown.exe” with params “/R /T 1”.

    The zip file gets transferred and unzipped into C:\ProgramData\Dell\KACE\kbots_cache\packages\kbots

    The computer restarts with a notice, as configured, but continues to boot from the hard drive.

    This is a freshly imaged PC and it does NOT have C|C installed. Perhaps this is where I'm confused, in that I need to have C|C installed, despite pushing the three indicated files out as part of the script.
    • can be a few things.
      on a machine that the script pushed to. Open a cmd window and try to manually run the cctk command out of the kbots directory to see if it works.

      you could have the wrong bit version for the OS,

      do you have a bios password?

      are the nic's bios settings correct for the pxe boot being enabled.

      is the nic enabled in the boot list

      are you using legacy or uefi
      • I will continue testing.

        I believe earlier this week when the task was working, I had C|C installed and indicated the directory exclusively instead of using $(Kacexxx).

        But then it occurred to me that if I want this capability on all machines, I need to push out the dependencies first, so I selected the default script installation directory.

        No BIOS password.
        The OS hasn't changed. It is Win7x64.
        PXE is enabled by default.
        Using legacy.

        Going to test the cmd locally now.

        EDIT: Just ran cctk.exe locally from the packages\kbots\404 directory and C|C crashed. That could be my issue there. Now to figure out why.

        EDIT 2: Ran it from cmd and pathed out the entire directory and ran cctk.exe bootorder --sequence=embnic,hdd.1,hdd.2,usbdev,cdrom and received the error:

        HAPI Driver Load Error. The system cannot find the path specified.

        I believe the error is that just pushing the cmd line C|C (cctk) to the target machine does NOT install the HAPI driver.
      • ahh with 3.1 that is required to be there. add the hapi subdir to the zip and that should fix it. Your settings are right on for this call
      • Even adding the HAPI subdir is failing.

        I think I'm going to instead work on pushing out the entire C|C application, suppress the desktop shortcut, and that I know I at least have the entire application installed.
      • never did figure out how to surpress the icon so I created a CIR that looks for it and deletes it if found

        ShellCommandTextReturn(cmd /c if exist "C:\Users\Public\Desktop\Configuration Wizard.lnk" del "C:\Users\Public\Desktop\Configuration Wizard.lnk" /q)
      • when I have time will look at zipping 3.1 version to see what need to be done for future reference
      • My tasks now are:

        1. Push and install C|C.msi. silent - OK
        2. BAT to delete shortcut - OK
        3. Change boot order - OK
        4. Restarts and boots to NIC and Kace kicks off automated deployment.

        As I was writing this, it worked, so I'm pretty psyched at the moment.
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