Chatta subito con l'assistenza
Chat con il supporto

KACE Systems Deployment Appliance 9.1 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 PowerShell Script

Add PowerShell Script

You can run PowerShell script as a pre-installation, mid-level, or post-installation task in the KACE Boot Environment (Windows) runtime environment or the Windows runtime environment.

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 Powershell Script.
3.
On the page that appears, in Name, enter a logical name for the task, such as My PowerShell script.
4.
Under Upload File, click Select File, and navigate to the PowerShell script.
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.
9.
On the list page, click the task name.
10.
On the task detail page that appears, review the contents of the Full Command Line field, and make any changes, as required.
11.
If you made any changes to the command line, click Save, or click Cancel to return to the list page.

Add Provisioning Package

Add Provisioning Package

Provisioning packages contain collections of configuration settings. You can use them to quickly configure a Windows device without having to install a new image. You can run a provisioning package as a post-installation task in the Windows runtime environment.

1.
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 Provisioning Package to display the Post-installation Task Detail page.
3.
On the page that appears, in Name, enter a logical name for the task, such as My Provisioning Package.
4.
Under Upload File, click Select File, and navigate to the Provisioning Package file.
The Reboot Required option is selected by default and cannot be disabled. This is because a device reboot occurs each time this task runs.
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.
8.
On the list page, click the task name.
9.
On the task detail page that appears, review the contents of the Full Command Line field, and make any changes, as required.
10.
If you made any changes to the command line, click Save, or click Cancel to return to the list page.

Add Service Pack

Add Service Pack

You can install service packs automatically as they become available for the operating system to devices on local and remote networks. If you have a service pack stored at a different location, you can browse to and upload that service pack manually.

The Service pack task runs in the Windows environment after booting in to the operating system.

1.
On the left navigation pane, click Library to expand the section, then click Post-installation Tasks to display the Post-installation Tasks page.
2.
Select Choose Action > Add Service Pack to display the Post-installation Task Detail page.
3.
In Name, enter a logical name to identify the task.
4.
Download the service pack automatically or manually.
◦
From the Service Pack drop-down list, select the service pack, and click Download Service Pack automatically.

The Command Line field is automatically populated with the recommended parameters based on the service pack selection. If you modify this line, include the service pack filename.

◦
Select Upload Service Pack manually, and click Browse to upload the file. For more information, see About uploading files.
* 
NOTE: When you upload the service pack manually, in Parameters, enter the command-line parameters to run the service pack.
5.
In Full Command Line, enter the command-line parameters for the task.
6.
Select the Reboot Required check box to reboot the appliance and run the next task in the sequence.
7.
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.
8.
In Notes, add a note to identify the task.
9.
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 scripted installation deployment or Assign tasks to system deployment.

Add Shell Script

Add Shell Script

You can create your own shell scripts to run as a pre-installation, mid-level, or post-installation task in the KACE Boot Environment (Mac OS X) before deploying 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 Shell Script.
3.
On the page that appears, in Name, enter a logical name to identify the task.
4.
Select a Runtime Environment:
◦
Pre-installation and mid-level shell scripts: Select SDA Boot Environment (Mac OS X).
◦
Post-installation shell scripts: Select Mac OS X.
For more information, see About runtime environments.
5.
In Shell Script, enter the script.
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.
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione