Blog Posts tagged with K2000 Systems Deployment Appliance

Ask a question

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

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
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.





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 (4)

Unattend LTI

The Unattend LTI application is a utility designed by Corey A. Serrins and Nick Morea to give users of the Quest | KACE K2000 some additional flexibility in the deployment of new computers into an organization by manipulating the unattend.xml file of the deployed device.

Read the included PDF for instructions on how to use these tasks, as they can be run in the most basic form of a user interface with all options available, or the UI can be narrowed down to just the options preferred by the administrator, or can be run silently.

To download, the user must be a member of the K2000 community.

Back to K2000 Deployment Workbench

View comments (5)
Showing 1 - 3 of 3 results

Top Contributors

Talk About Microsoft Office