kbox 2000 admin guide - university of washington

A D M I N G U I D E

KBOXTM 2000 Series Installation and Administration Guide

Release 3.1

© 2004-2009 KACE™ Networks, Inc. All rights reserved.

KACE and KBOX are trademarks of KACE Networks, Inc. AppDeploy is a service mark of KACE Networks, Inc. iPhone is a registered trademark of Apple Inc.

All other trademarks are the property of their respective owners.

Information concerning third-party copyrights and agreements, hardware and software warranty, hardware replacement, product returns, technical support terms and product licensing is in the KACE End User License agreement accessible at:

http://www.kace.com/license/standard_eula

Revision Date: November 19, 2009 Updated: January 28, 2010

http://www.kace.com/license/standard_eula

Contents

Preface vii Additional Information Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Contacting KACE Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Chapter 1: Start Here - KBOX 2000 Process Overview Read the overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Install and configure your KBOX 2000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Learn the KBOX 2000 administration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . 1 Collect node information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Collect and deploy software components . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Perform recovery on corrupted nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Create reports for your implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Chapter 2: Introducing Your KBOX 2000 Systems Deployment Appliance

About the KBOX 2000 Systems Deployment Appliance . . . . . . . . . . . . . . . . . 3

KBOX 2000 Series Appliance Components . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 About the physical system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 The Systems Deployment Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 The Windows Client Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 The Mac OS Client Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 3: Installing Your KBOX 2000 Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Step 1 - Reviewing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 KBOX 2100 and 2200 Features, Specifications, and System Requirements 9

Step 2 - Putting Your KBOX 2000 Series Appliance Together. . . . . . . . . . . . 10 Step 2a - Unpack Your KBOX 2000e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Step 2b - Setting up the physical location . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Step 2c - Installing the rails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Step 2d - Installing the outer brackets or rails . . . . . . . . . . . . . . . . . . . . . . . 11 Step 2e - Installing the hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Step 2f - Logging on to your KBOX 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Step 2g - Verify the KBOX 2000 network access . . . . . . . . . . . . . . . . . . . . 13 Step 2h - Verify the KBOX 2000e web access . . . . . . . . . . . . . . . . . . . . . . 13 Step 2i - Log on to the KBOX 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Step 3 - Configuring the KBOX 2000 Series Appliance Settings . . . . . . . . . . 15

Step 4 - Configuring Your DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Remote Site Appliance-specific configuration . . . . . . . . . . . . . . . . . . . . . . . 15

KBOX 2000 Series Installation and Administration Guide, version 3.2 1

Contents

Step 5 - (MAC OS Only) Configuring the NetBoot Server . . . . . . . . . . . . . . . 16

Chapter 4: Configuring Your KBOX 2000 Configuring Your KBOX 2000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Configure the KBOX 2000 General Settings: . . . . . . . . . . . . . . . . . . . . . . . 17 Configure Date & Time Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Configure Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Apply Security Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Configure Registration & Licensing settings . . . . . . . . . . . . . . . . . . . . . . . . 22

Administering Users and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Using Labels to Organize KBOX 2000 Users and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Administering KBOX 2000 Node Licenses . . . . . . . . . . . . . . . . . . . . . . . . . 25 Using VNC to Control Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Adding and Managing Admin Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Managing user authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Configuring Single Sign-On for Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Connecting KBOX 2000 Series appliances with Linking . . . . . . . . . . . . . . . 31 Disabling KBOX 2000 linking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Linking KBOX 2000 Series appliances . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 5: Administering Your KBOX 2000 Using the Control Panel to Administer Your KBOX 2000 . . . . . . . . . . . . . . . . 34

Setting Up Regularly Scheduled Administration Tasks . . . . . . . . . . . . . . . . . 35 Updating the KBOX 2000 Server Software . . . . . . . . . . . . . . . . . . . . . . . . . 35 Updating your RSA software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Backing up and transferring KBOX 2000 components with the import/export feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Confirming that you have 20% free disk space . . . . . . . . . . . . . . . . . . . . . . 41 Analyzing activity from KBOX 2000 logs . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Purging unused K-image files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Checking for KPE and KNOPPIX Updates . . . . . . . . . . . . . . . . . . . . . . . . . 42 Checking the KBOX 2000 RAID Disk Status . . . . . . . . . . . . . . . . . . . . . . . . 43

Performing General Administration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Rebooting a KBOX 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Powering Off a KBOX 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Chapter 6: Scanning for Nodes and Managing Systems Inventory

About KBOX 2000 System Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46


Contents

Creating and Managing Network Scans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Managing System Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Managing Network Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 7: Capturing Operating System Images Importing Windows OS images from a CD/DVD . . . . . . . . . . . . . . . . . . . . . . 53

Capturing a Windows OS image from a networked CD/DVD drive . . . . . . . 53 Capturing a Windows OS image from the KBOX CD/DVD . . . . . . . . . . . . . 56 Viewing Software Library item details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Deleting a Software Library item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Capturing and Deploying Mac OS Disk Images . . . . . . . . . . . . . . . . . . . . . . . 58 Configuring the KBOX 2000 NetBoot Server. . . . . . . . . . . . . . . . . . . . . . . . 58 Start the KBOX 2000 Imaging Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Capturing a Mac OS disk image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Deploying a new Mac OS disk image from the KBOX 2000 . . . . . . . . . . . . 61

Chapter 8: Managing Your Driver Library About the Driver Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Managing Your Driver Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Rules for organizing new drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Understanding the driver directory structure . . . . . . . . . . . . . . . . . . . . . . . . 65 Adding drivers to the driver library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Recaching drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Using the DriverHarvest Program to Capture Drivers . . . . . . . . . . . . . . . . . . 68

Searching for Drivers in the Driver Library . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Viewing Driver Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Finding the Hardware for a Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Troubleshooting Driver Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Chapter 9: Creating and Configuring Pre- and Post-Installation Tasks

About Pre- and Post-installation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Configuring and Creating Pre-installation Tasks . . . . . . . . . . . . . . . . . . . . . . 76 Understanding the pre-installation task types . . . . . . . . . . . . . . . . . . . . . . . 77 About the default pre-installation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Configuring the default pre-installation task. . . . . . . . . . . . . . . . . . . . . . . . . 78 Creating new pre-installation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Duplicating a preinstallation task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Deleting a pre-installation task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81


Contents

Creating Post-installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 To add a new application item. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 To add a new BAT script item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 To add a new shell script item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 To add a new KBOX 2000 agent installer item . . . . . . . . . . . . . . . . . . . . . . 84 To add a new naming rule item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 To add a new service pack item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 To add a new custom HAL replacement item . . . . . . . . . . . . . . . . . . . . . . . 86 Post-installation task for installing .NET 2.0 . . . . . . . . . . . . . . . . . . . . . . . . 87 Post-installation task for changing workstation name . . . . . . . . . . . . . . . . . 88 Post-installation task for joining domain . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Editing a Post-Installation Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Duplicating a Post-installation Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Deleting a Post-installation Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Chapter 10: Capturing and Deploying User States Capturing, Deploying, and Managing System User States . . . . . . . . . . . . . . 92

Understanding user states. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Understanding the KBOX 2000 USMT interface . . . . . . . . . . . . . . . . . . . . . 93 User state capture and deployment overview . . . . . . . . . . . . . . . . . . . . . . . 94 Downloading USMT software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Capturing user states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Troubleshooting capturing and deploying user states . . . . . . . . . . . . . . . . . 98

Deploying user states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Managing user states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Deleting user states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Viewing user state details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Chapter 11: Using Scripted Installations to Deploy Software Components

About Scripted Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Scripted Installation Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Creating a Scripted Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Creating an answer file from scratch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Uploading an existing answer file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Installing without an answer file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Managing Pre- and Post-installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . 110 Adding a pre-installation task to a Scripted Installation . . . . . . . . . . . . . . . 110 Removing a pre-installation task from a Scripted Installation . . . . . . . . . . 110 Adding a post-installation task to a Scripted Installations . . . . . . . . . . . . . 110


Contents

Removing a post-installation task from the Scripted Installations . . . . . . . 110 Changing the order of pre-installation and post-installation tasks . . . . . . . 111

Installing the KBOX 2000 Agent Software Using a Scripted Installation . . . 111

Deploying a Scripted Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Deploying a Scripted Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Deleting a Scripted Installation from a Deployed System. . . . . . . . . . . . . . . 114

Deleting a Scripted Installation from the KBOX 2000. . . . . . . . . . . . . . . . . . 115

Viewing and editing Scripted Installation Details . . . . . . . . . . . . . . . . . . . . . 115

Setting Boot Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Chapter 12: Using System Images to Deploy Software Components

About KBOX 2000 Series System Imaging . . . . . . . . . . . . . . . . . . . . . . . . . 118 Imaging environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Understanding the image formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Image Capture and Deployment Process Overview. . . . . . . . . . . . . . . . . . . 119

Capturing and Deploying Windows Images . . . . . . . . . . . . . . . . . . . . . . . . . 120

Deploying a System Image to a Non-networked Computer with a USB Drive . . . . . . . . . . . . . . . . . . . . . . . . 123

Deleting a Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Managing Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Deleting an Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Applying a label to an image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Viewing and Editing Image Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Managing system image files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Deploying a K-image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Using sysprep with K-images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Chapter 13: Deploying Software Components from a Remote Site Appliance

About Remote Site Appliances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 RSA Target host system requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Creating an RSA on a Virtual System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 To install the RSA and virtualization software: . . . . . . . . . . . . . . . . . . . . . 133 To configure and link your virtual KBOX:. . . . . . . . . . . . . . . . . . . . . . . . . . 134 To configure and sync an RSA: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 To set the RSA as your nodes’ boot device: . . . . . . . . . . . . . . . . . . . . . . . 136

Downloading Software Components to an RSA. . . . . . . . . . . . . . . . . . . . . . 137


Contents

Transferring Boot Environments to RSAs Using a CD or USB. . . . . . . . . . . 138

Administering RSAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 To view or edit the RSA details:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Updating RSA server software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 To delete an RSA: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Troubleshooting RSA operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Chapter 14: Recovering Corrupted Nodes Performing Recovery on Corrupted Nodes . . . . . . . . . . . . . . . . . . . . . . . . . 143

Recovery Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Setting up the corrupted node for recovery . . . . . . . . . . . . . . . . . . . . . . . . 144 Recovery using the Windows Deployment And Recovery Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

recovery using the Linux Deployment and Recovery Console . . . . . . . . . 146 Recovery from the Administrator Console using VNC. . . . . . . . . . . . . . . . 146

Chapter 15: Using the KBOX 2000 Deployment Client About the Boot Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Setting Up a Node To Boot The Boot Menu . . . . . . . . . . . . . . . . . . . . . . . . . 147

Windows Deployment And Recovery Console (KPE) . . . . . . . . . . . . . . . . . 148 About the File Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Scripted installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Imaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Hardware Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Powering off the client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Linux Deployment And Recovery Console (KNOPPIX) . . . . . . . . . . . . . . . . 151 Capture a machine image on the KBOX 2000. . . . . . . . . . . . . . . . . . . . . . 151 Deploy image to this machine from the KBOX 2000 . . . . . . . . . . . . . . . . . 151 Launch a shell to create partitions and set up devices . . . . . . . . . . . . . . . 151 Do nothing and reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Defining A Boot Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Setting up a system to load this boot environment . . . . . . . . . . . . . . . . . . 152 Creating another boot environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Viewing boot environment details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Chapter 16: Using the KBOX 2000 Reporting Tools Understanding the KBOX 2000 Reporting Features . . . . . . . . . . . . . . . . . . 156

Using the Default Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Understanding the Report Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158


Contents

To Run a Report select the output format . . . . . . . . . . . . . . . . . . . . . . . . . 159

Creating and Modifying Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Using the System Performance Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

KBOX 2000 Administrator Home Page Summary Reports . . . . . . . . . . . . . 163

Daily Status Emails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Appendix A Deploying Windows Service Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Deploying Windows Service Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Supported Windows service packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Creating a service pack post-installation task . . . . . . . . . . . . . . . . . . . . . . 166

Appendix B Warranty, Licensing, and Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Warranty And Support Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Third Party Software Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Apache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 EZ GPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 FreeBSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Knoppix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Microsoft Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 OpenSSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 PHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Samba . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Sendmail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Windows Pre-Installation Environment (Windows PE) . . . . . . . . . . . . . . . 187

Index .................................................................................................... 188


Contents


P R E F A C E

Preface

Additional Information ResourcesYou can refer to the following resources to install, configure, and maintain your KBOX™ 2000 Systems Deployment appliance:

• Silent Mode Installation Tips and Tricks - http://www.kace.com/support/customer/doc/SilentInstallationWhitepaper.pdf

• Installation and Scripting resources - http://www.kace.com/support/customer/additional_resources.php

• Tutorial Videos - http://www.kace.com/support/customer/training.php

Documentation ConventionsThis manual uses the following font conventions:

Font conventions:

Contact KACE Support if you do not have a user name and password to access these resources.

Font Format Description

Bold font Represents buttons, tab names, and menu selections on your KBOX 2000.

Typewriter font Represents text that you would literally type into, or see returned by your KBOX 2000.

Italic font Highlights new terms, and indicates variables which you replace with values specific to your organization. For example, when you see a variable such as mydomain replace it with the actual name of the domain you are using.

> (right arrow symbol)

Indicates selection order. For example, Inventory > Computers directs you to first Browse to the Inventory page of the KBOX 2000 Systems Deployment Con-sole, and then select the Computers tab underneath it.

vii

http://www.kace.com/support/customer/doc/SilentInstallationWhitepaper.pdf




http://www.kace.com/support/customer/additional_resources.php

http://www.kace.com/support/customer/training.php

http://www.kace.com/support/customer/training.php

Browsing to the Administrator and User Portals:

When this manual directs you to “browse to the KBOX Systems Deployment Console,” start a web browser and enter http://KBOX_name or http://KBOX_IP_address in the navigation window to connect to the KBOX. The KBOX Systems Deployment Console login page appears. Log on with the admin username and your password (also admin by default).

Similarly if you have a KBOX 1000 Systems Management appliance (KBOX 1000), “navigating to the KBOX User Interface” means logging on to the system running your KBOX 1000 by starting a web browser, and entering KBOX_name/user in the navigation window. The KBOX User Interface appears.

Note conventions:

Contacting KACE Technical SupportYour KBOX™ product includes software updates, telephone support, and access to the online support portal. To access the KACE support portal:

From your KBOX 2000 Series appliance Administrator interface:

Select the icon on right side of the KBOX 2000 Systems Deployment Console and select Settings > Support. The Settings: KACE Support page appears.

From any web browser:

If your KBOX 2000 is not functioning, browse to the www.kace.com/support website from any web browser and the Support overview page appears. Your Support login is required.

Text in a blue box next to the KACE logo represents a note. These notes include configuration questions, warnings, unusual KBOX 2000 behaviors, or instructions of particular importance.

KBOX 2000 Series Installation and Administration Guide viii

www.kace.com/support

C H A P T E R 1

Start Here - KBOX 2000 Pro-cess Overview

This section explains how to use the KBOX™ 2000 Systems Deployment appliance documentation to get the most out of your KBOX 2000 appliance. It covers the most popular KBOX 2000 features.

Read the overviewFirst, you need to understand your KBOX 2000. Start by reading the Introducing Your KBOX 2000 Systems Deployment Appliance section for an overview, information on its capabilities, and important concepts to understand.

Install and configure your KBOX 2000After reading the introduction, you are ready to get your KBOX 2000 running and configured. These chapters explain the process:

• Installing Your KBOX 2000• Configuring Your KBOX 2000

Learn the KBOX 2000 administration tasksOnce the KBOX 2000 is set up and configured, read through the Administering Your KBOX 2000 chapter to learn how to keep your KBOX 2000 working efficiently. That chapter explains both the tasks that you need to perform on a regular basis and those that you perform as necessary.

Collect node informationAfter your KBOX 2000 is installed, configured, and tuned, you can start the process of deploying software to the nodes on your LAN. The first step is to collect information about those nodes using the instructions in the Scanning for Nodes and Managing Systems Inventory section.

Collect and deploy software componentsNow, it’s time to begin collecting or creating the various software components to deploy on your nodes. First, you need to capture operating system images and the drivers that they rely on, for deployment on other nodes. Instructions for this are in the Capturing Operating System Images and Managing Your Driver

1

Start Here - KBOX 2000 Process Overview

Library chapters. Each operating system requires some pre-installation hardware configuration tasks, and you define those actions as pre-installation tasks. See the Creating and Configuring Pre- and Post-Installation Tasks chapter for details.

Once the operating system images and drivers are stored on your KBOX 2000, you need to add post-installation tasks to install or configure other software components. For details, see the Creating and Configuring Pre- and Post-Installation Tasks chapter.

Once you have collected software components to deploy, it’s time to collect them into the scripted installation or system images that you use to deploy them to your nodes. See these chapters for details:

• Using Scripted Installations to Deploy Software Components• Using System Images to Deploy Software ComponentsBefore deploying a new operating system, you can capture user settings and files for later re-deployment using the instructions in the Capturing and Deploying User States chapter.

If you have remote sites with better network connections with each other than they do with you KBOX 2000, you can set up a Remote Site Appliance (RSA) to deploy operating system images more efficiently. For details, see the Deploying Software Components from a Remote Site Appliance chapter.

Deploying Windows Service Packs requires special instructions; see the Deploying Windows Service Packs chapter for details.

Perform recovery on corrupted nodesAnother important KBOX 2000 feature is its ability to act as a target boot environment for nodes that cannot boot to their own disks. For example if the node becomes corrupted. You direct those nodes to boot to one of the default KBOX 2000 boot environments (or one you created). For details, see the Recovering Corrupted Nodes and Using the KBOX 2000 Deployment Client chapters.

Create reports for your implementationSee the Using the KBOX 2000 Reporting Tools chapter for details on the reports that summarize and display KBOX 2000 activity.

KBOX 2000 Series Installation and Administration Guide 2

C H A P T E R 2

Introducing Your KBOX 2000 Systems Deployment Appli-ance

This section introduces you to your KBOX 2000 Systems Deployment appliance’s main components and features.

About the KBOX 2000 Systems Deployment ApplianceYour KBOX™ 2000 Systems Deployment appliance simplifies, speeds up, and reduces the cost of deploying software images to the computers you administer. Your KBOX 2000 allows you to automatically deploy images to servers, desktops, and laptops with the help of an easy-to-use Web-based User Interface. The images can contain operating systems, applications, drivers, and any other software that your organization needs to deploy.

KBOX 2000 Series appliances provide automated deployment of software images, including:

• Remote disk image capture, archiving captured image, and deployment.

3

Introducing Your KBOX 2000 Systems Deployment Appliance

• Remote, unattended Scripted Installation.

• Slipstreaming of applications and files, such as the KBOX agent software.

• Integrated library of images and Scripted Installations.

• Remote system recovery.

• Flexible reporting with pre-configured reports.

You can extend the image deployment to perform other actions on the target node the next time it boots, such as:

• Run a Scripted Installation.

• Reboot the operating system after installation.

• Add other software or configuration information (before or after the operating system boot).

• Capture a Machine Image.

• Deploy a Captured Image.

• Boot to the Recovery Console.

KBOX 2000 Series Appliance ComponentsThis section introduces you to the components and concepts of your KBOX 2000 system, and to the KBOX 2000 workflow for systems deployment. A single KBOX 2000 is designed to support enterprises and business units with 100 to 8500 nodes.

The KBOX 2000 uses these main components:

• The physical system.

• The Administrator Console

• The Client Console.

About the physical systemThe KBOX 2000 is a high-performance 1 U rack server. Depending on the configuration, it includes:

• Dual on-board Xeon processors.

• Dual Gigabit Ethernet ports.

• Four hard disks in a RAID 5 configuration.

The Systems Deployment ConsoleThe KBOX 2000 Systems Deployment Console is a web-based interface that you use to:

• Collect or create software images, such as operating system images and application executables to deploy to your nodes.

• Define the pre- and post-installation tasks that use to configure the nodes being deployed and install the software images on them.

• Use a remote recovery console to repair nodes.

• Display reports on deployment statistics, and KBOX 2000 system performance.



The Systems Deployment Console also offer you alerts, tricks, tips, and up-to-date FAQ articles from KACE to help you get the most out of your KBOX 2000.

The KBOX 2000 Systems Deployment Console Home tab provides the following quick-reference information:

Important and useful technical tips, cau-tions, and tricks.

Quick links to fre-quently-used KBOX 2000 tasks.

A summary of the KBOX 2000 compo-nents.

A quick status of the KBOX 2000 tasks that you have initiated.



The Disk Usage section in the lower right of the Home page provides up-to-date information about the disk usage of your KBOX 2000 Series appliance:

The Windows Client ConsoleThe KBOX Windows Deployment Client (Client Console) - The Client Console is a web interface available from the target node for completing these tasks locally:

• Scripted Installation deployment.

• Disk image capture and deployment.

• Access to the Recovery Console.

Be sure to reserve about 20% of your Disk Usage as Free for optimal performance and to leave enough space to restore a backup to the KBOX 2000.



The Mac OS Client ConsoleThe KBOX Mac OS Imaging Utility (Client Console) - The Mac OS Imaging Utility is a web interface available from the target node for capturing and deploying Mac OS disk images.


C H A P T E R 3

Installing Your KBOX 2000

This section explains how to unpack, put together, turn on, boot, and configure the DHCP and NetBoot servers for your KBOX™ 2000 Series Systems Deployment appliance (KBOX 2000).

Installation StepsPerform the following general steps to install your KBOX 2000:

“Step 1 - Reviewing Requirements,” on page 9.

“Step 2 - Putting Your KBOX 2000 Series Appliance Together,” on page 10.

“Step 3 - Configuring the KBOX 2000 Series Appliance Settings,” on page 15.

“Step 4 - Configuring Your DHCP Server,” on page 15.

“Step 5 - (MAC OS Only) Configuring the NetBoot Server,” on page 16

Step 1 - Reviewing RequirementsThe KBOX 2000 Series appliances are available in two models. The KBOX 2100 Systems Deployment appliance is designed for environments of up to 1000 managed systems; the KBOX 2200 Systems Deployment appliance is designed for environments with more than 1000 managed systems. Take note of the following requirements before installing your KBOX 2000:

KBOX 2100 and 2200 Features, Specifications, and System RequirementsSee the last page of the KBOX 2000 Series System Deployment Appliance Data Sheet for the latest in KBOX 2100 and 2200 features and specifications and required hardware and software:

http://www.kace.com/pdf/datasheet/KBOX-Systems-Deployment-Appliance.pdf

Before you proceed, however, make sure you review the requirements listed in Step 1.

KACE also provides a poster version of the KBOX 2000 installation instructions, complete with photographs and diagrams.

9


Step 2 - Putting Your KBOX 2000 Series Appliance TogetherBefore you use your KBOX 2000 to manage the systems on your network, you need to assemble and install it with these instructions:

Step 2a - Unpack Your KBOX 2000eInspect the box in which the appliance was shipped, and note if it is damaged in any way.

In addition to the KBOX 2000 hardware, the box includes:

1 set of inner and outer rail assemblies

6 rail mounting brackets

Mounting screws for installing the system into the rack

Figure 3-1: Box Contents

Step 2b - Setting up the physical locationFigure out where you will install the appliance before you assemble the rails:

Install the appliance in a clean, dust-free area that is well-ventilated.

Avoid areas where heat, electrical noise, and electromagnetic fields are generated. Install it near a grounded power outlet.

Use a regulating uninterrupted power supply (UPS) to protect the server from power surges and voltage spikes, and also to keep your system operating in case of a power failure.

Leave approximately 30 inches of clearance in the back of the rack, to allow sufficient airflow and ease in servicing.

Step 2c - Installing the railsTo install the rails, perform the following procedure:

Be sure to read all installation instructions carefully. KACE also provides a poster version of the KBOX 2000 instructions, complete with photographs and diagrams.



1. Locate the inner rail.

2. Align the four square holes on the right inner rail against the hooks on the right side of the chassis. Then slide the rail forward.

3. Securely attach the rail to the chassis with two flat head screws.

4. Repeat these steps to install the left inner rail to the left side of the chassis.

Figure 3-1: Installing the Rails

Step 2d - Installing the outer brackets or rails

Standard Rack Installation

1. Mount the short unthreaded brackets [B] in the front of the rack and the longer unthreaded brackets [A] in the back. Installa-tion may vary depending on the model and manufacturer of your rack. In rare cases, it is necessary to use the shorter threaded bracket [C] on the front or rear of the rack. Some racks require the use of cage nuts which should be supplied by your rack manufac-turer.

Figure 3-1: Standard Rack Installation

3. Make sure you align the brackets and screws in the same level in the rack, from front to back and from left to right.

4. Improper alignment can cause the appliance to fall out of the outer rails.

5. Slide each of the outer rails into the brackets, until the front end of the outer rail lines up with the front end of the outer fixed brackets.

6. Secure with four screws on each side.



Telco Rack Installation Only

1. Attach the shorter unthreaded brackets [B] to the front of the rack and the longer unthreaded brackets [A] to the back of the rack.

2. Make sure you align the brackets and screws in the rack, from front to back and from left to right. Improper alignment can cause the appliance to fall out of the outer rails.

3. Slide the outer rails into the brackets and loosely secure them with four domed head screws on each side. Leave enough of the outer rails extended in the front to attach the small threaded bracket [C].

4. Once the small threaded brack-ets [C] are in place, tighten all the screws.



Step 2e - Installing the hardwareYou now have rails attached to both the chassis and the rack unit. To install the appliance into the rack, line up the rear of the chassis rails with the front of the rack rails. Slide the chassis rails into the rack rails, keeping the pressure even on both sides (you may have to depress the locking tabs when inserting). You hear the “click” of the locking tabs, when you push the server completely into the rack.

Step 2f - Logging on to your KBOX 2000Connect a network cable to the KBOX 2000, and start the appliance. Your machine requires 5 to 10 minutes when you start the server for the first time. At the logon prompt, enter:

Login: konfig Password: konfig

Using UP and DOWN arrows to move between fields, modify the static IP address, subnet mask, default gateway, and DNS settings to match your network (Fig. 4).

We recommend adding a static IP entry for ikbox to your DNS. Enter a fully qualified hostname and domain name for the KBOX 2000. The fully-qualified host name of the KBOX 2000 on your network is the DNS entry (ikbox) concatenated with the domain name.

After confirming all the values on the screen, use the DOWN arrow and go to Apply. Use the RIGHT arrow key to restart the KBOX 2000 to the new settings.

Step 2g - Verify the KBOX 2000 network accessA special netdiag user account is available on KBOX 2000 Server, to diagnose any network problems. This account allows administrators to run a restricted set of commands for network diagnostics. The login credentials are:

Login ID: netdiag Password: netdiag

This account:

Is limited to these netdiag commands:

arp, cat, dig, ifconfig, iostat, netstat, nslookup, ping, route, and top.

Can be used only on the KBOX 2000 console. The account does not support remote logons though SSH.

Step 2h - Verify the KBOX 2000e web accessPlug the Ethernet cable in the port closest to the KBOX 2000 power supply, and connect it to a router or a hub on your network.

Verify that the appliance is now online by browsing from another computer to http://ikbox.



Step 2i - Log on to the KBOX 2000After accepting the EULA, log on using the following credentials:

Login ID: admin

Password: admin

Figure 3-1: Logon Screen

The KBOX 2000 Systems Deployment Console appears:



Step 3 - Configuring the KBOX 2000 Series Appliance SettingsBefore you use the KBOX 2000 to manage software and machines on your network, it is necessary to properly configure it. See the Configuring Your KBOX 2000 section for details.

Step 4 - Configuring Your DHCP ServerYour DHCP server needs to direct the clients to the KBOX 2000 Series appliance for the next boot code, so that the clients can use PXE to start from the network. This occurs when two DHCP option values are set on the DHCP server.

Windows 2003 Server-specific configuration

To configure the DHCP Server on the Windows 2003 Server, perform the following steps:

1. Start the DHCP manager by selecting the DHCP option from the Admin Tools sub-menu of the Programs menu.

If you want to allow all the clients to network boot, select Server Options, then right-click and select Configure Options.

If you want to restrict network booting to a specific Scope, expand the Scope in the DHCP manager and select Scope Options. Right-click and select Configure Options.

2. In the option configuration window, select the General tab.

3. Select the Option 066 check box, and enter the IP address of the KBOX 2000 as the value.

4. Select the Option 067 check box, and enter kbox2000.0 as the value.

Remote Site Appliance-specific configurationYou must define different DHCP server scopes for different Remote Site Appliances. For each scope defined you need to configure the following scope options:

DHCP Option Setting

Option 66: TFTP server name Set this option to be the IP address of the KBOX 2000 server.

Option 67: Bootfile name Set this option to kbox2000.0.

DHCP Option Setting

Option 66: Boot Server host name

Set this option to be the IP address of the specific Remote Site Appliance.

Option 67: Bootfile name Set this option to kbox2000.0.



Step 5 - (MAC OS Only) Configuring the NetBoot ServerIf your KBOX 2000 supports Mac OS X nodes, complete these steps to allow them to boot over the network using an image on your KBOX 2000:

1. Browse to KBOX Systems Deployment Console > KBOX Settings and Maintenance > Control Panel.

The KBOX Settings: Network page appears.

2. Click [edit mode] at the bottom of the page.

3. Click the Enable NetBoot Server (for Mac OS X clients) check box.

The NetBoot settings appear.

4. If your organization has multiple KBOX 2000 Series appliances, use the BSDP Server Priority and Image Index to specify unique settings for each appliance.

The Image Index range is the range of 1-32768.

5. Click the Save Changes button at the bottom of the page.

Your NetBoot server is configured to be recognized by Mac OS nodes.

If different KBOX 2000 Series appliances have the same NetBoot servers settings, boot attempts will have unpredictable results.


C H A P T E R 4

Configuring Your KBOX 2000

This chapter explains the configuration steps necessary before you can start using your KBOX™ 2000 Systems Deployment appliance. Once configured, you will only rarely have to return to this chapter to reconfigure these steps.

This chapter assumes that you have already followed the instructions in the Introducing Your KBOX 2000 Systems Deployment Appliance and installed and logged into your KBOX 2000.

For information on tasks you need to perform regularly to keep you KBOX 2000 up to date, see the Administering Your KBOX 2000 chapter.

Configuring Your KBOX 2000Perform the steps in the sections below to configure your KBOX 2000.

Configure the KBOX 2000 General Settings:1. Browse to the KBOX Systems Deployment Console > KBOX Settings & Maintenance > Control

Panel.

The KBOX Settings: Control Panel page appears:

Any changes to the date, time, network, or security settings directs the KBOX 2000 to reboot as soon as you hit save. There is no warning.

17


2.

3. Click General Settings. The KBOX Settings: General page appears.

4. Click the [Edit Mode] link to make this page editable.

5. Specify the following settings:

Last Modified (Read only) Displays the date and time when the settings were last modified.

Action Icon #1 and

Action Icon #2

(Optional) Select an action from the Action Icon drop-down list. You can associate these two icons with remote actions. These Icons appear on System Inventory, Network Inventory and Boot Actions pages. If you are new to the KBOX 2000 you probably want to leave these decisions until you discover actions that make sense for your organization. For details on remote actions see the Enabling remote access with the Action Icons sec-tion.

