Blog Posts tagged with K2000 Deployment Workbench

Ask a question

K2000 Deployment Workbench

K2 Advisor

  • An .html overview of your SDA (version 3.6 and higher) that can identify issues and link to appropriate KB articles.

KBE Manipulator

  • Allows for manipulation of KBE that is uploaded to your K2000, including assigning static IP, adding ADSI, ODBC, DCCTK, Command | Configure, .Net4, Powershell, adding custom DOS commands, or uploading custom .wim/.iso's.

Sysprep Creator Wizard

  • Walks user through creating an unattend file for Windows 7/8/10

Driver Feed Builder

  • Harvest or extract executible drivers and upload to the K2000.

Get/Set ComputerName

  • Allows saving of computername from workstations or apply new names.
Unattend LTI
  • Tasks to help change the contents of unattend.xml based on administrator needs.
Kace Streaming WIM Toolkit
  • Toolkit that allows deployment of K2000 captured wims to be streamed
Default Deploy
  • Script that allows deployment of a default image/scripted install to machines
Export Wi-Fi Profiles
  • Script that will export profiles and .zip them up with a script to deploy them with a K1 or K2
Driver Feed Advisor
  • Script to show the driver feed path of a workstation, via the K1000 or K2000
Upgrading to Windows 10
  • Tasks that provide a solution to upgrading a workstation to Windows 10 using the K2000
USMT 10 loadstate fails when deploying Windows 7
  • A script that will copy the files necessary into USMT so that a Windows 7 deployment is successful with loadstate

Set Autologon Count

  • Change the autologon count in an unattend file of a sysprepped image

Task Timeout Modification Script

  • Modify the task timeout period of each task on version 3.6 or higher.
Using the K2000 UltraVNC during Windows Post Install Tasks - See more at: http://www.itninja.com/blog/view/using-the-k2000-ultravnc-during-windows-post-install-tasks#sthash.ZdF4KBXW.dpuf

Using the K2000 UltraVNC during Windows Post Install Tasks

  • Be able to remote into Windows during Windows PO Tasks
Dismiss Windows 7 Scripted Install Error in WinPE4 and WinPE5
  • Pre Installation task that will dismiss the errors when deploying a Windows 7 SI with WinPE4/5

Disable the DPInst Reboot for Windows 7 or higher Images that use driverfeed

  • disables the reboot for dpinst since it is not needed for Windows 7 or higher
Using the K2000 UltraVNC during Windows Post Install Tasks - See more at: http://www.itninja.com/blog/view/using-the-k2000-ultravnc-during-windows-post-install-tasks#sthash.ZdF4KBXW.dpuf

Kace Appliance Package Export Report

  • Creates an .html report of exported packages.

Linux Deployment Toolkit for 3.5 SP1 and 3.6

  • Allows for the deployment of linux kickstart

Automatically Naming a Macintosh Computer using the K2000

  • A script that behaves similarly to wsname for Windows.

Maintain KUID of a Macintosh System using the K2000.

  • capture the kuid of a Macintosh system and put it back to the workstation as a midlevel task.

Screen Resolution Changer

  • A script to either maintain screen resolution from each workstation, or assign a new one.
View comments (1)

Windows 7 Scripted Install Error in WinPE4, WinPE5 and WinPE10

When deploying Windows 7 Scripted install using WinPE4, WinPE5 or WinPE10, two errors appears that can be dismissed without causing issues to the deployment.  Unfortunately, this causes the deployment to not be 100% automated.

I created a script that runs as a pre installation task and will wait for those error messages.  When the error message appears, the script will dismiss them both, and then quit.  The Scripted Install will continue without any user interactions.

The download contains two K2000 tasks (one for each architecture) that can be imported from Settings | Package Management | Import K2000 Packages | Upload Package for Import...   One only needs to upload the necessary task needed, both are not required.

One must be a member of the K2000 Community Page to download.  The direct download link if you are a member.

Back to K2000 Deployment Workbench

Be the first to comment

Upgrading to Windows 10

*NOTE - If these tasks were downloaded and imported into your K2000 prior to September 4, 2015 please contact support.  We found an issue with the import of the task which we will need to fix on the backend.  The download available now does not have this issue.  We apologize for the inconvenience.

Many users will want to upgrade their current operating system to Windows 10, retaining all their user data and applications.  In order to upgrade to Windows 10, one must utilize the same edition of Windows 10 as the older version of Windows.  For example, if running Windows 7 Professional or Ultimate, Windows 10 Professional must be used.  If running Windows 8 Enterprise then Windows 10 Enterprise must be used to upgrade the system.


An upgrade to Windows 10 must take place within the operating system itself and cannot take place in KBE.  There are two methods to upgrading to Windows 10 using KACE appliances. The first method would be to create a K1000 script as outlined on an ITNinja blog post. The second method, which is detailed below, can be done from the K2000 with the provided tasks.
*Note, to download the tasks, it is necessary to be a member of the K2000 community.


First, use the current version of Media Manager to upload your Windows 10 source media, 3.7 SP2 supports Windows 10 so make sure you are using that version of Media Manager for the upload..  Once this is completed, the source media ID must be obtained from Library | Source Media.


Upload the attached .PKG files, which will create a Windows 10 K-Image for each architecture along with a few tasks.  Preinstall tasks such as partitioning and formatting should not be added to the image (or it will no longer be an upgrade).  The image that is being applied to the machine has no files, so nothing is overwritten.  The midlevel task is a template that should be duplicated and edited.  This midlevel task copies down the Windows 10 source media, enables autologon to the workstation and writes a setupcomplete.cmd file that gets applied at the end of the upgrade process.


The first few lines of the midlevel task contain variables that need to be changed by the user.

strUser should be an admin username

strPassword is the password of the above user

strDomain is the name of the domain, or leave as localhost if leveraging a local user

win10_source_cd_id is the ID number of the uploaded Windows 10 source media


The post install task, “Upgrade Windows 10” does not have to be modified by default.  However, the last command line switch is ‘/dynamicupdates disable’.

When Windows 10 setup begins, it will attempt to download available updates by default.  The command line switch above disables this behavior.  If you prefer for the updates to be downloaded immediately, just delete this switch from the command line.  For more commandline switches see http://winaero.com/blog/windows-10-setup-exe-command-line-switches/

Back to K2000 Deployment Workbench

View comments (39)

USMT 10 loadstate fails when deploying Windows 7

When deploying Windows 7 and using USMT 10 loadstate, the operation will fail due to missing files.
The issue was first outlined here http://deploymentresearch.com/Research/Post/497/Fix-for-Windows-7-deployments-failing-after-upgrading-to-Windows-ADK-10 and then acknowledged by Microsoft as an issue [https://support.microsoft.com/en-us/kb/3084782].
The resolution is to copy 7 files for each architecture into the directory that contains USMT 10 loadstate.

These files need to be in place prior to uploading USMT 10 to the K2000.  ADK 10 must be installed on the workstation along with the K2000 Media Manager.  To make the process easier, I wrote a script that will copy both x64 and x86 files to the correct location for you.

The tool can be downloaded from ITNinja, but you must join the K2000 community first.

Please let me know if there are any issues with the tool itself.

*K2000 3.7 SP3 and SP3 Media Manager are required.
View comments (1)

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 Dell | 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:

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:
TOGGLE=on will enable the tool
TOGGLE=off disables the tool
TYPE A = Kimage or WIM
TYPE B = Scripted Install
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.





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.
default_deploy.bat /ini_file:k:\folder\default_deploy.ini

/log_file allows the user to define the path of the log file.
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’
View comments (2)
Showing 1 - 5 of 5 results

Top Contributors

Talk About Application Repackaging