/build/static/layout/Breadcrumb_cap_w.png

K2000 Default Deploy


Download Default Deploy


****WARNING: Implementing this in an environment could have undesired results if a machine boots to the environment unexpectedly.  Please follow the instructions and take proper precautions.

The Default Deploy application is a utility designed by Corey A. Serrins to give users of the Quest | KACE K2000 some additional flexibility in the deployment of new computers into an organization.

This K2000 workbench tool was designed with one thought in mind; to deploy an operating system to a brand new computer using the K2000, without importing MAC addresses into the inventory detail.

Expand the .zip download into a folder of choosing.  Move default_deploy.ini to \\k2000\petemp and use the below instructions to set the preferences for x86 and x64 deployments.  Using KBE Manipulator, choose Configure | Modify KBE Tools.  Check the box for “Add files to KBE” and browse to the location of the extracted folder.  If this is indeed to be used as a boot environment for deployment to a new computer, then also de-selecting “KACE Deployment Menu” would be beneficial so that the default menu does not appear.  Select Configure | Add custom dos command(s) and then enter in the following line:
x:\applications\default_deploy.bat

There are a number of options that must be set in the .ini file that will reside in the petemp directory of any K2000 or RSA.

The instructions in the original .ini file are as follows:
[INSTRUCTIONS]
TOGGLE=on will enable the tool
TOGGLE=off disables the tool
TYPE A = Kimage or WIM
TYPE B = Scripted Install
TYPE C = Custom Deployment
ID refers to the ID number of the image or scripted install
Timeout refers to the number of seconds prior to deployment starting
Timeout=0 means no timeout will be used.
TimeoutDeploy=yes sets the default action of timeout to deploy
TimeoutDeploy=no sets the default action of timeout to cancel
Log File can be found on petemp by default, logs are stored by day.


 

These settings exist for both x86 and x64 systems, just change the settings per the architecture.

Examples:

[SETTINGSx86]
TOGGLE=on
TYPE=A
ID=5
TimeoutValue=30
TimeoutDeploy=Yes

[SETTINGSx64]
TOGGLE=on
TYPE=B
ID=5
TimeoutValue=30
TimeoutDeploy=Yes

 

By default, the script looks for the ini file on t:\default_deploy.ini and the log file is written to t:.  The .bat file can be called with 2 commandline switches if desired to change these settings

/ini_file allows the user to define the path and file name of the settings file, but should end with the .ini extension.
Example:
default_deploy.bat /ini_file:k:\folder\default_deploy.ini

/log_file allows the user to define the path of the log file.
Example:
default_deploy.bat /log_file:k:

Both switches can be used in combination and in any order. 

 

***Note: This KBE should not be set as a default KBE as it could cause the reimage of machines that pxe to KACE.  When automated deployments are complete, the default_deploy.ini should either be renamed or removed or the value of Toggle and/or TimeoutDeploy should be set to ‘No’

Comments

  • I followed the instructions and the KBE Manipulator reports that the KBE was uploaded but the filesize is listed as 0 B in Library, Source Media. It does not show up at all in Deployments, Boot Environments. I'm using the most recent version of KBE Manipulator. - chucksteel 5 years ago
    • I was able to resolve the problem by updating my drivers in the drivers share and not using a space in the name of the KBE. Not sure which one actually fixed the problem. - chucksteel 5 years ago
      • I'm pretty sure it is not the spaces.
        -Corey - cserrins 5 years ago
  • I'm still having problems with the KBE Manipulator not uploading KBEs consistently. After it reports that the KBE was uploaded checking the K2000 shows the KBE in Library, Source Media but the size is 0. Opening the KBE shows a status of "Uploading Files". The KBE does not appear under Deployments, Boot Environments. Does the manipulator keep a log file that I can check? - chucksteel 5 years ago
    • Log file is in %temp% of the account used to create kbe. Do KBEs from MM upload fine?
      -Corey - cserrins 5 years ago
      • I just tried and I got the following error:
        Error connecting to hashstore server. - chucksteel 5 years ago
    • Make sure you are using a vanilla machine (vm), not joined to a domain, no AV, no Security, Firewall off and ports are not blocked. Make sure the right drivers are in the kbe_windows_xXX folder and have recached.
      -Corey - cserrins 5 years ago
  • Download link is broken. - Techman D 3 years ago
    • It is working again, apologies, that was my fault. - cserrins 3 years ago
  • I do not have PXE boot and have to use the SDA to re-image. I have always done this using an older method, https://imgur.com/a/VJfPQMS. It seemed like this would have the added benefit of not needing an additional KBE for each image. I could just point to the relevant ini file. But now that I look into it more, it seems like I'll either have to rename the file to default_deploy.ini on the petemp folder or I'll have to hardcode in the name of the ini file (for each relevant image/installer) when I create the kbe. Is that correct? Can you think of a way that I could do this on the fly, without having to bake it into the kbe? Actually I think I just thought of a way. I could have the renaming of default_deploy.ini built into the batch file on the k1 for each image. So that's not so bad. Anyways, I wanted to get your thoughts. I put a copy of the script I was thinking of out on imgur with the other stuff. It's the last one. - five. 3 years ago
  • I am new at this, but where is petemp folder? The root of \\k2000\ has the 4 default folder (clientdrop,Drivers, drivers_postinstall, restore). - calpia 8 months ago
This post is locked
 
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