Boot Manager Timeout Enter the time out interval (in seconds). The boot manager time-out determines time span for which the boot menu is dis-played before the default boot entry is loaded. You can extend or shorten the timeout value. If the value is 0, then you need to enter the choice while booting.

Boot Manager Style Select the boot style (Graphical Menu/Text Menu/Basic) from the drop-down list.

Local Hard Disk Boot Method Select the boot method (Chain Boot/Local Boot) from the drop-down list. The Chain Boot is the default method.

Boot Manager Password Enter the password for Boot Manager. This could be either Graphical or Text Menu.

VNC Password Enter the password for the VNC. The VNC program included with the KBOX 2000 allows remote control of nodes. For details see the Using VNC to Control Nodes section.

Driver/Restore Share Password Enter the password for accessing the drivers and restore shares.



6. Click Save Changes to save your changes.

Enabling remote access with the Action Icons

The Action Icons allow remote access to nodes directly from the KBOX 2000 User Interface. The Action Icons can also be programmed for other tasks. The KBOX 2000 Series appliances ship with Action Icon #1

configured to use VNC through an Internet Explorer browser.

To run an action on any host machine, you can specify the string KACE_HOST_NAME after the executable of the specified action. The KBOX 2000 substitutes the KACE_HOST_NAME variable with the target machine name and launches the specified executable on the target machine.To run an action without the executable, you need to specify the action icon in the form of URL such as http://KACE_HOST_NAME or https://KACE_HOST_NAME. The KBOX 2000 substitutes the KACE_HOST_NAME variable with the target machine name and launches the URL in a different browser instance on the target machine.

To configure remote access with the Action Icons:

The following example displays steps for configuring Action Icons:

1. Browse to the KBOX Systems Deployment Console > KBOX Settings and Maintenance > Control Panel > General Settings.

The KBOX Settings: General page appears.


3. In Action Icon #1 drop-down list, select putty.exe KACE_HOSTNAME.


5. Select Systems > System Inventory. The System Inventory page appears.

Default KBOX Deployment and Recovery Environment

Select default environments from the drop-down list for each of the platforms listed:

• Windows x86 Deployment and Recovery Console (KPE).

• Windows x64 Deployment and Recovery Console (KPE x64)

• Linux Deployment and Recovery Console (KNOPPIX).

• Mac OS X Intel (NetBoot).

• Mac OS X PowerPC (NetBoot).

Most actions in the Action Icon drop-down list require you to install additional software for them to function. For example, using TightVNC requires you to install TightVNC on the administrative workstation.

Some of the actions listed in Action Icon drop-down list require Internet Explorer. This is because KBOX 2000 uses ActiveX to launch these programs on the local machine. Firefox does not support this feature.



6. Click Action Icon #1 of the target machine.

A putty session opens for the user, for connecting to the target machine.

Configure Date & Time SettingsIt is very important to keep the date and time of your KBOX 2000 accurate, as date and time are used in most KBOX 2000 deployment or Scripted Installation operations.

1. Browse to the KBOX Systems Deployment Console > KBOX Settings & Maintenance > Control Panel. The KBOX Settings: Control Panel page appears.

2. Click Date & Time Settings. The KBOX Settings: Date and Time page appears.

3. Click [Edit Mode] link to make this page editable.

4. Verify that the clock is set to the correct date and time.

5. If you need to change the date and time, enter following information:

6. Click Save Changes to save your changes. Click Revert Changes to undo the changes you made.

When updating the time or time zone, the KBOX 2000 Web Server is restarted in order to reflect the new time or zone information. This may disrupt KBOX 2000 operation for 10 to 15 seconds. Active connections may be dropped during the restart of the Web server. You may need to manually refresh this page in the browser in order to display the new time and zone settings.

Last Modified Displays the date and time that your KBOX 2000 date and time were last modified. This is a read-only field.

Current Time Displays the current date and time according to your KBOX 2000. This is a read-only field.

Time Zone Select the appropriate Time Zone from the drop-down list.

Automatically synchronize with an Internet time server

Select the check box to automatically synchronize the KBOX 2000 with an Internet time server.

Time Server Enter the hostname of an Internet Time Server.

Set the clock on the KBOX manually Select the check box to manually set the clock on the KBOX 2000. To select this option, the Automatically synchronize with an Internet time server option must be unchecked.

New Time Select the appropriate H(our), M(inute), and S(econd) values from the drop-down lists.

New Date Select the appropriate M(onth), D(ay), and Y(ear) values from the drop-down lists.



Configure Network SettingsNetwork settings vary depending on your network configuration. You should adjust these settings depending on your network configuration. After making changes to networks settings, restart your KBOX 2000 and verify that the network settings are appropriate for your local network.

1. Browse to the KBOX Systems Deployment Console > KBOX Settings & Maintenance > Control Panel.

The KBOX Settings: Control Panel page appears.

2. Click Network Settings. The KBOX Settings: Network page appears.


4. Enter following information:

Changes to the network settings directs the KBOX 2000 to reboot—total reboot downtime depends on the number of Scripted Installations (assuming the network settings are valid).

Host Name Enter the fully qualified domain name of your KBOX 2000.

Domain Name Enter the domain name of your KBOX 2000. For example, kace.com

IP Address Enter the static IP address for deployment for the KBOX 2000. When you modify the IP address, be extremely careful in setting the new address. Ensure you use the correct new address, or it will be difficult to locate the KBOX 2000 on your network without knowing the exact IP address as configured.

Network Speed Select a network speed from the drop-down list.

Default Gateway Enter the default gateway.

Subnet Mask Enter the subnet mask.

Primary DNS Enter the primary DNS.

Secondary DNS Enter the secondary DNS.

Enable Onboard DHCP Server

Select the check box if you want to use the KBOX 2000’s onboard DHCP (Dynamic Host Configuration Protocol Server). Leave this check box blank if you use a different DHCP server in your environment.

DHCP Pool Start. Enter the starting IP address for the DHCP pool.

DHCP Pool End. Enter the ending IP address for the DHCP pool.



5. Click Save Changes. Click Revert Changes to undo the changes you made.

Apply Security SettingsThe Security settings enable or disable access to SSH and Offboard database. The database is externally not accessible by default.



2. Click Security. The KBOX Settings: Security page appears.


4. Select from the following options to enable or disable SSH and Offboard DB Access:

• Allow SSH Root Login (used by KACE Support).

SSH is required in order for KACE Support personnel to connect a tether to and perform diagnostics on your KBOX 2000 in the event the it becomes unresponsive. If the recommended free disk space is not available and you encounter a problem, this is the only way Support personnel can diagnose and fix problems with your KBOX 2000. This is less secure, but only slightly so. A hacker would need physical access to your network to exploit this as a security hole.

• Allow Offboard Database Access

• Enable SNMP Monitoring. The default Community String is public; change this if your organization uses a different string.

5. Click Save Changes. This applies the security settings as selected by you and reboots the KBOX 2000 Server. You are re-directed to the Administrator Console for re-login, after some time.

Configure Registration & Licensing settingsBefore your KBOX 2000 will work you must first Enter the Registration information and Licence Key.

Use Proxy Server Select the check box if your KBOX 2000 must use a proxy server to access the Internet in order to contact www.kace.com to download software updates and check license information.

Proxy Type. Enter the proxy type, either HTTP or SOCKS5.

Proxy Server. Enter the name of the proxy server.

Proxy Port. Enter the port for the proxy server, the default sport is 8080.

Proxy (Basic) Auth. Select the check box to use the local credentials for accessing the proxy server.

Proxy Username. Enter the username to access the proxy server.

Proxy Password Enter the password to access the proxy server.

Use SMTP Server. Enter the Enter the SMTP IP address. Be sure to config-ure your SMTP Server to allow anonymous login for outbound mail transport.

Changes to the network settings direct the KBOX 2000 to reboot. Total reboot downtime depends on the number of Scripted installations, provided that the changes result in a valid configuration.


www.kace.com




2. Click Registration & Licensing. The KBOX Settings: Registration & Licensing page appears.


4. Enter the following information:

5. Enter the license key in the License Key field.

6. Click Save Changes.

Administering Users and ResourcesThis section explains tasks that you use to administer the users and resources on your KBOX 2000, including:

• Using Labels to Organize KBOX 2000 Users and Resources• Administering KBOX 2000 Node Licenses• Using VNC to Control Nodes

Using Labels to Organize KBOX 2000 Users and ResourcesYou use labels to organize and manage KBOX 2000 users, machine images, user states, and other KBOX 2000 resources. The labels your organization uses depend entirely on your organization’s needs. For example, labels can reflect corporate structures, organizations, processes, or geographical locations: “Engineering”, “QA”, “Staging”, “Building A”, and so on.

Company-Institution Name Enter the name of your organization.

Organization Name (Optional) Enter the name of your division or organization.

Administrator Email Enter the email address of the KBOX 2000 administrator. KBOX 2000 daily status emails are sent to this address.

Send Crash Reports to KACE It is highly recommended that you enable this check box to send a report to KACE in the event of a KBOX 2000 crash.

Status Displays whether the KBOX 2000 license is valid or invalid.

Expires Displays the license expiration date.

Modules Displays the optional modules that the license includes.

Seats Displays the number of seats the license is applicable for.



Each user or resource can be in none, one, or multiple labels. Once grouped by label, you can perform most KBOX 2000 actions on a per-label basis.

Creating labels

1. Browse to the KBOX Systems Deployment Console > KBOX Settings & Maintenance > Control Panel sub-tab. The KBOX Settings: Control Panel page appears.

2. Select Labels. The KBOX Settings: Labels page appears.

3. From the Choose action drop-down list, select Add New Item.

The KBOX Settings: Edit Label Detail page appears.

4. Specify the following details:


Deleting labels

Deleting labels removes any existing association of that label with any machine, user, or system images.

To delete a label:

1. Browse to the KBOX Systems Deployment Console > KBOX Settings & Maintenance > Control Panel sub-tab. The KBOX Settings: Control Panel page appears.

2. Select Labels. The KBOX Settings: Labels page appears.

3. Select the checkbox for the name of the label to delete.

4. From the Choose action drop-down list, select Delete Selected Item(s).

5. Click OK to confirm the deletion.

You can also delete a label from the Label Detail page.

Applying labels

You apply labels to users and images from the Users or Image Library pages.

Deleting labels removes any existing association of that label with a user, image or user state.

Record Created Indicates when the record was created. This is a read-only field.

Record Last Modified Indicates when the record was last modified. This is a read-only field.

Label Name Displays the label name. This is a required field.

Label Type This field is populated automatically. The Label Type for all labels is by default “Manual Label”.

Notes Enter a descriptive comment about the label.



To apply a label to a user:



2. Click Users.

The KBOX Settings: Users page appears.

3. Select the check box next to the user, you wish to apply the label to.

4. From the Choose action drop-down list, select the label you want to apply from Apply Label section.

The KBOX Settings: Users page now shows the user associated with the label.

To apply a label to a machine image:

1. Browse to the KBOX Systems Deployment Console > Deployments > System Images.

The Image Library page appears.

2. Select the check box beside the image, you wish to apply a label to.

3. From the Choose action drop-down list, select the label you want to apply from Apply Label section.

The Image library now shows the image associated with the label.

Viewing label details

Once you have created a label, you can associate the label to the system inventory, users, or system images on your network. You can filter the data for above categories by the label name. From the label detail view, you can view label name, label type, notes and about the label.

To view label details:



2. Click Labels. The KBOX Settings: Labels page appears.

3. Click the linked name of the label. The KBOX Settings: Edit Label Detail page appears, where you can view the label details.

Administering KBOX 2000 Node LicensesYour KBOX 2000 supports a specific number of node licenses that is set when you purchase it. The licenses are transferable, and are only counted against nodes that are currently connected to your KBOX 2000. If you run out of licenses, releasing some PXE boot nodes can free some up for you to use.

For more information on creating labels, see Chapter 4,“Creating labels,” starting on page 24.



To view KBOX 2000 seat licence information:



2. Select Registration & Licensing.

The KBOX Settings: Registration & Licensing page appears.

3. The following fields show you the applicable license key details:

To release PXE boot and NetBoot licenses from nodes:

Each PXE boot (Windows) or NetBoot (Mac OS) initiated from your KBOX 2000 counts as a licensed use of the software. This can artificially inflate the number of nodes using a software version. Perform these steps to release nodes from the KBOX 2000 and free the licenses.

1. Browse to the KBOX Systems Deployment Console > Systems > System Inventory.

The Systems Inventory page appears.

2. To release the license, select the check box next to the IP address of the machine and select the Delete Selected item(s) option from the drop-down list.

Used seats count decreases by one on deleting any machine from the System Inventory tab.

Using VNC to Control NodesVirtual Network Computing (VNC) is a graphical (GUI) desktop sharing system that is used to remotely control another computer. You can use VNC from:

• The Administrator Console to access the Windows Deployment and Recovery Console.

• The Linux Deployment and Recovery Console for performing tasks such as capturing and deploying images, deploying Scripted Installations, recovering the system, and so on.

Product Displays the name of the licensed product.

Version Displays the current version of the licensed product.

Status Displays whether the License Key is Valid, or Expired or Invalid.

Expires Displays the expiry date of the product. If the license key does not have an expiration date, the value displayed in this field is Never.

Modules Displays the KBOX Systems Deployment Appliance module, which provides a complete set of features available on the KBOX 2000.

Seats Displays the maximum number of licenses available. This number is equivalent to the maximum number of machines that can boot from KBOX 2000 server at any given time.

Used Seats Displays the number of used licenses. This number is equal to the number of machines that boot from the KBOX 2000 server.



Accessing the target machine using VNC

1. Boot the Target Machine to the Windows Deployment and Recovery Console or Linux Deployment and Recovery Console. For more information on how to set up boot actions, refer to Setting Boot Actions, for more information.

2. Browse to the KBOX Systems Deployment Console > Systems > Boot Actions.

The Boot Actions page appears.

Note: VNC can be accessed from Network Scan Inventory page also. Select Systems > Network Inventory. The Network Scan Inventory page appears.

3. Click the first Action Icon next to the IP address of the Target Machine. This launches JavaVNC, and will allow you to view the Windows Deployment and Recovery Console or Linux Deployment and Recovery Console remotely using your Web browser.

Adding and Managing Admin UsersThe KBOX 2000 supports two user roles: admin and read-only admin. All KBOX 2000 actions are performed as administrator. The read-only admin role can view all KBOX 2000 settings and features but cannot change any of them. Ignore references to the user role.

Managing users on your KBOX 2000 includes adding, deleting, and applying labels to admin users.

Adding admin users

Only the username, full name, email, and password fields are required when you add an admin user, but KACE recommends that you fill in the form completely. Do not leave the new user’s password field blank or empty.

To add an admin user:



2. Click Users. The KBOX Settings: Users page appears.


4. Select Add New Item from the Choose action drop-down list.

The KBOX Settings: Edit User Detail page appears.

5. Enter the user details that are used to authenticate users:

Before you can use VNC from the Administrator Console, the Target Machine must first be booted to the Windows Deployment and Recovery Console or Linux Deployment and Recovery Console. See Setting Boot Actions for more information.

Record Created Displays the date and time when this user was first created. This field is read-only.

Record Last Modi-fied

Displays the date and time when the user details were last modified. This field is read-only.



6. Click Save Changes to save your changes, or click Revert Changes to undo the changes made. The Users page appears.

To delete an admin user:




3. To delete users, do one of the following:

• From the Users List view, select the check box beside the user(s), then select Delete Selected Item(s) from the Choose action drop-down list.

• From the KBOX Settings: Edit User Detail page, click Delete.

4. Click OK to confirm deleting the selected user.

To apply a label to an admin user:



2. Click Users.

The KBOX Settings: Users page appears.

3. Select the check box beside the user(s) you want to apply a label to.

User Name Enter the name the user should use to log in to the User Portal. This is a required field.

Full Name Enter the user’s full name. This is a mandatory field.

Email Enter the user’s email address. This is the address to which Help Desk messages, if enabled, are sent to. This is a mandatory field.

Domain An active directory domain. This is an optional field.

Budget Code The financial department code. This is an optional field.

Location The name of a site or building. This is an optional field.

Password Enter a password for the new user. Do not leave this field blank or empty. Though a new user is created, the user rights cannot be activated without a valid password. This is a mandatory field.

Confirm Password Retype the password.

Permissions Specify the logon permissions for the user:

• Admin - This user can log on and access all the features of the administrator console.

• ReadOnly Admin - This user can log on to the administrator console, but cannot modify any settings.

• User - Ignore this role.



4. Select and apply the appropriate label from the Choose action drop-down list.

5.

6.

7.

8.

9.

10.

To remove a label from an admin user:




3. Select the check box beside the user(s) you want to remove the label from.

4. Select the appropriate label under Remove Label from the Choose action drop-down list.

Managing user authenticationYou can configure the KBOX 2000 for local authentication, or External LDAP Server Authentication. The KBOX 2000 can then access a directory service (such as LDAP) for user authentication. This allows users to log into the KBOX 2000 Systems Deployment Console using their domain user name and password. This eliminates the need to add users individually from the Users link on the Control Panel tab.

Supply the appropriate credentials if the external server requires credentials for administrative login (Non-anonymous login).

An anonymous bind will be attempted if no LDAP user name is specified. The configured LDAP user should have at least READ access to the “search base” area.

Ensure that the LDAP server is accessible from the KBOX 2000 and that the server access settings are correct.

To authenticate an admin user:





2. Click User Authentication.

The KBOX Settings: Authentication page appears.


4. Select the appropriate option as described in the following table:

5. Click to modify the server definition, to remove a server or to change its order in the drop-down list.

You can have more than one LDAP Server/Active Directory configured.

6. Click Add New Server to add a new LDAP Server.

7. Click on to specify the following information:

KBOX (local) Authentication

Select this option to enable local authentication. If local authentication is enabled, the password is authenticated against the entry in the local database. This is the enabled by default.

External LDAP Server Authentication

Select this option to enable external user authentication. External authentication can be used against an LDAP server or Active Directory server. If External LDAP Server Authentication is enabled, the password is authenticated against the External LDAP Server. Contact KACE customer support if you need assistance with this process.

All servers must have a valid IP address entered in the Server Host Name field, or the KBOX 2000 waits to timeout on an invalid IP address, resulting into login delays when using LDAP Authentication.

Server Friendly Name Enter a name for the server.

Server Hostname (or IP) Enter IP or Host Name of the LDAP Server.

LDAP Port Number Enter the LDAP Port number which could be either 389 / 636 (LDAPS).

Search Base DN Enter the Search Base DN.For example:OU=sales, DC=kace or DC=com

Search Filter Enter the Search Filter.For example: (samaccountname=KBOX_USER)

LDAP Login Enter the LDAP login.For example:CN=Administrator, CN=Users, DC=kace or DC=com

LDAP Password (if required) Enter the password for the LDAP login.

User Permissions Enter the following user’s permissions from the drop-down list:

• Admin—This user can log on to and access all features of the administrator user interface.

• ReadOnly Admin—This user can log on, but cannot modify any settings in the administrator user interface.

• User—This user can log in only as a user with read access.



8. You can test the settings, by entering a Test User Password and then clicking on Test LDAP Settings.


Configuring Single Sign-On for UsersThe Single Sign-On feature (KBOX 2000 Linking and Manage Linked KBOX Appliances) enables users to authenticate once and gain access to multiple KBOX 2000 Series appliances. The Single Sign-On feature allows users to switch between different KBOX 2000 Series appliances without having to re-login into each appliance individually.

KBOX 2000 Linking allows multiple KBOX 2000 owners to easily switch between their different KBOX 2000 management consoles. To configure KBOX 2000 linking on your network, linking must first be enabled on each appliance, and each appliance must be given a unique name. After KBOX Appliance Linking is enabled, you can manage linked KBOX 2000 Series appliances from the KBOX Linked Appliances list page.

Connecting KBOX 2000 Series appliances with LinkingPerform these steps to link two KBOX 2000 Series appliances, set linking timeout parameters, and establish a linking key:



2. Click KBOX Linking.

The KBOX Settings: KBOX Linking page appears. By default, this page is disabled.


4. Select the Enable KBOX Linking check box to enable the linking.

Once linking is enabled, return to the Control Panel page and select Manage Linked KBOX Appliances to configure remote KBOX 2000 Series appliances.

5. Specify the following:

KBOX Friendly Name (this server)

This value is used by all other KBOX 2000s as a system reference in the user interface.

Remote Login Expira-tion

This value corresponds to the amount of time after the initial login to this server. You can use the Organization fast switching drop-down to switch to a linked KBOX 2000 without providing login credentials. After this time lapse, you will need to provide login credentials when switching to a linked KBOX 2000.

Request Timeout This value corresponds to the amount of time this server will wait for a remote KBOX 2000 to respond to a linking request.

KBOX Linking Key Fin-gerprint

This key will be generated after you click Save Changes.

KBOX Linking Key (this server)

This key will be generated after you click Save Changes. Copy the Linking Key details into the other KBOX 2000 for linking them together.



Disabling KBOX 2000 linkingPerform these steps if you need to sever a link between two KBOX 2000 Series appliances



2. Click KBOX Linking.

The KBOX Settings: KBOX Linking page appears. By default, this page is disabled.


4. Uncheck the Enable KBOX Linking check box to disable linking.


Linking KBOX 2000 Series appliancesClick this link for linking other KBOX 2000 Series appliances to the KBOX 2000 you configured in KBOX Settings & Maintenance > Control Panel > KBOX Linking.



2. Click Manage Linked KBOX Appliances.

The KBOX Settings: KBOX Linked Appliances page appears.

3. Select Add New Item from the Choose action drop down list.

The KBOX Settings: Add Linked Appliance page appears.

4. Enter details for the following fields:


For linking two KBOX 2000 Series appliances, the Linking Key of one KBOX 2000 (for example, KBOX A) must be copied into the other KBOX 2000 (for example, KBOX B).

Similarly, the Linking Key of the “KBOX B” appliance must be copied into the “KBOX A” appliance.

Host Name The name of the KBOX 2000 on which linking is enabled (KBOX A).

Connect using SSL If the remote KBOX 2000 is configured for SSL, ensure that you select this check box.

Key Fingerprint This key will be generated after you click Save Changes.

Linking Key The linking key of the KBOX 2000 on which linking is enabled. The linking details can only be edited here.

Status Messages If the settings are configured correctly, the Connection successful message is displayed after you click Save Changes and Test Connection.



6. Repeat the above steps to add another KBOX 2000 (KBOX B).

7. Login to the previously configured KBOX 2000 (KBOX A) and the copy the linking key. Paste it in the Linking Key field for this KBOX 2000 (KBOX B).

8. Similarly, copy the linking key from the KBOX B appliance and paste it in the Linking Key field of KBOX A.

9. Click Save.

10. Click Test Connection to verify the linking between the two linked KBOX 2000 Series appliances.

11. You will need to re-login into the KBOX 2000 to see the newly updated linked KBOX 2000 Series appliances with the friendly name prefixed in the Organization fast switching drop-down list.

The KBOX Linked Appliances page contains the fields described in the table below:

To delete a link from a KBOX 2000:



2. Click Manage Linked KBOX Appliances.

The KBOX Settings: KBOX Linked Appliances page appears.

3. Select the check box beside the KBOX Link Appliance(s) you want to delete.

4. Select Delete Selected Item(s) from the Choose action drop-down list.

5. Click OK to confirm deletion.

What’s NextNow that your KBOX 2000 is configured, go on to the next chapter Administering Your KBOX 2000 for information on keeping it maintained.

Host Name Indicates the host name.

Status Indicates whether the Host was unavailable or the connection was successful.

Key Fingerprint Displays the key fingerprint associated with the linked KBOX 2000.

You can now browse from one KBOX 2000 to another and then back to the previous KBOX 2000 from the Organization fast switching drop-down list using the Single Sign-On feature. The login credentials should be same for the two KBOX 2000 Series appliances to be able to get linked.


C H A P T E R 5

Administering Your KBOX 2000

This section explains the administration tasks necessary to maintain your KBOX™ 2000 Systems Deployment appliance. You need to perform some of these tasks regularly; the sections below have details.

This chapter assumes that you have already followed the instructions in the Introducing Your KBOX 2000 Systems Deployment Appliance and Configuring Your KBOX 2000 chapters and installed and configured your KBOX 2000.

Using the Control Panel to Administer Your KBOX 2000The KBOX 2000 Settings & Maintenance page has links to most of the KBOX 2000 administration tasks that you will perform, including:

• Activating your KBOX 2000 using your license key, and manage node licenses.

• Uploading and installing KBOX 2000 server updates

• Managing KBOX 2000 backups

To access the Settings & Maintenance page, browse to the KBOX Systems Deployment Console > KBOX Settings & Maintenance > Control Panel. The KBOX Settings: Control Panel page appears, offering you links to the various administration pages available:

Note: Any of the activities listed above can reboot the KBOX 2000. Be cautious when rebooting the KBOX 2000 while it is operationally active.

34


Setting Up Regularly Scheduled Administration TasksThis section explains tasks that you perform on a regular basis to keep your KBOX 2000 performing efficiently, including:

• Updating the KBOX 2000 Server Software• Backing up and transferring KBOX 2000 components with the import/export feature• Analyzing activity from KBOX 2000 logs• Purging unused K-image files• Checking for KPE and KNOPPIX Updates• Checking the KBOX 2000 RAID Disk Status

Updating the KBOX 2000 Server SoftwareMaintaining a KBOX 2000 includes updating the software that runs on the KBOX 2000 server. Software updates are available from the KACE Customer Support Site or by contacting KACE Technical Support directly.

This process also involves verifying that you are using the minimum required version of KBOX 2000, as well as updating the KBOX 2000 license key to reflect the current product functionality.



Verifying the minimum server version

Before applying this update, verify your KBOX 2000 Series appliances server version meets the minimum version requirement.

1. Open a browser and log into your KBOX http://KBOX_name.

2. Click the About KBOX link in the lower left-hand corner of the screen.

Automatically updating the KBOX 2000 server

You can automatically update KBOX 2000 server from KBOX Settings & Maintenance > Server Maintenance page.

1. Browse to the KBOX Systems Deployment Console > KBOX Settings & Maintenance > Server Maintenance.

The KBOX Settings: Server Maintenance page appears.

2. Following details are displayed under the Automatic KBOX Update area:

Applying software updates will cause the KBOX 2000 to reboot. Be cautious when rebooting the KBOX 2000 while it is operationally active.

Update Status Displays the KBOX 2000 server status. You are notified of a new server version, if available here. This is a read-only field.

Last Check Displays the date and time when the last check was performed. This is a read-only field.

Current Version Displays the current server version. This is a read-only field.

Available Version

This field is displayed only when a new server version is available. It displays the new server version. This is a read-only field. Click Release Notes to open release notes for this update in .pdf format.

Server version level




4. Click Check for Server Updates to search for any new update.

5. Click Apply Update to update your KBOX 2000 server to the new server version available.

Manually updating the KBOX 2000 server

Perform these steps to update the KBOX 2000 server manually from Manually Update KBOX area on KBOX Settings & Maintenance > Server Maintenance page.




3. Under the Manually Update KBOX area, click Browse to select the update file.

4. Select the update file provided by KACE and click Open.

5. Click Update KBOX to update the KBOX 2000 server.

Updating your RSA softwareIf you use the KBOX 2000 Remote Site Appliance (RSA) feature to use remote shares to distribute software components, you need to update the RSA installers each time you update the KBOX 2000 server. For details see the Updating RSA server software section.

Backing up and transferring KBOX 2000 components with the import/export featureUsing the KBOX 2000 import/export feature you can package KBOX 2000 software components and back up (export) those packages to a simple share on the KBOX 2000. The export process is a manual one that you do as needed. Once KBOX 2000 components are exported, you use the off-board package transfer feature to copy the share directory contents to a remote location that you pick. You can do off-board package transfer manually as needed, or schedule the process to take place automatically.

If the exported packages are stored in a local location, you can import them back into your KBOX 2000 if the originals become corrupted or otherwise unusable. You can also populate other KBOX 2000 Series appliances with the packages by importing them into any other KBOX 2000 linked to the original.

If you use the off-board package transfer feature to store export packages on a remote site (usually an FTP site), other KBOX 2000 Series appliances can import and use those same components.

You can import/export these KBOX 2000 components as packages:

• Database Backup (Export Only)

• Scripted Installation

• Boot Environment

Available Version and Apply Update is displayed only if, a new server version is available.



• Linux-Based System Images

• K-images

• Pre-installation Tasks

• Post-installation Tasks

• User States

The KBOX 2000 creates a .pkg and an associated .xml file for each component that you package. The two files have the same root filename and must be stored in the same location (\\KBOX_name\Restore by default). The .xml file contains metadata for the .pkg file.

Understanding the import/export copying rules

Boot environment, Scripted Installation, and K-Image packages are created with their associated source CDs, and pre- and post-installation tasks. You can also package the pre- and post- installation tasks separately. On import of a Scripted Installation or K-Image package, the KBOX 2000 checks the associated source CD and pre- and post-installation tasks for already-stored duplicates using characteristics such as name, type, application, size, and .bat script. If a package is the same as an already-stored package, a duplicate copy will not be imported. Instead, the KBOX 2000 associates the already-stored package to the Scripted Installation or K-Image being imported.

You can copy and paste the package files into the \\KBOX_name\Restore directory of any other KBOX 2000 that you need to. However, be sure to keep the .pkg and .xml files together.

To export packages:

1. Browse to the KBOX Systems Deployment Console > KBOX Settings & Maintenance > Export page.

The KBOX Settings: Package Export/Import page appears, showing you the list of software components available for export.



2. Under Export KBOX Packages (most of the way down the page), click the [Edit Mode] link to make this section editable.

3. Click the checkboxes for the components to export.

4. Click Export Selected Items.

The items you selected are converted to packages and store in the \\KBOX_name\Restore folder.

To import packages into a KBOX 2000:

You can import packages stored in a KBOX 2000 \\KBOX_name\Restore folder.

1. Browse to the KBOX Systems Deployment Console > KBOX Settings & Maintenance > Export.

The KBOX Settings: Package Export/Import page appears.

2. Under Import KBOX Packages, click the [Edit Mode] link to make this section editable.

3. Click the checkboxes for the components to export.

4. Click Import Selected Items.



The KBOX 2000 adds a copy of the packages you select to the list of packages available on the KBOX Settings: Package Export/Import page. For details on what is an is not copied see the Understanding the import/export copying rules section.

Backing up KBOX 2000 export packages with off-board package transfer

You use the off-board package transfer feature (on the KBOX Settings & Maintenance > Export page) to copy all exported packages from KBOX 2000's Restore directory to a remote FTP or secure FTP (SFTP) site. You can create a schedule to do this automatically. The .xml and .pkg files are copied to an FTP location that you specify.

The KBOX 2000 automatically creates a new directory at the FTP site for every transfer. The remote directory naming convention is /FTP_path/data_timestamp. Transfer results are logged in the Schedule Action Server - Output Log.

To configure off-board package transfer:

1. Browse to the KBOX Systems Deployment Console > KBOX Settings & Maintenance > Export page.

The KBOX Settings: Package Export/Import page appears.

2. Under Off-Board Package Transfer, click the [Edit Mode] link to make this section editable.

3. Specify the following information:

4. Click Test to test the configuration. Test results are shown in a text area. You can edit the test results if needed.

5. Click Update Configuration to update the FTP configuration.

Your automatic backup schedule transfers copies of all packages from the \\KBOX_name\restore directory to the FTP site on the day(s) you specified.

The off-board package transfer feature does not automatically remove files from either its local restore directory or the remote FTP site. Delete files manually as needed from the restore share or the target FTP site.

Last Modified (Display only) Shows the date and time when the FTP configura-tion was last modified.

Enable Backup Select the check box to enable backup.

Schedule (Run Every) Select a day and time from the drop-down lists for a schedule run. The automatic package transfer is performed every week on the selected day and time.

Backup Protocol: Select FTP or Secure FTP (SFTP) from the drop-down list.

FTP Backup Site Enter the FTP backup site.

FTP Path Enter the FTP path.

FTP User Name Enter the FTP user name.

FTP User Password Enter the FTP password.



Confirming that you have 20% free disk spacePeriodically browse to the KBOX 2000 System Deployment Console > Home tab and confirm that the Disk Usage chart shows about 20% free disk space. This is not a hard and fast percentage. About 20% free disk space provides optimal performance of your KBOX 2000 and allows you to stage or restore backup files as required.

Analyzing activity from KBOX 2000 logsThe KBOX 2000 maintains the logs listed below. They are useful for analyzing KBOX 2000 activities:

System System Messages Displays miscellaneous information about the server's operation and execution.

Outgoing Mail Log Displays information about the informational email messages that the KBOX 2000 has sent.

Web Server Access Log Displays HTTP Server access information.

Error Log Displays HTTP Server error information.

KBOX Server Output Log Displays miscellaneous information about KBOX 2000 Server operation and execution.

Error Log Displays errors or server warnings regarding KBOX 2000 onboard server processes.



To view KBOX 2000 logs:

1. Browse to the KBOX Systems Deployment Console > KBOX Settings & Maintenance > Logs.

The KBOX Settings: Logs page appears.

2. Click the linked log name to view that log. You can easily cut and paste log content out of the log if you need to save it, print it, or send it to KACE Support.

To download KBOX 2000 logs:

1. Browse to the KBOX Systems Deployment Console > KBOX Settings & Maintenance > Logs.

The KBOX Settings: Logs page appears.

2. Click Download Logs to open or save a zip file that contain all of the current logs.

Purging unused K-image filesPurging unused K-Image files from the hash store is a good way to recover some disk space.




Click Purge. The KBOX 2000 deletes all unused K-image files from hash store.

Checking for KPE and KNOPPIX UpdatesKACE usually only updates KPE and KNOPPIX software at major releases. However occasionally a bug fix causes an out-of-cycle update, so KACE recommends that you check for KPE and KNOPPIX updates once a month.

Privileged Action Server

Output Log Displays miscellaneous information about the application's operation and execution.


Scheduled Action Server

Output Log Displays miscellaneous information about Scheduled Action Server operation and execution.


Network Driver Server

Output Log Displays messages from the process that handles network drivers for Scripted Installations.

Error Log Displays errors or server warnings for the process that handles network drivers for Scripted Installations.

File Servers TFTP Transfer Log Displays TFTP Server access information.

NETBIOS Name Server

Displays miscellaneous Windows File Server information.

Windows File Server

Displays Windows File Server access information.



To check for Windows Deployment and Recovery Console (KPE) updates:




3. Click Check for KPE Updates under the KBOX 2000 Pre-installation Environment (KPE) Updates area to check for updates. If updates exist, they are downloaded by the KBOX 2000. The Update Status will be “Downloading Updates” while the updates are being downloaded. When the download is complete, the updates will be applied to the Imaging and Recovery Consoles.

To check for Windows x64 Deployment and Recovery Console (KPE) updates:




3. Click Check for KPE x64 Updates under the KBOX 2000 Pre-installation Environment x64 (KPE x64) Updates area to check for updates. If updates exist, they are downloaded by the KBOX 2000. The Update Status will be “Downloading Updates” while the updates are being downloaded. When the download is complete, the updates will be applied to the Imaging and Recovery Consoles.

To Check for KNOPPIX updates:




3. Click Check for KNOPPIX Updates under the KBOX KNOPPIX Updates area to check for updates. If updates exist, they are downloaded by the KBOX 2000. The Update Status will be “Downloading Updates” while the updates are being downloaded. When the download is complete, the updates will be applied to the Imaging and Recovery Consoles.

Checking the KBOX 2000 RAID Disk StatusThis section explains the RAID database protection that the KBOX 2000 provides, and shows you how to confirm that the RAID disks are functioning correctly. You normally do not need to check the RAID status. The KBOX 2000 administrator automatically receives an email message indicating that a disk has failed and explains that you need to call KACE Customer Support immediately. Checking the RAID status just confirms this. But if you experience a sudden unexplained drop in system performance this is one thing you can check.

Your KBOX 2000 uses these RAID levels to protect your data:

• KBOX 2100 Systems Deployment appliance - RAID level 1.

• KBOX 2200 Systems Deployment appliance - RAID level 5.

Your KBOX 2000 checks the RAID disk array status every few minutes.

To check the current RAID status for a KBOX 2000:



1. Browse to KBOX Systems Deployment Console > Settings and Maintenance > RAID.

The KBOX Settings : RAID page appears showing the latest RAID status. This is the KBOX 2100 Systems Deployment appliance level 1 version:

2. Click the Refresh RAID Status button to get an up-to-date RAID status. This should take less than a minute.

You now have an updated status for your KBOX 2200 Systems Deployment appliance. If the Status value is not ONLINE, contact KACE Customer Support immediately at this URL: www.kace.com/support.

Performing General Administration TasksThis section explains administration tasks that you will perform as needed, including:

• Rebooting a KBOX 2000• Powering Off a KBOX 2000



Rebooting a KBOX 2000You reboot a KBOX 2000 from the Server Maintenance page.



2. Click [Edit Mode] link to make this page editable. Make sure that no KBOX 2000 activities are in progress.

3. Click Reboot. Refresh your browser page to return to the KBOX 2000 System Deployment Console.

Powering Off a KBOX 20001. Browse to the KBOX Systems Deployment Console > KBOX Settings & Maintenance > Server

Maintenance.


2. Click [Edit Mode] link to make this page editable. Make sure that no KBOX 2000 activities are in progress.

Click Power Off. The KBOX 2000 power off notice appears.

Do not reboot a KBOX 2000 if it is operationally active.

Be cautious when powering off the KBOX 2000 while it is operationally active.


C H A P T E R 6

Scanning for Nodes and Managing Systems Inventory

This section explains how to use the KBOX 2000 Systems Module to probe for, capture, and store details about the nodes on you LAN. Your KBOX 2000 requires this information in order perform administration tasks, such as deploying system images to those nodes or remotely repairing them.

About KBOX 2000 System DiscoveryYou use these KBOX Systems Deployment Console > Systems tabs to search for or store information about the systems on your LAN:

• System Inventory - Stores information captured when nodes booted into KPE. The nodes on this page are considered “managed” and count against your KBOX 2000 license. For details see Managing System Inventory.

• Network Inventory - Stores information about nodes captured as the result of a network scan, or captured when the system booted to the Boot Manager menu. For details, see Managing Network Inventory.

• Network Scan - Stored the network scans that you use to capture information about individual systems on your LAN. For details, see Creating and Managing Network Scans.

Note that a system that booted into KPE appears in both the System Inventory and Network Inventory lists.

The Network Scan uses the Address Resolution Protocol for system discovery. This is important for two reasons:

1. The KBOX 2000 cannot administer systems over a router connection, and

2. All systems that the KBOX 2000 administers must have MAC addresses.

46


Once you have collected information about your nodes on your KBOX 2000, organize them into logical groups using labels for easier and faster administration. For more information see the To apply or remove a label:.

Figure 6-1: Systems Module

Creating and Managing Network ScansIn order to use the KBOX 2000 to administer the systems on your LAN, you must first collect details about those systems, including communication information and settings. You gather this information using network scans.

You scan for systems on your LAN using a range of IP addresses, or by specifying specific TCP or UDP ports. The KBOX 2000 then probes for and gathers information about the systems with those IP addresses, or those that are listening on the specified ports.

The KBOX 2000 stores an inventory of network scans so you save and reuse them. Most KBOX 2000 users use the scan scheduling feature to run their scans periodically. That way, the KBOX 2000 automatically captures information about any new systems (and some devices) you add. You can always run the network scans manually as needed.

To create a new network scan:

1. Browse to the Systems Deployment Console > Systems > Network Scans.

The Network Scans page appears.



2. Select Choose Action... Add New Item from the drop-down list.

The Network Scan Detail page appears.

3. Enter a name for the scan in the Name field.

4. Enter the IP range to scan in the IP Range field.

5. Select the Enable Ping Test check box.

The Ping test determines if the system is up and running.

6. Specify the time out interval (in seconds) in the Ping Timeout field.

7. Specify Port scan test details:

8. Specify the DNS lookup test details:

9. (Optional) Specify a scan schedule:

a Select the Enable Scheduled Run check box.

b Select a specific day at HH:MM AM/PM to run scan on specified day at the specified time.

10. Click Save.

The new network scan that you added appears in the Network Scans list.

11. After clicking Save, the following additional details appear on Network Scan Detail page.

To run a network scan:

1. Browse to the Systems Deployment Console > Systems > Network Scans.

The Network Scans page appears. You can run a network scan from either the Network Scans list page or the Network Scan Detail page.

2. In the Network Scans list page, click the name of the network scan you want to run. The Network Scan Detail page appears. Review and modify the details, if required. Click Save and Run Now to run the network scan immediately.

3. (Optional) In the Network Scan Detail page, select the check box beside the network scan(s) you want to run. Select Run Scan(s) Now from the Choose action drop-down list to run network scan on selected network scan names.

Enable Port Test Select the check box to enable port scanning of device ports.

Port Timeout Enter the time out interval (in seconds).

TCP Port Configuration Enter a comma-separated list of TCP ports to scan.

UDP Port Configuration Enter a comma-separated list of UDP ports to scan.

Enable DNS Lookup If selected, live addresses will be checked against the DNS server to see if they have a name associated with them. This can help you identify known nodes on your network.

DNS Lookup Timeout Specify the time out interval (in seconds).

Created (Read only) The date and time the Network Scan was created.

Modified (Read only) Displays the date and time the Network Scan was last modified.

Status (Read only) Displays the status of the Network Scan. When you run a network scan, this field also displays the scan progress.



To delete a network scan:

1. To delete a network scan do one of the following:

• From the Network Scans page, select the check box beside the network scan(s), then select Delete Selected Item(s) from the Choose action drop-down list.

• From the Network Scan Detail page, click Delete.

2. Click OK to confirm deleting the selected network scan.

Managing System InventoryThe System Inventory sub-tab lists of all the nodes that have boot into KPE, or have been discovered from a network scan. The nodes are listed in numerical order by their IP address. For more information on uploading Hardware Inventory, see the Windows Deployment And Recovery Console (KPE) section.

The information returned for these nodes includes IP addresses, hardware and software titles, hardware specifications, ping status, PXE installation status, and other details.

To manage system inventory:

1. Browse to the KBOX Systems Deployment Console > Systems > System Inventory.

The System Inventory page appears.

2. Select the IP address of a node.

The System Detail page appears. This page shows data the KBOX 2000 has collected from the network scan and the hardware inventory actions.

3. Enter or review the following information:

IP Address (Read only) The IP address of the node.

MAC Address (Read only) The unique MAC address of the node in hexadecimal format: xx:xx:xx:xx:xx:xx.

Platform (Read only) The type of node. For example Mac or Windows.

Hostname Enter the host name of the node. Click Save to update this value in the DNS Lookup field.

Created (Read only) The date and time when this record was created.

Modified (Read only) The date and time when this record was last modified.

Set Boot Actions for this System

See Setting Boot Actions.

Ping Status (Read only) The ping status. For example, Failed.

PXE Status (Read only) The PXE Status. The PXE Status indicates whether this node (iden-tified by the MAC Address) has ever requested a network boot from the KBOX 2000.

TCP Port Status (Read only) The TCP Port Status. For example, A TCP Port state of “open” indi-cates that the KBOX 2000 was able to open a connection to a network server running on the node.



4. Scroll down to view the hardware inventory.

5. Click Set Boot Action(s) to set boot actions for this system. For more information on how to setup boot actions, refer to Setting Boot Actions.

6. Select an operating system from the Select Operating System drop-down list and click Show compatibility. This refreshes the table below. This table actually lists all the plug and play devices and checks their driver compatibility with the target operating system. By default, the compatibility is

displayed for Windows XP Professional SP2 Edition. A icon means the device is supported by the

target operating system. While the icon denotes that device is incompatible with the target operating system.

The following table lists the OS versions used to generate the driver data:

To send Wake-on-LAN:

1. Select Systems > System Inventory.

The System Inventory page appears.

2. Select the IP address of the node you want to send a Wake-on-LAN action.

3. Select Send Wake-on-LAN from the Choose Action drop-down list.

To delete a machine from the System Inventory:

1. To delete a machine from the System Inventory do one of the following:

• From the System Inventory page, select the check box beside the IP address(es), then select Delete Selected Item(s) from the Choose action drop-down list.

UDP Port Status (Read only) The UDP Port Status. For example, A UDP Port state of “open/fil-tered” indicates that the KBOX 2000 did not receive a “port closed” message from the client and was unable to determine the status. Note: Most firewall software do not send these “port closed” messages to cli-ents sending data, so results may appear incorrect when performing UDP port scans.

Operating Systems Version actually used to generate driver data

Windows 2000 Windows 2000 Professional SP4

Windows Server 2003 x64 Edition Windows Server 2003 x64 Edition

Windows Server 2003 Windows Server 2003 Enterprise Edition SP1

Windows XP x64 Edition Windows XP x64 Edition

Windows XP Windows XP Professional SP2

Windows Vista Windows Vista Ultimate Edition

Windows Vista x64 Edition Windows Vista x64 Edition

Windows Server 2008 (32-bit) Windows Server 2008 x86

Windows Server 2008 (64-bit) Windows Server 2008 x64

Windows 7 x86 Windows 7 x86

Windows 7 x64 Windows 7 x64



• From the System Detail page, click Delete.

2. Click OK to confirm deleting the selected IP address.

To apply or remove a label:

1. Select Systems > System Inventory. The System Inventory page appears.

2. Select the IP address of the machine you want to apply or remove a label.

3. To apply a label, select the label you want to apply from the Choose Action drop-down list.

4. To remove a label, select the label you want to remove from the Choose Action drop-down list.

Managing Network InventoryThe Network Inventory includes nodes and other devices that were discovered in a network scan, or that have uploaded software to your KBOX 2000.

The information returned for these nodes includes IP addresses, hardware and software titles, hardware specifications, ping status, PXE installation status, and other details.

To manage network inventory:

1. Browse to the Systems Deployment Console > Systems > Network Inventory.

The Network Scan Inventory page appears.

2. Select the IP address of the machine.

The Network Node Detail page appears. This page shows data the KBOX has collected by network scan or by management of a node.

3. Enter or review the following information:

IP Address (Read only) The IP address of the machine.

MAC Address

(Read only) The unique MAC address of the Target Machine in hexadecimal format: xx:xx:xx:xx:xx:xx.

Host Name Enter the host name of the Target Machine. Click Save to update the value in the DNS Lookup field.

Created (Read only) The date and time when this record was created.

Modified (Read only) The date and time when this record was last modified.

Ping Status (Read only) The ping status. For example, Failed.

PXE Status (Read only) The PXE Status. The PXE Status indicates whether this node (identified by the MAC Address) has ever requested a network boot from the KBOX.

TCP Port Status

(Read only) The TCP Port Status. For example, A TCP Port state of “open” indicates that the KBOX was able to open a connection to a network server running on the node.

UDP Port Status

(Read only) The UDP Port Status. For example, A UDP Port state of “open/filtered” indi-cates that the KBOX did not receive a “port closed” message from the client and was unable to determine the status. Note: Most firewall software does not send these “port closed” messages to clients sending data, so results may appear incorrect when performing UDP port scans.



4. Click Set Boot Action(s) to set boot actions for this system. For more information on how to setup boot actions, see Setting Boot Actions.

To send Wake-on-LAN:

1. Browse to the KBOX Systems Deployment Console > Systems > Network Inventory or Systems > Network Inventory.

2. Select the IP address of the machine you want to send Wake-on-LAN.

3. Select Send Wake-on-LAN from the Choose Action drop-down list.

To delete a machine from the Network Inventory:

1. To delete a machine from the Network Inventory do one of the following:

• From the Network Scan Inventory page, select the check box beside the IP address(es), then select Delete Selected Item(s) from the Choose action drop-down list.

• From the Network Node Detail page, click Delete.

2. Click OK to confirm deleting the selected IP address.


1. Select Systems > Network Inventory. The Network Scan Inventory page appears.

2. Select the IP address of the machine you want to apply or remove a label.

3. To apply a label, select the label you want to apply from the Choose Action drop-down list.

4. To remove a label, select the label you want to remove from the Choose Action drop-down list.


C H A P T E R 7

Capturing Operating System Im-ages

This section explains how to gathering operating system images, store them on your KBOX 2000, and deploy them to your nodes as needed. You import OS images into the KBOX 2000 so you can then deploy them to your nodes as part of a Scripted Installation, System Image, or boot environment.

Importing Windows OS images from a CD/DVDYou have two options for copying CD/DVD images to your KBOX 2000 software library. You will probably want to upload a CD/DVD image from the system that controls your KBOX 2000 (technically a networked drive). However, if your KBOX 2000 is physically close to where you work, you can always use its CD drive to capture the operating system image. For details, see the Capturing a Windows OS image from a networked CD/DVD drive and Capturing a Windows OS image from the KBOX CD/DVD sections.

Most of the information in this section pertains to Windows operating system images. For details on capturing Mac OS images see Capturing and Deploying Mac OS Disk Images.

Capturing a Windows OS image from a networked CD/DVD driveFollow these steps to copy a CD/DVD image from a local CD/DVD drive to your KBOX 2000 software library, instead of using the KBOX 2000 CD drive:

• Download and extract the Desktop CD uploader utility to remote machine.

• Configure the Desktop CD uploader utility to upload the contents of a CD.

Types of CDs that can be uploaded

The following table lists the types of CDs and the corresponding Operating Systems, they can be uploaded for:

Scripted Installation

53

Capturing Operating System Images

To download and extract desktop source CD uploader utility to remote machine:

1. Browse to the KBOX Systems Deployment Console > Library > Source CDs.

The Source CDs page appears.

2. Select Download Desktop CD Uploader from the Choose action drop-down list. The Desktop Source CD Uploader page appears.

3. Click Download. Depending on your Operating System, click Download for Windows or Download for Mac OS X Leopard.

4. Click Save and save this utility on the local drive of a remote machine.

Extract the kcduploader installer to a specified path.

To upload a CD image using the GUI version of kcduploader

1. Download the utility to a remote system. See To download and extract desktop source CD uploader utility to remote machine: for details.

win2000 Windows 2000

winxp Windows XP

winxpx64 Windows XP 64

win2003 Windows Server 2003

win2003x64 Windows Server 2003 x64

winvista Windows Vista

winvistax64 Windows Vista x64

win2008 Windows Server 2008 (x86)

win2008x64 Windows Server 2008 (x64)

win7 Windows 7 (x86)

win7x64 Windows 7 (x64)

KBOX 2000 Deployment and Recovery Environment CDs

kpe KPE

kpex64 KPE x64

kboxi KBOX 2000 Imaging (KNOPPIX)

kboxr KBOX 2000 Recovery (KNOPPIX)

osxnetboot Mac OX X NetBoot Image (Recovery)

KBOX 2000 Deployment and Recovery Environment CDs

knoppix KNOPPIX (Recovery)

winpe2004 WinPE 2004 (Recovery)

winpe2005 WinPE 2005 (Recovery)

winpe2005x64 WinPE 2005 x64 (Recovery)



2. From the remote system, open the Start menu and select the KBOX 2000 Source CD Uploader.

The CD uploader window appears:

3. Enter:

• The hostname or IP address of the KBOX to store the CD image on.

• A name for the CD image

• Select a a Source CD type (OS or boot environment) from the drop-down list.

• The path to the CD.

4. Select the Start Upload button.

The CD image starts uploading to the KBOX. For details on the progress, see To view the uploading status of the CD:.

To upload a CD image using command-line version of kcduploader utility:

1. Insert the CD containing the installers of Operating Systems in the CD-ROM of the remote machine. Verify that you can browse the contents of the CD through Windows Explorer.

2. Open:

• (Windows) A Command Prompt.

• (MacOS) A Terminal Window.

3. Change to the directory in which kcduploader installer is saved.

4. Use the uploader utility to upload the image. This is the syntax; all parameters are required:

kcduploader.exe -h hostname -n "CD_image_name" -t CD_type -p CD_location

Where:

• hostname is the hostname or IP address of your KBOX 2000 server. This name must be unique to your KBOX 2000.

• CD_image_name is a CD image name to use.

• CD_type is the type of CD being uploaded. Refer to, “Types of CDs that can be uploaded,” on page 53.

• CD_location is the location of CD on your local system. On Windows, specify the drive letter that the disc is mounted on. On Macintosh OS X, the disc is mounted inside the /Volumes directory.

Command-line examples:



Windows:

kcduploader.exe -h ikbox -n "Windows XP Professional" -t winxp -p D:

MacOS:

./kcduploader -h ikbox -n "Windows XP Professional" -t winxp -p /Volumes/WXPFPP_EN

To view the uploading status of the CD:

1. Browse to the KBOX Systems Deployment Console > Library tab.

The Library Overview page appears.

2. Click View all Source CDs.

3. Click on the name of the source CD. The Source CD’s page appears.

The upload status is displayed in the status field.

4. After a successful upload to the KBOX 2000, the status of upload is displayed as Completed.

Capturing a Windows OS image from the KBOX CD/DVDScripted installations download software images from your KBOX 2000 software library to your nodes. This section explains how to copy a CD or DVD image to the software libary.

A KNOPPIX Recovery Console is bundled with the KBOX 2000. You can also download your own KNOPPIX Recovery Console, KNOPPIX Imaging Console, or Windows Pre-installation Source CD image from the KBOX 2000.

You can also use a customized KNOPPIX build by loading your pre-installation environment and defining a Scripted Installation to use it. It then becomes an option on the Administrator Console and Client Boot Menus.

Windows platforms supported for KBOX 2000

The following Windows platforms are supported for KBOX 2000:

• Microsoft Windows 7 (64-bit)


• Microsoft Windows Server 2008 (64-bit)


• Microsoft Windows XP x64 Edition (64-bit)

• Microsoft Windows XP (32-bit)

• Microsoft Windows Vista x64 Edition (64-bit)

• Microsoft Windows Vista (32-bit)

An error is returned if the CD name already exists on the KBOX 2000, or if an empty name is specified. Use a unique name for every upload.



• Microsoft Windows Server 2003 Server x64 Edition (64-bit)



To import an OS image to the KBOX 2000 from a CD/DVD:


The Source CDs page appears.

2. Select Add New Item from the Choose action drop-down list. The Import a Source CD page appears.


4. Click Next.

5. Place the CD/DVD in the KBOX 2000 CD-ROM drive.

6. Click Next.

The CD/DVD image is copied onto your KBOX 2000. The Import Status line reads “Completed” when the import completes.

7. Click Next.

The KBOX 2000 displays the amount of data copied from the CD/DVD.

• If the image is much smaller than expected, click Cancel to delete the CD/DVD from the library, and try again.

• Otherwise, click Next.

8. Repeat with the other CDs/DVDs you want to store.

Viewing Software Library item details1. Browse to the KBOX Systems Deployment Console > Library > Source CDs. The Source CDs page

appears.

2. Click on a Source CD to view the details about that CD.

Deleting a Software Library item1. Browse to the KBOX Systems Deployment Console > Library > Source CDs. The Source CDs page

appears.

2. Check the Source CD or CDs you want to delete.


4. Click OK to delete the Source CD.

Source CD Name Enter a name for the CD/DVD image.

Operating System Select an operating system from the drop-down list. For a list of the supported Windows platforms, see the Windows platforms supported for KBOX 2000 section.



Capturing and Deploying Mac OS Disk ImagesYou boot a Mac OS node from the KBOX 2000 NetBoot server to:

• Capture the node’s disk image to store and administer using the KBOX software library.

• Deploy a new disk image to the node to replace an old, incorrect, or corrupted version.

Before performing either of these tasks, you need to first follow the instructions in the Configuring the KBOX 2000 NetBoot Server section. Once the NetBoot server is configured, follow the instructions in either the Capturing a Mac OS disk image or Deploying a new Mac OS disk image from the KBOX 2000 section depending on your requirements.

Configuring the KBOX 2000 NetBoot ServerFollow these steps to make your Mac OS node to boot to the KBOX 2000 NetBoot server:

1. Configure the KBOX 2000 NetBoot Server.

2. Create a boot environment and upload it to your KBOX 2000.

3. (Optional) Add boot actions to the image.

4. Select a default boot environment.

Configure the KBOX 2000 NetBoot Server

See the Step 5 - (MAC OS Only) Configuring the NetBoot Server section for details.

Create a boot environment and upload it to your KBOX 2000

You need to create at least one boot environment for your Mac OS to load so that it can boot from your KBOX 2000. Complete these steps to create a Mac OS boot environment:


2. Select Choose Action... Download CD Desktop Uploader from the drop-down list.

3. Select Download for Mac OS X or Download for Mac OS X (CLI) depending on whether you want to use desktop or command-line interface.

4. Follow the instructions on the Download CD Desktop Uploader page to capture a boot image and upload it to the KBOX 2000.

Mac OS 10.5 and 10.6 are the only releases currently supported for booting a Mac OS node to the KBOX 2000 NetBoot server.

Scripted installations are not currently supported for Mac OS nodes.



Now that you have created a boot environment to use as the default, you will probably want to follow the instructions in the next section to add boot actions to it.

(Optional) Add boot actions to the image

The boot actions available for Mac OS boot images are the same as for Windows boot images.

1. Browse to the KBOX Systems Deployment Console > Deployments > Boot Environments page.

The Boot Environments page appears.

2. Select a Mac OS Boot Environment from the list.

The Boot Environment Detail page appears.

3. Click the Setup a System to load this Boot Environments link.

The Boot Action Setup page appears.

4. Select systems from the Systems: drop-down list.

5. Select the First Boot Action:

6. (Optional) Select the Next Boot Action:

7. Click the Next button.

The boot actions are now saved. The next time the node boots it performs the boot actions you specified.

Select a default boot environment

If you only have one boot environment, it is used as the default and you can skip this section. If you have more than one boot environments, complete these steps to boot your nodes from the default:

1. Browse to the KBOX Systems Deployment Console > KBOX Settings and Maintenance > General Settings > Control Panel page.

The KBOX Settings: General page appears.

2. Click [edit mode] at the bottom of the page.

3. Select Default KBOX Deployment and Recovery Environments from the Mac OS X Intel (Netboot) and or Mac OS X PowerPC (Netboot) drop-down lists.

4. Click the Save Changes button.

Start the KBOX 2000 Imaging UtilityPerform these steps to bring up the KBOX 2000 Imaging Utility once you have booted a Mac OS node from the KBOX 2000 NetBoot server:

1. Follow the instructions in the Configuring the KBOX 2000 NetBoot Server section to set up the KBOX 2000 NetBoot server. Be sure to keep the password you add in this step handy.

The boot environment you create requires a password. Record this password where you can retrieve it, because you need it to boot the Mac OS node boots into this environment.



2. Boot the Mac OS node to the KBOX 2000.

There are two ways to boot a Mac OX node over the network using a boot image on your KBOX 2000:

• Using the Node’s System Preferences > Startup Disk menu to select the KBOX 2000 NetBoot server. Remember to undo this change after the disk image is deployed. Otherwise, the node boots to the KBOX 2000 every time.

• Configuring the KBOX 2000 NetBoot server, and then physically going to the node and rebooting the system while holding the “N” key.

3. Enter the password when prompted. The system them finishes booting to the default KBOX 2000 NetBoot image.

4. Once the Mac OS desktop loads, select the Imaging Utility icon:

The KBOX 2000 Imaging Utility appears:



Capturing a Mac OS disk imagePerform these steps to capture a Mac OS node’s disk image (or a part thereof) to store, manage, and deploy as needed from the KBOX 2000:

1. Follow the instructions in Start the KBOX 2000 Imaging Utility to bring up the Imaging Utility.

2. Select the Capture Image tab.

3. Enter a name for the new disk image.

4. Select the check boxes for the disk partitions to include in the new image.

5. Click the Start Capture button.

The new disk image is created and automatically uploaded to the KBOX 2000, and is displayed on the Deployments > System Images sub-tab.

Deploying a new Mac OS disk image from the KBOX 2000Perform these steps to deploy a new Mac OS image from those managed on the KBOX 2000:

1. Follow the instructions in Start the KBOX 2000 Imaging Utility to bring up the Imaging Utility.

2. Select the Deploy Image tab. The Deploy Image window appears:



3. Select a disk image to download from the Image Name drop-down list. All of the Mac OS disk images currently on the KBOX 2000 are listed.

4. (Optional) Select the Automatically Reboot After Deployment check box if you want this option.

5. Select the Start Deploy button.

The new disk image is deployed to the Mac OS node. If you select the automatic reboot option, any post-installation tasks take effect immediately. If not, the post-installation tasks take effect the next time the Mac OS node reboots.


C H A P T E R 8

Managing Your Driver Library

This section starts with an introduction to the KBOX 2000 device Driver Library, and then explains how to efficiently add and organize new drivers, including using the Driver Harvesting utility to upload drivers from remote systems. Finally this chapter offers troubleshooting information on how to avoid or solve common driver-related problems.

About the Driver LibraryYou use the Driver Library to store drivers that you will need for Scripted Installations or booting to pre-boot environment (PXE). This section provides an overview of the KBOX 2000 Driver Library, and explains how drivers are organized.

By default your KBOX 2000 supports over 160,000 hardware device IDs, each of which can be used for a driver. Many drivers support more one of these hardware IDs.

You manage drivers from the KBOX Systems Deployment Console > Library > Drivers sub-tab:

Even with all these drivers, you will almost certainly need to add more drivers to your KBOX 2000 to meet your organization’s needs and as you add new hardware.

The KBOX 2000 Driver Library manages drivers that use the .inf and .sys file formats. However, many drivers also depend on files in formats such as .cat, .dll, .din, and others. While the KBOX 2000 cannot parse these other file formats, you can add them to the drivers share to ensure that their drivers function correctly.

63


Planning how and where to store new drivers on your KBOX 2000 is an important step and requires some planning to avoid these common problems:

• Referencing the wrong driver. If the KBOX 2000 finds duplicate drivers, it may use the wrong version.

• Degrading system performance by having too many drivers in the same place (usually the all directory).

Managing Your Driver LibraryManaging drivers on your KBOX 2000 mainly involves keeping them organized by using and expanding upon the default driver directory structure.

