Chat now with support
Chat with Support

KACE Systems Deployment Appliance 4.1 - Administrator Guide

About the KACE Systems Deployment Appliance (K2000) Getting started Using the Dashboard Configuring the K2000 Setting up user accounts and user authentication Configuring security settings Preparing for deployment Managing device inventory Using labels Creating a Windows Boot Environment Managing drivers Capturing images Capturing user states Creating scripted installations Creating a task sequence Automating deployments Performing manual deployments Imaging Mac devices About the Remote Site Appliance Importing and exporting appliance components Managing disk space Troubleshooting appliance issues Updating appliance software About us Legal notices Glossary

View source media details

View source media details

You can view information about source media, such as the file size and the date that the files were uploaded to the K2000 appliance.

1.
On the left navigation pane, click Library to expand the section, then click Source Media to display the Source Media page.
2.
Under Name, select the image to display the Source Media Detail page.
* 
NOTE: You can modify the name of the image and add notes to indicate changes to the image.
3.
Optional: Click Cancel to close the page.
4.
Click Delete to remove the source media from the appliance.
5.
Click Save.

Choosing the type of deployment

Choosing the type of deployment

You can deploy the operating system to different devices models, and the K2000 appliance will pull the drivers from its resource library for scripted installation deployments. You can copy the state of a device, such as all of the drives, the OS and system settings, programs, and files to perform system image deployments.

Scripted installation deployments

Use a scripted installation when using an ISO for the OS and create an answer file for the deployment.

System image deployments

Capture an image from a device including all of the device drives, the OS, system settings, programs, and files.

Deployment methods

•
Automated Deployments: Uses boot actions to initiate scripted installation and system images deployments. Supports unicast and multicast deployments.
•
Manual Deployments: Use manual deployments when deploying directly from the source media, for USB image deployments when the target device is not connected to the network.
* 
NOTE: Both deployment methods load the devices in to a K2000 Boot Environment or a NetBoot environment to initiate the deployment. For Mac devices, see Imaging Mac devices.

Supported images types

Supported images types

You can capture WIM and K-Image from devices with Windows 7 and higher and UEFI image from devices with Window 8 higher. You can also capture DMG images from Mac OS X devices.

Image types

WIM images

•
The WIM image file-based format stores information as files, rather than as sectors. You can add multiple files to a WIM image.
•
WIM images provide faster OS installations.
•
Multicast WIM image deployments enable you to broadcast one image to multiple devices at the same time to reduce network bandwidth if the routers on your network support multicast. The target devices must have the bandwidth for the image.
•
UEFI WIM image deployments larger than 4GB must be provisioned from a network resource, because images larger than 4GB cannot be deployed using a USB flash device.
•
WIM image deployments are hardware independent.

K-Images

•
The K-Image file-based format stores files as sectors, enables easy editing, and uses de-duplication to eliminate the need to rebuild images.
•
K-Images enable you to edit a base image that changes often without having to re-send the entire image or having to recapture or deploy the image.
•
K-Image deployments are hardware independent.

UEFI images

•
You can capture WIM UEFI images and UEFI K-Images.
•
UEFI K-Images larger than 4GB must be provisioned from a network resource, because images larger than 4GB cannot be deployed using a USB flash device.
•
Target devices must be UEFI-compatible and require creating a UEFI partition using the Create UEFI Partitions pre-installation task.

Managing device inventory

Configure and run a network scan
Add network inventory to the appliance
Scan active and non-active devices on the network
Add devices manually
Upload specific target device models
Join devices to a domain
Issue a Wake-on-LAN request
Deploy to devices in the K1000 inventory
View device details from a network scan
Apply a KUID to the K1000 Agent
Collect the computer name
Apply the computer name
Delete devices from Device Inventory
Delete devices from Network Inventory
Unregister devices
About the device action icons
Run an action on devices
Access remote devices using a VNC session

When a device boots in to the K2000 Boot Environment (KBE), the appliance identifies the device by its MAC address and lists the device on the Device Inventory page. The appliance lists devices that are on the network, but have not booted in to the appliance on the Network Inventory page.

About adding devices to K2000 Inventory:

•
You can list devices in a comma-separated (CSV) formatted file, and upload the file to the appliance.
•
You can run a Network Scan to detect devices on the network.
•
You can issue a Wake-on-LAN request to power on remote devices.
•
You can enter the MAC address to add devices to a boot action deployment.
•
You can run device actions, which are scripted actions that can be performed on managed devices.
•
You can unregister devices.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating