Chat now with support
Chat with Support

KACE Systems Deployment Appliance 7.0 Common Documents - Administrator Guide

About the KACE Systems Deployment Appliance Getting started Using the Dashboard Configuring the KACE SDA 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

Capture native WIM images

Capture native WIM images

You can capture WIM images for faster deployments using automated multicast deployments to send the same WIM image to multiple devices simultaneously. You can also deploy WIM images across all devices in the enterprise, and across hard disks of any size in the KACE Boot Environment (KBE).

The device with the image that you want to capture does not have to match the target devices for deployments; however, drivers are required for each device model to which you are deploying the image.

2.
Click Capture image of this machine.
3.
In Image Name, create a name to identify the image.
4.
In Image Source, select the drive letter from where you are capturing the image.
5.
Select Windows Imaging Format (Fast compression) for Image type.
6.
Click Start capture to upload the image to the System Images page.

Edit a system image

Edit a system image

You can rename, replace, remove, or edit K-Images and WIM images.

The System Image Detail page allows you to view the image settings, add a boot action, download the log files for the image, and set the options for how the appliance responds to errors. For Windows K-Images and WIM images, it also indicates if an image is sysprepped.

You can only edit system images on the appliance that captured them. For example, if you view the details of a system image captured by the KACE SDA, you can edit that image on the System Image Detail page in the KACE SDA Administrator Console, but not in the KACE Remote Appliance Console. If that system image is captured on the KACE SDA and synced to the RSA, the System Image Detail page in the KACE Remote Appliance Console only allows you to review the system image details, but not to edit them. A link appears on this page that allows you to quickly navigate to the System Image Detail in the KACE SDA Administrator Console, and edit the system image, as required.

The Installation Plan enables you to create a task sequence by adding the available pre-installation, mid-level, and post-installation tasks to run in the order that you place the tasks for the deployment.

The Browse Files option is only available for system images.

1.
Select the name of the image to display the System Image Detail page to edit the image.
2.
Click Browse Files to open the Browsing Files dialog box to edit the images with the following options:
Click Add Drive to add a partition. The drive name must contain an uppercase letter with a colon at the end.
To add a directory, click Add Directory, then type the name of the new directory that you want to add.
To add a file, click Add File, navigate to the desired file, and click Submit.
3.
When you finish your edits, click Cancel to roll back the changes, or Save to apply the changes to the image.
4.
Optional: Under Deploy Options, select Remove local files not in image when restoring the original image to a device, and when files have been added or modified on the device that is not in the original image.

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, but not on the Remote Site Appliance.

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

Option

Description

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.

4.
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.
5.
Optional. When the import is complete, observe the imported image details, and make any changes, as required.
a.
On theSystem Images page, in the row containing the imported image, click the Name column to display the System Image Details page.
c.
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.
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 KACE SDA 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

Sysprep

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.

Capture

Deploy

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 KACE SDA post-installation tasks.
Use call when using .bat scripts in application tasks. For example: call myscript.bat
Related Documents