The next two sections, Rules for organizing new drivers and Understanding the driver directory structure both explain where to put a new driver in the KBOX 2000, but the explain it from different viewpoints. Rules for organizing new drivers gives you step-by-step rules for adding a new driver. Understanding the driver directory structure lists all of the driver directories and their explains their contents.

Rules for organizing new driversThis section provides rules to follow when adding new drivers to your Driver Library. Remember, you’re trying to avoid duplicate drivers to ensure that the KBOX 2000 finds the correct version. For that reason, do not organize your drivers by computer model, because too many drivers work with multiple systems. To check whether you have duplicate drivers on your KBOX 2000, see the Searching for Drivers in the Driver Library section.

For information on how to add drivers to the Driver Library, see the Adding drivers to the driver library section.

1. If the driver is a RIS driver, put it in the kpe or kpe64 directory or their subdirectories.

RIS drivers that you use for KPE pre-boot images are significantly different from the other drivers that the KBOX 2000 manages, and must be in their own kpe or kpe64 directory. RIS drivers are the exceptions to the “no duplicates” rule. You need to put the RIS version of a driver in the kpe (or kpe64) directory, and the non-RIS version of the driver in to the appropriate windows* directory (see previous section).

2. Drivers for Windows Vista, Windows 7, and Windows 2008 Server must be placed in their corresponding operating system directory. One of these:

The all directory is becoming less useful because the latest operating systems cannot use it.

all was intended as a repository for drivers used by multiple operating systems, and it still serves that purpose for Windows XP, Windows 2000, Windows Server 2003, 2004, 2005, and 2008, Windows PE, and KPE. However, starting with Windows Vista, the latest operating systems cannot share drivers, so the all directory is largely empty now, and will remain so over time.

See the Rules for organizing new drivers and Understanding the driver directory structure sections for details on where to put new drivers.



• windows_vista

• windows_vista_x64

• windows_7_x64

• windows_7_x86

• windows_2008_x86

• windows_2008_x64

These operating systems cannot reference drivers in the all directory.

3. If a driver is used by more than one of these operating systems, put it in the all directory:

• Windows 2000

• Windows XP

• Windows Server 2003

• KPE

Remember that only Windows 2000, XP, 2003 and their 64-bit equivalents use the all directory.

4. If a driver is used by only one of these operating systems, put it in the directory that corresponds to that operating system:

• For Windows 2000 use windows_2000.

• For Windows XP use windows_xp or windows_xp_x64.

• For Windows Server 2003 use windows_2003 or windows_2003_x64.

• For KPE use kpe or kpe64.

Now that you know which directory your new driver goes in, see the Adding drivers to the driver library section for instructions on how to add it to the KBOX 2000 driver library.

Understanding the driver directory structureThe default KBOX 2000 driver share contains these directories. You’ll find it located in //KBOX_name/drivers or //KBOX_IP_address/drivers. See the Rules for organizing new drivers section before adding any new drivers:

Directory Type of Drivers

all Drivers that do not apply to Windows Vista and later operating systems. Usually used for drivers that apply to more than one of these: Windows XP, Windows 2000, Windows Server 2003, 2004, and 2005, Windows PE, and KPE. This direc-tory has these subdirectories by default; you can add more subdirectories if you need to: c - Chipset driverscpu - CPU driversg - Graphics driverslan - LAN driversm - Mass Storage driversmo - Modem (KACE recommends that you create this one)

s - Sound Card driversw - Wireless LAN drivers



Adding drivers to the driver libraryHardware changes quickly and you will almost certainly need to add more drivers for your KBOX 2000 to use in deploying software images to your nodes. This section explains the process of how you add drivers to the KBOX 2000 Driver Library and make them available for use in software deployments.

You can also use the DriverHarvest program to capture drives from a computer. For details, see the Using the DriverHarvest Program to Capture Drivers section.

For information on where to add drivers in the Driver Library, see the Rules for organizing new drivers section.

To add a driver to the KBOX 2000 Driver Library:

1. Read through the Rules for organizing new drivers section to figure out where to put the driver. the Understanding the driver directory structure section may also be of help.

2. Browse to the KBOX Systems Deployment Console > Library > Drivers.

The Drivers page appears.

kpe Pre-boot RIS-based network drivers and mass-storage device drivers only. The kpe and kpe64 directories are the only location where duplicate drivers are allowed. Drivers in these directories have non-RIS duplicates in other operating system-specific directories.

kpe64 64-bit pre-boot RIS-based network card and mass-storage device drivers only. The kpe and kpe64 directories are the only location where duplicate drivers are allowed. Drivers in these directories have non-RIS duplicates in other operating system-specific directories.

windows_2000 Intended for drivers that only work on Windows 2000 Professional.

windows_2003 Intended for drivers that only work on Windows Server 2003.

windows_2003_x64 Intended for drivers that only work on 64-bit Windows Server 2003.

windows_2008_x86 Intended for drivers that only work on 64-bit Windows Server 2008.

windows_2008_x64 Intended for drivers that only work on Windows Server 2008.

windows_7_x64 Intended for drivers that only work on 64-bit Windows 7.

windows_7_x86 Intended for drivers that only work on x86-based Windows 7.

windows_vista Intended for drivers that only work on Windows Vista.

windows_vists64 Intended for drivers that only work on 64-bit Windows Vista.

windows_xp Intended for drivers that only work on Windows XP.

windows_xp_x64 Intended for drivers that only work on 64-bit Windows XP.

winpe_2004 Intended for drivers that only work on Windows PE 2004.

winpe_2005 Intended for drivers that only work on Windows PE 2005.

winpe_2005_x64 Intended for drivers that only work on 64-bit Windows PE 2005.

Directory Type of Drivers




The Managing Drivers page appears.

Follow the instructions on this page to add a new driver.

4. Recache the drivers library. If you have made changes to only one of the driver directories, you can use the relevant button to recache only those drivers. This option is faster, but be sure to recache all directories that changed. Once recached, your new drivers are available to use through your KBOX 2000.

For more information and cautions about recaching drivers, see the Recaching drivers section.

Recaching driversAfter adding a new driver to the KBOX 2000, you must recache the driver list so that the KBOX 2000 can access the new driver.

To Recache your drivers:



2. Select Recache Drivers from the Choose action drop-down list.

The Managing Drivers page appears.

3. Select one of these options:

a Select Recache All Drivers.

a If you only made changes in one of the driver directories, use the relevant button to recache only that directory. This option is faster, but make sure you recache all the directories you changed.

Recaching the drivers can take a few minutes to complete. Therefore, do not perform any deployment operations on the KBOX 2000 while recaching is in progress.



4. Wait for the recache to finish.

Your new driver has been added to the KBOX 2000 driver library and is available to deploy to your nodes.

Using the DriverHarvest Program to Capture DriversThe Driver Harvesting feature searches for drivers on a computer and uploads them to your KBOX 2000 Driver Library. Once in the KBOX 2000 Driver Library and cached, you can add them to Scripted Installations that you deploy to your nodes. This section explains how to download the Driver Harvesting Utility to a computer, and then use it to upload (harvest) drivers to your KBOX 2000 drivers library.

The instructions below include logging into your KBOX 2000 to download the driver harvesting utility. This is only necessary to get the utility from the KBOX 2000 the first time. Once on a remote system, you can copy the driver harvesting utility .zip file from system to system like any other file.

Recaching drivers can take a few minutes. Recaching all KBOX 2000 default drivers takes about 20 minutes.

You can also recache drivers from the Server Maintenance page. Select KBOX Settings & Maintenance > Server Maintenance.



Downloading the Driver Harvesting Utility to a computer:

1. Log on to the computer.

If the remote system is not the computer you normally work on, physically go to the system, or use some form of remote control software to control it. For details on using VNC software to do this, see the Using VNC to Control Nodes section.

2. Browse to the KBOX 2000 Systems Deployment Console > Library > Drivers.


3. Select Choose Action... Download Driverharvesting Utility from the drop-down list.

The Driver Harvesting Uploader page appears.

This option is also available on the Library > Overview tab.

4. Select the appropriate Download button for the remote system.

The Driverharvest_x86.zip or Driverharvest_x64.zip file is downloaded to your system.

The driver harvesting utility file is now available for you to upload drivers to your KBOX 2000. For details, see the Harvesting drivers from a remote system: section.

Driver harvesting is only supported on Windows-based systems with Microsoft .NET 2.0 or later software installed.



Harvesting drivers from a remote system:

1. This section assumes that you have obtained the Driver Harvesting Utility by either:

• Following the instructions in the Downloading the Driver Harvesting Utility to a computer: section, or

• Copying the Driverharvest_x64.zip or Driverharvest_x86.zip file from another system.

2. Extract the files from Driverharvest_x86.zip or Driverharvest_x64.zip into a convenient location on your system.

Tip: Extracting these files into %systemroot%\system32 allows you to run the program from a command line regardless of your other path settings.

3. Confirm that the Driverharvest.exe, Driverharvest.dll, and inf.exclude files are all present in the directory you extracted the files to.

4. Select the Driverharvest.exe file (or type Driverharvest.exe in a command line) to start the Driver Harvesting utility. The Driver Harvesting window appears:

5. Select the Collect Device Information button to collect drivers from the system. The Driver Harvesting utility automatically probes the system for all drivers and displays them with checkboxes in the window at the bottom of the page:



6. Select drivers to upload to the KBOX 2000 by selecting the checkboxes next to their names.

7. Filter the list of selected drivers using the Select All, None, and Revert radio buttons. Revert allows you to reverse the driver selection. If you select a driver and then the Revert button, that driver is de-selected and all other drivers are selected.

8. Enter your KBOX 2000 IP address and Driver/Restore Share password in the fields provided.

You set the Driver/Restore Share password in the KBOX Settings and Maintenance > Control Panel page.

9. Select the Send Drivers to KBOX button to upload the drivers to your KBOX 2000. The selected drivers are uploaded to the \\KBOX_name\drivers\all\driverharvest\harvest_system_name directory on your KBOX 2000, where harvest_system_name is the name of the computer you are harvesting drivers from.

10. Go back to the system that you use to run the KBOX 2000.

11. Move the new drivers to the appropriate directories. See the Rules for organizing new drivers section for information.

12. Browse to the KBOX Systems Deployment Console > Library > Drivers sub-tab.



13. Select Choose Action... Recache Drivers from the drop down list to recache the KBOX 2000 drivers.

The drivers are now available to use in Scripted Installations, system images, or K-images.

Searching for Drivers in the Driver LibraryThe default KBOX 2000 Driver Library contains over 160,000 drivers. You can filter this list to make it more manageable by operating system or by driver name.

To search for drivers


The Drivers page appears displaying all drivers in your KBOX 2000 driver library.

2. To limit the list of drivers displayed:

a (By operating system) Select an operating system in the View by Operating System... drop-down list.

b (By driver name) Type all or part of a driver name in the Search box and select the Search button. The KBOX 2000 displays a list of drivers matching the search phrase.

Viewing Driver DetailsSelect a driver from the KBOX Systems Deployment Console > Library > Drivers List to view its details.

The Driver Detail page provides the driver’s filename and hardware class, and lists the operating system Scripted Installations the drivers are associated with.

Finding the Hardware for a DriverThere is an easy trick for finding out what hardware devices a driver is used for:


2. The Drivers are listed in the Hardware ID column. Copy the Hardware ID for the driver in question. In this example, the hardware ID is PCI\VEN_1317&DEV_1985:

Remember, if you are going to add a driver in a KPE image, you must move it into the \\system_name\drivers\kpe or kpe64 directory.



3. Paste the hardware ID into a web search engine and search for references to it.

You may find a direct reference to the device’s hardware, or you may have to sift through the search results. The search for PCI\VEN_1317&DEV_1985 displayed this .inf file identifying it as a network adapter card:

Troubleshooting Driver ProblemsThis section provides information to help you diagnose and fix driver problems.

Remember, the most common driver problem (Driver Not Found) is usually caused by adding drivers to the KBOX 2000, but then forgetting to recache the Driver Library. For instructions, see the Recaching drivers section.



Required Network Card Driver Not in the kpe Directory

The operating system image you selected does not contain the necessary drivers for your network adapter. Try selecting a different operating system image. If the problem persists, contact your system administrator. Setup cannot continue. Press any key to exit.

If you added the required drivers, make sure you recached the correct driver directory. For instructions, see the Recaching drivers section.

The driver logs can be useful. See the next section for information.

Using the driver logs

The KBOX Settings and Maintenance > logs > Network Driver Server > Output Log displays the most useful driver status information, including hardware devices trying unsuccessful to find drivers.

Search this log for Driver Not found messages, and check the text above it. Copy the hardware ID portion of the reference, and paste it into a browser search field to find out the hardware name is. For example, for this hardware reference:

Probing for PCI\VEN_8086&DEV_27DC&SUBSYS_01A71028&REV_01...

copy this hardware identifier (from PCI to just before the second ampersand):

PCI\VEN_8086&DEV_27DC

You can use this hardware identifier to:



• Search the Internet for the hardware name.

• Search inside of driver files to see if the driver applies to the hardware. The hardware identifier appears somewhere in all driver file that support it.


C H A P T E R 9

Creating and Configuring Pre- and Post-Installation Tasks

This section explains how to create, modify, and manage the Pre- and Post-installation tasks for an operating system deployment.

About Pre- and Post-installation tasksPre- and post-installation tasks are actions that you direct the KBOX 2000 to take during the process of deploying an operating system to a node. As the name implies, Pre-installation tasks are executed before an operating system is installed; they configure system hardware for an operating system. Post-installation tasks are executed just after the operating system is installed and boots for the first time.

The KBOX 2000 comes complete with a set of pre-installation tasks created and ready for you to use. But let’s face it - there aren’t that many actions that you can or should perform on a computer to configure it for an operating system. You might format a disk, create a partition on the disk, configure a RAID device, or capture the computer name, but not much more than that. The default pre-installation tasks should satisfy most of your hardware preparation needs. You might add more, but you will probably just configure and use the defaults tasks provided. For details see Configuring and Creating Pre-installation Tasks.

The KBOX 2000 also comes with some default post-installation tasks to configure the hardware system after the operating system is deployed. However, this is an area where we cannot predict the kinds of system configuration or software installation tasks that your organization requires. You will almost certainly create a number of additional post-installation tasks to configure nodes the way your organization requires. For details on the types of post-installation tasks you can create, see Creating Post-installation Tasks.

Configuring and Creating Pre-installation TasksPre-installation tasks are the first tasks performed during a Scripted Installation. These tasks are executed before the KBOX 2000 deploys the operating system to a Target Machine. Pre-installations tasks include for example, creating a partition on a target machine to deploy the operating system to. For more information

76


on adding pre-installation tasks to Scripted Installations, see the Adding a pre-installation task to a Scripted Installation section.

Understanding the pre-installation task typesThe types of pre-installation tasks are described below. For details on the KPE command line options see the Windows PE documentation. For details on the MacOS X NetBoot options, see the Apple documentation.

About the default pre-installation tasksThese pre-installation tasks defined and ready to use on your KBOX 2000 by default:

Pre-installation Task Type Architecture Description

Application KPE or MacOS X Net-boot

Can be a file (including a zip file) that the KBOX 2000 references. The file can also be a batch file (use the CALL function to run it). For details on creating an application task, see the To Add a new application task section.

BAT Script KPE A KPE command line that calls a batch script. See the screen help on the Preinstallation Tasks > Choose Action... Add New BAT Script Item page for a list of commonly-used commands. For details on creating a BAT script task, see the (Win-dows only) Adding a New BAT Script Task section

Shell Script MacOS X Netboot A MacOS X NetBoot script. See the Apple documenta-tion for details on options and script syntax. For details on creating a shell script task, see the (Mac OS only) To add a new shell script task section

DISKPART Script KPE DISKPART A KPE command that uses the Microsoft DISKPART utility to create a disk partition. See the screen help on the Preinstallation Tasks > Choose Action... Add New DISKPART Script Item page and the Microsoft documentation for details. For details on creating a DISKPART task, see the Adding a new DIS-KPART task and DISKPART command syntax and commonly used options: sections.

Name Type Description

Collect Computer Name Application Captures the computer name for reuse in the Apply Computer Name post-installation task.

Create Single HFS+ par-tition on Disk0

Shell Script Creates a single partition in HFS+ format using either APM or GPT format.

Create Single Partition DISKPART script Creates a single primary partition on the target machine.



Configuring the default pre-installation task1. Browse to the KBOX Systems Deployment Console > Library > Preinstallation Tasks.

The Preinstallation Tasks page appears.

2. Select the name of a pre-installation task to edit. The Preinstallation Task Detail page appears.

3. Make any changes to the pre-installation task that your organization requires.

4. Edit the Command Line, DISKPART Script or BAT Script depending on the type of preinstallation task you are editing.

5. Click Replace to replace the uploaded file, if the pre-installation task you are editing is of the Application type.

6. Click Save to save the changes.

Creating new pre-installation tasksThis section explains how to create your own custom pre-installation tasks. The process is different for each of the task types:

• To Add a new application task• (Windows only) Adding a New BAT Script Task• (Mac OS only) To add a new shell script task• Adding a new DISKPART task

To Add a new application task

1. Browse to the KBOX Systems Deployment Console > Library > Preinstallation Tasks.


Format C: as NTFS BAT script Formats the C drive and sets it as an NTFS file sys-tem.

Display Device Compati-bility

BAT script Uploads the client's hardware inventory to KBOX 2000 during deployment and displays the list of incompatible devices on the client console.

Install 2000/XP/2003 MBR

BAT script Installs the master boot record for Windows 2000, Windows XP, or Windows 2003.

Install Vista/2008/7/MBR

BAT script Installs the master boot record for Windows Vista, Server 2008, and 7.

Upload Inventory to KBOX

BAT script Uploads hardware inventory to KBOX 2000.

While associating pre-installation tasks to a Scripted Installation, ensure that the Format C: pre-installation task is after the Create Single Partition pre-installation task.



2. Select Add New Application Item from the Choose action drop-down list.

The Preinstallation task Detail page appears.

3. Enter the pre-installation task details as follows:

See the KBOX 2000 online help on the right of the Preinstallation Task Detail page for information on how the upload file and command line arguments interact.

(Windows only) Adding a New BAT Script Task

1. Browse to the KBOX Systems Deployment Console > Library > Preinstallation Tasks. The Preinstallation Tasks page appears.

2. Select Add New BAT Script Item from the Choose action drop-down list. The Preinstallation Task Detail page appears.


See the online help to the right of these settings on the Preinstallation Task Detail page for more information.

4. Click Save to save the pre-installation task details.

Name Enter the name of the pre-installation task.

Type (Read-only) Application. The type of pre-installation task.

Runtime Environ-ment:

Select KPE for Windows-based systems, or Mac OS X NetBoot for MacOS sys-tems.

Upload File Select Browse to select a single file or zip file to associate with this pre-instal-lation task. zip files are uncompressed before deployment begins.

Command Line Enter any command line arguments for the pre-installation task. You can include a bat file in the command line, preferably called with the call function to avoid collisions with other preinstallation tasks.

Notes: (Optional) Add explanatory notes about the tasks being performed.


Type (Read only) BAT Script. The type of pre-installation task.

Runntime Environ-ment

(Read only) KPE. The supported runtime environment.

BAT Script Enter the BAT Script.


Following are the frequently used commands, available from within the KBOX 2000 pre-installation environment:

• bcdedit.exe

• bootsect.exe

• chkdsk.exe

• format.com



(Mac OS only) To add a new shell script task



2. Select Add New Shell Script Item from the Choose action drop-down list. The Preinstallation Task Detail page appears.


4. Select Save to save the pre-installation task details.

Adding a new DISKPART task



2. Select Add New DISKPART Script Item from the Choose action drop-down list. The Preinstallation Task Detail page appears.


4. Select Save to save the pre-installation task details.

DISKPART command syntax and commonly used options:

Following are a few commonly used DISKPART Commands:


Type (Read only) Shell Script. The type of pre-installation task.


(Read only) Mac OS X NetBoot. The supported runtime environment.

Shell Script Enter the shell script.


Name Enter a name for this pre-installation task.

Type (Read only) DISKPART Script. The type of pre-installation task.


(Read only) KPE. The supported runtime environment.

DISKPART Script Enter the DISKPART Script. For details, see the DISKPART command syntax and commonly used options: section.


You must create a custom DISKPART script, by booting the target machine into the KPE, and run DISKPART on the command line.



Duplicating a preinstallation task1. Browse to the KBOX Systems Deployment Console > Library > Preinstallation Tasks.


2. Select the Name of a preinstallation task to duplicate.

The Preinstallation Task Detail page appears.

3. Select the Duplicate button at the bottom of the page.

A new Preinstallation Task Detail page appears for the new task.

Make any changes to the new task that your organization requires.

4. Select the Save button at the bottom of the page.

Deleting a pre-installation task1. Browse to the KBOX Systems Deployment Console > Library > Preinstallation Tasks.


2. Select the Name of a preinstallation task to delete.

The Preinstall Tasks Detail page appears.

3. Select the Delete button at the bottom of the page.

4. Select OK to confirm deletion.

Action DISKPART Command Notes

(Mandatory) Selecting objects

select disk=[number] select partition=[number] select volume=[{number\drive_letter}]

You must select a disk, partition, or vol-ume before to operate on with one of these commands. Where number is the disk, partition, or volume number.

Cleaning parti-tions

clean [ all ] This command quickly removes all parti-tions from a disk. The all option zeros all sectors on the disk.

Creating parti-tions

create partition [ primary | extended | logical ] [ size=number | offset=number ]

If you do not specify a size, the partition consumes the remaining available space. If you do not specify an offset, the partition is created in the first avail-able space for it.

Marking the boot partition

active The currently selected partition is marked as an active, or bootable par-tition.

Assigning a drive letter to a partition

assign letter=letter The currently selected partition is assigned a drive letter. If you do not specify a letter, the first available letter (starting with C) is used.



Creating Post-installation TasksPost-installation tasks are actions that you choose to perform on a node after you have installed the underlying operating system. For example, after deploying Windows XP Professional to a Target Machine, you may want to install a specific software application on that machine. You can direct post-installation tasks to occur either before or after the operating system is booted.

There are some default post-installation tasks, but you will almost certainly create your own custom post-installation tasks to meet your organization’s needs. This section explains how to create new post-installation tasks.

For information on how to add post-installation tasks to a Scripted Installation, see the Adding a post-installation task to a Scripted Installations section.

To add a new application item1. Browse to the KBOX Systems Deployment Console > Library > Postinstallation Tasks.

The Postinstallation Tasks page appears.

2. Select Add New Application Item from the Choose action drop-down list. The Postinstallation Task Detail page appears.

3. Enter the post-installation task details:

4. Select the Save button to create your new application post-installation task.

5. Your application post-installation task is now displayed on the Library > Postinstallation sub-tab.

The new post-installation task is now available for you to use when you create or modify a Scripted Installation using the Deployments > Scripted Installations sub-tab.

To add a new BAT script item1. Browse to the KBOX Systems Deployment Console > Library > Postinstallation Tasks.


2. Select Add New BAT Script Item from the Choose action drop-down list.

The Postinstallation Task Detail page appears.


Name Enter the name for the post-installation task.

Type (Read only) Application. The type of post-installation task.


Select a runtime environment. One of: KPE, Windows, Mac OS X NetBoot, or Mac OS X.

Upload File Select Browse to select a single file or zip file to associate with this pre-instal-lation task. zip files are uncompressed before deployment begins.

Command Line Enter Command line options for this post-installation task.


Name Enter a name for the post-installation task.

Type (Read only) Bat Script. The type of post-installation task.



4. Select the Save button to create your new shell script post-installation task.

5. Your new shell script post-installation task is now displayed on the Library > Postinstallation sub-tab.


To add a new shell script item1. Browse to the KBOX Systems Deployment Console > Library > Postinstallation Tasks.


2. Select Add New Shell Script Item from the Choose action drop-down list.



4. Select the Save button to create your new shell script installer post-installation task.

5. Your shell script post-installation task is now displayed on the Library > Postinstallation sub-tab.



Select a runtime environment. One of: KPE or Windows.

BAT Script Enter the BAT Script.


These tasks are executed at the first login after the Scripted Installation is successfully deployed to a machine.


Type (Read only) Shell Script. The type of post-installation task.


Select a runtime environment. One of: Mac OS X NetBoot or Mac OS X.

Shell Script: Enter the shell script commands for this post-installation task.




To add a new KBOX 2000 agent installer itemThe KBOX 2000 Client Agent Setup area supports the automatic bootstrapping of the KBOX 1000 Series Systems Management appliance (KBOX 1000) Series Agent Technology. This enables you to use a KBOX 2000 with a KBOX 1000 Series appliance.

To load newer or alternate versions of the KBOX 1000 Client technology, contact KACE Technical Support.

The KBOX 1000 Client is available in two configurations:

• KBOX 1000 Client with .NET Framework

This setup.exe executes an installation, which includes the run-time .NET Framework required for by KBOX nodes.

• KBOX 1000 Client without .NET Framework

This setup.exe installs the KBOX agent on machines that already have .NET Framework installed.

1. Browse to the KBOX Systems Deployment Console > Library > Postinstallation Tasks.


2. Select Add New KBOX Agent Installer Item from the Choose action drop-down list.



The KBOX Client tab is only used if you want to use your KBOX 2000 in conjunction with a KBOX 1000 Series appliance.

The Agent requires either .NET 1.1 or .NET 2.0 Frameworks installed on the managed computers before the KBOX 1000 Series Client installation.

KBOX 2000 Agent Installers require the target system to have .NET 1.1 or later installed.


Type (Read only) KBOX Agent. The type of post-installation task.


Select a runtime environment. One of: Windows or Mac OS X.

Upload File Select Browse to select a single file or zip file to associate with this pre-installa-tion task. zip files are uncompressed before deployment begins.



4. Select the Save button to create your new agent installer post-installation task.

5. Your new naming rule post-installation task is now displayed on the Library > Postinstallation sub-tab.


Command Line: Enter or change Kinstaller.exe command line switches. The command line switches for kinstaller.exe override the respective values in the kin-staller.exe.config file.

-display_mode= [ interactive | quiet | silent ]

Display Mode supports the options/values of Interactive, quiet, and silent.

Interactive mode provides a complete and visible User Interface and requires the user interaction to trigger actions.

quiet mode provides a reduced User Interface to display the progress but does not require or accept user input.

silent mode shows no user interface at all and operates without user input.

-server=kbox Enter the 1000 Series Agent's respective KBOX 2000 hostname or IP address.

-uninstall Forces kinstaller.exe into uninstall action mode. kinstaller.exe uninstalls the KBOX 1000 Agent, services and files in this mode.

-clone_prep Set this option to true when using kin-staller.exe to create a “clone-able” master disk image. To use the KBOX 2000 to slipstream the KBOX 1000 Client onto target deployment machines, set the option to true. Addition-ally, set the KBOX 2000 Application Command for the KBOX 1000 application Client to include the -clone_prep command line switch.

-ssl_enabled=0 Enables SSL for the KBOX 1000. 0=disabled, 1=enabled

-amp_ssl=0 Allows AMP traffic to be un-encrypted even though all other KBOX 1000 communication is SSL encrypted. 0=disabled, 1=enabled. The activation of SSL is for AMP Only. Note: This setting requires that you also set -ssl_enabled=1 (enabled).




To add a new naming rule item1. Browse to the KBOX Systems Deployment Console > Library > Postinstallation Tasks.


2. Select Add New Naming Rule from the Choose action drop-down list.


3. Enter the post-installation task details as follows:

4. Select the Save button to create your new naming rule post-installation task.

5. Your new naming rule post-installation task is now displayed on the Library > Postinstallation sub-tab.


For more details, see the Post-installation task for changing workstation name section.

To add a new service pack itemFor details on adding a new service pack item, see the Creating a service pack post-installation task section.

To add a new custom HAL replacement item This procedure assumes that you have created and thoroughly tested a custom HAL to use, and have the hal.dll, ntkrnlpa.exe, and ntoskrnl.exe files available locally. Your KBOX 2000 renames these files if they do not use the default names. You must upload all three files to add a custom HAL.

Name Enter name of the post-installation task.

Type (Read only) Naming Rule The type of post-installation task.


(Read only) Windows.

Upload File Select Browse to select a file containing the address and host names that you wish to upload.

Command Line Enter command line options for this post-installation task.


These tasks will be run upon the first login after the Scripted Installation is successfully deployed to a machine.





2. Select Add Custom HAL Replacement Item from the Choose action drop-down list.


3. Enter the post-installation task details as follows:

4. Select the Save button to create your new Custom HAL Replacement post-installation task.

5. Your new Custom HAL Replacement post-installation task is now displayed on the Library > Postinstallation sub-tab.


To troubleshoot custom HAL replacement tasks

Problems with your new HAL will return error messages like this one:

Windows could not start because the following file is missing or corrupt: \windows\system32\hal.dll

Be sure that you are trying to install the correct HAL for the operating system.

Post-installation task for installing .NET 2.0The Microsoft .NET Framework Version 2.0 SP1 post-installation task remotely installs .NET Framework version 2.0 from KBOX 2000 server.

This post-installation task installs:

Custom HALs only work on the 32-bit versions of these operating systems: Windows 2000, Windows XP, and Windows 2003. This feature does not apply to any 64-bit systems, or any other operating systems.

Be sure to test your custom HAL thoroughly. A bad HAL will prevent a windows system from booting.

Name Enter name for this post-installation task.

Type (Read only) Custom HAL Replacement


(Read only) KPE

Upload HAL DLL: Select Browse to select a HAL.DLL file to use.

Upload NTKRN-LPA.EXE

Select Browse to select a NTKRNLPA executable to use.

Upload NTOSK-RNL.EXE

Select Browse to select a NTOSKRNL executable to use.




• .NET Framework 2.0 SP1 (32-bit) and Windows Installer 3.1 on a 32-bit supported windows platform without the Windows Installer 3.1 installed.

• .NET 2.0 SP1 on 32-bit supported Windows platform with Windows Installer 3.1 installed.

• .NET 2.0 SP1 64-bit on 64-bit supported Windows platform

The following resources offer you more details:

• Supported Operating Systems and software for .NET Framework 2.0 SP1 (32-bit):

http://www.microsoft.com/downloads/details.aspx?familyid=79BC3B77-E02C-4AD3-AACF-A7633F706BA5&displaylang=en

• Supported Operating Systems and software for .NET Framework 2.0 SP1 (64-bit):

http://www.microsoft.com/downloads/details.aspx?FamilyId=029196ED-04EB-471E-8A99-3C61D19A4C5A&displaylang=en

• Supported Operating Systems and software for Windows Installer 3.1:

http://www.microsoft.com/downloads/details.aspx?FamilyID=889482FC-5F56-4A38-B838-DE776FD4138C&displaylang=en

Post-installation task for changing workstation nameThis task uses the utility WSName.exe to assign unique host names to the client machines after running a Scripted Installation or deploying a K-image.

The process for changing the workstation name involves the following steps:

• Creating a file containing the MAC address and host name of the client machine

• Uploading the file to the KBOX 2000 server

• Associating this task to a Scripted Installation or K-image

• Changing host name of the client machine

To Create a file containing the MAC address and host name of the client machine:

1. Create a text file and specify the MAC address and host name for which you need to change the host name. The format for the text file should be as follows:

mac_address = host name

2. Save this file locally on any client machine.

Installing Windows 3.1 on a remote machine as part of post-installation task does not automatically reboot the machine; you must manually reboot to complete the installation.

For details on associating a post-installation task to a scripted image, see the Managing Pre- and Post-installation Tasks section. For details on associating a post-installation task to a K-image, see the Viewing and Editing Image Details section.



Upload the file to the KBOX 2000 server:


The Postinstallation tasks page appears.

2. Select Add new naming rule from the choose action drop down list.

The Postinstallation task detail page appears.

3. Click Browse button and browse to the specified file containing the MAC address and host names that you wish to upload.

4. Click Save button to upload the file to the KBOX 2000 server.

The uploaded file is displayed as namedb.dat on Postinstallation task detail page.

Associate this task with a Scripted Installation or K-image:

Refer to Managing Pre- and Post-installation Tasks to associate a post-installation task to a Scripted installation.

Refer to the Viewing and Editing Image Details section to associate post-installation task to a K-Image.

To change the hostname of the remote machine:

Deploy Scripted Installation or K-image having this post-installation task associated to the client machine.

Refer to Deploying a Scripted Installation to deploy the Scripted Installation on the client machine.

Refer to the Capturing and Deploying Windows Images section to deploy the image on the client machine.

During deployment, this post-installation task verifies the MAC address specified in the namedb.bat file with the MAC address of the client machine. If the MAC addresses match, the host name of the client machine is changed.

Post-installation task for joining domainThis default post-installation task serves as an example that administrators can duplicate and customize. It allows a machine to join a Windows domain.

To modify the join domain post-installation task:



This post-installation task does not automatically change the host name of Windows Vista machine. You need to manually reboot the machine to assign the new host name. Also refer “To add a new naming rule item,” on page 86.

Refer to the link http://mystuff.clarke.co.nz/MyStuff/wsname.asp#Disclaimer for documentation and disclaimer on the WSNAME.exe utility.

The WSName.exe utility supports the host name change only for Windows.


http://mystuff.clarke.co.nz/MyStuff/wsname.asp#Disclaimer


2. Click Example: Join Domain post-installation task.


3. Following details are displayed:

The join_domain.vbs script file accepts the following command line parameters:

join_domain.vbs my_domain admin_user admin_password primary_dns_IP

Where,

The first 3 parameters are mandatory for all platforms.

Name Example: Join Domain. You can rename this post-installation task, if required.

Type Displays the type of post-installation task: Application. This is a read-only field.

Created Displays the date and time that this post-installation task was first created. This is a read-only field.

Modified Displays the date and time when this post-installation task was last modified. This is a read-only field.

Version Displays the version of this post-installation task. Each time this post-installation task is modified, the version number gets updated. This is a read-only field.

File Displays the script file join_domain.vbs. Click Replace to change the file or the file location.

File Size Displays the size of the file. This is a read-only field.

Command Line Enter the command line switches for this post-installation task.

Scripted Installa-tions

A list of pre-defined Scripted Installations with which you have associatedthis post-installation task.

System Images A list of pre-defined System Images with which you have associated thispost-installation task.

my_domain Enter the name of the domain to join.

admin_user Enter a username with administrator-level privileges.

admin_password Enter the password for the username listed above.

primary_dns_IP The IP address of DNS.Note: This command line parameter is optional for Windows XP and Windows Server 2003. It is required for Windows Vista and Windows Server 2008.

This post-installation task is not supported on Windows 2000 and earlier versions of Windows.



Editing a Post-Installation Task1. Browse to the KBOX Systems Deployment Console > Library > Postinstallation Tasks.


2. Click the post-installation task you want to edit.


3. Modify the post-installation task name.

4. Edit the Command Line, DISKPART Script or BAT Script depending on the type of post-installation task you are editing.

5. Click Replace to replace the uploaded file, if the post-installation task you are editing is Application type.


Duplicating a Post-installation Task1. Browse to the KBOX Systems Deployment Console > Library > Postinstallation Tasks.


2. Click the post-installation task you want to duplicate. The Postinstallation Task Detail page appears.

3. Click Duplicate.

Deleting a Post-installation Task1. Browse to the KBOX Systems Deployment Console > Library > Postinstallation Tasks.


2. Select the post-installation tasks you want to delete.

3. Select Delete Selected Item(s) from the drop-down list.

4. Click OK to confirm deletion.

You can also delete a post-installation task from the Postinstallation Tasks Detail page.

The system needs to be manually restarted after successful execution of this post-installation task.


C H A P T E R 10

Capturing and Deploying User States

This section explains how to capture, manage, and deploy user states. Capturing user states requires Microsoft’s USMT software, which we provide tools for you to download.

Capturing, Deploying, and Managing System User StatesThis section explains how to capture and use user states to distribute user settings and preferences.

Understanding user statesYour KBOX 2000 integrates the Microsoft® Windows® User State Migration Tool (USMT) software functionality, allowing you to capture and move a user’s desktop environment.

See the Microsoft documentation for an exhaustive list of the files, folders, and settings included in a user state. In general however, they include the following user data and operating system components:

• The files and folders needed for each user profile, including:

• All the “My” folders: My Documents, My Videos, My Pictures, etc.

• Desktop files.

• The Start menu.

• Favorites.

• Address book.

• Desktop wallpaper.

• Mouse and keyboard settings.

• Group memberships.

• Windows Internet Explorer settings.

• The All Users and Public profiles including:

• All the “Shared” folders: Shared Music, Shared Video, etc.

• Access Control Lists.

92


• Accessibility settings.

• Command-prompt settings.

• EFS files.

• Folder options.

• Fonts.

• ODBC settings.

• Phone and modem options.

• Regional settings.

• Remote Access.

• Taskbar Settings.

• Windows Media Player.

Understanding the KBOX 2000 USMT interfaceYour KBOX 2000 adds a GUI interface to the USMT feature that allows you to:

• Capture user state information from local or remote systems.

• Store states in an integrated user state library for easy storage, archiving, and management.

• Deploy user states to your nodes using the pre-defined Deploy User States postintallation task. Once captured, user states are available for you to deploy along with other system information during:

• Scripted installations.

• Remote site deployments.

• K-image deployments.

• Deploy user states by making them a part of a boot action or a client KPE installation.

USMT scanning rules

USMT 4.0 scans user states from Windows XP, Vista, and 7.

USMT 3.0.1 scans user states from Windows 2000, XP, and Vista.

See the USMT scanning and deployment matrices: section for a list of the operating systems.

USMT scanning and deployment matrices:

These compatibility matrices shows the USMT/OS capture/deploy options:

The KBOX 2000 user state features support both the 32 and 64-bit versions of the supported operating systems.



USMT 4.0 deployment compatibility matrix:

USMT 3.0.1 deployment compatibility matrix

User state capture and deployment overviewThe KBOX 2000 User State features allow you to capture a state over your network. They also allow you deploy remotely or locally deploy the remote machine state to a remote machine anywhere over your network.

You will follow these general steps to use the user state tasks features:

• Download the Microsoft USMT software - This step is integrated into your KBOX 2000 user interface, and is a one time-only task.

• Capture user states - You capture states from the Library > User States page, using the Choose Actions... Scan New User State item.

• Deploy user states - You use the pre-defined Deploy User States task to add a user state to a postinstallation task. You can then deploy states to nodes as part of a Scripted Installation or a K-image.

• Manage your user states - Your KBOX 2000 contains a library of user states that you can rescan or remove as required.

User States Scanned from:

Can be Deployed to these x86 systems

Can be Deployed to these x64 systems:

Windows 7 x86 Windows 7 x86 Windows 7 x64

Windows 7 x64 - Windows 7 x64

Windows Vista x86 Windows 7 x86, Windows Vista x86 Windows 7 x64, Windows Vista x64

Windows Vista x64 - Windows Vista x64

Window XP x86 Windows 7 x86, Windows Vista x86 Windows 7 x64, Windows Vista x64

Windows XP x64 - Windows 7 x64, Windows Vista x64

User States Scanned from:

Can be Deployed to these x86 systems

Can be Deployed to these x64 systems:

Windows Vista x86 Windows Vista x86 Windows Vista x64

Windows Vista x64 - Windows Vista x64

Window XP x86 Windows XP x86, Windows Vista x86

Windows XP x64, Windows Vista x64

Windows XP x64 - Windows XP x64, Windows Vista x64

Windows 2000 x86 Windows XP x86, Windows Vista x86

Windows XP x64 Windows Vista x64



User State Files and Settings

For details on the files and settings contained in a user state, see the Microsoft USMT documentation at this site: http://technet.microsoft.com/en-us/library/cc722387(WS.10).aspx.

Downloading USMT softwareThis step is required before you can capture and manage a library of user states. You can download either the 3.0.1 or 4.0 versions of USMT depending on the operating systems you are collecting user states from:

To download the USMT 3.0.1 software:

1. Browse to the KBOX Systems Deployment Console > Library > User States sub-tab.

The User States library page appears.

2. Select Choose Action... Upload USMT Software to KBOX from the drop-down menu.

The Upload User State Migration page appears.

3. Scroll to the bottom of this page and select the [ Edit Mode ] button.

4. You have these choices for downloading the USMT software:

• Automatically. The Download USMT Installer button uploads the USMT 3.0.1 software directly onto your KBOX 2000. This is the more efficient option, but if your KBOX 2000 system firewall won’t permit it, you can download the installers manually.

• Manually. This option uploads the USMT installers to a local location that you choose. You can then upload the installers from the local location to your KBOX 2000. You must upload both x86 and .64 versions in order for the USMT software to function correctly. Select the Browse buttons and choose a local location for each of the installers. Then select the Upload USMT installer button to upload the software on your KBOX 2000.

5. Once the download/upload completes a confirmation message is displayed.

Now that the USMT software is on your KBOX 2000, you can capture, manage, and deploy user states.

To download the USMT 4.0 software:

1. Browse to the KBOX Systems Deployment Console > Library > User States sub-tab.


2. Select Choose Action... Upload USMT Software to KBOX from the drop-down menu.

The Upload User State Migration page appears.

3. Scroll to the bottom of the Upload ZIP archive of Microsoft User State Migration Tool section and select the [ Edit Mode ] button.

The field be come configurable.

4. Select the URL next to the Download WAIK for USMT: item to download the WAIK.

Extract and install the ISO file that is downloaded to your system.

5. Select the Upload Zipped USMT button.

Extract and install the ISO file that is uploaded to your system.



Capturing user statesThis sections assumes that you have:

• Selected a USMT version to use for the operating system your are scanning. For details, see the USMT scanning and deployment matrices:.

• Downloaded the USMT software to your KBOX 2000. If not, see the instructions in the Downloading USMT software.

To scan user states:

1. (Windows XP systems only) Turn off Simple File Sharing on the target system.

2. (All Windows systems using a firewall) Enable File and Print Sharing on the target system. You will find this setting on the Exceptions list of the Firewall Configuration.

3. (All Windows Vista and Windows 7 systems) Bring up the Control Panel:

a Turn off Account Control > User Account Control.

b Change Network and Sharing from Public to Private.

c Enable Network and Sharing > Network Discovery and File Sharing.

4. (All Windows 7 systems) Bring up the Control Panel > System and Security > Local Policies > Security Options and change Network Security: LAN Manager Authentication level to Send LM and NTLM responses.

5. (All Windows 2000 SP4 systems) Confirm that the Windows installer version (C:\WINDOWS\system32\msi.dll) is 3.0.1 or later.

6. Browse to KBOX Systems Deployment Console > Library > User States.




7. Select Choose Action... Scan New User State from the drop-down list. The Scan new User State page appears:

Fill in details about the system you are scanning:

8. Select the Next button to start the user state capture. Screen 2 of 4 appears, with a progress message, and then the Scan new User State page appears with you a list of users:

Host/I.D. Enter the fully qualified hostname or IP address for the system to col-lect user states from.

Domain: This is optional unless the authenticating user is a domain user. How-ever if you do not specify a domain, the username syntax on the deployed system changes to hostname\username.

User Name/Password

The username and password of a user with administrator privileges.

USMT Version to be used:

Select the User State Migration Tool version compatible with the oper-ating system you are scanning. For details, see the USMT scanning and deployment matrices:.



9. Select the checkboxes next to the users to scan states for, and select the Next button. A status screen appears, and then the state upload/collection completes. The User States page reappears.

Repeat these steps as necessary to capture all the user states your organization requires. You are then ready to manage and deploy those states.

Troubleshooting capturing and deploying user statesIf you have trouble capturing or loading user states, here are some suggestions for making the process work:

• If you have trouble connecting to the remote system (LOGON FAILURE messages):

• Make sure you turned off Simple File Sharing, and turn off any firewalls on the remote system.

• Use a local (not domain) user account to make the capture. Try capturing the state as administrator.

• If you have trouble capturing user states, you can always run the USMT locally from a command prompt:

a Change directory to where the USMT is installed (C:\Program Files by default)

b Run this command

ScanState.exe /i:miguser.xml /i:migapp.xml /l:scan_state_log_path\ScanState.log /ue:*\* /ui:account_name user_state_target_path

Where: scan_state_log_path is the location of the ScanState logs (can be current directory)

The user account you use to capture states must have already logged on to the system at least once.



account_name is the username of the user collecting the user state. user_state_target_path is the path where you want the user states located.

States are store in the state_target_path directory.

For example:

ScanState.exe /i:miguser.xml /i:migapp.xml /l:c:\dir1\ScanState.log /ue:*\* /ui:user1 c:\dir2

• If you have trouble deploying user states, you can always run the USMT locally from a command prompt with this syntax:

As a local user:

LoadState.exe user_state_target_path /i:migapp.xml /i:miguser.xml /lac /lae

As a domain user:

LoadState.exe user_state_target_path /i:migapp.xml /i:miguser.xml

Where user_state_target_path is the path where you want the user states located.

• If your usernames are given the syntax hostname\username on deployed systems, you did not specify a domain in the Scan New User State window. See Capturing user states for details.

Deploying user statesNow that you have a library of user states, they are automatically made available to you to when you create Scripted Installations or K-Images.

Once created, you can deploy users states as part of a post-installation task.

Remember, you can only deploy states to the same or later operating systems. If you scan states from and XP system, you can deploy to XP or Vista systems. If you scan from a Vista system, you can only deploy to Vista systems (or later Windows releases).



...or as part of a K-image or PKE environment specified in a boot action like one of these:

Managing user statesThis section contains instructions for managing your library of User States.

Applying a label to a user state

You can use Labels to organize and categorize your User States. Create the labels you need first, then follow these steps to apply them to your user states.

For details on creating labels, see the Using Labels to Organize KBOX 2000 Users and Resources section.


1. Browse to KBOX Systems Deployment Console > Library > User States.

The User States page appears.

2. Select the checkboxes for the User States to getting the change.

3. Select either Choose Action... Apply Label: or Choose Action... Remove label: from the drop-down list.

4. The change is automatically applied.

Deleting user states1. Browse to KBOX Systems Deployment Console > Library > User States.



2. Select the checkbox for the user state to delete, and select Choose Action... Delete Selected Item(s) from the drop-down list.

3. Select the Delete button.

4. Select OK to confirm the deletion.

Viewing user state details

To view image details:

1. Browse to the KBOX Systems Deployment Console > Library > User States.

The User State page appears.

2. Select the Name of the User State to view.

The User State Detail page appears.

3. This page displays following User State information:

• Profile Name.

• Host.

• Domain.

• Time and date the State was created.

• Time and date the State was last modified.

• The User State version number.

• Notes. This is the only editable field. Enter any relevant information.

• Operating System

• System architecture.

• The size of the user state (in bytes)




103

C H A P T E R 11

Using Scripted Installations to Deploy Software Components

You use Scripted Installations to install operating system images and other software components, and perform pre-boot configuration tasks on your KBOX 2000 nodes. Scripted installations can be remote, unattended, and hardware-independent.

About Scripted InstallationsYou use Scripted Installations to distribute operating system images and other software components such as drivers and user states to your nodes as needed. You define the scripted images on the Deployments tab.

Figure 11-1: Scripted Installation Library


Each Scripted Installation or K-image is a combination of:

• Pre-installation tasks which execute before the actual operating system installation. For example selecting and partitioning a disk for the operating system.

• A Scripted Installation which actually installs the operating system (but does not boot it yet).

• Post-installation tasks which execute after the operating system has been deployed, but before the OS boots the first time. For example, specifying a name for the computer.

• Post-installation tasks which execute after the operating system has booted. For example, installing the KBOX 2000 agent software on the node.

You specify tasks to include on a Scripted Installation by dragging and dropping them from the right column of the Deployments > Scripted Installations sub-tab to the left column. The figure below shows three pre-installation tasks specified to run for this Scripted Installation: Create Single Partition, Format C: as NTFS, and Install 2000/KP/2003 MBR:

Figure 11-1: Scripted Installation Tasks



Your KBOX 2000 comes pre-configured with default pre- and post-installation tasks, but you will almost certainly also define your own custom tasks to fit your organization’s requirements. You create, manage, and store pre and post-installation tasks using the Preinstallation and Postinstallation sub-tabs under the Library tab of the KBOX 2000 interface.

Once defined, you can run a Scripted Installation as many times and on as many nodes as you need to, locally or remotely, attended or unattended. The agentless, PXE-based design allows you to deploy to any LAN-connected desktop, laptop, or server. You can remotely deploy images from your KBOX 2000 to any node accessible through LAN without installing an Agent/Client.

Scripted Installation Process OverviewFollow these steps to perform a Scripted Installation on a target machine:

1. Import a Source OS Image to use - You can import the OS source from a CD/DVD locally or remotely, onto the KBOX 2000. Once on the KBOX 2000, you can use the OS image in Scripted Installations without having to use physical CDs. This allows for a faster installation, and relieves you of the burden of using physical media. For details, see the Capturing Operating System Images section.

2. Search for drivers (optional) - You can search for any required drivers you may need for your Scripted Installation, before proceeding with the rest of this process. For details, see the Managing Your Driver Library section.

3. Define pre-installation tasks (optional) - You can define the tasks to perform before you deploy an operating system on the Target Machine. The pre-installation tasks can be used in multiple Scripted Installations. For details, see the Configuring and Creating Pre-installation Tasks section.



4. Define post-installation (pre os boot) tasks (optional) - You can define the tasks to perform after you deploy an operating system on the Target Machine, but before the OS boots. For details, see the Creating Post-installation Tasks section.

5. Define post-installation (post os boot) tasks (optional) - You can define the tasks to perform after you deploy an operating system on the Target Machine after the OS has booted. For details, see the Creating Post-installation Tasks section.

6. Define the Scripted Installation - This is where you put all the pieces together. You specify an OS image, and all the pre- and post-installation tasks for a scripted image. This usually includes the KBOX 2000 agent software. Once defined, your images and task are available on the Deployments > Scripted Installations sub-tab, and you can drag and drop them onto your Scripted Installation. For details on Scripted Installations setup, see the Creating a Scripted Installation section. For details on adding the KBOX 2000 agent software, see the Installing the KBOX 2000 Agent Software Using a Scripted Installation section.

7. Deploy the Scripted Installation - The Scripted Installation is ready for deployment on your nodes. The Scripted Installation can either be attended or unattended (automatic). For details, see the Deploying a Scripted Installation section.

Creating a Scripted InstallationOnce you have created or gathered all the requisite software parts for a software image, you put them all together in a Scripted Installation which you can use to deploy to your nodes. This section assumes that you have all the OS images, drivers, and pre- and post-installation tasks ready to add to your Scripted Installation.

To create a Scripted Installation:

1. Browse to Deployments > Scripted Installations. The Scripted Installations page appears.



4. Click Next.

5. You have the following options when defining a Scripted Installation:

a Walk me through creating an answer file for unattended setup:

You can use the KBOX 2000 wizard to create an answer file for unattended setup and installation. Refer to “Creating an answer file from scratch,” on page 107.

If you want to install Windows Server 2003 R2, install Disk 1 using Scripted Installation and upload Disk 2 as a post-installation task.

Name Enter a descriptive name for the Scripted Installation.

Source CD Select the source CD of the operating system, you are installing using Scripted Installations, from the Source CD drop-down list.



b Upload an existing answer file for unattended setup:

You can upload an existing answer file for unattended setup and installation. Refer to “Uploading an existing answer file,” on page 109.

c No answer file; This is a server-based attended setup:

You can perform manual installation on the Target Machine without an answer file. Refer to “Installing without an answer file,” on page 109.

Creating an answer file from scratch1. Browse to the KBOX Systems Deployment Console > Deployments > Scripted Installations.

The Scripted Installations page appears.



4. Click Next.

5. Select Walk me through creating an answer file for unattended setup.

6. Click Next.


Name Enter a descriptive name for the Scripted Installation.

Source CD Select the source CD of the operating system, you are installing using Scripted Installations, from the Source CD drop-down list.

Registration Data Name* Specify your computer hostname.

Organization* Organization name.

Product Key* Specify the product key for the operating system.

Licensing Mode The licensing mode.Note: This field is only available if you select a Windows 2003 source CD.

Client Licenses The number of available client licenses available.Note: This field is only available if you select a Windows 2003 source CD.

General Settings

Time Zone* Select a time zone from the drop-down list. This time zone is same as Active Directory time zone.

Screen Colors Select a screen color palette from the drop-down list.

Screen Area Select a screen display area from the drop-down list.

Custom Specify a custom screen area, if the Screen Area drop-down list does not include the area you want.

Refresh Frequency Select a screen refresh frequency (in Hz) from the drop-down list.



* Required for Unattended Install ** Required for Unattended Application Install

8. Click Next.

9. Select the pre-installation and post-installation tasks that run along with the Scripted Installation.

To add a pre-installation task to a Scripted Installation, drag the pre-installation task from the Available Preinstallation Tasks list and drop into the Run Preinstallation Tasks list.

To add a post-installation task to a Scripted Installation, drag the post-installation task from the Available Postinstallation Tasks list and drop into the Run Postinstallation Tasks list.

10. When the Scripted Installation is created, the page displays “Scripted Installation Status: Completed”. The new Scripted Installation appears in the Scripted Installations list.

11. Click Next. Your Scripted Installation has been successfully copied from the Source CD. Click the appropriate link to proceed:

• Deploy this Scripted Installation to a System,

Administrator Account

Password Enter the administrator password for the Target Machine. Leave this field blank if there is no administrator password.

Automatically log computer in to the Administrator account**

Select the check box, if you want the Scripted Installation to automatically logon to the Administrator account on the Target Machine.

Disable automatic login after n system boots

Select the check box and specify the number of boots, if you want to allow the Target Machine to automatically log on for a specified number of boots only.

Networking Computer Name

Enter a computer name or “*” for Windows to generate a name automatically.

How will the destination computers access the local network?

Workgroup* Select the check box if the Target Machine is a part of a workgroup.

Domain Select the check box if the Target Machine is a part of a domain.

Create a computer account in the domain

Select the check box to create a new computer account in the domain.

Domain Administrator Enter the name of the domain administrator.Note: The administrator must have the privilege to add a machine to the domain.

Password The administrator password for the domain.

Windows Com-ponents

Allow Windows Setup to install Unsigned Drivers

Select the check box, to allow the Scripted Installation to install the unsigned versions of drivers that are currently undergoing WHQL validation testing.

Enable Automatic Updates Select the check box to enable automatic Windows updates.



• Create another Scripted Installation

• View this Scripted Installation’s Details

For more information on how to deploy a Scripted Installation to a system, refer to Chapter 11,“Deploying a Scripted Installation,” starting on page 113.

Uploading an existing answer file1. Select Upload an existing answer file for unattended setup.

2. Click Next.

3. Click Browse to select the answer file.

4. Click Next. The Create a Scripted Installation page appears.

5. Select the pre-installation and post-installation tasks that will be run along with the Scripted Installation.




7. Click Next.

For more information on how to deploy this Scripted Installation to a system, refer to Chapter 11,“Deploying a Scripted Installation,” starting on page 113.

Installing without an answer fileIn this case, you will need to attend to the installation on the target machine.

To install without an answer file:

1. Select No answer file; This will be a server-based attended setup.

2. Click Next. The Create a Scripted Installation page appears.

3. Select the pre-installation and post-installation tasks that run along with the Scripted Installation.




Set OemPreinstall = “yes” in the uploaded answer file, for post-installation tasks to run. This is necessary for slipstreaming post-installation tasks.



5. Click Next.

For more information on how to deploy this Scripted Installation to a system, refer to Chapter 11,“Deploying a Scripted Installation,” starting on page 113.

Managing Pre- and Post-installation TasksYou can add or remove pre-installation and post-installation tasks to a Scripted Installation.

Adding a pre-installation task to a Scripted Installation1. Browse to the KBOX Systems Deployment Console > Deployments > Scripted Installations.


2. Click the Scripted Installation file to which you want to add the pre-installation task.

3. Drag the pre-installation task from the Available Preinstallation Tasks list and drop it into the Run Preinstallation Tasks list.

4. Click Save.

Removing a pre-installation task from a Scripted Installation1. Browse to the KBOX Systems Deployment Console > Deployments > Scripted Installations.


2. Click the Scripted Installation file, from which you want to remove a pre-installation task.

3. Drag the pre-installation task from the Run Preinstallation Tasks list and drop it into the Available Preinstallation Tasks list.

4. Click Save.

Adding a post-installation task to a Scripted Installations1. Browse to the KBOX Systems Deployment Console > Deployments > Scripted Installations. The

Scripted Installations page appears.

2. Click the Scripted Installation file, to which you want to add the post-installation task.

3. Drag the post-installation task from the Available Postinstallation Tasks list and drop it into the Run Postinstallation Tasks list.

4. Click Save.

Removing a post-installation task from the Scripted Installations1. Browse to the KBOX Systems Deployment Console > Deployments > Scripted Installations.


2. Click the Scripted Installation file, from which you want to remove a post-installation task.



3. Drag the post-installation task from the Run Postinstallation Tasks list and drop it into the Available Postinstallation Tasks list.

4. Click Save.

Changing the order of pre-installation and post-installation tasks1. Browse to the KBOX Systems Deployment Console > Deployments > Scripted Installations.


2. Click the Scripted Installation file, for which you want to update the order of the pre-installation or post-installation tasks.

3. To update the order of the pre-installation tasks, drag the task up or down in the Run Preinstallation Tasks list.

4. To update the order of the post-installation tasks, drag the task up or down in the Run Postinstallation Tasks list.

5. Click Save to save your changes.

Installing the KBOX 2000 Agent Software Using a Scripted InstallationThe KBOX 2000 Client Agent Setup area supports the automatic bootstrapping of the KBOX 1000 appliance Agent Technology. This enables you to use a KBOX 2000 with a KBOX 1000.

To load newer or alternate versions of the KBOX 1000 Client technology, contact KACE Technical Support.

The KBOX 1000 Client is available in two configurations:

• KBOX 1000 Client with .NET Framework

This setup.exe executes an installation, which includes the run-time .NET Framework required for the KBOX 1000 Client.

• KBOX 1000 Client without .NET Framework

This setup.exe installs the KBOX 1000 Client on machines that already have .NET Framework installed.

The KBOX Client tab is only used if you want to use your KBOX 2000 in conjunction with a KBOX 1000.

The Agent requires either .NET 1.1 or .NET 2.0 Frameworks installed on the managed computers before the KBOX 1000 Client installation.



To add the KBOX 1000 client agent to a Scripted Installation:


The KBOX Agent Setup page appears.

2. Enter following information:

Name Enter a descriptive name for the KBOX 1000 Client Agent.

Type (Read only) Displays the KBOX 1000 Client name.

Created (Read only) Displays the date on which the KBOX 1000 Client Agent was first cre-ated.

Modified (Read only) Displays the date on which, the KBOX 1000 Client Agent was last modi-fied.

File Displays the source file for the KBOX 1000 Client Agent Installer. Click Replace to change the file and file location.

Upload File If you change the source file, enter a file name or click Browse to select another file.

File Size (Read only) Displays the size of the file.

Command Line

Kinstaller.exe command line switches. The command line switches for kinstaller.exe override the respective values in the kinstaller.exe.config file.

-display_mode= interactive | quiet | silent

Display Mode supports the options/values of “interactive”, “quiet”, and “silent”.

“Interactive” mode provides a complete and visible User Interface and requires the user interaction to trigger actions.

“Quiet” mode provides a reduced User Interface to display the progress but does not require or accept user input.

“Silent” mode shows no user interface at all and operates without user input.

-server=kbox Enter the 1000 Series Agent's respective KBOX 1000 Appliance hostname or IP address.

-uninstall Specify “-uninstall” on the command line to force the kinstaller.exe into the uninstall action mode. kinstaller.exe uninstalls the KBOX 1000 Agent, services and files in this mode.

-clone_prep Set this option to “true” when using kinstaller.exe to create a “clone-able” master disk image. To use the KBOX 2000 to slipstream the KBOX 1000 Client onto target deployment machines, set the option to “true”. Additionally, set the KBOX 2000 Application Command for the KBOX 1000 Client to include the “-clone_prep” command line switch.

Scripted Installations

Displays a list of Scripted Installations that have this KBOX 1000 Client Agent assaulted as post-installation tasks.



3. Click Save to save the KBOX 1000 Client details.

Deploying a Scripted InstallationYou can deploy a Scripted Install action in two ways:

1. Deploy a Scripted Installation from the Boot Menu:

You can deploy a Scripted Installation manually from the boot menu. See To deploy a Scripted Installation from the Windows Deployment and Recovery Console: for details.

2. Deploy a Scripted Installation automatically from the Administrator Console:

You can deploy a Scripted Installation automatically from the administrator console. See Setting up the target machine for a Scripted Installation: for details.

Deploying a Scripted InstallationTo deploy a system from the Boot Menu of the Target Machine, select Show Boot Menu from the Next Boot Action drop-down list while setting up the deployment or alternatively deploy a Scripted Installation from the Administrator Console.

Setting up the target machine for a Scripted Installation:



There are two ways that you can set up your Boot Action:

• Select the Target Machine from the Boot Actions list to automatically populate the Boot Action Setup information.

• Enter the Boot Action Setup information manually.Instructions for both methods are given below.

2. To populate the Boot Action Setup information automatically, click the linked host entry for the Target Machine to which you want to deploy the Scripted Installation and then select Set Boot Action(s) for this system from the Choose action drop-down list.

3. To enter the Boot Action Setup information manually, select Add New Item from the Choose action drop-down list. The Boot Action Setup page appears.

4. Enter or review the Boot Action Setup information as follows:

System Images

Displays a list of System Images that have this KBOX 1000 Client Agent associated as post-installation tasks.

You can deploy a Scripted Installation from the Boot Menu even if you create or upload an Answer File. You can do for the security of the machine, or if you want no interference with the installation.

Systems Select the IP address of the Target Machine from the drop-down list.



5. Click Next. The System Deployment list page appears.The boot action that you defined appears in the Boot Actions list. The next step is for you to physically go to the Target Machine and reboot it. It will automatically boot to either the Boot Menu or to the Windows Deployment and Recovery Console.

To deploy a Scripted Installation from the Windows Deployment and Recovery Console:

1. Boot the Target Machine. The KBOX Boot Menu appears.

2. Highlight Windows Deployment and Recovery Console. The Windows Deployment and Recovery Console Main Menu appears.

3. Select Scripted Installation on the Main Menu. This page displays the Scripted Installations that you have created using the Administrator console. Select a Scripted Installation.

4. The selected Scripted Installation gets installed.

Deleting a Scripted Installation from a Deployed SystemTo delete a Scripted Installation deployment before it is deployed:



2. Select the check box of the Scripted Installation deployment or deployments you want to delete.

MAC Address The unique MAC address of the Target Machine is in a hexadecimal format: xx:xx:xx:xx:xx:xx. it is populated on the basis of the selected IP address of the target machine.

First Boot Action If you want to boot using the Boot Menu, select Show Boot Menu from the First Boot Action drop-down list.If you want to boot from the local hard drive, select Boot from the Local Hard Drive from the First Boot Action drop-down list.If you want to boot using automated Scripted Installations, select the appropri-ate Scripted Installation under Automated Scripted Installations from the First Boot Action drop-down list.If you want to boot using default KBOX client environments, select the appropri-ate option under Default KBOX Client Environments from the First Boot Action drop-down list.To boot using other KBOX 2000 client environments, select the appropriate option under Other KBOX Client Environments from the First Boot Action drop-down list.

Number of Boots Input 0 to always perform the first boot action while booting. Input any other number and the KBOX 2000 performs the first boot action for that many boots, then perform the next action listed below.

Next Boot Action Select any action that you want to perform during the next (subsequent) boot. Refer to the examples listed in the First Boot Action.

Number of Boots Input a number and the KBOX 2000 performs the boot action for that many boots, Then revert to displaying the System Deployment Boot Menu. Input 1 to perform this action at the next boot.



3. Select Delete Selected Item(s) from the Choose Action drop-down list.


Deleting a Scripted Installation from the KBOX 20001. Browse to the KBOX Systems Deployment Console > Deployments > Scripted Installations.

The Scripted Installations list page appears.

2. Select the check box of the Scripted Installation you want to delete.


4. Click OK to confirm the deletion or click Cancel to cancel the deletion.

Viewing and editing Scripted Installation Details1. Browse to the KBOX Systems Deployment Console > Deployments > Scripted Installations.

The Scripted Installations list page appears.

2. Click the Scripted Installation for which you want to view or edit details.

The Scripted Installation Detail page appears.

3. This page displays following information:

Name Displays the name of the Scripted Installation. You can change the name of the Scripted Installation.

Type Displays the type of the Scripted Installation: wizard or cloning console. This is a read-only field.

Source CD Displays the source CD used for this Scripted Installation. This is a read-only field.

Created Displays the date and time on which, the Scripted Installation was first created. This is a read-only field.

Modified Displays the date and time on which, the Scripted Installation was last modified. This is a read-only field.

Status Displays the status of the Scripted Installation. This is a read-only field.

Version Displays the version of the Scripted Installation. Each time the Scripted Installa-tion is modified this version number gets updated. This is a read-only field.

Installation Plan Allows you to add or remove pre-installation and post-installation tasks for this Scripted Installation. For more information, refer “Managing Pre- and Post-installation Tasks,” on page 110.Note: Installation plan is available only if the Scripted Installation is for win-dows setup.



4. Click Deploy this Scripted Installation to a System. For more information on how to deploy a Scripted Installation, refer to “Deploying a Scripted Installation,” on page 113

Click Download a bootable ISO for this Scripted Installation to download the KBOX 2000 Pre-installation Environment (KPE) as a bootable ISO file. Burn this file onto a CD and use it to boot a machine without enabling network booting.

Note: You must refresh this CD as network drivers are added or removed from the KBOX 2000, or if the IP address of the KBOX 2000 changes.

5. Select appropriate action from the Preinstallation Task Error Handling drop-down list

The selected action decides the further progress during a Scripted Installation, if one or more pre-installation task fails. In case of attended installations, the user aborts or continues the Scripted Installation, if any pre-installation task fails.

In case of unattended installations, the following scenarios occur depending upon the action selected from the Preinstallation Task Error Handling drop-down list:


Setting Boot ActionsBoot Actions page shows the currently configured boot actions. Using the Boot Actions page you can set up a deployment that directs your KBOX 2000 to run a Scripted Installation unattended the next time the Target Machine boots. You can also choose to deploy a system directly from the Boot Menu of the Target Machine. The Boot Menu will appear on the Target Machine the next time it is booted.

To set boot actions:




• Select the Target Machine from the Boot Actions list on the Boot Actions page in order to automatically pre-populate the Boot Action Setup information.

• Enter the Boot Action Setup information manually.

Instructions for both methods are given below.

2. To pre-populate the Boot Action Setup information automatically, click the linked Host entry for the Target Machine to which you want to deploy the Scripted Installation and then click Set Boot Action(s) for this system.

Continue on Errors The Scripted Installation ignores any pre-installation task failure and continues without prompting the user.

Prompt on Errors The Scripted Installation prompts the user to abort or continue with the Scripted Installation if pre-installation task fails.

Halt on Errors The Scripted Installation directly aborts the installation if any pre-installation task fails.



3. To enter the Boot Action Setup information manually, select Add New Item from the Choose action drop-down list.


4. Enter or review Boot Action Setup information as follows:

5. Click Next. The System Deployment list page appears.

The boot action that you defined appears in the Boot Actions list.


MAC Address

The unique MAC address of the Target Machine in hexadecimal format: xx:xx:xx:xx:xx:xx. is populated on the basis of selected IP address of the target machine.

First Boot Action

You can select any action that you want to perform during the first boot.For example, If you want to boot using the Boot Menu, select Show Boot Menu from the First Boot Action drop-down list.If you want to boot directly using the Windows Deployment and Recovery Console or Linux Deployment and Recovery Console, select the appropriate option from the First Boot Action drop-down list.If you want to deploy a Scripted Installation, select the appropriate Scripted Installation from the First Boot Action drop-down list.If you want to deploy a K-image, select the appropriate image name under Automated K-image deployments from the First Boot Action drop-down list.

Number of Boots

Input 0 to always perform this action at boot. Input any other number and the KBOX 2000 performs the boot action for that many boots, then perform the next action listed below.

Next Boot Action

You can select any action that you want to perform during the next (subsequent) boot.You can refer to the examples listed for First Boot Action.

Number of Boots

Input a number and the KBOX 2000 performs the boot action for that many boots, then reverts to displaying the System Deployment Boot Menu.Input 1 to perform this action at the next boot.


C H A P T E R 12

Using System Images to Deploy Software Compo-nents

This section explains the features that your KBOX 2000 uses to deploy software components to the nodes it administers. These features provide centralized remote disk image capture, archival, and deployment.

About KBOX 2000 Series System ImagingThe KBOX 2000 Series appliances provide centralized, remote disk image (system image) capture and deployment. You capture and store system images using the your KBOX 2000 Library module, and deploy them using a scripted image from the Deployments module.

The KBOX 2000 system imaging features include:

• Remote disk imaging from a central, easy-to-use Web-based console.

• Full disk and partition-based imaging supports any NTFS, FAT, EXT2 or EXT3 file system.

• The K-image based imaging supports NTFS and FAT32 file systems. It supports all types of files on those file systems.

• Integrated library for easy and centralized image archiving and management.

• Agent-less, PXE-based design allows for remote deployment of any LAN connected desktop, laptop, or server.

• “Bare-metal” system build outs.

Imaging environmentsThe KBOX 2000 has two pre-installation environments for system imaging: KPE and KBOX KNOPPIX. KPE (KBOX Pre-installation Environment) is a Windows PE-based environment used for file-based imaging of NTFS and FAT32 file systems. KBOX KNOPPIX is a Linux-based environment that can be used for sector-based imaging, as well as NTFS Optimized imaging.

118

Using System Images to Deploy Software Components

Understanding the image formatsThe KBOX 2000 has three image formats: K-image, NTFS Optimized, and Sector-based. These formats have different requirements and benefits:

Image Capture and Deployment Process OverviewThe KBOX 2000 Series disk imaging features allow you to remotely or locally capture a remote machine image over your network. You can remotely or locally deploy the system image to a computer anywhere over your network.

To performing the disk imaging tasks, follow these general steps:

1. Capture an image - You capture images using the Windows Deployment and Recovery Console or Linux Deployment and Recovery Console:

• From Boot Menu of the remote machine

• Using VNC from the Administrator Console

2. Deploy the image - In this step, you can set up a Scripted Installation to deploy a captured image to the Target Machine. You can then physically go to the Target Machine, reboot it, and deploy the image from the Boot Menu.

K-Image NTFS Optimized Sector-based

Supported Oper-ating Systems:

Windows and Mac OS Windows only Windows and MacOS

Filesystem types: NTFS or FAT32 NTFS

Image capture tool:

Windows Deployment and Recovery Console.

Linux Deployment and Recov-ery Console.

Linux Deployment and Recov-ery Console.

Characteristics: -Fast image capture and deploy-ment. -Most efficient storage of all for-mats. -Can be deployed on different capacity disks. -Image contents can be viewed on the server. -Support pre-installation tasks for hardware and drive setup.

-Very fast for image capture and deployment. -Less efficient storage than K-image, but more efficient than Sector-based. -Can only be deployed onto identical hardware. -Contents cannot be viewed on the server. -Cannot automate hardware setup prior to image deploy-ment.

-Captures an exact, sector-by-sector copy of the disk. -Slowest format for image capture and deploy. -Least storage efficient for-mat. -Can only be deployed onto identical hardware. -Contents cannot be viewed on the server. -Cannot automate hardware setup prior to image deploy-ment.



Capturing and Deploying Windows Images

You have these options for capturing images:

• Using the Windows Deployment and Recovery Console from the boot menu.

• Using the Linux Deployment and Recovery Console from the boot menu.

• Use the boot menu to bring up a VNC from the Administrator Console, and use it to access the Windows Deployment and Recovery Console.

• Use the boot menu to bring up a VNC from the Administrator Console, and use it to access the Linux Deployment and Recovery Console remotely.

To set up the remote machine for image capture or deployment:



There are two ways that you can set up a Boot Action:

• Select the remote machine from the Boot Actions list on the Boot Actions page in order to automatically pre-populate the Boot Action Setup information.



2. To pre-populate the Boot Action Setup information automatically, select the linked Host entry for the remote machine to which you want to deploy the Scripted Installation and then click Set Boot Action(s) for this system.

3. To enter the Boot Action Setup information manually, select Add New Item from the Choose action drop-down list. The Boot Action Setup page appears.


In the process of disk imaging and deployment, you can boot either a remote machine, or a remote machine to a UNIX shell. This gives you the ability to create partitions or set up devices on the remote machine.

The shell offers you a Linux prompt, from which you can run any of the Linux utilities that you would normally use to create partitions or perform other tasks. Most Linux commands are available from the shell.

Systems Select the IP address of a KBOX 2000 node from the drop-down list.

MAC Addresses (Automatically populated) The unique MAC address of the remote machine in hexadecimal format: xx:xx:xx:xx:xx:xx.




The imaging boot action that you defined appears in the Boot Actions list and the next time the remote machine boots, you can capture an image of the remote machine

When the imaging is complete, the remote machine image will appear in the Image Library.

The next step is for you to physically go to the remote machine and reboot it. It will automatically reboot to either the Boot Menu or to the Windows Deployment and Recovery Console or Linux Deployment and Recovery Console.

To capture an NTFS or sector-based image from the remote machine Boot Menu:

1. Boot the remote machine. The KBOX Boot Menu appears.

2. Highlight Linux Deployment and Recovery Console.

3. Click the KBOX Imaging icon.

4. Type 1 and press Enter to capture an image of the remote machine to the KBOX 2000.

5. Enter a name for this image and press Enter. This name will appear later in the System Images, which is present in Deployment tab. The list of images captured is displayed in the Linux Deployment and Recovery Console when the user chooses the Deploy image to this machine from the KBOX option.

First Boot Action:

Show Boot menu Displays the Boot Menu after booting.

Boot from Local Hard Drive

Boots from the Local Hard Drive.

Automated Scripted Installations

Select a Scripted Installation from the list.

Automated K-image Deployment

Select a K-image from the list.

Default KBOX Client Environment

Select a client environment from the list.

Other KBOX Client Environments

Select a client environment from the list.

Number of Boots Enter 0 to always perform this action the next time the system boots. Enter any other number and the KBOX 2000 performs the boot action for that many boots, and then performs the next action listed below.



6. You have the following options when capturing a disk image:

The remote machine imaging will proceed. Status will be displayed on the remote machine to let you know how the imaging is progressing.

When completed, the captured image will appear later in the System Images, which is present on the Deployment tab. The list of images captured is displayed in the Linux Deployment and Recovery Console.

To capture a K-image from the remote machine Boot Menu:



3. Select Imaging on the Main Menu.

4. Select Capture image of this machine to the KBOX.

5. Enter the image name in the Image Name field.

6. Select the drives to capture.

7. Click Start capture. The message “Image Capture Completed” is displayed.

8. Click OK.

9. The Capture log is displayed on the screen which includes information such as: number of files to copy, number of files copied and the elapsed time.

To deploy a NTFS or sector-based image from the remote machine Boot Menu:



3. Click the KBOX Imaging icon.

4. Type 2 and press Enter to Deploy image to this machine from the KBOX 2000. A List of captured images is displayed.

5. Type the appropriate image number and press Enter.

The image gets deployed on the machine.

Full DiskNTFS Optimized

Type 1 and press Enter to capture an image of an entire NTFS disk. This option will only work for disks that have an NTFS file type. This optimized option cap-tures and saves each partition on the disk one partition at a time. As a result, the capture may be faster and more efficient than Option 2, the sector-based capture.

Full Disk Sector-based

Type 2 and press Enter to capture an image of an entire disk. This option will work for any disk file type. This option will be slower than Option 1.

Single PartitionNTFS Only

Type 3 and press Enter to capture an image of a single NTFS partition on a disk. This option will only work for partitions that have an NTFS file type. You will be prompted to identify the partition.If you need to set up partitions on the remote machine, you can do so from the Boot Menu.



To deploy a K-image from the remote machine Boot Menu:



3. Select Imaging on the Main Menu.

4. Select Deploy image of this machine to the KBOX.

5. Select the image name from the Image Name drop-down list.

6. Select Restart Automatically after Deployment check box to reboot the machine automatically after deployment.

7. Click Start deploy. The message “Image Deploy Completed” is displayed.

8. Click OK.

The Deploy log is displayed on the screen which includes information such as: number of files to copy, number of files copied and the elapsed time.

Deploying a System Image to a Non-networked Computer with a USB DriveYou can download a system image to a USB drive and then use the USB drive to deploy it to a computer. This is most useful for systems on closed networks, or systems that for whatever reason do not have network access. To do this, you need to perform these tasks:

• Download a KPE image to the USB drive.

• Download a K-Image to the USB drive.

• Physically carry the USB drive over to the non-networked system.

• Deploy the system image to the non-networked system by booting from the USB drive.

Detailed instructions for this process are in the KBOX 2000 online help. Browse to the Systems Deployment Console > Deployments > System Images > (select a system image). Then select this link:

The instructions for creating a USB drive with a system image appear on the USB Flash Drive Installer page:

This method is significantly slower than the standard (networked) system image deployment.



Follow the instructions on the USB Flash Drive Installer page to create a bootable system image on a USB drive and deploy it on a computer. Some additional notes on the process:

• The USB drive is formatted during this process, so dedicate a USB drive for this purpose.

• Once you put a system image on a USB drive, you can use it to deploy the system image as many times as you want.

• Remember to make the boot from USB drive a one-time event. Otherwise the system will try to boot from the USB drive each time it is rebooted.

• After you create USB drive images for the KPE and K-image, you can use install_bat usb_drive_letter commands to add them to another USB drive at any time.

Deleting a DeploymentYou can delete a deployment before the next boot on the remote machine.

To delete a deployment

1. Browse to the KBOX Systems Deployment Console Deployments > System Images.

2. Check the deployment or deployments you want to delete.


4. Click OK to delete the deployment or click Cancel to cancel the deletion.

Managing ImagesYou can manage the Images as follows:



Deleting an Image

To delete an image from the Image library:

1. Browse to the KBOX Systems Deployment Console > Deployments > System Images. The Image Library page appears.

2. Check the image or images you want to delete.


4. Click OK to delete the deployment or click Cancel to cancel the deletion.

Applying a label to an imageLabels can be used to organize and categorize your Images. You must first create labels before you can apply then to your Images.




2. Check an Image or Images.

3. To apply a label, select the label you want to apply from the Choose action drop-down list.

4. To remove a label, select the label you want to remove from the Choose action drop-down list.

Viewing and Editing Image Details1. Browse to the KBOX Systems Deployment Console > Deployments > System Images.


2. Click the System Image for which you want to view or edit details.

The System Image Detail page appears.

3. This page displays following information:

Image Name Displays the name of the System Image. You can change the name of the System Image.

Image Type Displays the type of System Image. For example, K-image. This is a read-only field.

Total Size Displays the size of the image. This is a read-only field.

Version Displays the image version. This is a read-only field.

Image Status Displays the status of the System Image. For example, Completed Upload. This is a read-only field.

Created Displays the date and time that the System Image was first created. This is a read-only field.

Modified Displays the date and time that the System Image was last modified. This is a read-only field.



4. Click Browse Files to browse files in the System Image.

The File Browser appears. For more information, see Managing system image files.

5. Click Deploy this System Image to a System to deploy this System Image to a specific system.

The Boot Action Setup page opens. For more information on how to deploy a system image, see Deploying a K-image.

6. Select appropriate action from the Preinstallation Task Error Handling drop-down list:

Harvested From Displays, in hexadecimal format (xx:xx:xx:xx:xx:xx), the unique MAC address of the remote machine whose image is captured. Click MAC address to view the system detail of the remote machine.

Harvest Started Displays the date and time when the image capture process started. This is a read-only field.

Harvest Completed

Displays the date and time when the image capture process completed. This is a read-only field.

Manufacturer Displays the name of the manufacturer of the remote machine.

Model Displays the model details of the remote machine.

Notes Enter description regarding this system image, if any.

Labels Select a label that you want to apply to the System Image. Press CTRL and click labels to select more than one label.

Deploy Options Remove local files not in image

Select this option to remove all newly created files from the remote machine after the K-image is captured.

Force continue on errors Select this option to continue the deployment process even if errors occur.

Include debug output in log

Select this option to include a debug output in the log after the K-image is deployed.

Enable Sysprep Integration

Select this option to run Microsoft’s System Preparation utility for Windows OS deployment. For details, see Using sysprep with K-images.

Installation Plan With the Installation Plan section, you can add or remove pre-installation and post-installation tasks for this System Image. For more information, refer “Man-aging Pre- and Post-installation Tasks,” on page 110.

Continue on Errors Ignore any pre-installation task failures and continue without prompting you.

Prompt on Errors Prompts you to abort or continue with the deployment in case any pre-installation task fails.

Halt on Errors Directly aborts the deployment if any pre-installation task fails.




Managing system image filesClick Browse Files on a System Image detail page to browse files in the System Image. The File Browser appears. Click C: to browse for files located in the C drive. Hover the mouse over a file or directory name to view options for renaming, replacing and removing a file or directory.

To add a file:

1. Click the icon to add a file.

2. Click Browse and locate the file.

3. Click Submit.

To add a directory:

1. Click the icon to add a directory.

2. Specify the directory name in the name field.

3. Click Submit.

To rename a file or directory:

1. Click the icon to rename a file or directory.

2. Specify the new name in the Rename to field.

3. Click Submit.

To remove a file or directory:

1. Click the icon to remove a file or directory.

2. Click OK in the confirmation dialog box.

To download a directory:

Directories are recovered in zip format from the System images. To do so,



You have the following options available only if the System Image is of type K-image:

• Browse Files

• Pre-installation Task Error Handling

• Deploy Options

• Installation plan



2. Click the name of the K-image which has the directory you wish to recover.


3. Click the Browse Files to browse to the directory you wish to recover from the available directories in the System K-image.

4. Click the icon besides the directory to be recovered. In the Directory Download dialog that appears

click the Save to download the directory

To replace a file:

1. Click the icon to replace a file.

2. Click Browse and locate the new file.

3. Click Submit.

After making any changes, the Image Status field displays the message “Files updated; revert or commit changes before deployment”. Click Commit Changes to save the changes you have done to the image, or click Revert Changes to undo the changes you made.

To download a file:

The KBOX 2000 provides an option to recover files from the System Images that were previously created and stored on your KBOX 2000. To do so,



2. Click the name of the K-Image which has the file you wish to recover.


3. Click the Browse Files to browse to the file you wish to recover from the selected K-Image.

4. Click on the file name you wish to recover. In the File Download dialog that appears, click the Save button to save the file.

Deploying a K-imageYou can deploy a System Image of the type K-image to a remote machine and specify the Boot Action setup.



Directory is downloaded in .zip format on desktop of local machine.

The file is saved on the desktop of the local machine by default.



2. Click the System Image you want to deploy to a remote machine.


3. Click Deploy this System Image to a System.


4. Enter the Boot Action Setup information as follows:

5. Click Next.

The System Deployment list page appears.

The boot action that you defined now appears in the Boot Actions list. You reboot remote machine manually to deploy the K-image.

Using sysprep with K-images This option is required for trouble-free deployment of images that use Sysprep. It delays the execution of post-installation tasks until the Sysprep utility has completed. You do this for K-images by enabling the Enable Sysprep Integration deployment option.

To do this you will:

• Configure Sysprep on the target node.

• Capture the K-image created using sysprep utility.

• Configure the K-image for sysprep integration.

• Deploy the K-image.

To configure sysprep on target node:

The System Preparation tool (Sysprep) is a technology that you can use to install Microsoft Windows operating systems with minimal intervention by an administrator.

Refer to link http://support.microsoft.com/kb/302577 for using sysprep tool for creating image based installations.

Systems Select the IP address of the remote machine from the drop-down list.

MAC Addresses The unique MAC address of the remote machine in hexadecimal format: xx:xx:xx:xx:xx:xx. is populated on the basis of selected IP address of the remote machine.

First Boot Action To deploy a K-image, select the appropriate image name under Automated K-image deployments from the First Boot Action drop-down list. This Boot Action executes at the next machine boot.

Number of Boots Enter 0 to perform this action at boot. Enter any other number for the KBOX 2000 to perform the specified boot action for that many boots, and then per-form the next boot action described below.

Next Boot Action You can select any action that you want to perform during the next (subsequent) boot. You can refer to the examples listed for First Boot Action.

Number of Boots Input a number for the KBOX 2000 to perform the boot action for that many boots, and then revert to displaying the System Deployment Boot Menu. Input 1 to perform this action at the next boot.


http://support.microsoft.com/kb/302577


To capture the K-image created using sysprep utility:

Refer to To capture a K-image from the remote machine Boot Menu: for capturing the image created after the execution of sysprep utility.

To configure the K-image for sysprep integration:



2. Click the specified K-image created using sysprep utility.

3. Select the check box “Enable Sysprep Integration”

4. Click Save.

You can associate any post-installation tasks to the K-image. Refer to Managing Pre- and Post-installation Tasks to associate the post-installation task to the K-image.

Deploying the K-image:

See Deploying a K-image for details regarding deploying the K-image.

Post-installation tasks are executed only after the sysprep utility is executed on the target machine.


C H A P T E R 13

Deploying Software Components from a Remote Site Appliance

This section explains the KBOX 2000 Remote Site Appliance (RSA) feature which you use to deploy Boot Environments, System Images, Scripted Installations, and User States from a remote virtual system. This feature is useful if you administer numerous remote systems that are clustered in locations with generally weaker network connections.

This chapter assumes that you have already followed the instructions in the Introducing Your KBOX 2000 Systems Deployment Appliance and Configuring Your KBOX 2000 chapters and installed and configured your KBOX 2000.

About Remote Site AppliancesRemote Site Appliances (RSAs) function as virtual remote shares that deploy the same software components that KBOX 2000 Series appliances do. An RSA is useful if you have a group of nodes with better bandwidth connections between each other, than they do to your KBOX 2000. Once installed and configured, you use the RSA Remote Site Console to deploy KBOX 2000 software components to nodes with slow or unreliable network access to your KBOX 2000.

You run an RSA on either the Sun Microsystems Inc. VirtualBox or the VMware Inc. OVF virtual machines. When you download the RSA software you choose one of these virtualization products to use. You will need to consult their product documentation during the RSA configuration process.

131


Figure 13-1: The RSA Remote Site Console

To set up and use an RSA, you:

• Download the RSA installer program to a target node which will serve as the RSA host.

• Link the RSA target node to a KBOX 2000. For details, see the Linking KBOX 2000 Series appliances section.

• Install and configure an RSA on the target node. Many aspects of setting up and configuring an RSA are similar to setting up a KBOX 2000.

• Log into a console on the target node and configure network settings.

• Use the KBOX 2000 Deployment Client to complete the configuration.

• Configure your DHCP server to direct the nodes to RSA to boot.

• Synchronize the RSA with its linked KBOX 2000 to automatically download the KBOX 2000 appliance’s default Boot Environments, System Images, and Scripted Installations as bootable ISO files.

• Upload any other KPEs, Scripted Installations, or System Images from the KBOX to the RSA that you need.

• Finally, you deploy ISOs from the RSA console to selected select nodes.

If you change any Scripted Installations or K-Images on the KBOX 2000, you need to upload new ISOs to your RSAs.

When you upgrade your KBOX 2000 to a new release you also need to upgrade the RSA software. For details see the Updating RSA server software section.



RSA Target host system requirementsThe target host that you use for an RSA must meet these minimum requirements:

• It must be running one of these 32-bit operating systems:

• Windows XP SP2

• Windows 2003 Enterprise Server

• Windows 2003 Standard Server

• Windows Vista (32-bit only)

• It must be capable of hosting a 32-bit VMware session. KACE suggests using at least a 2 GHz system with 2 GB of RAM.

• It must have 200 GB of disk space available.

• The linked KBOX 2000 must be able to access the virtual appliance using SSH on port 22 and HTTP on port 80.

• It must be able to access the KBOX 2000 using HTTP on port 80.

• KBOX Linking must be enabled on the KBOX 2000. For more details on KBOX Linking, see the Linking KBOX 2000 Series appliances section.

Creating an RSA on a Virtual SystemCreating an RSA includes these general steps:

• To install the RSA and virtualization software:• To configure and link your virtual KBOX:• To configure and sync an RSA:.• To set the RSA as your nodes’ boot device:

To install the RSA and virtualization software:1. Browse to the KBOX Systems Deployment Console > Deployments > Remote Sites page.

The Remote Sites page appears.

2. Select Choose Action... Download Remote Site Appliance Installer.

The Download Remote Site Application Installer page appears.

3. Follow the instructions on the Download Remote Site Application Installer page to download the installer to your KBOX 2000. You have the option of downloading either the VirtualBox or OVF virtual machines.

4. Follow the instructions on the Download Remote Site Application Installer page to copy the installer to a remote target Windows system.

5. Browse to the target Windows node.

6. Double-click the remote_site_installer.msi to start the installation.



7. After successful installation, click Close in the Installation Complete window.

8. In the Windows interface, click Start > Control Panel and select Network connections.

9. Press Ctrl and select Local Area Connection (your physical network adapter) and KBOX Host Interface (your virtual network adapter).

10. Right-click and select Bridge Connections.

11. Double-click the KBOX 2000 shortcut on the desktop to start it.

The Virtual Box window opens.

12. Right-click kbox_2000_extender and click Start.

The KBOX 2000 starts.

Your RSA and virtual software are now installed. Follow the instructions in the next section to finish the installation.

To configure and link your virtual KBOX:1. Configure this KBOX 2000. For details, see the Installing Your KBOX 2000 and Configuring Your KBOX

2000 chapters.

2. Open your browser, and browse to the URL for the KBOX 2000 (http://KBOX_name/admin).

3. Login to the Systems Deployment Console with these credentials:

Login: Admin Password: Admin

4. Link this Virtual KBOX to the KBOX 2000 server. For details, see the Linking KBOX 2000 Series appliances section.

5. Configure this Virtual KBOX 2000 to function as a remote appliance. Refer to To configure and sync an RSA:.

Your RSA is now set up and ready to configure.

Consult the Sun Microsystems Inc., or VMware documentation for instructions on installing the virtual machine product you have chosen.

Disable the Windows firewall on the remote Windows machine before configuring the network connections between the remote Windows machine and Virtual machine.

For more details on Virtual Box, refer to www.virtualbox.org


www.virtualbox.org


To configure and sync an RSA:This section assumes that you have followed the instructions in the Creating an RSA on a Virtual System section to install and start an RSA, and are now ready to configure it.

Before you begin you need the IP addresses of the nodes this RSA will administer.

1. Browse to the KBOX Systems Deployment Console > Deployments > Remote Sites page.

The Remote Site Appliances page appears.


The Add a Remote Site Appliance page appears.

3. Select the RSA to configure from the Remote Site Appliance drop-down list.

4. Click Next.

The Remote Site Detail page appears.

5. The following details are displayed:

6. In the Transfer Rate Limit area, specify the following:

7. In the Update Scheduling area, specify the following,

8. In the Scripted Installations area, select the Scripted Installation(s) to require for the RSA.

The KBOX 2000 and RSA versions of each Scripted Installation are displayed.

9. In the System Images area, select the system image(s) to require for the RSA.

The KBOX 2000 and RSA versions of image are displayed.

10. In the Boot Environment area, the default boot environments are already selected.

The KBOX 2000 and RSA versions of the boot environments are also displayed.

11. In the Dependencies area, click Show to see the list of dependencies selected for this RSA. The dependencies are automatically selected based upon the pre-installation tasks, post-installation tasks and Source CDs.

12. Click Save. You can click Save and Sync to save the changes and immediately sync the RSA.

Hostname (Read-only) The IP address of the RSA.

Created (Read-only) The date and time when the RSA was first created.

Modified (Read-only) The date and time when the RSA was last modified.

Last Sync (Read-only) The date and time when the RSA was last synced.

Status (Read-only) The status of the RSA sync.

Limit average trans-fer rate to

(Optional) Select the check box and specify the value in KB/sec. For details, see the To specify the bandwidth limit for RSA synchronization: section.

Update Remote Site Manually

Select to update RSA manually.

Update Remote Site specific day at HH:MM AM/PM

Select to update the RSA automatically on the specified day and time.



To specify the bandwidth limit for RSA synchronization:

You can specify a bandwidth limit to restrict the network resources that your KBOX 2000 uses to synchronize the Scripted Installations, System Images, Boot Environments, and associated dependencies with an RSA. This optional feature is most useful if you want to synchronize RSAs with your KBOX 2000 during normal working hours. Without a bandwidth limit, your KBOX 2000 tries to synchronize as fast as possible, which can adversely affect network performance for the people working at the remote site. Especially if the network connection is slow to begin with. You will have to experiment to find the optimal bandwidth limit for each remote site.

This section assumes that you already have followed the instructions in the Creating an RSA on a Virtual System and To configure and sync an RSA: sections and have an RSA created and configured.

1. Browse to the KBOX Systems Deployment Console > Deployments > Remote Sites.


2. Click the hostname of the RSA.


3. Select the Limit average transfer rate to check box and specify the value for the transfer rate in KB/sec.

4. Select the Scripted Installations, System Images, or Boot Environments that you want to sync and click on Save and Sync.

The selected items start synchronizing with the RSA. When the sync is complete, your default boot environments are automatically available as ISO files on the RSA.

To set the RSA as your nodes’ boot device:You need to configure your DHCP server to use the RSA as the boot device for the nodes it administers.

You need to know the IP addresses of the nodes to administer before you start.

rsync is used to synchronize items with remote appliances. The speed of transfer of the items is controlled by the use of bandwidth limit parameter bwlimit of rsync. The value of bandwidth limit parameter is equal to the value specified by the user in the field Limit average transfer rate to.



If you use the RSA DHCP server:

1. Browse to RSA Systems Deployment Console > Settings & Maintenance > Network Settings.

The KBOX Settings: Network page appears.

2. Select Edit Mode.

The fields become editable.

3. Select the Enable On-Board DHCP Server check box.

The DHCP Pool Start and DHCP Pool End boxes appear.

4. Enter the IP address range (scope) that matches the nodes for this RSA to administer.


If you use your own DHCP server:

Follow the instructions in the Step 4 - Configuring Your DHCP Server section of the Installing Your KBOX 2000 chapter to configure your DHCP server to use the RSA as the boot device for the nodes it administers. See your DHCP server documentation for details.

This completes the installation process. You can start deploying software components from the RSA to your nodes, or create and upload ISOs for any of the other boot environments that your nodes require.

Downloading Software Components to an RSAThe sync operation you performed as part of the To configure and sync an RSA: section automatically downloaded the KBOX 2000 Series appliances’ default boot averments for all platforms. You almost certainly need to upload more boot environments and other software components from the KBOX 2000 to an RSA as you need, create, or update them. The steps in this section explain how.

1. Browse to KBOX Systems Deployment Console > Deployments > Remote Sites.

The Remote Sites Appliances page appears.

2. Select a remote site from the list.

The Remote Detail Site page appears. The software components already installed on the RSA are shown with blue highlighting and a checkmark.

If you had previously managed these nodes from a different DHCP server, be sure to remove them from that server’s scope to prevent DHCP server conflicts. This includes the KBOX DHCP server.



3. Select the check boxes of additional software components to add to the RSA. The pre- and post-installation tasks are listed under the Dependencies (Hidden). Select Show to view and select them.

4. Select the Save and Sync button.

The software components you selected are copied to the RSA. This may take a few minutes depending on the size of the software components you are syncing and the speed of the network connection.

Transferring Boot Environments to RSAs Using a CD or USBYou can configure the RSA system to start in a specific KBOX 2000 Pre-installation Environment (KPE). You first need to replicate the Scripted Installations, Boot Environments, System Images on the RSA before using them on the target machine.

Follow these general steps to create a bootable ISO, USB drive, or UFD for an RSA:

• Create a bootable ISO or UFD image from an RSA.

The bootable drive still requires a network connection to the KBOX 2000 to deploy the KPE. If the target system does not have a network connection, see the Deploying a System Image to a Non-networked Computer with a USB Drive section. Note that a non-networked deployment is significantly slower than a networked deployment.



• Create a bootable ISO, USB flash drive image, or UFD image for the specified RSA.

• Select the specified Scripted Installations, System Images, Boot Environments, and Sync with the Remote Appliance Site.

• Create a bootable CD or UFD image of the RSA.

• Boot the target machine using bootable ISO or UFD image of the RSA.

To create a bootable ISO or UFD image from an RSA:

1. Browse to the KBOX Systems Deployment Console > Deployments > Remote Sites.


2. Click the RSA you want to create bootable ISO or UFD image for.


3. In the Boot Environments section:

a Select the Create bootable ISO images for this Remote Site check box for creating the bootable ISO.

b Select the Create bootable USB flash drive images for this Remote Site checkbox for creating a bootable UFD image.

4. Click Save.

5. Select Deployments > Remote Sites.


6. Click the RSA you want to create bootable ISO or UFD image from.


7. Select the required Scripted Installations, System Images, or Boot Environments.

8. Click Save and Sync.

This replicates the software components on the RSA.

9. After sync is complete, the Remote Site Detail page displays Download bootable ISO for specified version of KPE and Download bootable USB flash drive for specified version of KPE options.

10. Download the bootable ISO or UFD image on CD-ROM or USB drive.

To create a bootable CD or UFD image of RSA:

1. Insert the CD or USB in the remote machine where you have downloaded the bootable ISO or UFD image.

2. Create a bootable CD or UFD from downloaded ISO or UFD image.

To boot the target machine using bootable ISO or UFD image of the RSA:

To boot the target machine into specified KPE version of RSA, boot the target machine from the bootable CD or UFD created in the step above.

Refer to readme.txt available with the downloaded UFD image for creating a bootable UFD.



Administering RSAsThis section explains the tasks you will use to view, edit, update, delete, and troubleshoot RSAs.

To view or edit the RSA details:1. Browse to the KBOX Systems Deployment Console > Deployments > Remote Sites.


2. Select an RSA from the list to view or edit.


3. The following RSA details are displayed:

4. In the Update Scheduling area specify the following,

5. In the Scripted Installations area, select the required script(s). The current version and the remote version of a script is displayed.

6. In the System Images area, select the required system image(s). The current version and the remote version of a image is displayed.

7. In the Boot Environment area, the default boot environments are already selected. The current version and the remote version of a boot environment is displayed.

8. In the Dependencies area, click Show to see the list of dependencies selected for this RSA. The dependencies are automatically selected depending upon the pre-installation tasks or post-installation tasks and Source CDs.

9. Click Save. You can click Save and Sync to save the changes and immediately sync the RSA.

Updating RSA server softwareWhen you update your KBOX 2000 release level, you also need to manually or automatically update your RSA server software.

Hostname (Read only) The RSA IP address.

Created (Read only) The date and time when the RSA was first created.

Modified (Read only) The date and time when the RSA was last modified.

Last Sync (Read only) The date and time when the RSA was last synced.

Status (Read only) The status of the RSA sync.

Update Remote Site Manually

Select to update RSA manually.

Update Remote Site specific day at HH:MM AM/PM

Select to update the RSA on the specified day and time.

If you change an RSA IP address, you also must sync the RSA before deploying any software components.



To Automatically update an RSA server

You update the RSA installer from the KBOX 2000 Settings & Maintenance > Server Maintenance page:



2. Following details are displayed under the Automatic Remote Site Appliance Installer Update area:


4. Click Check for RSA Installer Updates to download the latest version of the remote_site_installer.msi utility.

To Manually update an RSA server

Update the RSA Installer manually from the KBOX 2000 Settings & Maintenance > Server Maintenance page.




3. Under the Manually Update Remote Site Appliance Installer area, click Browse to select the update file.

4. Select the update file downloaded from www.kace.com and click Open.

5. Click Update RSA Installer to upload the RSA Installer. The update status is displayed as Completed in the Update Status field.

To delete an RSA:1. Browse to the KBOX Systems Deployment Console > Deployments > Remote Sites.


2. Select the check box for the remote site appliance(s), and then select Delete Selected Item(s) from the Choose action drop-down list.

3. Click OK.

4. Select Remote Site Console from the Organization drop-down list.

5. Select KBOX Settings & Maintenance > Control Panel.


6. Click Remote Site Settings.

The KBOX Settings: Remote Site page appears.

Update Status (Read only) The status as Completed after downloading the remote_site_installer.msi utility.

Checksum (Read only) The checksum for the remote_site_installer.msi utility.

Last Check (Read only) The date and time of the last check performed.


www.kace.com



8. Select Clear Configuration to clear configuration settings for this remote site.

The RSA is now deleted successfully. Be sure to also reconfigure your DHCP server to use a different boot device for the nodes that RSA used to administer.

Troubleshooting RSA operationsThis section provides information to help you avoid common problems using RSAs.

Problems syncing your KBOX 2000 with an RSA

If you encounter a problem syncing information between your KBOX 2000 and an RSA:

• Ensure that you have ports 22 and 80 configured correctly. For details, see RSA Target host system requirements.

• Ensure that your KBOX 2000 is linked to the RSA.

• If you get this error message:

Error occurred syncing file list: exit code = 12

The RSA and the KBOX 2000 are not properly linked. To solve this problem:

1. Browse to the RSA Systems Deployment Console > Settings and Maintenance > Control Panel > KBOX Linking.

Confirm that the Enable KBOX Linking box is checked.

2. In the KBOX Friendly Name (this server): field, enter either the RSA IP Address or a fully qualified hostname.

3. Browse to the KBOX Systems Deployment Console > Settings and Maintenance > Control Panel > Managed Linked Appliances.

4. Open each linked profiled and make sure that Host Name field has either the correct IP Address or fully qualified hostname of the linked system.


C H A P T E R 14

Recovering Corrupted Nodes

This section explains how to use the KBOX 2000 remote recovery features to repair and restore corrupted nodes.

Performing Recovery on Corrupted NodesThe KBOX 2000 enables remote emergency recovery of systems that are unable to boot to their local hard drives.

The recovery features include:

• Remote Recovery Consoles for Windows and Linux systems.

• Support for third-party, pre-installation environments such as WinPE and KNOPPIX.

• Remote control integrated into Recovery Console to speed repair of corrupted systems.

• Agent-less, PXE-based design allows for remote recovery of any LAN-connected desktop, laptop, or server

You can also import and use your own KNOPPIX Recovery Console or Windows PE Source CD to the KBOX 2000. A KNOPPIX Recovery Console is bundled with the KBOX 2000, but you may use your own and add it to a KBOX 2000 Scripted Installation if you prefer. Your KNOPPIX Recovery Console then become an option in the KBOX 2000 Administrator Console and in the Client Boot Menus. See Using Scripted Installations to Deploy Software Components for more information.

Recovery Process OverviewWhen performing a remote recovery, you will follow these general steps:

• Set up the target node to boot to the Boot Menu or a Recovery Console - In this step, you will set up the corrupted node to boot to one of these KBOX 2000 tools:

• Boot Menu

• Windows Deployment and Recovery Console

• Linux Deployment and Recovery Console.

For details See Setting up the corrupted node for recovery.

143


• Access the Recovery Console Using VNC - After you have booted the node to a Recovery Console, you can access it from the KBOX 2000 Systems Deployment Console using the KBOX 2000 on-board Virtual Network Computing (VNC) software. See Recovery from the Administrator Console using VNC.

Setting up the corrupted node for recoveryThe first step in recovering a corrupted node is to set it up to boot using the Boot Menu or directly using the Windows Deployment and Recovery Console or Linux Deployment and Recovery Console.

To set up the target node for recovery:




• Select the corrupted node from the Boot Actions list on the Boot Actions page in order to automatically pre-populate the Boot Action Setup information.



2. To pre-populate the Boot Action Setup information automatically, click the linked Host entry for the corrupted node to which you want to deploy the Scripted Installation and then click Set Boot Actions for this system.






Systems Select the IP address of the corrupted node from the drop-down list.

MAC Address The unique MAC address of the node in hexadecimal format: xx:xx:xx:xx:xx:xx. is populated on the basis of selected IP address of the target node.

First Boot Action If you want to boot to the Boot Menu, select Show Boot Menu from the First Boot Action drop-down list.If you want to boot directly to Windows Deployment and Recovery Con-sole or Linux Deployment and Recovery Console, select the appropriate option from the First Boot Action drop-down list.

Number of Boots Input 0 to always perform this action at boot. Input any other number and the KBOX 2000 performs the boot action for that many boots, and then perform the next action listed below.

Next Boot Action You can select any action that you want to perform during the next (subse-quent) boot. You can refer to the examples listed for First Boot Action.

Number of Boots Input a number and the KBOX 2000 performs the boot action for that number of boots, then reverts to displaying the System Deployment Boot Menu. Input 1 to perform this action at the next boot.



The next step is for you to physically go to the corrupted node and reboot it. It automatically reboots to one of: the Boot Menu, the Windows Deployment and Recovery Console, or the Linux Deployment and Recovery Console.

Recovery using the Windows Deployment And Recovery Console1. Boot the corrupted node. The KBOX Boot Menu appears.


You can work with the Command Prompt by editing a file with notepad, editing the Registry, and editing the User’s Registry.

To work with the command prompt:

1. Select Recovery on the Main Menu.

2. Select Command Prompt.

The Command Prompt can be used to edit the registry (type regedit in the Command Prompt window), compare file sizes, search for files, and so on.

To edit a file with notepad:


2. Select Edit a File with Notepad.

3. To select a file, do one of the following:

• Click the file format you want in the Files of type box. You can also type the extension in the File name box.

• If you want to open a file that was saved in a different folder, locate and open the folder.

4. Click the file you want to open in Notepad. For example you can edit files like boot.ini, and so on for which no other editor is available.

5. Click Open.

6. Edit the file as required and then click Save in the File menu.

To edit the registry:


2. Select Edit the Registry. The Browse For Folder dialog box appears.

3. Select the folder that contains the registry to edit.

4. Click OK. A message showing the registry location is displayed.

5. Click OK. The Registry Editor is displayed.

Closing the registry folder commits your changes to the registry.



To edit a user’s registry:


2. Select Edit a User’s Registry.

3. Select the registry to edit in the Target Registry to Edit list.

4. Click Edit the Registry. A message showing the registry location is displayed.

5. Click OK. The Registry Editor is displayed.

recovery using the Linux Deployment and Recovery Console1. Boot the target node. The KBOX 2000 Boot Menu appears.


3. Click the KBOX 2000 Imaging icon.

4. Type 3 and press Enter to launch a shell to create partitions or setup devices.

You can also use basic Linux commands to perform tasks like recovering or copying data off of the machine, replacing corrupted drivers, and so on.

Recovery from the Administrator Console using VNCYou can use VNC from the Administrator Console to recover the target node. For more information on how to use VNC, see the Using VNC to Control Nodes section.

Closing the registry folder commits your changes to the registry.


C H A P T E R 15

Using the KBOX 2000 Deploy-ment Client

This section explains the KBOX 2000 boot menu and the Deployment Client that you run on the nodes themselves. You use these tools to perform boot actions, capture and deploy images, and Scripted Installations, and system recovery.

About the Boot MenuThe Boot Menu on the target machine allows you to perform tasks such as capturing and deploying images, deploying Scripted Installations, recovering the system, and so on.

The Boot Menu provides access to the Windows Deployment and Recovery Console and the Linux Deployment and Recovery Console.

For more information on the Windows Deployment and Recovery Console, refer to “Windows Deployment And Recovery Console (KPE),” on page 148.

For more information on the Linux Deployment and Recovery Console, refer to “Linux Deployment And Recovery Console (KNOPPIX),” on page 151.

Setting Up a Node To Boot The Boot MenuYou can set up a target node to boot the ‘Boot Menu’. The boot menu gives you access to the Windows Deployment and Recovery Console and Linux Deployment and Recovery Console.

To set up a machine to boot the Boot Menu:




• Select the node from the Boot Actions list on the Boot Actions page in order to automatically pre-populate the Boot Action Setup information.

147

Using the KBOX 2000 Deployment Client


The instructions for both methods are given below.

2. To pre-populate the Boot Action Setup information automatically, click the linked Host entry for the node to which you want to deploy the Scripted Installation, and then click Set Boot Action(s) for this system.




5. Click Next.

The System Deployment list page appears.

The boot action that you defined now appears in the Boot Actions list.

Windows Deployment And Recovery Console (KPE)The KBOX 2000 Windows Deployment and Recovery Console, also known as KPE (KBOX Pre-installation Environment), is an environment for performing various windows-based tasks on the Target Machine.


MAC Address The unique MAC address of the Target Machine in hexadecimal format: xx:xx:xx:xx:xx:xx. is populated on the basis of selected IP address of the target machine.

First Boot Action To boot to the Boot Menu, select Show Boot Menu from the First Boot Action drop-down list.

Number of Boots Input 0 to always perform this action at boot. Input any other number and the KBOX 2000 performs the boot action for that many times, before performing the next action listed below.


Number of Boots Input the number of times you need the node to boot before displaying the Sys-tem Deployment Boot Menu. Input 1 to perform this action at the next boot.



To bring up the KPE on a node:


2. Highlight Windows Deployment and Recovery Console.

The Windows Deployment and Recovery Console Main Menu appears.

You can perform the following actions with Windows Deployment and Recovery Console:

• View files and tasks using the File Browser

• Install a Scripted Installation

• Capture an image of the machine

• Deploy an image to the machine

• Edit a file with the notepad

• Edit the Registry and also edit a User’s Registry

• Collect the inventory and upload it to KBOX 2000

• Restart or shut down the machine

About the File BrowserThe File Browser displays a hierarchical structure of files, folders, and drives on your KBOX 2000. Using the file browser, you can copy, move, rename, and search for files and folders. Quick links on the toolbar



enable you to zip, unzip, unrar, or create an executable. You can also view all pre-installation and post-installation tasks by clicking the appropriate folder in the left-hand side pane.

To view the file browser:


2. Click File Browser. The file browser appears.

Scripted installationYou can install a Scripted Installation using the Main Menu.

For more information on installing a Scripted Installation from the Windows Deployment and Recovery Console, see the To deploy a Scripted Installation from the Windows Deployment and Recovery Console: section.

ImagingYou can capture an image of the machine and also deploy image to the machine.

For more information on capturing an image from the Windows Deployment and Recovery Console, refer to the To capture a K-image from the remote machine Boot Menu: section.

For more information on deploying an image from the Windows Deployment and Recovery Console, refer to To deploy a K-image from the remote machine Boot Menu:.

RecoveryWith the Recovery option, you can work with Command Prompt, edit a file with notepad, edit the Registry, and edit a User’s Registry.

For more information on the various options and how to recover your system from the Windows Deployment and Recovery Console, refer to Recovering Corrupted Nodes.

Hardware InventoryYou can collect hardware inventory and upload it to the KBOX 2000.

To collect inventory and upload it to your KBOX 2000:

1. Select Hardware Inventory on the Main Menu.

2. Click Collect Inventory and Upload to KBOX.

The Hardware details are uploaded in Systems > System Inventory. The system starts gathering information, then contacts the server. The gathered information is displayed on the screen. The icon is displayed against the particular IP in the Network Scan Screen that comes under the Systems Tab.

Powering off the clientFollow these steps to power off the client:

To restart the machine:

Select Restart Machine on the Main Menu. The machine is restarted.



To shut down the machine:

Select Shut Down Machine on the Main Menu. The machine is shut down.

Linux Deployment And Recovery Console (KNOPPIX)The Linux Deployment and Recovery Console also known as the KNOPPIX, is an environment for performing various Windows or Linux based tasks on the target Machine.

To view the Linux Deployment and Recovery Console:



You can perform the following actions with Linux Deployment and Recovery Console:

• Capture an image of the machine

• Deploy an image to the machine

• Launch a Shell

• Reboot the machine

Capture a machine image on the KBOX 2000You can capture an image of the machine to the KBOX 2000.

For more information on how to capture an image from the Linux Deployment and Recovery Console, refer to the To deploy a NTFS or sector-based image from the remote machine Boot Menu: section.

Deploy image to this machine from the KBOX 2000You can deploy an image to this machine from the KBOX 2000.

For more information on how to deploy an image from the Linux Deployment and Recovery Console, refer to To deploy a NTFS or sector-based image from the remote machine Boot Menu:.

Launch a shell to create partitions and set up devicesYou can launch a shell to create partitions, set up devices, and perform other recovery tasks.

To launch a shell from the Linux Deployment and Recovery Console, refer to Recovering Corrupted Nodes.

Do nothing and rebootChoose this option if you want to do nothing and reboot the machine.

Linux Deployment and Recovery Console has been used throughout the document instead of the acronym KNOPPIX.



Defining A Boot EnvironmentThe client machine can be booted on your network using the server, and the options shown on the client machine can be deployed by defining the boot environments.

To define a boot environment:

1. Browse to the KBOX Systems Deployment Console > Deployments > Boot Environments.


2. Select Add New Item from the Choose action drop-down list. The Create a Boot Environment page appears.


These details will be used as the basis for this Boot Environment.

4. Click Next.

This may take a few minutes. The Boot Environment Status will read “Completed” after creating the Boot Environment.

5. Click Next.

You have the following options when creating a Boot Environment:

• Setup a System to load this Boot Environment: You can use the KBOX 2000 wizard to set up a system to load this boot environment. Refer “Setting up a system to load this boot environment,” on page 152.

• Create another Boot Environment: You can create another boot environment. Refer “Creating another boot environment,” on page 154.

• View this Boot Environment’s Details: You can view this Boot Environment’s Details. Refer “Viewing boot environment details,” on page 154.

Setting up a system to load this boot environment1. Click the Setup a System to load this Boot Environment link. The Boot Action Setup page

appears.


Name Enter a descriptive name for the boot environment. This name will be referred to in the KBOX 2000 boot menu.

Source CD Select the source CD from the Source CD drop-down list.


MAC Addresses The unique MAC address of the Target Machine in hexadecimal format: xx:xx:xx:xx:xx:xx. is populated on the basis of selected IP address of the target machine. You can supply one or more MAC Addresses.



3. Click Next. The Boot Actions page appears.


4. Enter a host name in Host Name.

For information on how to set boot actions, see Setting Boot Actions.

To delete a boot environment:



2. Select the check box beside the boot environments(s), then select Delete Selected Item(s) from the Choose action drop-down list.


You can also delete the boot environment from the Boot Environment Detail page.

To view the boot environment details:



2. Click on the boot environment you wish to view from the list.


First Boot Action If you want to boot using the Boot Menu, select Show Boot Menu from the First Boot Action drop-down list.If you want to boot from the local hard drive, select Boot from the Local Hard Drive from the First Boot Action drop-down list.If you want to boot using automated Scripted Installations, select the appropri-ate Scripted Installation under Automated Scripted Installations from the First Boot Action drop-down list.If you want to boot using default KBOX 2000 client environments, select the appropriate option under Default KBOX Client Environments from the First Boot Action drop-down list.To boot using other KBOX 2000 client environments, select the appropriate option under Other KBOX Client Environments from the First Boot Action drop-down list.

Number of Boots Input 0 to always perform this action while booting. Input any other number and the KBOX 2000 performs the boot action that many times, then performs the next action listed below.


Number of Boots Input a number and the KBOX 2000 performs the boot action that many times, then revert to displaying the System Deployment Boot Menu.Input 1 to perform this action at the next boot.



To duplicate boot environment details:



2. Click on the boot environment you wish to duplicate from the list.


3. Click Duplicate.

Creating another boot environmentTo create another boot environment:

1. Click the Create another Boot Environment link. The Create a Boot Environment page appears.


These details will be used as the basis for this Boot Environment.

3. Click Next.

The Boot Environment is complete when the Status changes to Completed.

4. Click Next.

You have the following options when creating a Boot Environment:

• Setup a System to load this Boot Environment: You can use the KBOX 2000 wizard to set up a system to load this boot environment. Refer “Setting up a system to load this boot environment,” on page 152.

• Create another Boot Environment: You can create another boot environment. Refer “Creating another boot environment,” on page 154.

• View this Boot Environment’s Details: You can view this Boot Environment’s Details. Refer “Viewing boot environment details,” on page 154.

Viewing boot environment details1. Click the View this Boot Environment’s Details. The Boot Environments page appears.

2. Click on the boot environment you wish to view from the list. The Boot Environment Detail page appears.

3. The information is displayed as follows:

Name Enter a descriptive name for the boot environment. This name will appear in the KBOX 2000 boot menu.

Source CD Select the source CD from the Source CD drop-down list.

Name Displays the name of the boot environment you entered. You can change the name of the boot environment.

Type Displays the type of boot environment. This is a read-only field.

Source CD Displays the source CD used for this boot environment. This is a read-only field.



4. Select one of these options:

a Select Setup a System to load this Boot Environment to set up this boot environment to a system. For more information on how to set up a boot environment, refer to “Setting up a system to load this boot environment,” on page 152.

b Select the Download a bootable ISO for this Boot Environment checkbox to download the KBOX 2000 Pre-installation Environment (KPE) as a bootable ISO file. This file can be burned onto a CD and used to boot a machine to KPE without enabling network booting.

c Select the Download a bootable USB flash drive image for this Boot Environment checkbox to download the KBOX Pre-installation Environment (KPE) as a bootable ISO file on a USB drive. The USB drive then can be used to boot a machine to KPE without enabling network booting.

Note: You must refresh this CD as network drivers are added or removed from your KBOX 2000, or if the KBOX 2000 IP address changes.

5. Click Save.

Created Displays the date and time when the boot environment was first created. This is a read-only field.

Modified Displays the date and time when the boot environment was last modified. This is a read-only field.

Status Displays the status of the boot environment. This is a read-only field.

Setup Configura-tion

This is a configuration file for WinPE or KPE. Click Hide or Show to hide or dis-play the setup configuration details.

WINBOM Configu-ration

This is also a configuration file for WinPE or KPE. Click Hide or Show to hide or display the WINBOM configuration details.

Factory (Driver Detection) Mode

Select the appropriate driver detection mode from the drop-down list.


C H A P T E R 16

Using the KBOX 2000 Reporting Tools

This section explains the reporting features of your KBOX 2000, including the system performance meters on the Home page of the Systems Deployment Console, and the default reports offered on the Reports tab. This chapter also explains how to edit a default report or create a new one.

Understanding the KBOX 2000 Reporting FeaturesThe KBOX 2000 Series includes integrated reporting tools to give you detailed statistical analysis of the Systems Deployment and installation tasks, and at-a-glance performance charts of system status. The KBOX 2000 2000 Series includes pre-configured default reports covering deployed system history, captured images, Scripted Installations, and other categories.

The Systems Deployment Console Reports tab has two sub-tabs, Reports and System Performance.You use the Reports sub-tab to:

• Output report information in your choice of HTML, PDF, text, comma-separated variable, and Microsoft Excel formats (html, .pdf, .txt, .csv, and XLS).

• Create new reports or customize existing reports with an intuitive web interface. The reports are defined as pre-generated SQL queries, and you can select the output format you want.

156


For details on the default reports see “Using the Default Reports,” on page 158.

You use the System Performance sub-tab to:

• View KBOX 2000 performance statistics on: Apache web server use, Disk Usage, MySQL use, Network use, Other usage, Processes, Samba process, and System processes.

The System Performance reports are Munin plugins and have a different format from the rest of the Administrator Console:



For more details on the System Performance reports see “Using the System Performance Reports,” on page 162.

Using the Default ReportsThe following sections explains the default KBOX 2000 2000 Series reports and how you can use, modify, or create your own reports.

Understanding the Report CategoriesBy default, KBOX 2000 2000 provides reports in the following categories:

• Imaging reports that show statistics on the system images that have been uploaded to or deployed by the KBOX 2000.

• A licensing report that shows how many nodes count against your KBOX 2000 license agreement.

• Recovery reports that show how many nodes have been booted from the KBOX 2000 Recovery Console.



• Scripted installation reports that show statistics on the Scripted Installations that have been deployed by the KBOX 2000.

Within each of the general categories mentioned above, there are various reports you can run to display information about the computers on your network. Each type of report you can run is described below.

To Run a Report select the output formatTo run any of the KBOX 2000 reports, just select the desired format type (HTML, PDF, CSV, TXT, or XLS) and the report starts running immediately. For HTML, PDF, and TXT formats, the report output is displayed in a new window. If you select CSV or XLS, you are prompted to open the output file or save it to your computer.

In this example we’re running the Image Capture Log report by selecting the HTML output format:

This is the HTML report output:

Category Report Description

Image Image Capture Log Displays a reverse chronological list of the system images that have been uploaded to your KBOX 2000.

Image Deploy Log Displays a reverse chronological list of the system images that have been deployed from your KBOX 2000.

Image Library Detail Provides a detailed report of every captured disk image sorted by image. This report includes the source, size, and the pre- and post-installation tasks involved.

Licensing KBOX 2000 License Usage Log

Displays a chronological order log of the first time each managed node booted from the KBOX 2000.

Recovery Recovery Console Boot Log

Displays a reverse chronological list of the machines that have booted a Recovery Console from the KBOX 2000 2000 Series.

Recovery Console Detail Displays a detailed report of every configured Recovery Con-sole sorted by name, providing listing of Source CD and con-figuration information.

Scripted Installation

Scripted Installation Detail Provides a detailed report of every configured Scripted Installation sorted by install. For each Scripted Installation, the report will list associated source and application information.

Scripted Installation Log Displays a reverse chronological list of the Scripted Installations that have been performed from the KBOX 2000 2000 Series.

Table 16-1: Default Reports



Creating and Modifying ReportsIf the default reports don’t meet your needs you can either create a new report from scratch, or copy an existing report and modify it. The KBOX 2000 reports use SQL to pull information out of the KBOX 2000’s Microsoft MySQL database.

The KBOX 2000 uses JasperReports’ open source JRXML Java format as the report output. To change the way your reports are formatted, use the JasperReports iReports tool. Information and documentation are available at http://jasperforge.org/.

To create a new report from scratch:

1. Browse to the KBOX Systems Deployment Console > Reports > Reports.

2. Select Add New Item from the Choose action drop-down. The Report Detail page appears.

3. Enter the following report details:

A strong knowledge of SQL is required to create or modify reports.

JasperReports format does not support field names using the <TABLE_NAME.FIELD_NAME> format. Either alias the field name, or just use <FIELD_NAME>. This is especially important in cases where the query has multiple fields with the same name, because JasperReports converts each of them to <FIELD_NAME>. In these cases it essential to have a different alias for each unique field name to generate correct output.

Title Enter a name for the report.


http://jasperforge.org/jaspersoft/opensource/business_intelligence/ireport/


4. Click Save

To edit an existing report:


2. Select Report Title of the report to edit.

The Report Detail page appears.

3. Edit the report details:

Report Category Enter the report category. If the category does not already exist, it is added to the drop-down list on the Reports list page when the report is saved.

Output File Name (Filled in by default) You can replace this with a different name if want.

Description Describe the information that the report will provide.

Output Types Select check boxes for the output formats to make available for this report.

SQL Statement Enter a SQL query statement to generate the report data. For reference, consult the MYSQL documentation.

Break on Columns Enter a comma-separated list of SQL column names. The report will generate break headers and sub totals for these columns. This setting refers to the auto-generated layout.

XML Report Layout Select this check box if you made changes to the SQL query. This option generates the XML Report Layout using the col-umns you specified.

Title Enter a descriptive name for the report. Can be any string.

Report Category Enter the report category. If the category does not already exist, it is added to the drop-down list on the Reports list page when the report is saved.

Output File Name (Filled in by default) Replace this with a different name if want.

Description Briefly describe the information that the report provides.

Output Types Select check boxes for the output formats you want available for this report.

SQL Statement Enter the query statement that will generate the report data. For reference, consult the MYSQL documentation.

Break on Columns Enter a comma-separated list of SQL column names. The report generates headers and sub totals for these columns. This setting refers to the auto-generated layout.

XML Report Layout Select this check box if you have changed the columns that are being returned by the query. This option generates the XML Report Layout using your columns.


http://dev.mysql.com/doc/refman/5.0/en/

http://dev.mysql.com/doc/refman/5.0/en/


To duplicate an existing report:


2. Select the Report Title of a report to duplicate.

The Report Detail page appears.

3. Click the Duplicate button.

4. (As needed) Select the Auto-generate Layout check box if you made any changes to the query

5. Modify the report details as necessary, then click Save.

Using the System Performance ReportsThe System Performance reports show information on these aspects of the KBOX 2000 activity. The System Performance reports are hard-coded and cannot be changed.

All System Performance reports show daily and weekly statistics by default. Select the report category to see the monthly and yearly views. The default System Performance reports show:

Report Category Subcategory

Apache Accesses

Processes

Volume

Disk usage Filesystem usage

Inode usage

MySQL Throughput

KBDB isam/myisam tablespace usage

Queries

Slow Queries

Threads

Network em0 traffic

em0 errors and colli-sions

Netstat

Other DHCP leases

Processes Number of processes

VMstat

Samba Samba status



To view the System Performance Reports:

1. Select Reports > System Performance.

The KBOX 2000 System Performance Report default view appears. This page displays the daily and weekly charts of the system performance reports for all categories.

2. (Optional) Select on of the report category links (Apache, Disk, Mysql, Network, Other, Processes, and Samba System) to add the monthly and yearly charts.

KBOX 2000 Administrator Home Page Summary ReportsThe KBOX 2000 Summary portion of the Administrator Console Home page provides information about the configuration and operation of your KBOX 2000 including:

• Deployment Statistics - Provides information on the activities that you have performed using your KBOX 2000.

• Disk Usage - Provides statistics on disk usage.

System CPU usage

Load Average

Memory Usage

Swap i/o



Figure 16-2: The KBOX 2000 2000 Home Page Reporting Tools

Daily Status EmailsKBOX 2000 automatically sends status emails at the end of each day to the KBOX 2000 2000 Series system administrator. You specified this address on the KBOX 2000 Settings and Registration > Registration and Licensing > Control Panel sub-tab in the Administrator Email field.


AA P P E N D I X

Deploying Windows Service Packs

This section lists the Windows Service Packs supported by your KBOX 2000, and explains how to install a service pack as a post-installation task.

Deploying Windows Service PacksYou can deploy specific Windows service packs using KBOX 2000. You need to upload the service pack to the KBOX 2000 server in order to deploy it to the target machines. For a list of the service packs, see the Supported Windows service packs section.

Supported Windows service packsFollowing Windows Service Packs can be installed using a KBOX 2000,

Windows 7

No service packs have been released yet.

Windows XP:

Windows XP Service Pack 1a

Windows XP Service Pack 2

Windows XP Service Pack 3

Windows XP x64 Edition:

Windows XP Professional x64 Edition Service Pack 2

Windows Server 2003:

Windows Server 2003 Service Pack 2

Windows Server 2003 R2 Service Pack 2

165


Windows Server 2003 x64 Edition:

Windows Server 2003 x64 Edition Service Pack 2

• Windows Vista:

Windows Vista Service Pack 1 (x86)


• Windows Vista x64 Edition:


Creating a service pack post-installation taskTo update your nodes with a Windows service pack, create a post-installation task for it and add it to a Scripted Installation or System Image. This section explains how to create a post-installation task for the service pack.

1. Browse to the KBOX Systems Deployment Console > Library > Post-installation Tasks.


2. Select Add New Service Pack Item from the Choose action drop-down list.


3. Specify the post-installation task details as follows:

4. Click Save to save the post-installation task details.

A window appears that provides the details on the status of the file upload.

Name Enter the name of the post-installation task.

Type Displays the type of post-installation task, Service Pack. This is a read-only field.

Select Service Pack

Select the service pack you want to deploy from the Select Service Pack drop-down list.

Download Ser-vice Pack Auto-matically.

Automatically downloads the service pack to your KBOX 2000 from the Microsoft web site when you save changes. If you have already downloaded the service pack to a local location, use the Upload Service Pack Manually option to upload it to the KBOX 2000.

Upload Service Pack Manually:

Uploads the service pack to your KBOX 2000 from a non-Microsoft location that you pick, usually a local cache. Click Browse to browse to the service pack loca-tion. The service pack is uploaded when you save changes to this post-installation task.

Command Line This field is automatically populated with the default command line options for the service pack. You can modify this command line to suit your organization’s needs. For some examples on customized command line switches, refer to Command Line Parameters for Windows Service Packs.

Notes: Enter any explanatory information, cautions, or reminders for the post-installation task.



Command Line Parameters for Windows Service Packs

Following are some examples of command line parameters that you can use for windows service packs,

Service Pack Example Command-line Parameters

Windows XP Service Pack 1a xpsp1a_en_x86.exe -u

Windows XP Service Pack 2 Windowsxp-KB835935-SP2-ENU.exe /quiet /norestart /o /n

Windows XP Service Pack 3 windowsxp-kb936929-sp3-x86-enu.exe /quiet /passive

Windows XP Professional x64 Edition Service Pack 2

Windowsxp-KB914961-SP2-x64-ENU /quiet /passive

Windows Server 2003 Service Pack 2

WindowsServer2003-KB914961-SP2-XXX-LLL.exe /quiet /passive

Windows Server 2003 R2 Service Pack 2

WindowsServer2003-KB914961-SP2-XXX-LLL.exe /quiet /passive

Windows Server 2003 x64 Edition Service Pack 2

WindowsServer2003-SP2-x64-ENU.exe /Q


Windows6.0-KB936330-X64-wave0 /unattend


de_en_es_fr_ja_windows_vista_service_pack_1_x86_72327.exe /quiet


A P P E N D I X B

Warranty, Licensing, and Support

Warranty And Support InformationInformation concerning hardware and software warranty, hardware replacement, product returns, technical support terms and product licensing can be found in the KACE End User License agreement accessible at:

HTTP://WWW.KACE.COM/LICENSE/STANDARD_EULA

Third Party Software NoticeKBOX 2000 TM is licensed per the accompanying Third Party License Agreements in addition to the KBOX 2000 license noted above. KBOX 2000 includes software redistributed under license from the following vendors. In addition, KBOX 2000 contains paid licences to MySQL and RLib that have been purchased and embedded within KBOX 2000 by KACE. Copyright 2004, KACE Networks, Inc. and other copyrights.

• Apache

• EZ GPO

• FreeBSD

• Knoppix

• Microsoft Windows

• OpenSSL

• PHP

• Samba

• Sendmail

• Windows Pre-Installation Environment (Windows PE)

168

http://www.kace.com/license/standard_eula.pdf

HTTP://WWW.KACE.COM/LICENSE/STANDARD_EULA�


ApacheThis product (KBOX 2000) includes software developed by The Apache Software Foundation (http://www.apache.org/). Apache License Version 2.0, January 2004 http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions. “License” shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. “Licensor” shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. “Legal Entity” shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, “control” means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. “You” (or “Your”) shall mean an individual or Legal Entity exercising permissions granted by this License. “Source” form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. “Object” form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. “Work” shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). “Derivative Works” shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. “Contribution” shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, “submitted” means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as “Not a Contribution.” “Contributor” shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.


http://www.apache.org/

http://www.apache.org/

http://www.apache.org/licenses/


4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:

a You must give any other recipients of the Work or Derivative Works a copy of this License; and

b You must cause any modified files to carry prominent notices stating that You changed the files; and

c You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and

d If the Work includes a “NOTICE” text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.

a You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any



other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

EZ GPOCopyright (c) 2003-2007, The Environmental Protection Agency.

All of the documentation and software included in the EZ GPO PC Monitor Power Management Tool software is copyrighted by the Environmental Protection Agency.

All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

* Neither the name of the Environmental Protection Agency nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE ENVIRONMENTAL PROTECTION AGENCY AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FEDERAL GOVERMENT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

FreeBSDThis product (KBOX 2000) includes software developed by Free Software Foundation, Inc. GNU GENERAL PUBLIC LICENSE, Version 2, June 1991. Copyright (C) 1989, 1991 Free Software Foundation, Inc.,675 Mass Ave, Cambridge, MA 02139, USA.Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

Preamble

The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the



software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow.

GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

1. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The “Program”, below, refers to any such program or work, and a “work based on the Program” means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term “modification”.) Each licensee is addressed as “you”. Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.

2. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.



3. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:

a You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.

b You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.

c If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

4. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

a Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

b Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

c Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.



If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.

5. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

6. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

7. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.

8. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

9. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.



10. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and “any later version”, you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

11. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.

NO WARRANTY

12. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS

KnoppixThis product (KBOX 2000) includes the Knoppix software developed by Klaus Knopper. Knoppix is a registered trademark of Klaus Knopper. The KNOPPIX software collection and all included programs that are authored by Klaus Knopper, are subject to the terms and conditions of the GNU GENERAL PUBLIC LICENSE Version 2, as quoted herein.

Please note that this license does NOT automatically apply to third-party programs included on this CD. Check /usr/share/doc/*/copyright* and other supplied license files of each software package carefully for more information.

GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free



Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow.

GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION.

0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Pro-gram or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or



else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to con-trol the distribution of derivative or collective works based on the Program. In addition, mere aggrega-tion of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the fol-lowing: a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sec-tions 1 and 2 above on a medium customarily used for software interchange; or, c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the pro-gram in object code or executable form with such an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.


5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohib-ited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the Program), the recipient automati-cally receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of



the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.

7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to con-test validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.


9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number.

If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.


NO WARRANTY

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PRO-GRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIM-ITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PUR-POSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVIC-ING, REPAIR OR CORRECTION. 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA



OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the fol-lowing notices to the program. It is safest to attach them to the start of each source file to most effec-tively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. <one line to give the program's name and a brief idea of what it does.> Copyright (C) <year> <name of author> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Soft-ware Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Pub-lic License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Bos-ton, MA 02111-1307 USA Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode: Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the pro-gram `Gnomovision' (which makes passes at compilers) written by James Hacker. <signature of Ty Coon>, 1 April 1989 Ty Coon, President of Vice This General Public License does not permit incorporat-ing your program into proprietary programs.

If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License.

Microsoft WindowsThis Product is designed for use in supporting the deployment of the following operating systems: Microsoft Windows 95, Microsoft Windows 98, Microsoft Windows 98 Second Edition, Microsoft Windows Millennium Edition, Microsoft Windows NT Workstation 4 Service Pack 5 or later, Microsoft Windows NT Server 4 Service Pack 5 or later, Microsoft Windows 2000 Professional, Microsoft Windows 2000 Server (Standard, Advanced and Datacenter Editions), Microsoft Windows XP Professional, Microsoft Windows XP Tablet PC Edition, Microsoft Windows XP Media Center Edition, or Microsoft Windows Server 2003 (Web, Standard, Enterprise and Datacenter Editions). This Product is designed for use on processor architectures supported by the operating system that the Product was built from: e.g., the x86 32-bit version may only deploy X86 32-bit Microsoft operating systems, the Intel Itanium version may only deploy versions of Microsoft Windows designed for this architecture, and the 64-bit extended version may only deploy versions of Microsoft Windows designed for this architecture. The Product may not function properly with other operating system products or other processor architectures.



OpenSSLThe OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact [email protected].

OpenSSL License

Copyright (c) 1998-2005 The OpenSSL Project. All rights reserved.


1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgment:

"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].

5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.

6. Redistributions of any form whatsoever must retain the following acknowledgment:

"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes cryptographic software written by Eric Young ([email protected]). This product includes software written by Tim Hudson ([email protected]).

Original SSLeay License

Copyright (C) 1995-1998 Eric Young ([email protected]) All rights reserved.

This package is an SSL implementation written by Eric Young ([email protected]). The implementation was written so as to conform with Netscapes SSL.


[email protected]

http://www.openssl.org/

[email protected]

http://www.openssl.org/

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]


This library is free for commercial and non-commercial use as long as the following conditions are aheared to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson ([email protected]).

Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed.

If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.


1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.


3. All advertising materials mentioning features or use of this software must display the following acknowledgement:

"This product includes cryptographic software written by Eric Young ([email protected])". The word 'cryptographic' can be left out if the rouines from the library being used are not cryptographic related :-).

4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement:

"This product includes software written by Tim Hudson ([email protected])".

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The licence and distribution terms for any publically available version or derivative of this code cannot be changed, i.e. this code cannot simply be copied and put under another distribution licence [including the GNU Public Licence.]

PHPThis product (KBOX 2000) includes software developed by The PHP Group. The PHP License, version 3.0. Copyright (c) 1999 - 2004 The PHP Group. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted provided that the following conditions are met:


[email protected]

[email protected]

[email protected]


1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.


3. The name “PHP” must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].

4. Products derived from this software may not be called “PHP”, nor may “PHP” appear in their name, without prior written permission from [email protected]. You may indicate that your software works in conjunction with PHP by saying “Foo for PHP” instead of calling it “PHP Foo” or “phpfoo”.

5. The PHP Group may publish revised and/or new versions of the license from time to time. Each version will be given a distinguishing version number. Once covered code has been published under a particular version of the license, you may always continue to use it under the terms of that version. You may also choose to use such covered code under the terms of any subsequent version of the license published by the PHP Group. No one other than the PHP Group has the right to modify the terms applicable to covered code created under this License.

6. Redistributions of any form whatsoever must retain the following acknowledgment: “This product includes PHP, freely available from <http://www.php.net/>”. THIS SOFTWARE IS PROVIDED BY THE PHP DEVELOPMENT TEAM ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PHP DEVELOPMENT TEAM OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This software consists of voluntary contributions made by many individuals on behalf of the PHP Group. The PHP Group can be contacted via Email at [email protected]. For more information on the PHP Group and the PHP project, please see <http://www.php.net>. This product includes the Zend Engine, freely available at <http://www.zend.com>.

Samba GNU GENERAL PUBLIC LICENSE

Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, Cambridge, MA 02139, USA

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

Preamble

The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it.


[email protected]

[email protected]

http://www.php.net/

[email protected]

[email protected]

http://www.php.net

http://www.php.net

http://www.zend.com


(Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we

want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.

Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.

The precise terms and conditions for copying, distribution and modification follow.

GNU GENERAL PUBLIC LICENSE

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law:

that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.

You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.



2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:

a You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.

b You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.

c If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works inthemselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

a Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

b Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

c Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components



(compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.


5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.

7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.




9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.


NO WARRANTY

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

SendmailThis product (KBOX 2000) includes software developed by Sendmail, Inc.

SENDMAIL LICENSE

The following license terms and conditions apply, unless a different license is obtained from Sendmail, Inc., 6425 Christie Ave, Fourth Floor, Emeryville, CA 94608, USA, or by electronic mail at [email protected].

License Terms:

Use, Modification and Redistribution (including distribution of any modified or derived work) in source and binary forms is permitted only if each of the following conditions is met:

1. Redistributions qualify as “freeware” or “Open Source Software” under one of the following terms:

a Redistributions are made at no charge beyond the reasonable cost of materials and delivery.

b Redistributions are accompanied by a copy of the Source Code or by an irrevocable offer to provide a copy of the Source Code for up to three years at the cost of materials and delivery. Such


[email protected]


redistributions must allow further use, modification, and redistribution of the Source Code under substantially the same terms as this license. For the purposes of redistribution “Source Code” means the complete compilable and linkable source code of sendmail including all modifications.

2. Redistributions of source code must retain the copyright notices as they appear in each source code file, these license terms, and the disclaimer/limitation of liability set forth as paragraph 6 below.

3. Redistributions in binary form must reproduce the Copyright Notice, these license terms, and the disclaimer/limitation of liability set forth as paragraph 6 below, in the documentation and/or other materials provided with the distribution. For the purposes of binary distribution the “Copyright Notice” refers to the following language: “Copyright (c) 1998-2003 Sendmail, Inc. All rights reserved.”

4. Neither the name of Sendmail, Inc. nor the University of California nor the names of their contributors may be used to endorse or promote products derived from this software without specific prior written permission. The name “sendmail” is a trademark of Sendmail, Inc.

5. All redistributions must comply with the conditions imposed by the University of California on certain embedded code, whose copyright notice and conditions for redistribution are as follows:

a Copyright (c) 1988, 1993 The Regents of the University of California. All rights reserved.

b Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: (i) Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. (ii) Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. (iii) Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

6. Disclaimer/Limitation of Liability: THIS SOFTWARE IS PROVIDED BY SENDMAIL, INC. AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL SENDMAIL, INC., THE REGENTS OF THE UNIVERSITY OF CALIFORNIA OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Windows Pre-Installation Environment (Windows PE)The KBOX Pre-Installation Environment (KPE) contains the Microsoft® Windows® Pre-Installation Environment (Windows PE) and includes the following licensing provisions: (i) KPE is licensed and not sold. KACE and its suppliers reserve all rights not expressly granted; (ii) this license is limited to use of KPE containing Windows PE as a boot, diagnostic, disaster recovery, setup, restoration, emergency services, installation, test and/or configuration utilities program, and not for use as a general purpose operating system or as a substitute for a fully functional version of any operating system product; (iii) KPE is provided “as is”; (iv) KPE and Windows PE contain a security feature that will cause the computer system to reboot without prior notification to the end-user after 24 hours of continuous use; (v) MS and MS Affiliate(s) disclaim liability related to KPE or Windows PE; (vi) All customer support issues will be handled solely by KACE; (vii) All reverse engineering, decompiling, or disassembly of Windows PE is prohibited, except to the extent expressly permitted by applicable law; and (viii) KPE contains Windows PE and is subject to U.S. export jurisdiction.


IndexAabout 47about scripted installations 103about the KBOX 2000 administrator console 4about the KBOX 2000 physical system 4action icon

about 18Action Icons 19adding 27adding a change workstation name post-installation task 88adding a HAL replacement post-installation task 86adding a naming rule post-installation task 86adding a new BAT script post-installation task 82adding a post-installation agent installer 84adding a post-installation shell script 83adding an installing .NET2.0 post-installation task 87adding drivers to the driver library 66adding pre-installation tasks 110adding users 27administering your KBOX 2000 Series appliance 17, 34administrator console, about 4analyzing activity from the KBOX logs 41answer file

creating from scratch 107installing without 109uploading 109

Apache software copyright 168application items. adding 82application task 77application tasks

pre-installation tasks 78applying labels 101applying labels to images 125applying security settings 22automatic KBOX server update 36automatically backing up export packages 40Bbacking up data 37backing up export packages 40backup

automatically copying package files. 40bat script pre-installation tasks 79BAT script task 77Boot Actions 116boot actions

setting 116boot environment

viewing details 154boot environments

creating 58Boot Menu 147

Setting up Target Machine 147booting a Mac OS node over the network 58browse to the systems deployment console viiibrowse to the User Interface, explained viiiBSDP image index 16BSDP server priority 16


CCapabilities 4capture, troubleshooting 98capturing and deploying 120capturing and deploying Mac OS Disk Images 58capturing and deploying system images 120capturing user states 96capturing, deploying, and managing system user states 92categories of reports 158CD image

importing from a networked drive 53CD uploader

command-line version, using 55status of upload, viewing 56using to upload a CD/DVD image 54

CD uploader utilityinstalling 54

CDsviewing library of 57

client consoleabout (Mac OS) 7

Client Console (Windows) 6client console (Windows)

about 6command-line parameters for 166components that can be packaged 37configuring date & time Settings 20configuring KBOX general settings 17configuring pre-installation tasks 78contacting KACE Technical Support

from your KBOX viiionline Support portal viii

Conventions viicopying pre-installation tasks 81copyrights

Apache software 168EZ GPO 171FreeBSD 171Knoppix 175Micorsoft Windows 179OpenSSL 179PHP 181Samba 182Sendmail 186

corrupted nodes, system recovery 143create a boot environment and upload it to your KBOX 58creating a custom postinstallation task 78creating a label 24creating a scripted installation 106creating and configuring pre-installation tasks 76creating post-installation tasks 82creating reports 160custom HAL replacement 86CVD image

importing from a networked drive 53Ddaily reporting status email 164Daily Status Emails 164default location 38deleting a label 24deleting a link from a KBOX 33deleting a scripted installation 115


deleting a scripted installation from a deployed system 114deleting a system from system inventory 50deleting pre-installation tasks 81deploying a K-image 128deploying a new Mac OS image from the KBOX 61deploying a system image to a non-networked system 123deploying K-images 128deploying scripted installations 113deploying user states 99Deployment Client 147deployment statistics 156DHCP server

configuring 15using with RSA 136

directories used for 65disabling KBOX links 32disk image

capturing from a Mac OS node 61disk images

Mac OS nodes 58disk usage

reserve 20% as free 6DISKPART task

pre-installation, adding 80DISKPART task command syntax 80DISKPART task type

pre-installation task type

DISKPART 77DNS

looking for with network scans 47documentation conventions vii

font conventions viidomain�sername syntax, why 99downloading KBOX logs 42downloading the driver harvesting utility 69downloading USMT to your KBOX automatically 95driver harvesting utility

downloading to a remote system 69driver not found message 74driverharvest program

using to upload drivers 68drivers 63, 64, 65

adding to the library 66details, viewing 72driver not found message 74driverharvest utility, using 68hardware IDs 74hardware, finding for a driver 72harvesting from a remote system 70importing from a remote system 68log of 74recaching 67searching for in the library 72troubleshooting problems with 73Windows Vista, XP, and 7 64

duplicating 91duplicating post-installation tasks 91

Eediting 91, 160editing images 125editing post-installation tasks 91editing reports 160


export feature 37, 38about 37automatically backing up 40exporting packages 38import/export copying rules 38

EZ GPO copyright 171FFile Browser 149

about 149file types 63font conventions viiformats for reports 156formats of reports 156formatting reports 160free disk space required 41FreeBSD 171FreeBSD copyright 171Ggathering node information with system discovery 46general settings 17Getting Started 3HHAL

replacing 86Hardware Inventory 150Iimage capture and deployment overview 119image capture log

about 159image category reports

about 159image deploy log

about 159image library details report

about 159images 119

applying labels to 125details, viewing 125editing 125imaging environments 118introduction to 118K-image, about 119managing 124NTSF optimized, about 119operating systems, supported 118sector-based, about 119

imaging utility 59Imaging Utility (Mac OS) 7import feature

about 37components that can be packaged 37importing packages 39

importing software from a stored CD/DVD image 56installation

logging on to your KBOX 2000 Series appliance 13putting your KBOX 2000 Series appliance together 10verifying network access 13


verifying web access 13Installation & Setup Checklist 9installation and scripting resources viiinstallation requirements 9installing .NET2.0 87installing the KBOX 1000 client software in a scripted installation 111introduction to the KBOX 2000 series appliances 3IP addresses

probing for with network inventory tab 51KKACE Support

contacting for username and password viiKACE support login, allowing 22KACE Technical Support

contacting viiiKACE tutorial videos viiKBOX

logs, viewing 41rebooting 45server software, minimum version 36updating the server software manually 37

KBOX 2000 imaging utility 59KBOX 2000 interface, about 93KBOX 2000 logs

viewing 42KBOX license usage log

about 159KBOX licensing

viewing 26KBOX linking

deleting a link 33disabling 32

KBOX logsdownloading 42

KBOX pre-installation environment 148KBOX systems deployment portal, explained viiiKBOX User Interface, explained viiikcduploader

downloading 54kcduploader utility

using command-line version 55using GUI version 54

K-imageabout 119capturing from a node 122deploying 122, 123

K-imagespurging unused files 42

k-imagesdeploying 128

KNOPPIXLinux deployment and recovery console 151Updates 43updating software for 43Warranty 175

Konppix copyright 175KPE

checking for updates to 42KBOX pre-installation environment 148same as KBOX Deployment Client 148updates 42


LLabel Details 25labels 23

creating 24deleting 24

licensereleasing from nodes 26status 26

license count 46licensing

administering 25configuring settings 22

licensing category reportsabout 159

licensing informationviewing 26

limitations of KBOX 2000 46Linked KBOX Appliances 32linking

about 31linking KBOX 2000 appliances 31Linux deployment and recovery console

KNOPPIX 151Log In 14logging on to your KBOX 2000 Series appliance 14logon failure message

see user states 98logs

viewing 41MMAC addresses, required for KBOX 2000 46Mac OS

capturing a disk image from 61deploying a disk image to 61pre-installation tasks 77shell scripts, about 77shell scripts, adding 80

Mac OS boot environmentdefault, selecting 59

Mac OS boot environment, creating 58Mac OS boot image

adding boot actions to 59Mac OS Netboot 77Mac OS nodes

booting from the KBOX 60booting over the network 58

managing 64Managing Images 124

Applying a Label 125managing images 124managing network inventory 51managing network scans 47managing system image files 127managing system inventory 49managing user states 101managing users 27managing your driver library 64manually update KBOX server software 37Microsoft Windows copyright 179minimum server version 36


NNetBoot server 58

configuring 16, 58network inventory

about 46network scan

about 46deleting 49limitations 46MAC addresses required 46

network scans 47creating 47running 48

Network Settings 21node licenses

administering 25nodes

MAC addresses an non-router connection required for 46non-networked computers, deploying to 123NTFS image

deploying 122NTFS optimized image

about 119Ooffboard database access

allowing 22off-board package transfer 40OpenSSL 179OpenSSL copyright 179overview of capture and deployment 119Ppackages

.pkg and .xml files 38about 38

performancereserve 20% of disk usage as free 6

performing recovery on corrupted systems 143PHP copyright 181physical system, about 4Post installation Tasks

.changing workstation name 88post-installation tasks 82, 87, 91

about 76adding 82adding a naming rule item 86adding a shell script item 83agent installer item 84BAT script item, adding 82changing workstation name 88editing 91HAL replacement 86managing 110troubleshooting new HALs 87

powering off a KBOX 2000 45Powering Off the Client 150pre-installation task

about 76pre-installation task types

BAT script 77shell script 77


pre-installation tasksadding a DISKPART task 80adding to a scripted installation 110application 77application tasks, adding 78bat script 79configuring 78copying 81creating 78default tasks 77deleting 81DISKPART task command-line syntax 80managing 110removing from a scripted installation 110shell script 80task types 77

preinstallation taskscreating and configuring 76

purging unused K-image files 42RRAID

about 43checking disk status 43, 44failure, contacting KACE customer support 44level 1 for KBOX 2100 appliance 43level 5 for KBOX 2200 appliance 43

rebootwithout warning caused by setting changes 17

rebooting the KBOX 2000 45recaching drivers 67Recovery 150recovery 143

set up the corrupted node 144setting up a node for recovery 144using the Linux deployment and recovery console 146using the windows deployment and recovery console 145using VNC 146

recovery category reports, about 159recovery console boot log

about 159recovery console detail report

about 159Recovery from the Administrator Console using VNC 146recovery process overview 143Recovery using Linux Deployment and Recovery Console 146Recovery using Windows Deployment and Recovery Console 145Registration 22registration

configuring settings 22releasing software licenses from nodes 26remote control software

VNC 26Remote machine Boot Menu 121

K-image 122remote machine boot menu

NTFS or sector-based image 122Remote machine for image capture 120Remote Site Appliance 15Remote Site Appliance, see RSA 131removing labels 101reporting

overview 156understanding 156


reporting toolsabout 156

ReportsManaging Reports 160Running Reports 159

reports 160 format not supported 160categories 158changing, knowledge of SQL required 160creating 160daily status emails 164default 158formats 156formatting 160image type, about 159licensing, about 159output format from JasperReports 160output formats 156output, field names require aliasing 160recovery category 159running by selecting the output format 159scripted installation category, about 159summary report 163system performance reports 162

Requirements 9RSA 133

about 131administering 140automatic server update 141bandwidth limit, setting 135, 136bootable CD for 139bootable UFD for 139configure and sync 135creating on a VirtualBox 133deleting 141DHCP server, configuring for 136downloading components to 137installing 133manual server update 141setting as the boot device for nodes 136system requirements 133transferring boot environments on CDs or USBs 138troubleshooting 142updating 140updating the installers 37viewing details 140virtual KBOX, configure and link 134

running reports by selecting the output format 159SSamba 182Samba copyright 182scanning compatibility rules 93Scripted Installation 103scripted installation

creating 106deleting 115deleting from a deployed system 114deploying 113detail, viewing and editing 115process overview 105

scripted installation category reports 159scripted installation detail

about 159


scripted installation logabout 159

scripted installations 78, 110about 103components of 104deploying 113installing KBOX client software 111removing pre-installation tasks 110

sector-based imageabout 119deploying 122

security settingschanging 22

Sendmail copyright 186Server Maintenance 34service packs

see Windows service packs 165setting boot actions 116setting changes that cause reboot without warning 17shell script pre-installation task 80shell script task type 77silent mode installation, tips and tricks viisingle sign-on

configuring 31SNMP community string, changing 22SNMP monitoring

allowing 22SNMP monitoring, allowing 22software

importing using a stored CD/DVD image 56software library

deleting an item from 57Specifications 9SSH login

about 22recommended 22

SSH root login, allowing 22standalone deployment 123supported Windows service packs 165sysprep

using to avoid system image task collision 129system administration

action icons 18configuring date and time settings 20configuring general settings 17

system administration of the 2000 Series appliance. 17, 34system discovery 46

network scans 46system images 120

managing files of 127see images 119

system inventoryabout 46deleting a system 50taking with system inventory 49

System Performance Report 162system performance reports 162system recovery 143system requirements 9systems deployment console, explained viiisystems that have uploaded to the KBOX 49

Ttarget host system requirements 133


Target Machine Boot MenuNTFS or Sector-based image 121

Technical Supportcontacting viiicontacting from your KBOX viiiusing the Support portal viii

tetherrequires SSH login 22

Third Party License Agreements 168transferring data from one KBOX 2000 Series appliance to another 37troubleshooting

HAL post-installation tasks 87logs, viewing and downloading 41

troubleshooting driver problems 73TSP or UDP port 47tutorial videos viiUunattanded installations

setting as boot actions 116understanding K-Image, NTFS Optimized, and Sector-based 119understanding the system image formats 119updating the KBOX server automatically 36upgrading to service packs

creating a post-installation task 166uploading an answer file 109uploading drivers from a remote system 68uploading USMT software to your KBOX manually 95USB drive

using to deploy to a non-networked system 123User Authentication 29User Interface, explained viiiuser name and password, contacting Support for viiuser state details 102user states 93, 98, 99, 101

capturing 96deleting 101deploying 99deployment matrices 93details, viewing 102logon failure message problem 98managing 101overview of capture and deployment 94troubleshooting 98understanding 92USMT 3.0.1 compatibility matrix 94USMT 4.0 compatibility matrix 94

users 27admin user adding 27managing 27single sign-on 31used by KBOX 2000 27

users roleunused on KBOX 2000 27

uses 58using the default reports 158using to organize KBOX resources 23using to probe for systems on your LAN 48using VNC to control a remote system 26USMT software

downloading 95downloading automatically 95uploading manually 95


Vviewing driver details 72viewing image details 125viewing KBOX 2000 logs 42VNC 26

accessing the target machine 27VNC remote control software 26Wwake-on-LAN, sending 50Warranty Information 168Web Access 13Windows 2003 R2 installation special note 106Windows 2003 Server 15Windows Client Console 6Windows deployment and recovery console (KPE) 148Windows Service Packs

deploying 165Windows service packs 166

creating post-installation task for 166installing on nodes 166supported 165

Yystem recovery 143
