Chat now with support
Chat with Support

KACE Systems Deployment Appliance 8.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 Imaging Mac devices About the Remote Site Appliance Importing and exporting appliance components Managing disk space Troubleshooting appliance issues Updating appliance software Glossary About us Legal notices

Deploy user states to target devices manually

Deploy user states to target devices manually

When you scan a device and capture the user states to the appliance, the USMT creates a .mig file, which contains the user states of the device. You can download and copy the .mig file from the appliance to any location on a target device that you want to update with the new user states.

The USMT ScanState utility performs the backup and generates the .mig file. The USMT LoadState utility performs the restore process using the .mig file. Running the LoadState utility in Administrator mode loads the user states to a target device.

1.
On the left navigation pane, click Library to expand the section, then click User States to display the User States page.
2.
Select a profile to display the User State Detail page.
3.
Click Download User State File.
The Opening USMT.MIG dialog box appears.
4.
Click Save File and save the file to any location.
5.
Copy the entire .mig file on to a target device.
a.
On the target device, create a local store, such as MyUserStates, with a subfolder named USMT, and copy the .mig file to the USMT folder.
b.
Run the loadstate.exe. on the USMT folder on the target device.

Use the following command-line options to deploy the user states:

Local account: loadstate.exe StorePath /i:miguser.xml /i:migapp.xml /lac /lae
Domain account: loadstate.exe StorePath /i:miguser.xml /i:migapp.xml

Creating scripted installations

You can upload an existing answer file (Windows) or preseed/kickstart file (Linux), or perform a server-based attended setup (Windows or Linux).

Prepare for a scripted installation:

Create a scripted installation

Create a scripted installation

The Create a Scripted Installation wizard guides you through the steps to define the scripted installation. The settings that you specify in the config.xml file must be compatible with the hardware. Windows only: If the hardware cannot handle the settings, the Windows installer causes the unattended scripted installation to fail.

1.
On the left navigation pane, click Deployments, then click Scripted Installations to display the Scripted Installations page.
2.
Select Choose Action > New.
Follow the steps provided by the Create a Scripted Installation wizard.
NOTE: Scripted installation deployments to UEFI-enabled devices require creating a UEFI partition using the Create UEFI Partitions pre-installation task and booting from a UEFI bootable FAT32 formatted USB flash device.

Next, using the wizard, upload an existing answer file (Windows) or preseed/kickstart file (Linux), or perform a server-based attended setup (Windows or Linux).

Create a configuration file

Create a configuration file

You can create your own configuration file or modify an existing one with the configuration tasks that are typically prompted for during an attended scripted installation. The type and name of the file depends on the OS used in the scripted installation. For example, for Microsoft Windows systems, you create or modify an answer file, unattend.xml, while Debian Ubuntu uses a preseed.cfg file.

1.
On the left navigation pane, click Deployments, then click Scripted Installations to display the Scripted Installations page.
2.
Select Choose Action > New to display the Create a Scripted Installation page.
3.
Enter a Name, and select the source files from the Source Media drop-down list, then click Next.
Walk me through creating a <configuration> file for unattended setup: Creates a configuration file using the unattended Installation wizard.
NOTE: The name of the configuration file displayed in these options depends on the target platform. For example, Windows uses an answer file (unattend.xml), while Ubuntu uses a preseed file (preseed.cfg) file.
Upload an existing <configuration> file for unattended setup: Uploads a configuration file for unattended installation.
No <configuration> file; This will be a server-based attended setup: Creates a basic configuration file that requires user input to complete the installation.
5.
Click Walk me through creating a <configuration> file for unattended setup, then click Next.
6.
Windows only. Complete the answer form.
EnableFirstLogonAnimation registry key to 0 (zero).
7.
Linux only. In the Configuration step, provide the following information.

Section

Option

Description

Select Preseed Template

Click and select the template that you want to use for this configuration. The list of templates that appear depends on the previously selected platform under Source Media.

Template Data

Root Password

Specify the root password for this configuration. If you want to disable root login for the target system, select Disable root login.

User Account

To add a new user account using this method, select Create User Account. Any user accounts that are created this way are granted sudo access.

Provide the full name, user name, and password for the account.

Time Zone

Select the time zone for the target system.

Time Zone Server

Specify the host name of the applicable time zone server.

Language

Select the locale for the target system.

Desktop GUI

Select the graphical user interface that you want to use on the target system: GNOME Desktop Environment, or KDE Desktop Environment, as applicable.

8.
Click Next to display the Pre-installation and Post-installation Tasks page, and add the required pre-installation and post-installation tasks.
9.
Windows only. Select the Task Error Handling option for how you want the appliance to respond to errors.
10.
Click Next.
The Scripted Installation Creation page displays the status.
The Create a Scripted Installation page refreshes and displays the results.
12.
Optional. To view the contents of the answer or configuration file, open the Scripted Installation Detail page for the newly created scripted installation, and under Setup Configuration, click Show. You can make edits to this file, if needed. Any edits you make in the file contents affect only the selected scripted installation.
Deploy the scripted installation from Automated Deployments or as a manual deployment from the KBE Main Menu, which displays on the target device after the target device boots in to the KBE.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating