Chat now with support
Chat with Support

KACE Systems Deployment Appliance 9.2 Common Documents - Administrator Guide

About the KACE Systems Deployment Appliance Getting started Using the Dashboard Configuring the appliance Setting up user accounts and user authentication Configuring security settings Preparing for deployment Managing device inventory Using labels Creating a Windows or Linux Boot Environment Managing drivers Capturing images Capturing user states Creating scripted installations Creating a task sequence Automating deployments Performing manual deployments Managing custom deployments Managing offline deployments About the Remote Site Appliance Importing and exporting appliance components Managing disk space Troubleshooting appliance issues Updating appliance software Glossary About us Legal notices

Add BAT Script

Add BAT Script

You can create your own batch scripts to run as a pre-installation, mid-level, or port-installation task in the KACE Boot Environment for Windows before or after installing the operating system, or re-imaging a target device.

1.
Complete one of the following steps:
a.
On the left navigation pane, click Library to expand the section, then click Pre-installation Tasks to display the Pre-installation Tasks page.
b.
On the left navigation pane, click Library to expand the section, then click Mid-level Tasks to display the Mid-Level Tasks page.
c.
On the left navigation pane, click Library to expand the section, then click Post-installation Tasks to display the Post-installation Tasks page.
2.
On the list page that appears, select Choose Action > Add BAT Script.
3.
On the page that appears, in Name, enter a logical name to identify the task.
The task runs in the KACE Boot Environment (Windows).
4.
In BAT Script, enter the script.
You can use the following commonly used commands available from within the KACE Boot Environment (KBE):
◦
bcdedit.exe
◦
bootsect.exe
◦
chkdsk.exe
◦
format.com
5.
Select the Reboot Required check box to reboot the appliance and run the next task in the sequence.
6.
In Expected Return Code, enter a code that the task should return, if applicable. Otherwise, leave the default value of zero '0'.
In general, most tasks exit with a zero '0' code, indicating success, but you can set it to any positive value, as applicable. Some installers exit with a different code, even when the install is successful. For example, anti-virus installers are typically successfully installed but exit with a different return code because they require a device reboot.
7.
In Notes, add a note to identify the task.
8.
Click Save.
The task is now available to assign to scripted installations, sysprepped system images, and non-sysprepped system image deployments.
See Assign tasks to system deployment or Assign tasks to scripted installation deployment.

Add Custom HAL Replacement

Add Custom HAL Replacement

You can replace the Hardware Abstraction Layer (HAL) using a mid-level task to customize the target device's HAL.

HAL replacement is only supported for system images.

1.
On the left navigation pane, click Library to expand the section, then click Mid-level Tasks to display the Mid-level Tasks page.
2.
Select Choose Action > Add Custom HAL Replacement to display the Mid-level Task Detail page.
3.
In Name, enter a logical name for the task.
The task runs in the KACE Boot Environment (Windows).
4.
Click Browse to upload the following files:
◦
Upload HAL DLL
◦
Upload NTKRNLPA.EXE
◦
Upload NTOSKRNL.EXE
* 
NOTE: If a filename is different from what displays in the Upload field, the files is renamed when uploaded to the appliance.
The files are copied to the target devices Windows\System32 directory as part of the mid-level task.
5.
In Expected Return Code, enter a code that the task should return, if applicable. Otherwise, leave the default value of zero '0'.
In general, most tasks exit with a zero '0' code, indicating success, but you can set it to any positive value, as applicable. Some installers exit with a different code, even when the install is successful. For example, anti-virus installers are typically successfully installed but exit with a different return code because they require a device reboot.
6.
In Notes, add a note to identify the task.
7.
Click Save.
The task is now available to assign to scripted installations, sysprepped system images, and non-sysprepped system image deployments.
See Assign tasks to system deployment.

Add DiskPart Script

Add DiskPart Script

Common DiskPart command-line options

You can add and run a DiskPart script as a pre-installation task on a Windows device that has booted in to the KACE Boot Environment (KBE) to erase all the data on a hard drive or partition, create new partitions, and assign drive letters.

Back up the components that you want to save before running this task.

For more information, see Common DiskPart command-line options.

1.
On the left navigation pane, click Library to expand the section, then click Pre-installation Tasks to display the Pre-installation Tasks page.
2.
Select Choose Action > Add DISKPART Script to display the Pre-installation Task Detail page.
3.
In Name, enter a name to identify this task. For example, Single NTFS Partition C.
The name is the identifier for the tasks that display on the Scripted Installation Detail and System Image Detail pages.
4.
In DISKPART Script, enter the script according to the partition that you are creating on the device, for example:
◦
select disk 0

clean

create partition primary

select partition 1

active

assign

exit

5.
In Expected Return Code, enter a code that the task should return, if applicable. Otherwise, leave the default value of zero '0'.
In general, most tasks exit with a zero '0' code, indicating success, but you can set it to any positive value, as applicable. Some installers exit with a different code, even when the install is successful. For example, anti-virus installers are typically successfully installed but exit with a different return code because they require a device reboot.
6.
In Notes, add a note to identify the task.
7.
Click Save.
See Assign tasks to scripted installation deployment or Assign tasks to system deployment.

Common DiskPart command-line options

Common DiskPart command-line options

You can use DiskPart scripts to select objects, remove partitions for a disk, create a partition, make partition active, and to assign drive letters.

Selecting objects

•
select disk=[n]
•
select partition=[n]
•
select volume=[{n|d}]

Use the parameter n to specify the number of the object to select. You can also select Volumes by the drive letter, specified as d.

Cleaning a disk

•
clean [all]

Removes all partitions from a disk. The all parameter specifies that every sector on the disk is zeroed.

Creating partitions

•
create partition primary [size=n] [offset=n]
•
create partition extended [size=n] [offset=n]
•
create partition logical [size=n] [offset=n]

Creates a primary, extended, or logical partition. If size is not specified, the partition consumes the remaining available space. If offset is not specified, the partition is created in the first available space. After the partition is created, it is selected.

Making the Boot partition

•
active

Marks the currently selected partition as the active or bootable partition.

Assigning drive letters

•
assign [letter=d]
•
Assigns a drive letter to the currently selected partition. If a letter is not specified, the first available letter (starting with C) is used.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating