Chat now with support
Chat with Support

KACE Systems Deployment Appliance 8.0 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

Import WIM images

Import WIM images

You can import an existing WIM image to your collection of system images on the appliance. This allows you to manage system images created by a third-party vendor.

To import a WIM image, place a copy of the image file to the appliance's Samba clientdrop share.

During a WIM image import, you must specify its OS architecture. The appliance detects if the imported image is sysprepped or not.

NOTE: When the appliance starts importing a system image, if it detects an unattend file, it flags the image as sysprepped. If the image does not include that file, the appliance flags it as not being sysprepped.

This feature is available on the KACE Systems Deployment Appliance and the Remote Site Appliance (RSA).

On the left navigation pane, click Deployments, then click System Images to display the Systems Images page.
Select Choose Action > Import to display the System Image Import page.



Image Name

Type the name that you want to assign to this system image.

Operating System

Select the OS architecture used by the WIM image.

Wim File

Select the name of the WIM image file on the Samba clientdrop share.

Click Import.
The System Image Import page closes and the System Images list page refreshes, showing the newly imported WIM image in the list. In the row containing the imported image, the Status column indicates the state of the import operation.
Optional. When the import is complete, observe the imported image details, and make any changes, as required.
On theSystem Images page, in the row containing the imported image, click the Name column to display the System Image Details page.
To download the WIM image, in the Wim Management section, in the row containing the partition that you want to download, Actions column, click the Download icon. In the dialog box that appears, specify the name to give to the WIM file. Then click Save.
NOTE: Like the original WIM image, the replacement image must also be stored in the Samba clientdrop share of the associated KACE Systems Deployment Appliance or RSA, in order to be accessible.
To do that, also in the row containing the partition that you want to replace, in the Actions column, click the Replace icon. In the dialog box that appears, select the desired image file, and click Replace.
The System Image Details page closes and the System Images list page refreshes, indicating that the WIM image is being replaced in the row containing the imported image, in the Status column.
The contents of the log appear on the page. Use this information to find out whether the image was captured on the appliance or imported from the clientdrop share, who and when imported the image, or whether the image was replaced and by which user. If the image consists of multiple partitions, the log shows any operations performed on the specific partitions.

Best practices for creating Windows system images

Best practices for creating Windows system images

This topic provides information about KACE-recommended best practices for creating a Windows Golden System Image.

Audit the appliance before beginning

Start fresh

Configure the workstation

The following KB articles are recommended best practice methods for creating the base OS installation for System Image capture. If using a Legacy enabled BIOS, use the Single Partition Golden Image KB. If the BIOS is in UEFI mode, use the UEFI KB. Kace highly recommends minimal partitions on your base OS.

If not following the above KB articles, use the following guidelines:

If the image is captured in WIM format, keep at least 60% of the drive space on each partition as free/available.

Sysprep, capture and deployment guidelines


If you configured a "default" account, ensure to set it to True in the unattend.xml file. The sysprep creator wizard has an option to copy the current profile to the default profile.
When running sysprep by command line and not the Sysprep Creator/Executor, use the /generalize, /oobe, /shutdown, and the /unattend switches.



Post-installation tasks

Use cscript with VB scripts. For example: cscript myscript.vbs
For .msi deployments, use the install switch last. For example: msiexec /qn /norestart /i agent.msi
Use CLONEPREP=1 on the .msi Agent install if it is not intended to have the Agent to -check in, and create a KUID until the next reboot. For example: msiexec /i agent.msi HOST=blah CLONEPREP=1
Use the start /wait command when deploying software through appliance post-installation tasks.
Use call when using .bat scripts in application tasks. For example: call myscript.bat

Capturing user states

The appliance uses the Windows User State Migration Tool (USMT) to migrate user profiles by running the USMT Scan State and Load State utilities. Before scanning devices for user states, you can configure the USMT Scan Templates that set the Scan State utility parameters and enable you to specify which data to migrate and which data to exclude from the capture. You can upload and install the USMT from the appliance or from the KACE Media Manager.

The USMT Scan State utility (Scanstate.exe) scans a device for data, and captures the information in a .mig file. The USMT Load State utility (Loadstate.exe) installs the data and settings from the .mig file on to a destination or target device. The Load State utility also enables you to migrate users states to devices manually.

Scan User States Offline: You can use the Scan User State Offline pre-installation task to scan user states from any device and upload the user state to the appliance.

Deploy User States: You can use the Deploy User States post-installation task to deploy the user states to target devices.

Upload USMT software from the appliance

Upload USMT software from the appliance

Scanning user states requires the Windows User State Migration Tool software (USMT) included in the Windows ADK (Automated Deployment Kit). You can upload the USMT software version 5.0 directly from the appliance. The appliance captures the user states by running the USMT Scan State utility on a device.

You can also upload USMT version 3.0.1 from the appliance.

On the left navigation pane, click Library to expand the section, then click User States to display the User States page.
Select Choose Action > Upload.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating