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

Configure the offboard DHCP server

Configure the offboard DHCP server

When you turn on a device for the first time, you can select the NIC or Network Boot option from the BIOS boot menu. Windows deployments require target devices to boot from somewhere other than the local drive. When you select the NIC or Network Boot option, the device sends an PXE request to the DHCP server to locate the iPXE server. In this case, the K2000 is the PXE server. You can configure an offboard DHCP server to acknowledge the appliance to enable target devices to UEFI boot from the K2000 appliance.

The steps might vary depending on which DHCP server you are using. Use the following settings for options 066 and 067 on any DHCP server.

If you are not using the Microsoft DHCP, see the following Knowledge Base article for additional information: https://support.quest.com/kace-systems-deployment-appliance/kb/112037

1.
Open the configuration application for your DHCP server.
2.
Set the following options for each subnet or scope that you want target devices to be able to boot from the K2000:
◦
Set Option 066 to the IP address of the K2000 appliance.

This option might appear as Next-Server, Boot Server Host Name or TFTP server name.

* 
NOTE: You might not be able to set Option 66 on some Cisco networking equipment. As an alternate configuration, you can set the sname and 244 options to the K2000 IP address.
◦
Set Option 067 to the string ipxe.efi (for UEFI devices), and undionly.kpxe (for BIOS devices).

This option might also appear as Boot File Name. Copy and paste the k2000.0 string as the Boot File Name option.

* 
NOTE: You can only have one PXE or TFTP server on a subnet. Disable other imaging tools on the subnets where you want to test the K2000.

The DHCP server automatically redirects PXE-compliant Windows devices to the appliance the next time the devices start up while connected to the network. The devices download the bootstrap file, and use the environment setup to boot.

Download and install the K2000 Media Manager

Download and install the K2000 Media Manager

You can download and install the K2000 Media Manager from the K2000 appliance to a device with the Windows ADK installed. The K2000 Media Manager uploads the K2000 Boot Environment (KBE) using the Windows ADK.

The Media Manager requires the full installation of Microsoft .NET 4.0. Download and install .NET 4.0 from http://www.microsoft.com/en-us/download/details.aspx?id=17851 .
1.
On the left navigation pane, click Library to display the Library Overview page.
2.
Under Source Media, select Choose Action > Download Media Manager to display the Media Manager page.
3.
Click Download for Windows.
The File Download window appears.
4.
Click Run or Save to download the installation file to the device, then double-click the file to start the installation.
The Welcome window appears.
5.
Run the Media Manager from Start > All Programs > Quest > K2000 Media Manager.
Build a K2000 Boot Environment. See Create a Windows boot environment.

Download and install Windows ADK

Download and install Windows ADK

Building a K2000 Boot Environment requires installing the Windows Assessment and Deployment Kit (Windows ADK) for Windows 7 and higher and Windows Server® 2012 devices.

You need ISO mounting software or a blank DVD, and a Windows device or a Windows Server with administrator privileges.
1.
Download and install the Windows ADK, see http://www.microsoft.com/en-us/download/details.aspx?id=30652.
2.
Under Select the features you want to install, select all of the features in the list.
Download and install the K2000 Media Manager to the same device where you installed the Windows ADK. For instructions, see Download and install the K2000 Media Manager.

Upload OS installation or source files

Upload OS installation or source files

You can use the K2000 Media Manager to upload the operating system source and installation files to the K2000 appliance.

Uploading the source media requires:
•
The K2000 Media Manager and .NET 4.0.
•
Installation disks or mounted ISO image.
* 
NOTE: Uploading the source files can take several hours.
1.
Insert the operating system disk in to the media drive on the device where the Media Manager is installed.
2.
Click Start > All Programs > Quest > K2000 Media Manager to display the K2000 Media Manager.
3.
In the K2000 Host Name field, type the host name or IP address of the appliance.
4.
In the Samba Share Password field, type the same password that you entered for the K2000 Samba Share.
5.
In Source Media Name, type a unique logical name.
This name identifies the image on the appliance; it is used to assign the image to scripted installations and boot actions.
6.
In Source Media Type, select the name of the operating system.
7.
In Path, click Browse and select the location of the image.
When attempting to upload media to the RSA, the Media Manager displays the error: Invalid Response: Please check the hostname provided.

Verify that the host name or the IP address is the host name or IP address of the K2000, and not the RSA.

8.
Click Start Upload.

When the process completes, the image appears on the K2000 appliance Source Media page.

Related Documents