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

Set default boot action

Set default boot action

By default, devices that are not in the appliance Device Inventory boot in to the KBE Main Menu. For example, devices on your network that have been scanned display in your appliance Network Inventory. You can set the boot action to boot to the hard drive for devices that are not in the appliance Device Inventory or Network Inventory.

1.
On the left navigation pane, click Settings > Control Panel to display the Control Panel, then click General Settings to display the General Settings page.
2.
Under PXE Options, set the default boot action to one of the following options:
◦
Boot to the KBE Main Menu for devices that are not in the appliance Device Inventory.
◦
Boot to the hard drive for devices that have not booted in to the KBE. Include devices that are not in Network Inventory
3.
Click Save.

Configure new WIM images to stream directly from or to the server

Configure new WIM images to stream directly from or to the server

When you capture or deploy WIM images, you have an option to stream the image directly from or to the server instead of using a local drive.

After an image is captured locally, it is sent to the server through network sockets. Some network configurations may cause issues when files are transferred this way. Streaming the image directly to the server causes its files to be copied directly to the server share instead of using network sockets.

1.
On the left navigation pane, click Settings > Control Panel to display the Control Panel, then click General Settings to display the General Settings page.
2.
Set the Imaging Options as required:
◦
Default setting to capture WIM files directly to server (individual captures can be changed on the KBE image capture page): Select this option for the default setting in the KBE to stream directly to the server.
▪
WIM images captured directly to the server must also be deployed directly from the server. This option cannot be changed on the image detail page.
▪
If you choose not to select this option, and there is not enough disk space locally, the image is streamed directly to the server.
◦
Default setting to deploy new WIM files directly from server (individual deployments can be changed on the image detail page): Select this option so the default setting on newly captured images is to deploy directly from the server.
* 
NOTE: This setting will only apply to those WIM images that have been captured directly to the server.
3.
Click Save.

Specify deployment options

Specify deployment options

The System Image Detail page allows you to view the image settings, add a boot action, download the log files associated with the image, and set the options for how the appliance responds to errors. It also allows you to specify deployment options.

1.
Under Deployments, select the deployment to display the System Image Detail page.
2.
Under Deploy Options, select any of following options, as required:
◦
Deploy directly from server: Select this option if you want to deploy this WIM image directly from the server. WIM images captured directly to the server must also be deployed directly from the server. In that case, this option appears selected, and cannot be changed.
◦
Force continue on errors: Select this option if you want to continue the capture and the upload process even if warnings and fatal errors occur.
◦
Include debug output in log: Select to enable debugging level logging and upload the logs to the Appliance Logs page.
* 
CAUTION: This option considerably increases the time of deployment. Only use it while troubleshooting.
◦
Use driver feed (only with Sysprepped images): Select to enable the Driver Feed for sysprepped system images to obtain missing drivers. For Windows K-Images and WIM images, the Sysprepped field on the System Image Detail page indicates if an image is sysprepped. Optionally, enable this option by default:
1.
Open the Administrator Console in a new browser instance or tab.
2.
On the left navigation pane, click Settings > Control Panel to display the Control Panel, then click General Settings to display the General Settings page.
3.
Under Imaging Options, select the Enable driverfeed for newly captured sysprepped images check box. Selecting this option automatically adds drivers to the target system deployed with newly captured sysprepped system images.
4.
Click Save, and return to the Deploy Options on the System Image Detail page.
◦
Shutdown target device after last task: Select if you want to turn off the target device when the image is installed.
◦
Allow Appliance to calculate Auto Logon Count for Unattend file: Select this option if you want to enable the appliance to calculate the number of auto logon attempts that take place during installation. The number of auto logon attempts is written to the Unattend.xml file, that contains parameters for a Windows system setup. When this option is enabled, the appliance calculates the auto logon count by adding the number of system reboots that are specified in the tasks contained in the installation plan.
◦
Hide Deployment from KBE: Select this option if you want to hide the system image from the KACE Boot Environment (KBE).
* 
NOTE: Scripted deployments marked as hidden from KBE do not appear in the Deployment drop-down list on the Automated Deployment Detail page when creating a boot action.
◦
Use Unattend File from Library: Select this option if you want to use one of the Sysprepped unattend files stored on the appliance as a mid-level task, and select a desired unattend file. Selecting this option enables the mid-level task automatically. The OS and architecture of the unattend file must match those of the system image to make the file available for selection.
◦
Set Auto Logon Count (Leave blank for no change): Select this option if you want to limit the number of auto logon attempts that take place during system installation. You can enter any value between zero and 99.

Schedule a deployment

Schedule a deployment

You can schedule system image or scripted installation deployments to a single device or to multiple devices to run later. You can also schedule multiple deployments to the same device. You cannot schedule Mac OS X image deployments to run later.

You can add or remove devices when you schedule a deployment.

1.
On the left navigation pane, click Deployments, then click Automated Deployments to display the Automated Deployments page.
2.
Select Choose Action > New Boot Actions or select an existing boot action to display the Automated Deployment Detail page.
3.
Under Options > Schedule, select one of the following to run the deployment:
a.
Run at next boot: Initiates the deployment on the next network boot.
b.
Schedule to run later: Specifies a day and time: Run once on: every (day), at: H (hour), and M (minute). Run repeatedly runs the deployment every day at the time you specify.
4.
Click Save.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating