Chatee ahora con Soporte
Chat con el soporte

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

Add KACE Agent Installer

Add KACE Agent Installer

You can download the KACE Agent file to a local directory, then upload the installer as a single file or a ZIP archive to run as a post-installation task. The appliance runs the task in the runtime environment that you specify.

You can assign the Apply KUID to KACE Agent post-installation task to prevent a duplicate asset on the KACE Systems Management Appliance if the KUID of the KACE Agent that was installed on the target device was not maintained. The KACE Agent software is in the \\KACE_Systems_Management_Appliance_host_name\client\agent_provisioning directory. For an explanation of available command-line options and Agent configuration properties, see the KACE Systems Management Appliance Administrator Guide. The KACE Agent does not require .NET 4.0 to install.

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 SMA Agent Installer to display the KACE Agent Installer detail task page.
3.
In Name, change the name to identify the task, for example KACE Agent for Windows.
4.
Select a Runtime Environment. See About runtime environments.
5.
Next to Upload, click Browse to select the appropriate file.
6.
In Full Command Line, enter the command-line parameters for the task.
7.
Select the Reboot Required check box to reboot the appliance and run the next task in the sequence.
8.
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.
9.
In Notes, add a note to identify the task.
10.
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 Windows Script

Add Windows Script

You can run Windows scripts as a pre-installation, mid-level, or post-installation task in the KACE Boot Environment (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, selectChoose Action > Add Windows Script.
3.
On the page that appears, in Name, enter a logical name for the task, such as Collect computer information before formatting.
4.
Next to Upload, click Browse to select the appropriate file, such as a VBScript or a JavaScript.
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.

Working with task groups

Working with task groups

Add task group

Task groups allow you to create a sequence of common tasks to build and capture a system image.

You can easily reuse a task group, when needed, to create system images of the same type and function. For example, you can create a task group that builds a Microsoft Windows 10 system with a Microsoft Office suite, and associate one or more task groups with system images and scripted installations each time you need to re-create a common deployment scenario.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación