You are on page 1of 170

K2000 Deployment Appliance v3.

3, Administrator's Guide

Contents
Getting Started.....................................................................................................5
Setting up the Appliance.........................................................................................6
Configuring network settings from the console..............................................................7 Logging in to the Administrative Console.......................................................................8 Completing the Initial Configuration...............................................................................9 Registering the appliance............................................................................................10 Configuring the date & time settings............................................................................11 Changing default passwords........................................................................................12 Setting up administrator accounts...............................................................................13 Enabling the Driver Feed.............................................................................................16 Enabling access for KACE Support.............................................................................16 Enabling offboard access to database.........................................................................17 Setting up monitoring of the appliance (SNMP)...........................................................17

Setting Up Network Booting..................................................................................18


Overview MAC Boot Environments..............................................................................18 Overview Windows PXE Boots....................................................................................19 Configuring the K2000 (Windows) Boot Manager.......................................................20 Building Boot Environments.........................................................................................22 Setting the default boot environment...........................................................................29 Directing network boots to the appliance.....................................................................29

Setting up a Remote Site Appliance.....................................................................33


Downloading the RSA OVF.........................................................................................34 Installing RSA..............................................................................................................34 Configuring network settings from the console............................................................35 Activating the RSA.......................................................................................................36 Configuring the date & time settings............................................................................36 Configuring authentication settings..............................................................................37 Linking the RSA and the K2000 appliance..................................................................41 Extending the K2000 Appliance...................................................................................42 Directing network boots to the RSA.............................................................................42

Capturing user states for online migration.....................................................45


Excluding users and data from a capture..............................................................45 Uploading the Windows User State Migration Tool...............................................46 Capturing user states from a target.......................................................................46 Loading user profiles on targets............................................................................48

Installing Operating Systems from source......................................................49


Setting up Library Components.............................................................................50
Uploading Operating System Installation Files............................................................50 Capturing user states for online migration...................................................................52 Checking driver compatibility.......................................................................................55 Adding Drivers to appliance cache..............................................................................55 Preinstallation Tasks: Prepare a computer for a new operating system.......................59 Postinstallation Tasks: Customizing the installation.....................................................61

Setting up a Windows Scripted Installation...........................................................64


Setting up an Unattended Installation..........................................................................64 Setting up an attended installation...............................................................................65
ii K2000 Deployment Appliance v3.3, Administrator's Guide

Contents

Setting up the Pre- and Postinstallation Tasks.............................................................66

Deploying Scripted Installations............................................................................66


Deploying on the next network boot.............................................................................67 Performing a clean OS installation...............................................................................67

Imaging Systems...............................................................................................70
Setting up Library Components.............................................................................70
Capturing user states for online migration...................................................................70 Preinstallation Tasks: Prepare a computer for a new operating system.......................74 Postinstallation Tasks: Customizing the installation.....................................................76

Capturing a system image....................................................................................79 Configuring System Images..................................................................................81


Capturing a system image...........................................................................................82 Setting up the Pre- and Postinstallation Tasks.............................................................84 Editing System Images................................................................................................85

Deploying a System Image...................................................................................85


Reimaging from the Recovery Console.......................................................................85 Deploying on the next network boot.............................................................................87

Maintaining the appliance.................................................................................88


Updating appliance software.................................................................................88
Displaying the appliance version.................................................................................88 Checking for updates...................................................................................................88 Updating the appliance directly from KACE.................................................................88 Manually updating the appliance.................................................................................89 Updating RSA software...............................................................................................89

Viewing and downloading log files........................................................................89


Displaying log files.......................................................................................................90 Downloading all logs....................................................................................................90

Managing drivers...................................................................................................90
Managing the drivers share files..................................................................................91 Getting drivers from Dell KACE...................................................................................93

Managing Disk Space...........................................................................................93


Verifying available disk space......................................................................................94 Removing unused image files......................................................................................94 Deleting System Images..............................................................................................94 Deleting Scripted Installations and OS Source............................................................94 Deleting KBEs and NetBoot Environments..................................................................95 Deleting Preinstallation Tasks......................................................................................95 Deleting Postinstallation Tasks.....................................................................................95

Backing up and restoring data..............................................................................96


Exporting library components to packages..................................................................96 Scheduling backups.....................................................................................................96 Automatically transferring packages............................................................................97 Restoring Library components.....................................................................................97

Installing tools required to build KBE....................................................................98


Downloading and installing Media Manager................................................................99 Installing Windows Automated Installation Kit (AIK)..................................................100

Understanding Action Icons................................................................................100


Programming remote access icons...........................................................................100 Opening a VNC session to a target in the Boot Environment....................................101

Using the Deployment and Recovery Console....................................................102


Opening the Recovery Console.................................................................................102
iii

Uploading Hardware Inventory..................................................................................104 Capturing a system image.........................................................................................105 Reimaging from the Recovery Console.....................................................................107 Performing a clean OS installation.............................................................................109 Accessing information on a corrupted node from KBE..............................................110

Administrative Console...................................................................................113
Home ..................................................................................................................113
Tasks .........................................................................................................................113 Guided Tour ..............................................................................................................114 Search (Global Search).............................................................................................114

Library ................................................................................................................114
Overview ...................................................................................................................114 Source Media ............................................................................................................114 Drivers ......................................................................................................................116 Driver Feed ...............................................................................................................118 Preinstallation Tasks .................................................................................................119 Postinstallation Tasks ................................................................................................124 User States ...............................................................................................................131 USMT Scan Template ...............................................................................................134

Deployments ......................................................................................................136
Scripted Installations .................................................................................................136 System Images .........................................................................................................140 Boot Environments ...................................................................................................143 Remote Site Appliances ...........................................................................................144

Systems .............................................................................................................146
System Inventory ......................................................................................................146 K1000 Inventory.........................................................................................................148 Network Inventory .....................................................................................................148 Network Scans ..........................................................................................................149 Boot Actions ..............................................................................................................151

Reports ..............................................................................................................153
Reports......................................................................................................................153 System Performance.................................................................................................154

Settings & Maintenance .....................................................................................154


Control Panel ............................................................................................................154 Appliance Logs .........................................................................................................165 RAID..........................................................................................................................166 Package Management ..............................................................................................166 Appliance Maintenance ............................................................................................169

iv

K2000 Deployment Appliance v3.3, Administrator's Guide

Getting Started

This section walks you through the tasks required to connect your appliance to thenetwork, create a boot environment, direct clients to network boot from the appliance, and test the configuration.

Before you can install operating systems, re-image and recover systems, and maintain computers from the appliance you must set up the appliance and connect it to your network and then direct target computers to network boot in the K2000 Boot Environment. Required Tasks The following table describes the minimal set up tasks required to prepare your Dell KACE K2000 appliance:
Task Description

Configuring network settings from the console on Connect Dell KACE K2000 appliance to your network using the console. Requires page 35 monitor and keyboard directly connected to the K2000 unit. Logging in to the Administrative Console on page 8 Registering the appliance on page 10 Installing Media Manager on Windows on page 99 Installing Windows Automated Installation Kit (AIK) on page 100 Building a New Windows KBE on page 27 Setting up an external DHCP server on page 32 Setting the default boot environment on page 29 Access the Dell KACE K2000 appliance Administrative Console from web browser.

Enter license information to start using the appliance. Tool required to create a K2000 Network Boot Environment (KBE).

Third-party tool required to create a KBE.

Create the K2000 Boot Environment that allows targets to boot from the appliance. Direct PXE boot requests to the appliance.

Select KBE that targets boot from.

K2000 Deployment Appliance v3.3, Administrator's Guide

Task Testing network booting

Description Verify that the target can boot from the appliance.

Setting up the Appliance


To set up the appliance, you must configure the host name and IP address, connect the appliance to the network, and then activate it by entering the license key. To assist you with the set up steps, Dell KACE provides the following Wizards: Konfig Console: Connect a monitor and keyboard directly to the appliance and configure network settings. Administrative Console Configuration Wizard: Appears after the first login and requires you to complete the initial set up. This section also describes Dell KACE recommended tasks for completing your configuration. Configuration Wizard Settings The following table describes the settings required to get the K2000 appliance up and running:
Setup Wizards Konfig Console Settings Appliance Hostname and IP address Description

Configure the appliance host name, web server name, and static IP address from the appliance console after the first boot. Enter the key you received in your Welcome email. Change the admin password from the default. Password must be longer than six characters. (Optional) Enter the email address where the appliance sends important notifications on appliance status. (Optional) Manually set the system clock or choose to synchronize the system clock with the Dell KACE time server.

Admin Console

Activation (License Key) Admin account password

Admin account email address

Date & Time

Optional configuration steps The following table describes the optional tasks for completing the configuration of the K2000 appliance:
Settings Company name and Crash Reports Description

You enter the license key to activate your appliance in the Configuration Wizard that appears the first time you log in. Use these steps to complete the optional registration settings, such as your company name and enabling crash reports. By default, the system clock is set to synchronize with the Dell KACE time server. Use these instructions to manually change the system clock or synchronize with a different NTP server.

Date & Time

K2000 Deployment Appliance v3.3, Administrator's Guide

Settings

Description Setting the system clock prevents unexpected behavior, such as running resource intensive backups in the middle of the day. Note: The default time server is hosted by Dell KACE.

Default Passwords

Recommended during initial setup. Change the default appliance passwords for the shared directories: restore and drivers, K2000 Boot Manager, and K2000 Boot Environment (KBE) VNC application. Before using your appliance Dell KACE recommends choosing your authentication method and setting up K2000 administrator accounts. Dell KACE Support provides drivers for various computer models. When you check Enable Driver Feed a list of the available packages from Dell displays on the Driver Feed page. Enabling Allow SSH Root Login (Kace Support) on the Security page provides remote access to Dell KACE Support personnel. Dell KACE recommends enabling this feature before you begin to use the appliance. SSH remote access is the only method that support personnel can use to diagnose and fix problems if the appliance becomes unresponsive. For example, the recommended free disk space is not available. Enabling Allow Offboard Database Access on the Security page, makes the Dell KACE K2000 Appliance database available to external programs, such as Crystal Reports, for reporting. By default, the appliance does not allow external connections to the database. The Enable SNMP Monitoring setting allows clients to monitor the Dell KACE K2000 Deployment appliance. Once enabled, the appliance SNMP agent authorizes read-only access for all MIBs to any client querying the community string. Dell recommends creating a unique string; Public is the default.

Administrator Accounts

Driver Feed

Support Access

Reporting Tool Access

Monitoring of the Appliance

Configuring network settings from the console


Configure the appliance host name, web server name, and static IP address from the appliance console after the first boot. To access the console, connect a monitor and keyboard directly to the appliance or when configuring a trial version or RSA on a virtual machine, open the virtual machine console. To set up the appliance: 1. Power on the appliance. The appliance requires 5 to 10 minutes to start up for the first time.

K2000 Deployment Appliance v3.3, Administrator's Guide

2. At the login prompt, enter: Login: konfig

Password: konfig 3. Modify the following settings using the Up and Down arrow keys to move between fields. Field K2000 Server (DNS) Hostname Enter the name used to access the appliance from nodes. Node users connect to the appliance using the Web Server Name, which can be the hostname, FQDN (fully-qualified domain name), or IP address. The default setting is ikbox. (Recommended) Enter the static IP address of the appliance server. Static IP Address Enter the domain that the appliance is on. Domain Enter the subnet mask. Subnet mask Enter the network gateway for the appliance server. Default gateway Enter the IP address of the primary DNS server the appliances uses to resolve host names. Description Enter the host name of the appliance. The default setting is ikbox.

Web Server Name

Primary DNS

4. Press the Down arrow to move the cursor to Save, and then press Enter or Return. The appliance restarts. The initial configuration is complete. After the appliance finishing rebooting the Web Interface (Administrative Console) should be accessible. Connect the appliance to the network, and finish the configuration using a browser to access the Administrative Console (http://K2000_hostname).

Logging in to the Administrative Console


After the basic network configuration is complete, you can log in to the Administrative Console from any computer on the Local Area Network (LAN) using a web browser. To log in to the Administrative Console: 1. Open a web browser. 2. Enter the appliance Administrative Console URL: http://k2000_hostname/adminui
8 K2000 Deployment Appliance v3.3, Administrator's Guide

The Login page appears. 3. Enter your administrator account credentials. The first time you log in, enter the default account credentials: User name: admin Password: admin The appliance Administrative Console Home page appears. The Home page displays Alerts, that is items that need attention, statistical information, and links to common tasks. You can also access the User Forum, Support, and Training information from the Home page.

Completing the Initial Configuration


After the first time you log in, using the default administrator account (admin/admin) the Initial Configuration wizard appears. 1. In License Key, enter the key (including dashes), you in received in the welcome email from Dell KACE.

Contact Dell KACE support if you cannot locate your license key. 2. Change the admin account password.

a) In Password, enter a new password for the admin account. b) In Verify Password, re-enter the new password. The default admin account is the only account on the appliance at this time. If you lose the password and you have not enabled the Dell KACE support access, the password can only be reset by sending the appliance back to Dell KACE. 3. Register the appliance.

a) In Company Name, enter the name of your company or organization. b) In Administrator Email, enter the email address of the person or group that receives logs and notifications from the appliance. This email address is the email address of the default admin account. 4. In Time Zone, click the name of the region where the appliance is located.

K2000 Deployment Appliance v3.3, Administrator's Guide

By default, the appliance is set to synchronize with the Dell KACE time server. 5. Click Apply Settings and Reboot. The appliance restarts. The next time you log in, use the admin account with the new password you created.

Registering the appliance


You enter the license key to activate your appliance in the Configuration Wizard that appears the first time you log in. Use these steps to complete the optional registration settings, such as your company name and enabling crash reports. Perform these steps from the Administrative Console, see Logging in to the Administrative Console on page 8 for detailed instructions and the default user name and password. To activate the appliance: 1. Log in the K2000 Administrative Console. 2. Click Settings & Maintenance > Control Panel > Registration & Licensing. The Registration & Licensing page appears. 3. Click Edit. 4. Complete the registration form: Company-Institution Name Organization Name Administrator Email The name of organization to which this product is registered. (Optional) The name of the division or organization. The email address of the appliance administrator to whom daily status emails are sent. Send crash reports to KACE.

Send Crash Reports to KACE

5. Under Licensing, click Add License Key. The License Key fields appear. 6. In the License Key field, enter the appliance key, and then click Save. After you enter your license key, the following information displays.
Status Expires Seats Shows whether the license is valid or invalid. Shows the license key expiration date. Number of client seats licensed for use with this appliance. To unregister clients use the System Inventory page.

The appliance is activated.

10

K2000 Deployment Appliance v3.3, Administrator's Guide

Configuring the date & time settings


By default, the system clock is set to synchronize with the Dell KACE time server. Use these instructions to manually change the system clock or synchronize with a different NTP server. Setting the system clock prevents unexpected behavior, such as running resource intensive backups in the middle of the day. Note: Dell KACE K2000 appliance deployment operations, scheduled backups, exports, and offboard transfers rely on the date and time of the system clock. The appliance log timestamps are recorded in the appliance time zone. The K2000 database contains date and time in UTC, and is converted to the specified time zone when displayed to the user.

Manually configuring the date and time


Dell KACE K2000 appliance launches and logs deployment operations based on the date and time of the system clock. This section explains how to manually set the clock. To perform these steps, log in to the Administrative Console using an appliance Administrator account. To set up synchronization with an NIST Internet Time Server: 1. Click Settings & Maintenance > Control Panel > Date & Time Settings. The Date & Time Settings page appears. 2. Click Edit. 3. In Time Zone, click the name of the time zone the appliance is in. 4. Clear Automatically synchronize with Internet time server. 5. Click Set the clock on the K2000 manually. The New Time and New Date fields appear. 6. In New Time, set the correct H (hour), M (minute), and S (second) options. 7. In New Date, set the correct M (month), D (day), and Y (year) options. 8. Click Save. After changing the Date & Time Settings, the Dell KACE K2000 Appliance restarts. This disrupts appliance operations for 10 to 15 seconds and active connections are dropped. Manually refresh the browser and log in to display the new Date & Time Settings.

Synchronizing the system clock


Set up automatic synchronize between the system clock and an NTP server to automatically update the system clock. You can also synchronize with a NIST Internet Time Server, see for a list of available servers (http://tf.nist.gov/tf-cgi/servers.cgi). To perform these steps, log in to the Administrative Console using an appliance Administrator account. To set up synchronization with an NIST Internet Time Server: 1. Click Settings & Maintenance > Control Panel > Date & Time Settings. The Date & Time Settings page appears. 2. Click Edit to activate page menus. 3. In Time Zone, click the name of the appropriate time zone. 4. Clear Set the clock on the K2000 manually.

K2000 Deployment Appliance v3.3, Administrator's Guide

11

5. Click Automatically synchronize with Internet time server. The Time Server field appears. 6. In Time Server, enter the FQDN or the IP address of the NIST Internet Time Server or the host name of the time server on the local network. For example, nist1.aol-ca.symmetricom.com. 7. Click Save. After changing the Date & Time Settings, the Dell KACE K2000 Appliance restarts. This disrupts appliance operations for 10 to 15 seconds and active connections are dropped. Manually refresh the browser and log in to display the new Date & Time Settings.

Changing default passwords


Recommended during initial setup. Change the default appliance passwords for the shared directories: restore and drivers, K2000 Boot Manager, and K2000 Boot Environment (KBE) VNC application.

Changing the Boot Manager password


The K2000 Boot Manager displays on a target computer that has PXE booted from the Dell KACE K2000 appliance. The password protects the boot sequence from end-user interruption. During the Boot Manager Timeout period, a user can change the boot sequence and select a different option, such as boot from local drive or reimage system. By setting a password, you prevent users who you dont know the password with from changing the boot action. Note: By default there is no password. Perform this task from the Administrative Console. To change the Boot Manager password: 1. Click Settings & Maintenance > Control Panel > General Settings. The General Settings page appears. 2. Click Edit. 3. In Boot Manager Password, enter a new password. 4. Click Save. The Boot Manager password is changed for all new PXE boot request. The password for active sessions uses the previous password.

Changing the share passwords


The Dell KACE K2000 appliance hosts Samba shares for uploading drivers and backing up and restoring Library Components, such as Preinstallation and Postinstallation Tasks. You access the drivers and restore shares using the admin account. Note: The access account name is admin and the default password is also admin. Perform this task from the Administrative Console. 1. Click Settings & Maintenance > Control Panel > General Settings. The General Settings page appears.

12

K2000 Deployment Appliance v3.3, Administrator's Guide

2. Click Edit. 3. In Driver/Restore Share Password, enter a new password. 4. Click Save. The guest account password for the shares is changed.

Changing the VNC password


The Dell KACE K2000 appliance boot environments include a Java VNC client that allows you to connect to the target while it is booting from the appliance. Note: The VNC password is built into the Mac OS X NetBoot Environments when you create the Boot Environment on the target. Perform this task from the Administrative Console. 1. Click Settings & Maintenance > Control Panel > General Settings. The General Settings page appears. 2. Click Edit. 3. In VNC Password, enter a new password. 4. Click Save. The VNC password is changed. The next time a Windows target boots from the appliance, use the new VNC password to connect.

Setting up administrator accounts


Before using your appliance Dell KACE recommends choosing your authentication method and setting up K2000 administrator accounts. The appliance supports the following authentication methods: Local: Authenticates administrators against an internal user database. Administrator data, including login name, password, and email address, is stored on the appliance. For single sign-on, because each appliance in the environment has its own local database of accounts, the accounts on each linked appliance must match. For example, jsmith is configured as an administrator on the K2000 appliance and the same account (jsmith) is configured on a linked Remote Site Appliance, if jsmiths password is the same, signing into either the K2000 appliance or the RSA signs jsmith into both appliances. Note: Only use the local authentication method when an LDAP service, such as Active Directory, is not available in your environment. LDAP Service: Authenticates administrators against an external user database that identifies K2000 Administrators using a group or other method. This allows administrators to use their domain credentials to log in to the Administrative Console. For single sign-on, configure the LDAP server on all the linked appliance in the environment.

K2000 Deployment Appliance v3.3, Administrator's Guide

13

Setting up external authentication


Configure the Dell KACE K2000 appliance to authenticate appliance administrators against an external LDAP directory service, such as Active Directory (AD). This allows users to log into the Administrative Console with their domain credentials. Enabling an external authentication automatically disables the local user accounts, except for the admin account. Note: When logging in, the appliance automatically queries each listed external server; the timeout for a server is approximately 10 seconds. Dell KACE recommends deleting the sample LDAP server to decrease login delays. Log in to the Administrative Console to add an external LDAP directory. 1. Click Settings & Maintenance > Control Panel > User Authentication. 2. Click Edit. 3. Click External LDAP Server Authentication. Choosing this option disables all the local user accounts except for the admin account. 4. Click Add New Server. You can also modify the sample Admin Server. The New LDAP Server form appears below the existing servers (if any). 5. Enter the following information for the LDAP Service: Field Server Friendly Name Server Hostname (or IP) LDAP Port Number Description Enter a name for the server that identifies it in the list of external LDAP servers. Enter LDAP server IP address or host name. The appliance uses this address to authenticate users. Enter the LDAP Port number, the default is 389. Note: Contact Dell KACE support if you are using LDAPS, default port 636. Search Base DN Specify which area of the LDAP tree the appliance should begin to search for users. For example, specify OU=it, DC=kace, DC=com to search the IT group. Note: Searching the entire directory may cause lag time during login. Limiting the search base decreases these delays. Search Filter Enter (LDAP_attribute=KBOX_USER) where the LDAP_attribute is the name of the attribute that contains a unique user ID and KBOX_USER is a variable the appliance replaces at runtime with the Login ID the user enters. For example for Active Directory enter(samaccountname=KBOX_USER)and for most other LDAP servers enter (UID=KBOX_USER).

14

K2000 Deployment Appliance v3.3, Administrator's Guide

Field LDAP Login

Description Enter the bind DN; that is the user account with permission to query the search base. Use either the DN format: CN=username,DC=company, DC=com or the user principal name format username@company.com. Note: If the field is left blank the appliance connects to the LDAP server using an anonymous bind.

LDAP Password (if required) User Permissions

Enter the LDAP account password. Choose the permissions to assign to a user the first time they successfully log in: Admin: Read/write access. ReadOnly Admin: View all pages, no change access. User: No access.

Test LDAP Password

Change the KBOX_USER variable in the Search Filter to a valid Login ID, for example (samaccountname=jsmith) and enter the corresponding password for the LDAP account and click Test LDAP Settings. Note: Be sure to change the user name in the Search Filter back to the system variable KBOX_USER.

6. (Optional but recommended.) Click the delete button next to any external servers that are not configured to actual servers in your environment. 7. Click Save. The next time a user logs in, the appliance authenticates them against the LDAP servers in the order they are listed. Note: The admin account always authenticates against the internal database, even if an account with the same name exists in an external LDAP. This makes the appliance accessible when no LDAP services are available.

Adding a local administrator account


Set up administrator accounts in the K2000 user database when an external LDAP service, such as Active Directory, is not available in your environment. This method stores user information locally. To use Single Sign-on for linked appliance and the local administrator database, account information (that is login and password) must be the same on all linked appliances. If LDAP is enabled, all local accounts become inactive except for the admin account. Add users in the appliance Administrative Console. Only the user name, email address, password, and permissions fields are required. 1. Click Settings & Maintenance > Control Panel > Users. The Users page appears.

K2000 Deployment Appliance v3.3, Administrator's Guide

15

2. In Choose Action, click Add New User. The Edit User Details page appears. 3. Complete the user account form: User Name Full Name Email Domain Budget Code Location Password Enter a login ID. Enter the users first and last name. Enter the users email address. Enter the name of the domain the user is in. (Optional) Enter the budget code of the department the user is in. (Optional) Enter the site or location of the user. Enter the default password for the user. This field is required to activate the user. If the field is blank the user cannot log into the Administrative Console. Reenter the password. Choose a role for the user: User: No access to Administrative Console. Admin: Read/write access to Administrative Console. ReadOnly Admin: View only access to Administrative Console. 4. Click Save. The Users page appears. The user appears in the local account list and can now log in to the Administrative Console.

Confirm Password Permissions

Enabling the Driver Feed


Dell KACE Support provides drivers for various computer models. When you check Enable Driver Feed a list of the available packages from Dell displays on the Driver Feed page. 1. Click Library > Driver Feed. 2. In Choose Action, click Manage Driver Feed Settings. The Driver Feed Settings page appears. 3. Click Edit. 4. Click Enable Driver Feed and then Save. The appliance checks for packages and downloads the meta data of the available packages.

Enabling access for KACE Support


Enabling Allow SSH Root Login (Kace Support) on the Security page provides remote access to Dell KACE Support personnel. Dell KACE recommends enabling this feature before you begin to use the appliance. SSH remote access is the only method that support personnel can use to diagnose and fix problems if the appliance becomes unresponsive. For example, the recommended free disk space is not available. Enable SSH remote access from the Administrative Console. To enable the support login:
16 K2000 Deployment Appliance v3.3, Administrator's Guide

1. Click Settings & Maintenance > Security. The Security page appears. 2. Click Edit. 3. Click Allow SSH Root Login (Kace Support). 4. Click Save. Dell KACE Support remote access to the appliance is now available.

Enabling offboard access to database


Enabling Allow Offboard Database Access on the Security page, makes the Dell KACE K2000 Appliance database available to external programs, such as Crystal Reports, for reporting. By default, the appliance does not allow external connections to the database. The account for external access to the database is user name: report and password: box747. Enable offboard database access from the Administrative Console. To allow offboard access: 1. Click Settings & Maintenance > Security. The Security page appears. 2. Click Edit. 3. Click Allow Offboard Database Access. 4. Click Save. External applications can now query the K2000 appliance database.

Setting up monitoring of the appliance (SNMP)


The Enable SNMP Monitoring setting allows clients to monitor the Dell KACE K2000 Deployment appliance. Once enabled, the appliance SNMP agent authorizes read-only access for all MIBs to any client querying the community string. Dell recommends creating a unique string; Public is the default. Enable SSH remote access from the Administrative Console. To enable the support login: 1. Click Settings & Maintenance > Security. The Security page appears. 2. Click Edit. 3. Click Enable SNMP Monitoring. The SNMP Community String field appears. 4. Enter a unique community string. 5. Click Save.

K2000 Deployment Appliance v3.3, Administrator's Guide

17

Setting Up Network Booting


Before you can use the K2000 appliance, you must configure all the components required to network boot your systems. This section explains how to set up the boot environment on the K2000 appliance, direct network boot requests from the clients to the appliance, and ensure that clients can boot into the default Boot Environment. The following figure shows the basic configuration required for network booting.

Overview MAC Boot Environments


When a MAC connected to the network boots, it sends a BSDP request. The NetBoot server configured on the network receives the request and returns the boot server information to the client. The local Boot Manager presents the option to network boot to the computer user.

18

K2000 Deployment Appliance v3.3, Administrator's Guide

To re-image or recover, a networked MAC target from Dell KACE K2000 appliance, perform the following tasks: 1. Installing Media Manager for MAC OS X on page 99 2. Building Mac OS X NetBoot Boot Environments on page 28 3. Setting the default boot environment on page 29 4. Directing Mac network boot (BSCP) request on page 42

Overview Windows PXE Boots


When a Windows computer connected to the network boots, it sends a PXE request. The DHCP server receives the request and returns the boot server information. No Boot Actions assigned: The client downloads and loads the bootstrap from the K2000 appliance and then displays the K2000 Boot Manager. After the timeout period, if the user does not interrupt the boot sequence, the boot continues from the local hard drive. The user can also interrupt the boot sequence, and choose to boot into KBE to access the Recovery Console. Note: From the Recovery Console, you can upload hardware inventory, run a compatibility report, or choose a deployment option such as reimaging the machine or installing a new copy of the operating system. Boot Action assigned: The client downloads and loads the bootstrap, then boots directly into KBE and executes the assigned action.

K2000 Deployment Appliance v3.3, Administrator's Guide

19

Configuring the K2000 (Windows) Boot Manager


The Dell KACE K2000 appliance PXE Boot Manager displays on the target computer after the K2000 bootstrap loads (kbox2000.0) when a Boot Action has not been assigned to the computer. For most computers, you can use the default Boot Manager settings. However in some cases, such as installing and deploying operating systems in a test environment, in high latency networks or when supporting older computers, you may need to modify the default settings. The following table describes the circumstances when you may need to modify the default settings:
Condition Boot Manager fails to load Setting Some NIC architectures do not support graphics, such as nVidia nForce 415. Change the Boot Manager Interface Style to Basic. In a lab environment, where the deployments are being initiated from the computer and not using Boot Actions, you may want to increase the timeout period to allow administrators to select the deployment option. On a high latency network, the computer cannot boot into KBE. Increase the KBE Network Bring Up Delay.

Boot Manager timesout to default boot sequence (local driver) Fails to boot into KBE

Selecting the Boot Manager interface type


The K2000 Boot Manager is included with the bootstrap file downloaded by the client during the initial PXE boot. The interface displays on the client machine, allowing the boot sequence to be interrupted when no Boot Action is assigned. Most NICs (Network Interface Cards) support the default interface type, graphical. Graphical is the most user friendly; allows selection using arrow keys. However some NICs, such as the NVidia nForce 415, that do not support the graphics or use of arrow keys cannot load the Boot Manager.

20

K2000 Deployment Appliance v3.3, Administrator's Guide

Note: If the Boot Manager does not load, then switch the interface type to Basic. Perform this task from the Administrative Console. 1. Click Settings & Maintenance > General Settings. The General Settings page appears. 2. Click Edit. 3. In Boot Manager Style, click one of the following options: Graphical Menu: Default, user friendly interface that allows you to select options using arrow keys.

Text Menu: Supports some older NICs that do not support integrated graphics but allow the user of arrow keys.

Basic: Supports NICs that do have integrated graphic support and cannot recognize arrow keys.

4. Click Save. The Boot Manager interface for all PXE boots from the appliance is changed.

K2000 Deployment Appliance v3.3, Administrator's Guide

21

Configuring the timeout


The Boot Manager timeout determines how long the Boot Manager menu displays on the target before the default method is automatically selected. When the Boot Manager menu displays, the user can interrupt the sequence, and then select another option. Perform this task from the Administrative Console. 1. Click Setting & Maintenance > General Settings. The General Settings page appears. 2. Click Edit. 3. In Boot Manager Timeout, enter the duration in seconds. In a lab environment where administrators are setting up and troubleshooting machines, you may want to increase the period. However in production, you may want to decrease the time to a few seconds to discourage users from attempting to interrupt the boot. 4. Click Save. The Boot Manager interface for all PXE boots from the appliance is changed.

Increasing the KBE bring up for high latency networks


After the Boot Manager displays and the user selects the K2000 Boot Environment option or when a Boot Action is assigned, the boot loader mounts and boots the computer into the KBE. In high latency networks, you may need to increase the delay to ensure there is enough time to fully load KBE. Perform this task from the Administrative Console. 1. Click Settings & Maintenance > General Settings. The General Settings page appears. 2. Click Edit. 3. In KBE Bring up Network Delay, enter the duration in seconds. 4. Click Save. The boot loader allows more time to bring up the K2000 Boot Environment before timing out.

Building Boot Environments


The Boot Environment is mounted and loaded onto the computer during a network boot from the appliance. The Boot Environment provides the drivers and tools required to deploy operating system installations, recover, and re-image systems. Before you can network boot from the appliance, build the KBEs and NetBoot Environments required by the systems. The K2000 appliance comes with Windows KBEs for both x86 and x64; the same prebuilt KBEs are also available from the Driver Feed. Therefore, when running Windows you do not have to create a KBE unless the additional drivers are required to network boot. To network boot Mac OS X computers you must build the NetBoot environments using the Media Manager for the type of systems you are supporting (that is PowerPC and Intel x86).

Updating drivers in the K2000 Boot Environments (KBE)


You must build a new KBE to add drivers. The appliance comes with two prebuilt K2000 Boot Environments (KBE) that support network booting for most x86 and x64 Windows computers. You can also get the same
22 K2000 Deployment Appliance v3.3, Administrator's Guide

Boot Environment from Dell KACE using the Library > Driver Feed page. These KBEs include the drivers from the Windows Automated Installation Kit (WAIK). This section explains how to add drivers to the KBE driver cache and create a new Boot Environment using Media Manager and the Windows Automated Installation Kit (AIK).

Building KBE requires the use of an administrator PC with at least 5 GB of free space that has one of the following operating systems: Windows Server 2003 with Service Pack 2 Windows Vista with Service Pack 1 Windows Server 2008 family Windows 7 family Windows Server 2008 R2 family It also requires the following: ISO mounting utility K2000 Media Manager and Microsoft .NET 2.0 Windows Automated Installation Kit (Only if adding drivers) Access to driver files or packages and K2000 driver share

Adding Drivers to appliance cache


The K2000 appliance driver caches contain the meta data for drivers uploaded to the drivers share and allow the appliance processes to match the drivers with the correct hardware during Scripted Installations and Windows K2000 Boot Environment (KBE) builds. Recaching drivers for: KBE folders, kbe_windows_x86 and kbe_windows_x64, loads driver meta data and makes the drivers available for KBE builds. Most systems can network boot using the prebuilt K2000 Boot Environments (KBE) for x86 and x64 systems provided by Dell KACE. However, for systems that require additional drivers to network boot, add the drivers to the share and recache (using one of the method described below), and then create a new KBE from an administrator computer with Media Manager and Windows Automated Tool Kit (WAIK).

K2000 Deployment Appliance v3.3, Administrator's Guide

23

Scripted Installation folders, windows_2000 , windows_2003, windows_2003_x64, windows_2008_x64, windows_2008_x86, windows_7_x64, windows_7_x86, windows_vista, windows_vista_x64, windows_xp, windows_xp_x64, loads driver meta data and makes the driver available during a clean operating system installation from source media (Scripted Installation). Note: System Images contain the drivers capture on the system you imaged. To add a driver to a System Image, install the driver on the source computer, recapture the image and upload it to the appliance. Add the drivers to the share and recache using the following methods:

Method

Description

Library > Driver Feed > Download and Install Process that automatically downloads a package of drivers, installs the driver files Packages in the driver share file, and recaches the folder. Manually adding drivers Settings & Maintenance > Package Management > Import Package Driver Harvesting Utility Allows you to add drivers that you obtained to the appliance and recache the folder. Adds drivers you exported either as a backup or that you want to share between K2000 appliances. Allows you to scan a computer that has the drivers you want and upload them to the appliance driver share, and then you must manually recache the drivers.

Getting drivers from Dell KACE Dell KACE Support gathers drivers and provides packages that you can download and install on the Library > Driver Feed page. The model specific packages contain drivers for Scripted Installations (Windows only)

24

K2000 Deployment Appliance v3.3, Administrator's Guide

and System Images. The Windows KBE packages contain drivers contained in the Windows Automated Installation Kit (WAIK). Note: The KBE packages are the same as the prebuilt KBEs shipped with the Dell KACE Deployment Appliance. You must enable the driver feed to populate the available driver package list, see Enabling the Driver Feed on page 16 for details. 1. Click Library > Driver Feed. 2. Click the driver package you want to add to the appliance cache. If the drivers are required for network booting, add the Windows PE package. 3. In Choose Action, click Download and Install Packages. The process begins. The Status column changes to Installed into driver share when the process completes. The drivers are automatically recached and appear in the driver list. The drivers are now available for Scripted Installations and System Images or KBE (if you installed a Windows PE pack). Manually adding drivers After downloading and uncompressing drivers from the manufacturer web site or other resource, upload the driver files to the appliance and recache the corresponding driver folder. Recaching a KBE folder from the Managing Drivers page makes the drivers available to Media Manager when building a KBE. Recaching an operating system folder makes the drivers available to Scripted Installations (Windows only).

Note: Leave the drivers in the corresponding folder, even after recaching, to make it available to the appliance processes. The system compatibility report shows cached driver availability. Removing a driver without recaching may cause booting, installation, and recovery errors that result in system failure and compromise the issues shown in the compatibility report.

K2000 Deployment Appliance v3.3, Administrator's Guide

25

The UNC path to the driver share \\K2000_hostname\drivers. Under each directory you can create subfolders to organize the drivers you add. The path to the driver, including the driver name, cannot exceed 255 characters, the directories and driver names do not support special characters. 1. Download and uncompress the drivers to a computer that can access the appliance drivers share. 2. Open the driver share. You set the share password in Driver/Restore Share Password on the Settings & Maintenance > General Settings page. 3. Put the driver files in a folder that corresponds to the process to which you want to make the drivers available. For example, to make drivers available to Media Manager for a 32 bit KBE build, put the drivers to kbe_windows_x86. 4. Go to Library > Drivers, and then in Choose Action click Recache Drivers. The Managing Drivers page appears. 5. Click the button that corresponds to the driver share folder. Recache All Drivers updates the every cache and can take a long time to execute. Only recache the folders that changed. For example, Recache K2000 Boot Environment (Windows x86) updates the drivers from kbe_windows_x86. 6. Click the Drivers tab. The Drivers list appears. 7. Using the View by menu, filter the driver list and verify that the drivers you added are now cached. For example, click View by > KBE (Windows x86) to show the drivers you added to kbe_windows_x86.

Preparing a computer to build KBE


This section explains how to download and install the tools required to build KBE for Windows. Installing Media Manager on Windows Media Manager builds and rebuilds boot environments, uploads operating system source, and Windows User States to the Dell KACE K2000 Appliance. Download and install the Media Manager from the K2000 appliance. Media Manager requires Microsoft .NET 2.0. Before you install Media Manager, download and install .NET 2.0 from the Microsoft Download Center. Search this web site for NET and the computer operating system name to find the files you need. Perform these steps on the computer where you installed .NET. 1. Log in to the Dell KACE K2000 Appliance Administrative Console. 2. Click Library > Media Manager. The Media Manager page appears. 3. Click Download for Windows (Requires .Net 2.0). The File Download window appears. 4. Click Run or Save to download the installation file to the computer and then double-click it to begin installation. The Welcome window appears.

26

K2000 Deployment Appliance v3.3, Administrator's Guide

5. Click Next. The Select Installation Folder window appears. 6. (Optional) In Folder, click Browse and select a folder. 7. Click Next. The Confirm Installation window appears. 8. Click Next. After a few moments the Installation Complete window appears. 9. Click Close. The Media Manager is now installed on the computer. To start Media Manager, go to Start > Programs > KACE > K2000 Media Manager. Installing Windows Automated Installation Kit (AIK) Before you can build the K2000 Boot Environment (KBE) you must install the Windows AIK for Windows 7 on either a Windows 7 computer or Windows 2008 Server. During the Windows AIK installation process you accept the EULA terms and conditions that gives the user permission to use WinPE 3.0 and USMT 4.0. And the WAIK ISO for Windows 7 contain most of the mass storage and Network card drivers that are required to boot computers using KBE (WinPE3.0). This task requires an ISO mounting software or a blank DVD, a Windows 7 computer or Windows 2000 server with an account on the machine with elevated privileges such as an administrator account. Log in to a Windows 7 computer or Windows 2008 Server using an account that has permission to install software, such as an administrator account. 1. Download the Windows AIK for Windows 7 from the Microsoft web site to the computer. Ensure that you get correct package. The WAIK for Windows 7 download takes a minimum of 2.5 hours to complete. 2. Install the Media Manager application while the WAIK ISO downloads, see Installing Media Manager on Windows on page 99. 3. To access the installation files, either burn the WAIK ISO file to a DVD or mount the ISO to the computer using an ISO mounting utility. 4. Run the WAIK installer, by double-clicking StartCD.exe. Once the Media Manager and Windows AIK are installed, you are ready to capture an image and build the K2000 Boot Environment.

Building a New Windows KBE


Use Media Manager to build a new Windows K2000 Boot Environment (KBE). Building a KBE adds the cached drivers on the K2000 appliance to the KBE. You build new KBEs on a Windows computer that has both the Windows AIK and Media Manager. Note: On Windows XP, .Net is required to build the KBE. 1. On the computer that is on the same network as the Dell KACE K2000 appliance, open Media Manager. Click Start > All Programs > KACE > Media Manager. The Media Manager appears. 2. In K2000 Hostname, enter the IP address or host name of the Dell KACE K2000 appliance. 3. Click the Create K2000 Boot Environment tab. 4. In Name, enter a unique string to identify the KBE on the appliance.
K2000 Deployment Appliance v3.3, Administrator's Guide 27

The process first builds the KBE and then verifies that the name is unique during the upload. The process will fail if there is already a KBE with the same name. 5. In Architecture, click the chipset type. 6. In WAIK Path, either click Browse and select then the WAIK location or enter the path. 7. Click Start Upload. When the process finishes, the new KBE appears in the Deployments > Boot Environments list and a copy is also put in Library > Source Media.

Building Mac Netboot Boot Environments


Before you can network boot a Mac OS X computer from the appliance, you must build and upload a Mac Netboot network booting environment using the Media Manager. Netboot boot environments are specific for the CPU archtecture (that is PowerPC or Intel x86). Create a boot environment for each type in your environment.

Installing Media Manager for MAC OS X


K2000 Media Manager builds NetBoot network booting environments and uploads system image captures. Perform these steps on the Mac OS X computer with an administrator account. Note: The installation disk for the computer is required to build a network booting environment. 1. Log in to the Dell KACE K2000 Appliance Administrative Console. 2. Click Library > Media Manager. The Media Manager page appears. 3. Click Download for Mac OS X. The File Download window appears. The Media Manager is installed. Click the Media Manager application to run it.

Building Mac OS X NetBoot Boot Environments


To build a Mac OS X NetBoot Boot Environment and upload it to the appliance, you must use the K2000 Media Manager available for download from the Media Manager page and the Mac OS X installation disk. 1. 2. 3. 4. 5. 6. Log on as an administrator to a Mac OS X system that is connected to the appliance. Open the Media Manager. Go to the Create NetBoot Image page. In K2000 Host Name, enter the host name or IP address of the appliance. Browse to and select the Mac OS X Installation disks. In NetBoot Password, enter the VNC-Java Remote Control application password that allows you to establish a remote connection to a Mac OS X computer that has network booted from the appliance. 7. In Confirm Password, reenter the password. The VNC password is stored in the NetBoot Environment, to change the password you must rebuild the environment. 8. Click Start Build.

28

K2000 Deployment Appliance v3.3, Administrator's Guide

When the NetBoot Environment upload completes, the NetBoot Environment appears on the Source Media and Boot Environments pages.

Setting the default boot environment


You can create and set up different K2000 Boot Environments (KBEs) and Netboot network booting environments to support the computers on your network. The appliance directs targets to the default KBE, unless you specify a Boot Action for that computer. The appliance ships with a standard Windows (x86) for 32 bit computers and Windows (x64) for 64 bit computers. These KBEs include the drivers provided in the Windows Automated Installation Kit (AIK). Before you can network boot Mac computers, you must build the Boot Environment. 1. Click Settings & Maintenance > General Settings. The General Settings page appears. 2. Click Edit. 3. Under Default K2000 Boot Environments, click the name of the Boot Environment you want to assign for each type of target. 4. Click Save. The next time the target network boots from the appliance the default boot environment is used unless specifically assigned by a Boot Action.

Directing network boots to the appliance


To support network booting from the KACE K2000 Deployment appliance, the appliance hosts a PXE (Preboot Execution Environment) boot server for Windows clients and BSDP compatible boot server for MAC clients. Before you can capture and deploy images, install operating systems, or recover systems from the appliance, you must direct network boot requests to the appliance. Configure the DHCP server to direct PXE requests and a NetBoot server to direct BSDP requests to the K2000 appliance or RSA in remote sites.

Directing Mac network boot (BSCP) request


This section explains how to enable and configure the appliance NetBoot Server from the Administrative Console. A NetBoot Server directs network boot (BSCP) requests from the Mac nodes in your environment to the appliance. Only one NetBoot Server can be present on a subnet. To direct BSCP request across a subnet, see the Technical Note on the Dell KACE support site. Note: When a NetBoot Server already exists, configure the server with the settings described in this section.

K2000 Deployment Appliance v3.3, Administrator's Guide

29

To enable and configure the appliance NetBoot server: 1. Log in to the K2000 Administrative Console. 2. Go to Settings & Maintenance > Control Panel > Network Settings. The Network Settings page appears. 3. Click Edit. 4. Click the Enable NetBoot Server (for Mac OS X client) check box. The NetBoot Server fields appear. 5. Set the BSDP settings: BSDP Server Priority BSDP Image Index 6. Click Save. The next time a networked MAC client starts up, the NetBoot server present the Dell KACE K2000 appliance boot option to the user. Targets that are not assigned a Boot Action get the default Boot Environment specified for the type of computer, see Setting the default boot environment on page 29. Use the default, for example 32768. Use the default setting, for example 52230.

30

K2000 Deployment Appliance v3.3, Administrator's Guide

Directing PXE requests


Direct Windows Preboot Execution Environment (PXE) requests from clients to the Dell KACE K2000 appliance using the DHCP server. On the DHCP or Proxy DHCP server, set the following Bootstrap Protocol (BootP) parameters. If you have more than one scope, set the parameters for each one.
Option 66 67 Parameter BootP Server BootP Client Port 67 68 Value Enter the IP address or host name of the K2000 appliance or RSA. Enter kbox2000.0 for the bootstrap file name.

Note: The next time a client (that is PXE compliant Windows client) on the network starts, it downloads the bootstrap file from the appliance and boots from the appliance if assigned a Boot Action or if the user selects a KBE option. Directing PXE Requests on a WAN When deploying the K2000 across a Wide Area Networks (WAN), set up a DHCP scope for each location, such as a Austin, San Jose, and Boston offices shown below, and redirect clients to the Remote Share Appliance (RSA) or K2000 appliance instance on their LAN.

K2000 Deployment Appliance v3.3, Administrator's Guide

31

Setting up an external DHCP server


If your network already has a DHCP server that assigns IP addresses, configure BootP (Boot Parameters) Server and Client settings to allow Windows clients to locate the appliance and download the bootstrap file. To configure network boot parameters on a Windows DHCP 2003 Server: 1. On the DHCP Server, open the DHCP Manager by clicking Start > Programs > Control Panel > Administrator Tools > DHCP. 2. Configure client redirects as follows: For WAN set up Windows client redirects on each scope, click the name of the scope, click Scope Options, then right-click and choose Configure Options. For LAN (without scopes) set up redirect for all Windows clients, click Server Options, then right-click and choose Configure Options.

The Configuration window appears. 3. Click the General tab. 4. Click the Option 066 check box, and enter the FQDN or IP address of the local appliance (either the K2000 appliance or RSA instance). 5. Click the Option 067 check box, and enter kbox2000.0 for the bootstrap file name. 6. Click OK to apply the changes and then close the DHCP Manager. The DHCP server automatically redirects PXE compliant Windows clients to the appliance the next time they start up while connected to the network, the clients download the bootstrap file, and use the environment set up by the K2000 administrator to boot.

Directing PXE requests from the appliance


The appliance has a built-in DHCP Server. This section describes the process of enabling the DHCP Server. The appliance DHCP Server assigns a specific range of IP addresses to your networked clients and automatically set ups redirection of Windows client boots to the appliance. Before you configure this setting ensure that the appliance is the only DHCP server on the network and you configure the router to forward DHCP request to the appliance. Note: Routers in smaller environments typically have a hardware port that it forwards this type of traffic to. Plug the appliance ethernet cable into this hardware port. To enable DHCP on the appliance: 1. Log in to the Administrative Console. 2. Go to Settings & Maintenance > Control Panel > Network Settings. The Network Settings page appears. 3. Click Edit. 4. Click Enable On-board DHCP. The DHCP range fields appear. 5. In DHCP Pool Start, enter the lowest IP address in the range. 6. In DHCP Pool End, enter the highest IP address in the range. 7. Click Edit.

32

K2000 Deployment Appliance v3.3, Administrator's Guide

Setting up a Remote Site Appliance


A Remote Site Appliance (RSA) extends a K2000 Deployment Appliance to a location where a group of computers have higher bandwidth, that is faster connections, between each other than the K2000 appliance. Use RSAs to network boot, deploy System Images, Scripted Installations, and migrate Users Profiles in the remote location. RSA licenses are purchased separately. Note: The RSA is a virtual machine that runs on a computer or on VMware Vsphere at the remote site. The K2000 appliance replicates the deployment data to the RSA at scheduled intervals, typically when network traffic is low. Setting up an RSA requires the following: K2000 appliance: After you have installed and configured a K2000 appliance, you can purchase an RSA license and install it from the K2000 appliance. RSA License: Key sent to you by Dell KACE. Virtual Machine host with supported VMware product, see host system requirements below. Network settings: Static IP address and (optional) host name that you can assign to the RSA. (Optional) LDAP: LDAP server IP or host name, search filter for the K2000/RSA administrators, and account that the RSA uses to authenticate users. Network boot configuration: DHCP server scope that directs Windows PXE requests and NetBoot server that directs Mac BSCP requests from the remote computers to the RSA. RSA host system requirements The computer that hosts the RSA must meet the following minimal requirements:
Requirement Virtual Machine Description An installed version of an OVF compatible virtual machine, such as vSphere 4, ESX v4, or VMware Server 1.0 and 2.0. Note: To use VMware ESX version 3.x, you must convert the Virtual Appliance OVF. See the technical note on the Dell KACE support site.

Platform Hardware Ports

Windows-based system 2 GHz processor (Intel-VT or AMD-V capable) 4 GB RAM 250 GB of free disk space Ports 22 and 80 open.

Note: The RSA can also be hosted on Vsphere.

K2000 Deployment Appliance v3.3, Administrator's Guide

33

Downloading the RSA OVF


Download the RSA OVF package from the K2000 appliance Administrative Console to the computer at the remote site that will host the RSA. Perform these steps from the RSA host computer. 1. Log on to the K2000 Appliance. 2. Go to Deployments > Remote Sites. 3. In Choose Action, click Download Remote Site Appliance OVF. The Download Remote Site Appliance OVF Image page appears. 4. Click the download link and save the Zip file to the RSA host computer.

Installing RSA
On the host of the RSA where you installed VMware Workstation or Vsphere client, follow these instructions to create the RSA virtual machine. Note: The instructions in this section walk you through the process of creating an instance of RSA using VMware Workstation. Consult the VMware documentation for instructions on opening an OVF into other supported VMware products. 1. Unzip the RSA package. 2. Open the VMware Workstation. 3. Click File > Open. The Open Virtual Machine dialogue appears.

4. In Files of Type, click Open Virtual Machine Format Images and then browse to the location where you unzip the RSA package. 5. Select the K2000 extender OVF file and click Open. 6. Click Create Full Clone.

34

K2000 Deployment Appliance v3.3, Administrator's Guide

A progress bar displays and when the process completes, the home screen appears. 7. Right-click the RSA virtual machine and choose Play Virtual Machine. The Virtual RSA console appears and the machine boots up. Before you can begin using the RSA you must configure it from the console.

Configuring network settings from the console


Configure the appliance host name, web server name, and static IP address from the appliance console after the first boot. To access the console, connect a monitor and keyboard directly to the appliance or when configuring a trial version or RSA on a virtual machine, open the virtual machine console. To set up the appliance: 1. Power on the appliance. The appliance requires 5 to 10 minutes to start up for the first time. 2. At the login prompt, enter: Login: konfig

Password: konfig 3. Modify the following settings using the Up and Down arrow keys to move between fields. Field K2000 Server (DNS) Hostname Enter the name used to access the appliance from nodes. Node users connect to the appliance using the Web Server Name, which can be the hostname, FQDN (fully-qualified domain name), or IP address. The default setting is ikbox. (Recommended) Enter the static IP address of the appliance server. Static IP Address Enter the domain that the appliance is on. Domain Enter the subnet mask. Subnet mask Enter the network gateway for the appliance server. Default gateway Enter the IP address of the primary DNS server the appliances uses to resolve host names. Description Enter the host name of the appliance. The default setting is ikbox.

Web Server Name

Primary DNS

K2000 Deployment Appliance v3.3, Administrator's Guide

35

4. Press the Down arrow to move the cursor to Save, and then press Enter or Return. The appliance restarts. The initial configuration is complete. After the appliance finishing rebooting the Web Interface (Administrative Console) should be accessible. Connect the appliance to the network, and finish the configuration using a browser to access the Administrative Console (http://K2000_hostname).

Activating the RSA


Before you can use the RSA, you must enter the license key. 1. Log into the Administrative Console by opening a browser and entering the hostname of the RSA. The default account is username admin with password admin. 2. Go to Settings & Maintenance > Registration & Licensing. 3. Click Edit, and then click Add License Key. The License Key field appears. 4. In License Key, enter the key sent to you by Dell KACE when you purchased the RSA. 5. Click Save. You are automatically logged out of the Administrative Console.

Configuring the date & time settings


By default, the system clock is set to synchronize with the Dell KACE time server. Use these instructions to manually change the system clock or synchronize with a different NTP server. Setting the system clock prevents unexpected behavior, such as running resource intensive backups in the middle of the day. Note: Dell KACE K2000 appliance deployment operations, scheduled backups, exports, and offboard transfers rely on the date and time of the system clock. The appliance log timestamps are recorded in the appliance time zone. The K2000 database contains date and time in UTC, and is converted to the specified time zone when displayed to the user.

Synchronizing the system clock


Set up automatic synchronize between the system clock and an NTP server to automatically update the system clock. You can also synchronize with a NIST Internet Time Server, see for a list of available servers (http://tf.nist.gov/tf-cgi/servers.cgi). To perform these steps, log in to the Administrative Console using an appliance Administrator account. To set up synchronization with an NIST Internet Time Server: 1. Click Settings & Maintenance > Control Panel > Date & Time Settings. The Date & Time Settings page appears. 2. Click Edit to activate page menus. 3. In Time Zone, click the name of the appropriate time zone. 4. Clear Set the clock on the K2000 manually. 5. Click Automatically synchronize with Internet time server.
36 K2000 Deployment Appliance v3.3, Administrator's Guide

The Time Server field appears. 6. In Time Server, enter the FQDN or the IP address of the NIST Internet Time Server or the host name of the time server on the local network. For example, nist1.aol-ca.symmetricom.com. 7. Click Save. After changing the Date & Time Settings, the Dell KACE K2000 Appliance restarts. This disrupts appliance operations for 10 to 15 seconds and active connections are dropped. Manually refresh the browser and log in to display the new Date & Time Settings.

Manually configuring the date and time


Dell KACE K2000 appliance launches and logs deployment operations based on the date and time of the system clock. This section explains how to manually set the clock. To perform these steps, log in to the Administrative Console using an appliance Administrator account. To set up synchronization with an NIST Internet Time Server: 1. Click Settings & Maintenance > Control Panel > Date & Time Settings. The Date & Time Settings page appears. 2. Click Edit. 3. In Time Zone, click the name of the time zone the appliance is in. 4. Clear Automatically synchronize with Internet time server. 5. Click Set the clock on the K2000 manually. The New Time and New Date fields appear. 6. In New Time, set the correct H (hour), M (minute), and S (second) options. 7. In New Date, set the correct M (month), D (day), and Y (year) options. 8. Click Save. After changing the Date & Time Settings, the Dell KACE K2000 Appliance restarts. This disrupts appliance operations for 10 to 15 seconds and active connections are dropped. Manually refresh the browser and log in to display the new Date & Time Settings.

Configuring authentication settings


The Remote Site Appliance (RSA) supports authenticating administrators against a local internal database or an external LDAP server. Use the same authentication method on the RSA as the K2000 appliance it extends. The Remote Site Appliance supports single sign-on. Administrators with an account on the RSA and K2000 appliance can access both Administrative Consoles from the same session. Note: When using single sign-on and the local authentication method, the credentials (user name and password) on the linked appliances must match.

Changing the admin password


All K2000 appliances have internal user database with a default account, admin. The admin account always authenticates against the internal database, even if the appliance is configured to authenticate administrators

K2000 Deployment Appliance v3.3, Administrator's Guide

37

against an external LDAP server. The account is persistent: you cannot disable it, change the user name, or change the permissions. Note: To allow the admin account to access all linked appliances using single-sign on, the password on each linked appliance must be the same. Manage the admin account settings, including resetting the password, from the Administrative Console of each appliance. 1. Click Settings & Maintenance > Control Panel > Users. The Users page appears. 2. Click the user admin. The Edit User Details page appears. 3. In Password a new password, and then in Confirm Password reenter the password. 4. Click Save. The next time the admin logs in, the new settings apply.

Adding a local administrator account


Set up administrator accounts in the K2000 user database when an external LDAP service, such as Active Directory, is not available in your environment. This method stores user information locally. To use Single Sign-on for linked appliance and the local administrator database, account information (that is login and password) must be the same on all linked appliances. If LDAP is enabled, all local accounts become inactive except for the admin account. Add users in the appliance Administrative Console. Only the user name, email address, password, and permissions fields are required. 1. Click Settings & Maintenance > Control Panel > Users. The Users page appears. 2. In Choose Action, click Add New User. The Edit User Details page appears. 3. Complete the user account form: User Name Full Name Email Domain Budget Code Location Password Enter a login ID. Enter the users first and last name. Enter the users email address. Enter the name of the domain the user is in. (Optional) Enter the budget code of the department the user is in. (Optional) Enter the site or location of the user. Enter the default password for the user. This field is required to activate the user. If the field is blank the user cannot log into the Administrative Console. Reenter the password.

Confirm Password

38

K2000 Deployment Appliance v3.3, Administrator's Guide

Permissions

Choose a role for the user: User: No access to Administrative Console. Admin: Read/write access to Administrative Console. ReadOnly Admin: View only access to Administrative Console.

4. Click Save. The Users page appears. The user appears in the local account list and can now log in to the Administrative Console.

Setting up external authentication


Configure the Dell KACE K2000 appliance to authenticate appliance administrators against an external LDAP directory service, such as Active Directory (AD). This allows users to log into the Administrative Console with their domain credentials. Enabling an external authentication automatically disables the local user accounts, except for the admin account. Note: When logging in, the appliance automatically queries each listed external server; the timeout for a server is approximately 10 seconds. Dell KACE recommends deleting the sample LDAP server to decrease login delays. Log in to the Administrative Console to add an external LDAP directory. 1. Click Settings & Maintenance > Control Panel > User Authentication. 2. Click Edit. 3. Click External LDAP Server Authentication. Choosing this option disables all the local user accounts except for the admin account. 4. Click Add New Server. You can also modify the sample Admin Server. The New LDAP Server form appears below the existing servers (if any). 5. Enter the following information for the LDAP Service: Field Server Friendly Name Server Hostname (or IP) LDAP Port Number Description Enter a name for the server that identifies it in the list of external LDAP servers. Enter LDAP server IP address or host name. The appliance uses this address to authenticate users. Enter the LDAP Port number, the default is 389. Note: Contact Dell KACE support if you are using LDAPS, default port 636.

K2000 Deployment Appliance v3.3, Administrator's Guide

39

Field Search Base DN

Description Specify which area of the LDAP tree the appliance should begin to search for users. For example, specify OU=it, DC=kace, DC=com to search the IT group. Note: Searching the entire directory may cause lag time during login. Limiting the search base decreases these delays.

Search Filter

Enter (LDAP_attribute=KBOX_USER) where the LDAP_attribute is the name of the attribute that contains a unique user ID and KBOX_USER is a variable the appliance replaces at runtime with the Login ID the user enters. For example for Active Directory enter(samaccountname=KBOX_USER)and for most other LDAP servers enter (UID=KBOX_USER). Enter the bind DN; that is the user account with permission to query the search base. Use either the DN format: CN=username,DC=company, DC=com or the user principal name format username@company.com. Note: If the field is left blank the appliance connects to the LDAP server using an anonymous bind.

LDAP Login

LDAP Password (if required) User Permissions

Enter the LDAP account password. Choose the permissions to assign to a user the first time they successfully log in: Admin: Read/write access. ReadOnly Admin: View all pages, no change access. User: No access.

Test LDAP Password

Change the KBOX_USER variable in the Search Filter to a valid Login ID, for example (samaccountname=jsmith) and enter the corresponding password for the LDAP account and click Test LDAP Settings. Note: Be sure to change the user name in the Search Filter back to the system variable KBOX_USER.

6. (Optional but recommended.) Click the delete button next to any external servers that are not configured to actual servers in your environment. 7. Click Save. The next time a user logs in, the appliance authenticates them against the LDAP servers in the order they are listed. Note: The admin account always authenticates against the internal database, even if an account with the same name exists in an external LDAP. This makes the appliance accessible when no LDAP services are available.

40

K2000 Deployment Appliance v3.3, Administrator's Guide

Linking the RSA and the K2000 appliance


Before you can synchronize data from the K2000 appliance, manage systems in the remote location, and perform other operations, you must link the RSA and K2000 Deployment Appliance. To establish a link, you must enable linking and add a link on both systems. 1. Enable linking on both appliances (RSA and K2000): a) Log in to the Administrative Console and go to Settings & Maintenance > Control Panel > KACE Linking. b) Click Edit and then Enable KACE Linking. The connection settings appear. c) In K2000 Friendly Name (this server), enter a unique name that displays in the system list for single sign-on. d) In Remote Login Expiration, enter the duration of a single sign-on session in minutes. This is the length of time that a user logged into a remote linked appliance is able to access this appliance from the system list without re-entering their credentials. e) In Request Timeout, enter the number of seconds the remote appliance should wait before timing out while this appliance authenticates the login credentials from the remote appliance. f) Click Save. The KACE Linking Key Fingerprint and KACE Linking Key (this server) appear. g) Repeat these steps on the other appliance. 2. Create a link on both appliances to the other appliance (RSA and K2000): a) Click Settings & Maintenance > Control Panel > KACE Linking. The KACE Linking page appears. b) Click in the KACE Linking Key text box to highlight the text, and then right-click and select Copy.

c) On the other appliance, open Settings & Maintenance > Control Panel > Manage Linked Appliances. The Linked Appliances page appears. d) In Choose Action, click Add New Linked Appliance. The Add Linked Appliance page appears. e) In Host Name, enter the remote appliances DNS host name. The host name must match the host name set on the remote appliance Settings & Maintenance > Control Panel > Network Settings page. f) In Linking Key, paste the contents you copied from the remote appliances KACE Linking Key field. g) Click Save.

K2000 Deployment Appliance v3.3, Administrator's Guide

41

h) Repeat these steps on the other appliance. 3. After both links are created, click Test Connection on the Edit Linked Appliance Detailpage. The appliances are linked and when administrators with account on both appliances log in they can access the Administrative Console from the same session. Next, set up the RSA as an extension of the K2000.

Extending the K2000 Appliance


After linking a Remote Site Appliance, configure it as an extension of the K2000 appliance and synchronize components you want to use at the remote site. An RSA can extend one K2000 appliance only. Note: The RSA deploys Scripted Installations and System Images and acts as a local boot server. User States are deployed from the K2000 Appliance across the Wide-Area-Network. Perform these steps from the Administrative Console of the K2000 appliance. 1. Click Deployments > Remote Sites. The Remote Site Appliances page appears. 2. In Choose Action, click Add New Remote Site Appliance. The Add a Remote Site Appliance page appears. 3. In Remote Site Appliances, click the friendly name of the RSA. 4. Click Next. The K2000 Appliance connects to the RSA and registers it as an extension. When the process completes, the Remote Site Details page appears. 5. Scroll down to Boot Environments, click the default Boot Environments. Boot Environments are required to network boot computers to the RSA at the remote location and test your RSA configuration. If you have additional components you are ready to replicate, select those items. 6. Click Save and Sync. The RSA is locked until the synchronization completes. The RSA is ready for network booting.

Directing network boots to the RSA


Direct network boot requests in remote locations to the Remote Site Appliance (RSA) using a DHCP scope for PXE requests (Windows) and a NetBoot Server on the same subnet for BSDP requests (MAC).

Directing Mac network boot (BSCP) request


This section explains how to enable and configure the appliance NetBoot Server from the Administrative Console. A NetBoot Server directs network boot (BSCP) requests from the Mac nodes in your environment to the appliance. Only one NetBoot Server can be present on a subnet. To direct BSCP request across a subnet, see the Technical Note on the Dell KACE support site. Note: When a NetBoot Server already exists, configure the server with the settings described in this section.

42

K2000 Deployment Appliance v3.3, Administrator's Guide

To enable and configure the appliance NetBoot server: 1. Log in to the K2000 Administrative Console. 2. Go to Settings & Maintenance > Control Panel > Network Settings. The Network Settings page appears. 3. Click Edit. 4. Click the Enable NetBoot Server (for Mac OS X client) check box. The NetBoot Server fields appear. 5. Set the BSDP settings: BSDP Server Priority BSDP Image Index 6. Click Save. The next time a networked MAC client starts up, the NetBoot server present the Dell KACE K2000 appliance boot option to the user. Targets that are not assigned a Boot Action get the default Boot Environment specified for the type of computer, see Setting the default boot environment on page 29. Use the default, for example 32768. Use the default setting, for example 52230.

K2000 Deployment Appliance v3.3, Administrator's Guide

43

Directing PXE requests from the appliance


The appliance has a built-in DHCP Server. This section describes the process of enabling the DHCP Server. The appliance DHCP Server assigns a specific range of IP addresses to your networked clients and automatically set ups redirection of Windows client boots to the appliance. Before you configure this setting ensure that the appliance is the only DHCP server on the network and you configure the router to forward DHCP request to the appliance. Note: Routers in smaller environments typically have a hardware port that it forwards this type of traffic to. Plug the appliance ethernet cable into this hardware port. To enable DHCP on the appliance: 1. Log in to the Administrative Console. 2. Go to Settings & Maintenance > Control Panel > Network Settings. The Network Settings page appears. 3. Click Edit. 4. Click Enable On-board DHCP. The DHCP range fields appear. 5. In DHCP Pool Start, enter the lowest IP address in the range. 6. In DHCP Pool End, enter the highest IP address in the range. 7. Click Edit.

44

K2000 Deployment Appliance v3.3, Administrator's Guide

Capturing user states for online migration

Migration saves the user state on the appliance and allows you to put it on any number of targets during a Scripted Installation or System Image deployment. This preserves the users files, profile, and preferences while you change, fix, or replace their computer or operating system. Users are then able to access their files and settings are just as they remember. Scanning requires the Microsoft Windows User State Migration Tool software included in the Windows AIK (Automated Installation Kit). Upload USMT before performing a scan. K2000 captures user states by running the Scan State utility on the target. You can run the scan with the default settings or customize the capture using a USMT Scan Template.

Excluding users and data from a capture


The appliance migrates user profiles by running the USMT Scan State and Load State utilities. Before scanning targets for user states, configure the USMT Templates that set the Scan State utility parameters and allow you to exclude users, Windows and Document components, types of files, and specific files from the capture. You can also use a template to change the default runtime options, including logging, and debugging, and using the command line parameters for Windows Vista computer. Before capturing users for online migration or deploying a Scripted Installation or System Image to migrate users offline, configure a template. The default template, captures all users, components, and files. 1. 2. 3. 4. Click Library > USMT Scan Template. In Choose Action, click Add New Scan Template. In Name, type a unique name that identifies the template. Set the User selection options: Click Specify users to be excluded and enter a comma separated list of user IDs to ignore these profiles during online and offline target scans. The profiles are not captured. Click Scan all available user states to show all profiles during an online migration scan or to migrate all profiles on the target during an offline migration.

K2000 Deployment Appliance v3.3, Administrator's Guide

45

5. Set the Command line options for the Scan State utility runtime. In most cases, use default command line options. 6. Set the Content configuration options for capturing the Windows and Document Components Click Specify config file and upload a configuration file to exclude components using a custom configuration file. This option overrides the options Enabled under the Windows Components to be scanned and Documents to be scanned sections. Disable Specify config file and enable the components that you want to capture under the Windows Components to be scanned and Documents to be scanned sections.

7. Click Save. The USMT Scan Template is now available when scanning users for online migration from the User States page.

Uploading the Windows User State Migration Tool


Migrating users from one Windows target to another or upgrading the operating system from one version to another, such as XP to Windows 7, requires the Windows User State Migration Tool (USMT). The Windows Automated Installation Kit (AIK) includes USMT version 4.0. Upload the USMT to the Dell KACE K2000 appliance to prepare for Windows migrations. Note: On the Library > User States > Upload USMT Software page, you can upload the USMT v4.0 in a zip file or get USMT v3.0 from Microsofts web site. This task requires the Media Manager (See Installing Media Manager on Windows on page 99) and Windows AIK (see Installing Windows Automated Installation Kit (AIK) on page 100). 1. Open Media Manager, click Start > All Programs > KACE > K2000 Media Manager. The Media Manager appears. 2. In the Hostname field, enter the IP address or host name of the appliance. 3. Click the Upload USMT tab. 4. Click Browse and locate the Windows AIK. The default location is C:\Program Files\Windows AIK. 5. Click Start Upload. The USMT version 4.0 displays in the Library > User States > Scan New User State > USMT drop-down and is available for offline migration during a scripted installation.

Capturing user states from a target


The User States feature scans a target and captures user profiles and saves them to the K2000 for deployment. When the deployment includes the Deploy User State Postinstallation Task, you can select the profiles that you want to load onto the target when assigning a Boot Action.
46 K2000 Deployment Appliance v3.3, Administrator's Guide

Scanning requires USMT, an administrator account, and that the target is powered on and connected to the network. The target must have the following settings: All Windows systems using a firewall: File and Print Sharing is enabled. This setting is on the Exceptions list of the Firewall Configuration. Windows XP systems: Simple File Sharing is off. Windows 2000 SP4 systems: The Windows installer version (C:\WINDOWS\system32\msi.dll) is 3.0.1 or later. Windows 7 and Windows Server 2008: The Network Security LAN Manager Authentication Level is set to Send LM and NTLM responses. 1. Go to Library > User States. The User States page appears. 2. In Choose Action, click Scan New User State. The Host Scan form appears. 3. Complete the form for the targets you are scanning: Host Name/IP Enter the fully qualified hostname or IP address for the target system or enter a range of computers using a Comma, semicolon, and newline separated list. Note: To scan multiple hosts, enter one host name or IP per line. Domain User Name Password

Optional, unless the authenticating user is a domain user. Enter a user that has administrator privileges on the target system. Password of the user.

Confirm Password Reenter the password. USMT Version to be used USMT Template Select the User State Migration Tool version compatible with the operating system you are scanning. (Only available when using USMT v4.0 or higher) Select the name of USMT Scan Template that you want to use for the capture. A template determines which items to capture.

4. Click Next. The process status displays. If process completes successfully, a list of profiles appears. 5. Select the profiles that you want to capture onto the appliance and then click Next. The Results Log appears. 6. Click Finish. The User States that you selected are uploaded to the appliance. When the upload completes, they appear in the User State list and are available to assign to Scripted Installations and System Images.

K2000 Deployment Appliance v3.3, Administrator's Guide

47

Loading user profiles on targets


Online migration allows you to put user profiles that have been captured, using a scan, on target computers by assigning the Deploy User State Post Installation Task to the Scripted Installation or System Image and then selecting the user profiles you want to load when you assign the Deployment task to a system as Boot Action. Offline migration allows you capture the user profiles on the systems assigned to the Deployment task as Boot Action. The appliance captures the profiles if the Scan User States Offline Preinstallation Task is assigned to the Scripted Installation or System Image and then reloads those profiles after installation with the Deploy User States Post Installation Task. Once the profiles are captured (that is when the Scan User State Offline Preinstallation Task completes) the profiles are available for online migration. Note: When performing an offline migration, you can also choose to load additional profiles that are available on the appliance. Completing these steps requires: a Scripted Installation or System Image, target systems, and captured user states. Add the Deploy User States Post Installation Task to the Scripted Installation or System Image: a) Click Deployments, and then System Images or Scripted Installations. b) Click the name of the item to show the details. c) Scroll down to Installation Plan. The available and assigned tasks appear.

d) Drag Deploy User States Post Installation Task from the Available Postinstallation Tasks column on the right to the Run Postinstallation Tasks column on left. Set the execution order by moving it up and down in the list. e) Click Save. The appliance rebuilds the Deployment. When this Deployment item is assigned as a Boot Action, you are prompted to select user profiles from the list on the User States page.

48

K2000 Deployment Appliance v3.3, Administrator's Guide

Installing Operating Systems from source

The Scripted Installation feature allows you to set up a network installation of a Windows Operating System that preserves the targets data and automatically customizes and completes the computer setup. You can deploy the Scripted Installation from the appliance to target systems automatically on the next network boot, choose to install it from the Boot Manager interface of a network booted target, or install it from a USB drive. The following components are required to create a Scripted Installation:

Source Media: Installation disks or the ISO image. Upload the operating system installation disks using Media Manager that you want to deploy from the appliance. Drivers: Additional drivers for the targeted platforms that are not included on the Source Media. You must identify the drivers required by your target and add any missing drivers to the appliance share and cache the meta data to allow the appliance installation process to locate and install the drivers during the deployment. User Profiles: Capture and store user states on the appliance and migrate the profile to the targets during the deployment or capture the user states on the computer during the deployment and load them back onto the computer after the operating system installation.

K2000 Deployment Appliance v3.3, Administrator's Guide

49

Preinstallation Tasks: Automatically backup data from the target and prepare it for a clean operating system installation by partition and reformatting the hard drive. Set up tasks that the appliance can execute on the target while it booted into KBE. Postinstallation Tasks: Automatically customizes and finishes the installation by installing patches, applications, user profiles, naming the computer, joining the computer to the domain, and so forth. Set up tasks that the appliance executes after the operating installation while still booted into KBE or after the first reboot in the new operating system environment (Windows). Prerequisite checklist Before you can create and deploy a Scripted Installation, you must set up the following items: Network connection between the target PC and K2000 appliance DHCP server that directs PXE boot requests from the target PC to appliance Target PCs first boot option is set to Network Boot (NIC) K2000 Boot Environment (KBE) with all drivers required by target PC to network boot Note: To install from appliance on next network boot, you must assign the boot environment as the Default KBE. Administrator computer with Media Manager and Windows Installation media

Setting up Library Components


Before you can create a Scripted Installation you must populate your Library with all the components that you want to include.

Uploading Operating System Installation Files


Scripted Installations install an operating system from source on to a target computer. This section explains how to upload the source media required for the operating system installation process. Note: Uploads can take a significant amount of time depending on the connection speed. To upload the original installation media, the following items are required: K2000 Media Managed and .Net 2.0 Installation disks or mounted ISO image

Installing Media Manager on Windows


Media Manager builds and rebuilds boot environments, uploads operating system source, and Windows User States to the Dell KACE K2000 Appliance. Download and install the Media Manager from the K2000 appliance.

50

K2000 Deployment Appliance v3.3, Administrator's Guide

Media Manager requires Microsoft .NET 2.0. Before you install Media Manager, download and install .NET 2.0 from the Microsoft Download Center. Search this web site for NET and the computer operating system name to find the files you need. Perform these steps on the computer where you installed .NET. 1. Log in to the Dell KACE K2000 Appliance Administrative Console. 2. Click Library > Media Manager. The Media Manager page appears. 3. Click Download for Windows (Requires .Net 2.0). The File Download window appears. 4. Click Run or Save to download the installation file to the computer and then double-click it to begin installation. The Welcome window appears. 5. Click Next. The Select Installation Folder window appears. 6. (Optional) In Folder, click Browse and select a folder. 7. Click Next. The Confirm Installation window appears. 8. Click Next. After a few moments the Installation Complete window appears. 9. Click Close. The Media Manager is now installed on the computer. To start Media Manager, go to Start > Programs > KACE > K2000 Media Manager.

Uploading OS Installation Source Media


Use the Media Manager to upload the operating system installation files from an ISO image or disk on a computer connected to the appliance. 1. Insert the first Operating System disk into the media drive on the remote system. 2. Click Start > All Programs > KACE > K2000 Media Manager. The Media Manager appears. 3. In K2000 host name, type the host name or IP address of the appliance. 4. Go to the Upload Windows Media tab. 5. In Source CD Name, type a unique logical name. This name identifies the image on the appliance; it is used to assign the image to scripted installs, boot actions, and so on. 6. In Source Type, click the name of the operating system. 7. In Path, click Browse and select the location of the image. 8. Click Start Upload. The process of uploading the source begins and can take several hours. When the process completes the image appears on the K2000 appliance on the Library > Source Media page.

Viewing Source Media details


On the Source Details page you can add notes and change the name. 1. Click Library > Source Media.

K2000 Deployment Appliance v3.3, Administrator's Guide

51

The Source Media page appears. 2. Click the name of the source. The details page of the selected source appears.

Capturing user states for online migration


Migration saves the user state on the appliance and allows you to put it on any number of targets during a Scripted Installation or System Image deployment. This preserves the users files, profile, and preferences while you change, fix, or replace their computer or operating system. Users are then able to access their files and settings are just as they remember. Scanning requires the Microsoft Windows User State Migration Tool software included in the Windows AIK (Automated Installation Kit). Upload USMT before performing a scan. K2000 captures user states by running the Scan State utility on the target. You can run the scan with the default settings or customize the capture using a USMT Scan Template.

Excluding users and data from a capture


The appliance migrates user profiles by running the USMT Scan State and Load State utilities. Before scanning targets for user states, configure the USMT Templates that set the Scan State utility parameters and allow you to exclude users, Windows and Document components, types of files, and specific files from the capture. You can also use a template to change the default runtime options, including logging, and debugging, and using the command line parameters for Windows Vista computer. Before capturing users for online migration or deploying a Scripted Installation or System Image to migrate users offline, configure a template. The default template, captures all users, components, and files. 1. 2. 3. 4. Click Library > USMT Scan Template. In Choose Action, click Add New Scan Template. In Name, type a unique name that identifies the template. Set the User selection options: Click Specify users to be excluded and enter a comma separated list of user IDs to ignore these profiles during online and offline target scans. The profiles are not captured. Click Scan all available user states to show all profiles during an online migration scan or to migrate all profiles on the target during an offline migration.

5. Set the Command line options for the Scan State utility runtime. In most cases, use default command line options. 6. Set the Content configuration options for capturing the Windows and Document Components Click Specify config file and upload a configuration file to exclude components using a custom configuration file. This option overrides the options Enabled under the Windows Components to be scanned and Documents to be scanned sections. Disable Specify config file and enable the components that you want to capture under the Windows Components to be scanned and Documents to be scanned sections.

7. Click Save. The USMT Scan Template is now available when scanning users for online migration from the User States page.

52

K2000 Deployment Appliance v3.3, Administrator's Guide

Uploading the Windows User State Migration Tool


Migrating users from one Windows target to another or upgrading the operating system from one version to another, such as XP to Windows 7, requires the Windows User State Migration Tool (USMT). The Windows Automated Installation Kit (AIK) includes USMT version 4.0. Upload the USMT to the Dell KACE K2000 appliance to prepare for Windows migrations. Note: On the Library > User States > Upload USMT Software page, you can upload the USMT v4.0 in a zip file or get USMT v3.0 from Microsofts web site. This task requires the Media Manager (See Installing Media Manager on Windows on page 99) and Windows AIK (see Installing Windows Automated Installation Kit (AIK) on page 100). 1. Open Media Manager, click Start > All Programs > KACE > K2000 Media Manager. The Media Manager appears. 2. In the Hostname field, enter the IP address or host name of the appliance. 3. Click the Upload USMT tab. 4. Click Browse and locate the Windows AIK. The default location is C:\Program Files\Windows AIK. 5. Click Start Upload. The USMT version 4.0 displays in the Library > User States > Scan New User State > USMT drop-down and is available for offline migration during a scripted installation.

Capturing user states from a target


The User States feature scans a target and captures user profiles and saves them to the K2000 for deployment. When the deployment includes the Deploy User State Postinstallation Task, you can select the profiles that you want to load onto the target when assigning a Boot Action. Scanning requires USMT, an administrator account, and that the target is powered on and connected to the network. The target must have the following settings: All Windows systems using a firewall: File and Print Sharing is enabled. This setting is on the Exceptions list of the Firewall Configuration. Windows XP systems: Simple File Sharing is off. Windows 2000 SP4 systems: The Windows installer version (C:\WINDOWS\system32\msi.dll) is 3.0.1 or later. Windows 7 and Windows Server 2008: The Network Security LAN Manager Authentication Level is set to Send LM and NTLM responses. 1. Go to Library > User States. The User States page appears. 2. In Choose Action, click Scan New User State. The Host Scan form appears. 3. Complete the form for the targets you are scanning: Host Name/IP Enter the fully qualified hostname or IP address for the target system or enter a range of computers using a Comma, semicolon, and newline separated list.

K2000 Deployment Appliance v3.3, Administrator's Guide

53

Note: To scan multiple hosts, enter one host name or IP per line. Domain User Name Password

Optional, unless the authenticating user is a domain user. Enter a user that has administrator privileges on the target system. Password of the user.

Confirm Password Reenter the password. USMT Version to be used USMT Template Select the User State Migration Tool version compatible with the operating system you are scanning. (Only available when using USMT v4.0 or higher) Select the name of USMT Scan Template that you want to use for the capture. A template determines which items to capture.

4. Click Next. The process status displays. If process completes successfully, a list of profiles appears. 5. Select the profiles that you want to capture onto the appliance and then click Next. The Results Log appears. 6. Click Finish. The User States that you selected are uploaded to the appliance. When the upload completes, they appear in the User State list and are available to assign to Scripted Installations and System Images.

Loading user profiles on targets


Online migration allows you to put user profiles that have been captured, using a scan, on target computers by assigning the Deploy User State Post Installation Task to the Scripted Installation or System Image and then selecting the user profiles you want to load when you assign the Deployment task to a system as Boot Action. Offline migration allows you capture the user profiles on the systems assigned to the Deployment task as Boot Action. The appliance captures the profiles if the Scan User States Offline Preinstallation Task is assigned to the Scripted Installation or System Image and then reloads those profiles after installation with the Deploy User States Post Installation Task. Once the profiles are captured (that is when the Scan User State Offline Preinstallation Task completes) the profiles are available for online migration. Note: When performing an offline migration, you can also choose to load additional profiles that are available on the appliance. Completing these steps requires: a Scripted Installation or System Image, target systems, and captured user states. Add the Deploy User States Post Installation Task to the Scripted Installation or System Image: a) Click Deployments, and then System Images or Scripted Installations. b) Click the name of the item to show the details. c) Scroll down to Installation Plan.

54

K2000 Deployment Appliance v3.3, Administrator's Guide

The available and assigned tasks appear.

d) Drag Deploy User States Post Installation Task from the Available Postinstallation Tasks column on the right to the Run Postinstallation Tasks column on left. Set the execution order by moving it up and down in the list. e) Click Save. The appliance rebuilds the Deployment. When this Deployment item is assigned as a Boot Action, you are prompted to select user profiles from the list on the User States page.

Checking driver compatibility


When a computer network boots into a Boot Environment on the appliance, the appliance adds the computer to the System Inventory page, reserves a licensed seat, and automatically records the computers hardware inventory details. You can run a compatibility report to verify whether the Source Media contains the drivers for the computer. 1. Network boot the computer. 2. Log on to the K2000 Administrative Console. 3. Click Systems > System Inventory. The System Inventory page displays a list of computers that have PXE and NetBooted to the appliance. 4. Click the hostname or IP address of the computer. The System Details page appears. 5. In Select Operating System, such as Scripted Installation or System Image, and then click Show Compatibility. The results appear. The compatibility report compares the drivers required by the computer to the drivers available on the Source Media. Add any missing drivers, see Managing drivers on page 90.

Adding Drivers to appliance cache


The K2000 appliance driver caches contain the meta data for drivers uploaded to the drivers share and allow the appliance processes to match the drivers with the correct hardware during Scripted Installations and Windows K2000 Boot Environment (KBE) builds. Recaching drivers for:

K2000 Deployment Appliance v3.3, Administrator's Guide

55

KBE folders, kbe_windows_x86 and kbe_windows_x64, loads driver meta data and makes the drivers available for KBE builds. Most systems can network boot using the prebuilt K2000 Boot Environments (KBE) for x86 and x64 systems provided by Dell KACE. However, for systems that require additional drivers to network boot, add the drivers to the share and recache (using one of the method described below), and then create a new KBE from an administrator computer with Media Manager and Windows Automated Tool Kit (WAIK). Scripted Installation folders, windows_2000 , windows_2003, windows_2003_x64, windows_2008_x64, windows_2008_x86, windows_7_x64, windows_7_x86, windows_vista, windows_vista_x64, windows_xp, windows_xp_x64, loads driver meta data and makes the driver available during a clean operating system installation from source media (Scripted Installation). Note: System Images contain the drivers capture on the system you imaged. To add a driver to a System Image, install the driver on the source computer, recapture the image and upload it to the appliance. Add the drivers to the share and recache using the following methods:

Method

Description

Library > Driver Feed > Download and Install Process that automatically downloads a package of drivers, installs the driver files Packages in the driver share file, and recaches the folder. Manually adding drivers Settings & Maintenance > Package Management > Import Package Allows you to add drivers that you obtained to the appliance and recache the folder. Adds drivers you exported either as a backup or that you want to share between K2000 appliances.

56

K2000 Deployment Appliance v3.3, Administrator's Guide

Method Driver Harvesting Utility

Description Allows you to scan a computer that has the drivers you want and upload them to the appliance driver share, and then you must manually recache the drivers.

Getting drivers from Dell KACE


Dell KACE Support gathers drivers and provides packages that you can download and install on the Library > Driver Feed page. The model specific packages contain drivers for Scripted Installations (Windows only) and System Images. The Windows KBE packages contain drivers contained in the Windows Automated Installation Kit (WAIK). Note: The KBE packages are the same as the prebuilt KBEs shipped with the Dell KACE Deployment Appliance. You must enable the driver feed to populate the available driver package list, see Enabling the Driver Feed on page 16 for details. 1. Click Library > Driver Feed. 2. Click the driver package you want to add to the appliance cache. If the drivers are required for network booting, add the Windows PE package. 3. In Choose Action, click Download and Install Packages. The process begins. The Status column changes to Installed into driver share when the process completes. The drivers are automatically recached and appear in the driver list. The drivers are now available for Scripted Installations and System Images or KBE (if you installed a Windows PE pack).

Manually adding drivers


After downloading and uncompressing drivers from the manufacturer web site or other resource, upload the driver files to the appliance and recache the corresponding driver folder. Recaching a KBE folder from the Managing Drivers page makes the drivers available to Media Manager when building a KBE. Recaching an operating system folder makes the drivers available to Scripted Installations (Windows only).

K2000 Deployment Appliance v3.3, Administrator's Guide

57

Note: Leave the drivers in the corresponding folder, even after recaching, to make it available to the appliance processes. The system compatibility report shows cached driver availability. Removing a driver without recaching may cause booting, installation, and recovery errors that result in system failure and compromise the issues shown in the compatibility report. The UNC path to the driver share \\K2000_hostname\drivers. Under each directory you can create subfolders to organize the drivers you add. The path to the driver, including the driver name, cannot exceed 255 characters, the directories and driver names do not support special characters. 1. Download and uncompress the drivers to a computer that can access the appliance drivers share. 2. Open the driver share. You set the share password in Driver/Restore Share Password on the Settings & Maintenance > General Settings page. 3. Put the driver files in a folder that corresponds to the process to which you want to make the drivers available. For example, to make drivers available to Media Manager for a 32 bit KBE build, put the drivers to kbe_windows_x86. 4. Go to Library > Drivers, and then in Choose Action click Recache Drivers. The Managing Drivers page appears. 5. Click the button that corresponds to the driver share folder. Recache All Drivers updates the every cache and can take a long time to execute. Only recache the folders that changed. For example, Recache K2000 Boot Environment (Windows x86) updates the drivers from kbe_windows_x86. 6. Click the Drivers tab. The Drivers list appears. 7. Using the View by menu, filter the driver list and verify that the drivers you added are now cached. For example, click View by > KBE (Windows x86) to show the drivers you added to kbe_windows_x86.

58

K2000 Deployment Appliance v3.3, Administrator's Guide

Preinstallation Tasks: Prepare a computer for a new operating system


Configure Preinstallation Tasks to prepare a computer for installation of an operating system, either a clean installation (Scripted Installation) or reimaging (System Image). Default Tasks The appliance comes with the following set of default Preinstallation Tasks that you can customize for your environment.
Name Collect Computer Name Type Application Description Captures the name of a Windows computer for reuse in the Apply Computer Name postinstallation task. Only for System Image deployments. Captures the name of a Mac OS X computer for reuse in the Apply Mac OS X Computer name postinstallation task. Only for System Image deployments. Mac OS X only. Creates a single partition in HFS+ format using either the APM or GPT format. Creates a single primary partition. Uploads the hardware inventory and displays the list of incompatible devices on the client console. Formats the C drive and sets it as an NTFS file system. Installs the master boot record for Windows 2000, Windows XP, or Windows Server 2003. Installs the master boot record for Windows Vista, Windows Server 2008, and Windows 7. Captures the user state and allows you to migrate the user with the Deploy User State postinstallation task. Uploads hardware inventory.

Collect Mac OS X Computer Name Shell Script

Create Single HFS+ partition on disk0 Create Single Partition Display Device Compatibility

Shell Script

DISKPART script BAT script

Format C: as NTFS Install 2000/XP/2003 MBR

BAT script BAT script

Install Vista/2008/7/MBR

BAT script

Scan User States Offline

USMT

Upload Hardware Inventory

BAT script

Cleaning the hard drive or partitions


Create a DISKPART Preinstallation Task to erase all the data on the hard drive or partition, create new partitions, and assign letter drives. DISKPART is a Windows utility that runs on a Windows computer that is booted into the K2000 Boot Environment (KBE). This section walks you through the process of adding a task that cleans all the partitions and creates a single boot partition, C. Use these instructions guideline for creating a more advanced cleanup task. When assigning the task to a Scripted Installation or System Image, run the DISKPART task after the tasks that collect and back up the data you want to save from the computer.
K2000 Deployment Appliance v3.3, Administrator's Guide 59

Note: DISKPART supports NTFS drives only. 1. Click Library > Preinstallation Tasks. The Preinstallation Tasks page appears. 2. In Choose Action, click Add New DISKPART. The Preinstallation Task Detail page appears. 3. In Name, type a name that distinguishes this task from other similar tasks. For example, name this task Single NTFS Partition C. The name is the only identifier displayed when selecting the task on the Scripted Installation Details and System Image Details pages. 4. In DISKPART Script, enter the following: clean all create partition primary active 5. Click Save. The preinstallation task is available to assign to Scripted Installations and System Images Deployments.

Creating an application task


Provides an application or file, such as an installation file, that the appliance runs using the specified command-line either after the installation/deployment of the OS in the KBE or after the first reboot. Use application tasks to name the computer, install and configuration software, or perform any set up task that requires additional files. 1. Click Library > Preinstallation Tasks. The Preinstallation Tasks page appears. 2. In Choose Action, click Add New Application. The Preinstallation Task Detail page appears. 3. In Name, enter a name that distinguishes this task; for example Mac OS X 4. In Runtime Environment, click the target platform (Windows or Mac OS X). 5. In Upload File, enter the full path to the file or click Browse and select the file. Upload file size limit is 2 GB; use the appliance Restore share to upload large files. 6. Click Save. The task is now available for assignment in Scripted Installations and Windows System Image Deployments.

Running a Batch Script


Contains a batch script that appliance runs in the K2000 Boot Environment before installing the operating system or reimaging a target. 1. Click Library > Preinstallation Tasks. The Preinstallation Tasks page appears. 2. In Choose Action, click Add New BAT Script . The Preinstallation Task Detail page appears. 3. In Name, enter a name that distinguishes this task.
60 K2000 Deployment Appliance v3.3, Administrator's Guide

4. In BAT Script, enter the script you want to run. 5. Click Save. The task is now available for assignment in Scripted Installations and Windows System Image Deployments.

Postinstallation Tasks: Customizing the installation


Configure Postinstallation Tasks to finalize the set up after a clean installation of an operating system, either a clean installation (Scripted Installation) or reimaging (System Image).

Create a task that installs a driver


Many hardware drivers can be installed as part of the regular operating system installation or image however some drivers, especially video card, that have complex configuration or dependencies should be installed using the driver installation file provided by the manufacturer. Assign driver installation tasks, after the operating system or image installation completes, while the system is still booted into the Boot Environment. Get the driver installation file before creating the task. 1. Click Library > Postinstallation Tasks. 2. In Choose Action, click Add New Application. The Postinstallation Task Detail page appears. 3. In Name, enter a logical name for the task, such Install Dell E6410 Chipset Drivers. 4. In Type, choose the Windows. 5. In Runtime Environment, choose K2000 Boot Environment (Windows). 6. Next to Upload File, click Browse and select the installer. 7. In Command Line, enter the filename and the installation switches you want to use. 8. Click Save. The task is now available for assignment in Scripted Installations and Windows System Image Deployments.

Creating a Batch Script Task


Contains a batch script that appliance runs either in the KBE after installing/deploying the operating system or from Windows after the first reboot. Get the driver installation file before creating the task. 1. Click Library > Postinstallation Tasks. 2. In Choose Action, click Add New BAT Script. The Preinstallation Task Detail page appears. 3. In Name, enter a logical name for the task. 4. In Type, choose the target platform. 5. In Runtime Environment, choose K2000 Boot Environment (Windows) to run the script before the first reboot and Windows to run from OS after reboot. 6. In BAT Script, enter the script. 7. Click Save. The task is now available for assignment in Scripted Installations and Windows System Image Deployments.

K2000 Deployment Appliance v3.3, Administrator's Guide

61

Naming the target


Renames the target PC after the first reboot using a Workstation Name Changer compatible text file. For detailed information, see the WSName.exe web site. The appliance renames the computer using the command-line parameters that you specify in this task. Set up a naming database as described in the sidebar help. 1. Click Library > Postinstallation Tasks. 2. In Choose Action, click Add New Naming Rule. The Postinstallation Task Detail page appears. 3. In Name, enter a logical name for the task, such K1000 Agent for Windows with .Net. 4. Next to Upload File, click Browse and select the naming database file. 5. In Command line, change the name mapping in the command line if required. 6. Click Save. The task is now available for assignment in Scripted Installations and Windows System Image Deployments.

Installing the K1000 Agent


In environments that have a K1000 System Management Appliance, you may want to install the agent as a Postinstallation Task. Note: To install and run K1000 Agents for Windows v5.1 and lower the computer must have .Net v1.1 or higher. The K1000 appliance share \\K1000_hostname\client\agent_provisioning provides the following agent installation files:
Operating System Mac OS X File Description

\mac_platform \KBOX Agent 5.1.33710.dmg

Installs the K1000 Agent for Mac OS X.

Windows 2000 and higher Windows 2000 and higher

\windows_platform\KInstallerSetup.exe

Installs only the K1000 Agent for Windows on a computer that already has .Net.

\windows_platform\KInstallerSetupSilent.msi Silently installs the K1000 Agent for Windows on a computer that already has .Net. \windows_platform\KNISetup_v11Silent.msi Silently installs the K1000 Agent for Windows and .Net.

Windows 2000 and higher

1. Click Library > Postinstallation Tasks. 2. In Choose Action, click Add New K1000 Agent . The Postinstallation Task Detail page appears. 3. In Name, enter a logical name for the task, such K1000 Agent for Windows with .Net. 4. In Type, choose the platform. 5. Next to Upload File, click Browse and select the installer file. 6. In Command Line, ensure that the filename matches the one you uploaded and you specify your K1000 host name in the installation switches. For an explanation of available command line switches and agent configuration properties, see the K1000 System Management Appliance Administrator Guide Addendix E: Manually Deploying Agents.

62

K2000 Deployment Appliance v3.3, Administrator's Guide

7. Click Save. The task is now available for assignment in Scripted Installations and Windows System Image Deployments.

Installing applications
Provides an application or file, such as an installation file, that the appliance runs using the specified command-line either after the installation/deployment of the OS in the KBE or after the first reboot. Use application tasks to name the computer, install and configuration software, or perform any set up task that requires additional files. Note: In environments with K1000 System Management Appliance, use Post Installation Tasks to perform required one time installation, such as hardware drivers. Install and patch other software from the K1000 System Management Appliance. 1. Click Library > Postinstallation Tasks. 2. In Choose Action, click Add New Application. The Postinstallation Task Detail page appears. 3. In Name, enter a logical name for the task, such Install Adobe Reader 9. 4. In Type, choose the platform. 5. In Runtime Environment, choose whether to install the application before or after the first reboot. 6. Next to Upload File, click Browse and select the application installer. 7. In Command Line, enter the filename and the installation switches you want to use. 8. Click Save. The task is now available for assignment in Scripted Installations and Windows System Image Deployments.

Joining the domain


Once the computer is configured and named, you can automatically join it to the domain using a script. Dell KACE recommends customizing the Example: Join Domain Post Installation Task provided with your appliance. Note: The join_domain.vbs joins Windows 2000 and higher computers only. For information on automatically joining other types of systems refer to the Dell KACE Support Knowledge Base. The preconfigured Example: Join Domain Post Installation Task is an application task that has a Visual Basic script, join_domain.vbs, attached. Customize the task using the command line parameters, as follows: join_domain.vbs my_domain admin_user admin_password primary_dns_IP
Parameter Name Description The name of the domain to which the script joins the computer. The UID of the domain administrator with permission to join the computer to the domain. The password of the domain administrator account. Optional, the IP address of the primary DNS server.

my domain
admin user admin password primary dns IP

1. Click Library > Postinstallation Tasks. 2. Click Example: Join Domain. The Postinstallation Task Detail page appears.

K2000 Deployment Appliance v3.3, Administrator's Guide

63

3. Click Duplicate. A new task named Copy of Example: Join Domain is created and the Postinstallation Task Detail edit page appears. 4. In Name, enter a logical name for the task, such Join MyCompany Domain. 5. In Command Line, change my_domain , and admin_user admin_password . 6. Click Save. The task is now available for assignment in Scripted Installations and Windows System Image Deployments.

Installing a service pack


Installs the service pack that you selected or uploaded after the first reboot using the command-line parameters you specify. 1. Click Library > Postinstallation Tasks. 2. In Choose Action, click Add New Service Pack. The Postinstallation Task Detail page appears. 3. In Name, enter a unique name that identifies the service pack. 4. Load the service pack onto the appliance: Automatically: In Select Service Pack, choose a pack and click Download Service Pack Automatically. Manually: Click Upload Service Pack Manually and then Browse. Select the service pack file.

5. In Command line, verify that the command line options match the ones you want to use. 6. Click Save. The task is now available for assignment in Scripted Installations and Windows System Image Deployments.

Setting up a Windows Scripted Installation


Once you have created or gathered all the requisite components and drivers for an operating installation, put them together in a Scripted Installation that you can deploy to targets. Before you create a Scripted Installation, capture the user states you want to migrate, upload the OS installation source media, add drivers to the share and recache, create pre- and post-installation tasks, and optionally have a customized answer file ready.

Setting up an Unattended Installation


An unattended installation runs on the system without requiring user input. Unattended installations use an answer file.

Using the wizard to create an answer file


The Unattended Installation Wizard walks you through the process of setting up an answer file that the appliance uses when installing the operating system. 1. Click Deployments > Scripted Installations.
64 K2000 Deployment Appliance v3.3, Administrator's Guide

The Scripted Installations page appears. 2. In Choose Action, click Add New Scripted Installation. The Create a Scripted Installation page appears. 3. Enter a Name and select the Source Media, and then click Next. The Create a Scripted Installation (Windows) page appears. 4. Click Walk me through creating an answer file for unattended setup, and then click Next. The Create a Scripted Installation (Windows) page appears. 5. Complete the answer form. 6. Click Next. The Scripted Installation Details page appears where you set up the Pre- and Postinstallation Tasks. Next set up Pre- and Postinstallation Tasks to complete the Scripted Installation configuration.

Using an answer file


You can create an unattended installation by uploading an answer file that you configured. Once the answer file is uploaded, you can modify it on the set up page. 1. Click Deployments > Scripted Installations. The Scripted Installations page appears. 2. In Choose Action, click Add New Scripted Installation. The Create a Scripted Installation page appears. 3. Enter a Name and select the Source Media, and then click Next. The Create a Scripted Installation (Windows) page appears. 4. Click Upload an existing answer file for unattended setup, and then click Next. The Scripted Installation Details page appears. Next set up Pre- and Postinstallation Tasks to complete the Scripted Installation configuration.

Setting up an attended installation


During an attended installation, the administrator (or user) must select the configuration options during the OS installation phase of the Scripted Installation. You can attend the installation by connecting to the target using an Action Icon configured to launch a VNC-Java Remote Control session. VNC-Java Remote Control is built into the K2000 Boot Environment. 1. Click Deployments > Scripted Installations. The Scripted Installations page appears. 2. In Choose Action, click Add New Scripted Installation. The Create a Scripted Installation page appears. 3. Enter a Name and select the Source Media, and then click Next. The Create a Scripted Installation (Windows) page appears. 4. Click No answer file; This will be a server-based attended setup, and then click Next. The Scripted Installation Details page appears. Next set up Pre- and Postinstallation Tasks to complete the Scripted Installation configuration.

K2000 Deployment Appliance v3.3, Administrator's Guide

65

Setting up the Pre- and Postinstallation Tasks


Pre- and Postinstallation Tasks allow you automate the tasks that prepare the computer for the operating system and complete (customize) the set up after deployment. System Images: Configure the Pre- and Postinstallation Tasks after capturing and uploading the image from the reference machine. Scripted Installations: Configure the Pre- and Postinstallation Tasks after setting up the answer file or after choosing a server-based attended installation. Note: You can also modify which Pre- and Postinstallation Tasks are assigned to an existing deployment configuration by viewing the details. The New Scripted Installation wizard displays the Scripted Installation Details page after you set up the answer file. 1. To modify the Pre- or Postinstallation tasks of an existing Scripted Installation, click Deployments > Scripted Installations and then click on the name. The Scripted Installation Details page appears. 2. Click Setup Configuration to display the answer file in XML. You can change the settings by editing the XML. 3. In Preinstallation Task Error Handling, choose the script behavior when an error occurs: Continue on Errors: Ignore failures and continue without prompting. Prompt on Errors: Prompts with an option to abort or continue. Halt on Errors: Aborts if an error occurs.

4. In Installation Plan, configure the actions to run before and after the operating installation: a) Drag Pre- and Postinstallation Tasks from Available to Run. b) Put the tasks in the order you want them to be executed. 5. Click Save. If you click Cancel when using the Scripted Installation Wizard, the Scripted Installation is created without Pre- or Postinstallation Tasks assigned and manual changes to the configuration file are discarded. The Scripted Installation is now available from the Boot Manager window on computers that PXE booted to the appliance and can be assigned to a computer on the Boot Action Setup page.

Deploying Scripted Installations


Scripted Installations perform a clean installation of the operating system on a target node over the network. To deploy the Scripted Installation the computer must network boot to a K2000 Boot Environment. Use one of the following mehtods to initiate the deployment:

66

K2000 Deployment Appliance v3.3, Administrator's Guide

Method Systems > Boot Actions > Add Boot Action Systems > Boot Actions > Set Boot Action Boot Manager Recovery Console

Number of targets

Description Assigns the Scripted Installation to systems that have already network booted into KBE and/or systems by a list of IP addresses or MAC addresses. Assigns the Scripted Installation to the selected systems using the MAC address. Only for systems that have network booted into KBE.

1 or more

1 or more

Only 1

Start the installation by selecting it from a list in the Boot Manager interface on the target system.

Deploying on the next network boot


These instructions explain how deploy a Scripted Installation or a System Image on one or more target computers from the appliance the next time the computers network boot. Access the Boot Action Setup from the System Details, Scripted Installation Details, and System Image Details to populate fields with related options (such as the MAC address of the target machine). This tasks walks you through the process when assigning the boot action from scratch. Note: A target can only have one Boot Action assigned. When you assign a machine to a new boot action, the existing boot action is automatically deleted. 1. Click Systems > Boot Actions. 2. In Choose Action, click Add Boot Action. Choosing systems from the Boot Action list and clicking Set Boot Action populates the machines field with the MAC addresses of the selected systems. If you do not know the MAC address of the system, it is possible to assign the boot action to the IP address (not recommended) using this option. Saving a Boot Action replaces the existing one. The Boot Action Setup page appears. 3. In First Boot Action , click the type of the action (Show Boot Manager or Boot from Local Hard drive) or the name of the Scripted Installation or System Image you want to deploy. 4. In Number of Boots, enter the number of times you want this action to occur before executing the Next Boot Action. 5. In Next Boot Action, click the name of the Scripted Installation or System Image you want to deploy. 6. In Number of Boots, enter the number of times you want this action to occur before displaying the Boot Manager. 7. If you choose a System Image or Scripted Installation that has the Scan Users States Offline Preinstallation Task, the Scan User States Offline page appears. Select the USMT Scan Template and click Save. 8. If you choose a System Image or Scripted Installation that has only the Deploy User State Postinstallation Task, the Deploy User States page appears. Select the USMT version, the users you want to deploy, and click Save. The next time the targets boot from the appliance, the Boot Manager launches the action without displaying the Boot Manager menu.

Performing a clean OS installation


You can initiate the clean installation of an operating system, Scripted Installation, from the Deployment and Recovery Console on a target system.
K2000 Deployment Appliance v3.3, Administrator's Guide 67

PXE boot the target system, to display the Boot Manager. Note: Once the system boots, you can access the Boot Manager remotely using a VNC-Java Remote Control session. 1. On the target system Boot Manager, choose the KBE that supports the target hardware.

In a lab environment, you could increase the Boot Manager Timeout period on the Settings & Maintenance > General Settings page up to 15 minutes (900 seconds) to allow you to connect to the target and interrupt the boot sequence. In a production environment, 15 seconds is the default and in most cases increasing the time out could impact user productivity. The Deployment and Recovery Console appears.

68

K2000 Deployment Appliance v3.3, Administrator's Guide

2. Click Scripted Installation. 3. In Scripted Installation Name, click the one you want to install on this system. 4. Click Start installation. The process launches in a command prompt window. The VNC-Java Connection remains open until after the OS installation completes. The connection is dropped on the reboot. Depending on the bandwidth of your network, the number of tasks, and the size of the image you are deploying, and whether or not you turned on debugging the process may take several minutes to a few hours to complete.

K2000 Deployment Appliance v3.3, Administrator's Guide

69

Imaging Systems

System Imaging allows for the fast and complete deployment of operating systems to large numbers of computers in a short amount of time. Compared to Scripted Installation, System Imaging has added benefit of allowing applications and other settings to be embedded in the image in addition to allowing the flexibility of postinstallation tasks. There are times when software vendors do not have an unattended install option and adding the application to the image is the only deployment alternative. The innovative K-image format used by the K2000 offers two key benefits. First, the flexible file-based format of K-imaging is fully editable, allowing for granular control of images. Second, K-imaging's smart synchronization capabilities eliminate redundant transfers in the capture, storage, and transfers of images. For example, the first time an image is captured, all files on the source hard drive are uploaded. On subsequent uploads of other images, only files that are not already present on the K2000 will be uploaded. In essence, the K2000 only stores one copy of each unique file and that file is shared among all of the images that reference it. Although imaging is faster than scripted installation, it is also less flexible. Generally, images must be deployed to a computer of the same type as the source. However, special customizations can be made to manage these differences in hardware.

Setting up Library Components


Populate your Library with all the components that you want to include in Scripted Installations and System Images.

Capturing user states for online migration


Migration saves the user state on the appliance and allows you to put it on any number of targets during a Scripted Installation or System Image deployment. This preserves the users files, profile, and preferences while you change, fix, or replace their computer or operating system. Users are then able to access their files and settings are just as they remember. Scanning requires the Microsoft Windows User State Migration Tool software included in the Windows AIK (Automated Installation Kit). Upload USMT before performing a scan. K2000 captures user states by running the Scan State utility on the target. You can run the scan with the default settings or customize the capture using a USMT Scan Template.

70

K2000 Deployment Appliance v3.3, Administrator's Guide

Excluding users and data from a capture


The appliance migrates user profiles by running the USMT Scan State and Load State utilities. Before scanning targets for user states, configure the USMT Templates that set the Scan State utility parameters and allow you to exclude users, Windows and Document components, types of files, and specific files from the capture. You can also use a template to change the default runtime options, including logging, and debugging, and using the command line parameters for Windows Vista computer. Before capturing users for online migration or deploying a Scripted Installation or System Image to migrate users offline, configure a template. The default template, captures all users, components, and files. 1. 2. 3. 4. Click Library > USMT Scan Template. In Choose Action, click Add New Scan Template. In Name, type a unique name that identifies the template. Set the User selection options: Click Specify users to be excluded and enter a comma separated list of user IDs to ignore these profiles during online and offline target scans. The profiles are not captured. Click Scan all available user states to show all profiles during an online migration scan or to migrate all profiles on the target during an offline migration.

5. Set the Command line options for the Scan State utility runtime. In most cases, use default command line options. 6. Set the Content configuration options for capturing the Windows and Document Components Click Specify config file and upload a configuration file to exclude components using a custom configuration file. This option overrides the options Enabled under the Windows Components to be scanned and Documents to be scanned sections. Disable Specify config file and enable the components that you want to capture under the Windows Components to be scanned and Documents to be scanned sections.

7. Click Save. The USMT Scan Template is now available when scanning users for online migration from the User States page.

Uploading the Windows User State Migration Tool


Migrating users from one Windows target to another or upgrading the operating system from one version to another, such as XP to Windows 7, requires the Windows User State Migration Tool (USMT). The Windows Automated Installation Kit (AIK) includes USMT version 4.0. Upload the USMT to the Dell KACE K2000 appliance to prepare for Windows migrations. Note: On the Library > User States > Upload USMT Software page, you can upload the USMT v4.0 in a zip file or get USMT v3.0 from Microsofts web site. This task requires the Media Manager (See Installing Media Manager on Windows on page 99) and Windows AIK (see Installing Windows Automated Installation Kit (AIK) on page 100). 1. Open Media Manager, click Start > All Programs > KACE > K2000 Media Manager. The Media Manager appears. 2. In the Hostname field, enter the IP address or host name of the appliance.
K2000 Deployment Appliance v3.3, Administrator's Guide 71

3. Click the Upload USMT tab. 4. Click Browse and locate the Windows AIK. The default location is C:\Program Files\Windows AIK. 5. Click Start Upload. The USMT version 4.0 displays in the Library > User States > Scan New User State > USMT drop-down and is available for offline migration during a scripted installation.

Capturing user states from a target


The User States feature scans a target and captures user profiles and saves them to the K2000 for deployment. When the deployment includes the Deploy User State Postinstallation Task, you can select the profiles that you want to load onto the target when assigning a Boot Action. Scanning requires USMT, an administrator account, and that the target is powered on and connected to the network. The target must have the following settings: All Windows systems using a firewall: File and Print Sharing is enabled. This setting is on the Exceptions list of the Firewall Configuration. Windows XP systems: Simple File Sharing is off. Windows 2000 SP4 systems: The Windows installer version (C:\WINDOWS\system32\msi.dll) is 3.0.1 or later. Windows 7 and Windows Server 2008: The Network Security LAN Manager Authentication Level is set to Send LM and NTLM responses. 1. Go to Library > User States. The User States page appears. 2. In Choose Action, click Scan New User State. The Host Scan form appears. 3. Complete the form for the targets you are scanning: Host Name/IP Enter the fully qualified hostname or IP address for the target system or enter a range of computers using a Comma, semicolon, and newline separated list. Note: To scan multiple hosts, enter one host name or IP per line. Domain User Name Password

Optional, unless the authenticating user is a domain user. Enter a user that has administrator privileges on the target system. Password of the user.

Confirm Password Reenter the password. USMT Version to be used Select the User State Migration Tool version compatible with the operating system you are scanning.

72

K2000 Deployment Appliance v3.3, Administrator's Guide

USMT Template

(Only available when using USMT v4.0 or higher) Select the name of USMT Scan Template that you want to use for the capture. A template determines which items to capture.

4. Click Next. The process status displays. If process completes successfully, a list of profiles appears. 5. Select the profiles that you want to capture onto the appliance and then click Next. The Results Log appears. 6. Click Finish. The User States that you selected are uploaded to the appliance. When the upload completes, they appear in the User State list and are available to assign to Scripted Installations and System Images.

Loading user profiles on targets


Online migration allows you to put user profiles that have been captured, using a scan, on target computers by assigning the Deploy User State Post Installation Task to the Scripted Installation or System Image and then selecting the user profiles you want to load when you assign the Deployment task to a system as Boot Action. Offline migration allows you capture the user profiles on the systems assigned to the Deployment task as Boot Action. The appliance captures the profiles if the Scan User States Offline Preinstallation Task is assigned to the Scripted Installation or System Image and then reloads those profiles after installation with the Deploy User States Post Installation Task. Once the profiles are captured (that is when the Scan User State Offline Preinstallation Task completes) the profiles are available for online migration. Note: When performing an offline migration, you can also choose to load additional profiles that are available on the appliance. Completing these steps requires: a Scripted Installation or System Image, target systems, and captured user states. Add the Deploy User States Post Installation Task to the Scripted Installation or System Image: a) Click Deployments, and then System Images or Scripted Installations. b) Click the name of the item to show the details. c) Scroll down to Installation Plan. The available and assigned tasks appear.

K2000 Deployment Appliance v3.3, Administrator's Guide

73

d) Drag Deploy User States Post Installation Task from the Available Postinstallation Tasks column on the right to the Run Postinstallation Tasks column on left. Set the execution order by moving it up and down in the list. e) Click Save. The appliance rebuilds the Deployment. When this Deployment item is assigned as a Boot Action, you are prompted to select user profiles from the list on the User States page.

Preinstallation Tasks: Prepare a computer for a new operating system


Configure Preinstallation Tasks to prepare a computer for installation of an operating system, either a clean installation (Scripted Installation) or reimaging (System Image). Default Tasks The appliance comes with the following set of default Preinstallation Tasks that you can customize for your environment.
Name Collect Computer Name Type Application Description Captures the name of a Windows computer for reuse in the Apply Computer Name postinstallation task. Only for System Image deployments. Captures the name of a Mac OS X computer for reuse in the Apply Mac OS X Computer name postinstallation task. Only for System Image deployments. Mac OS X only. Creates a single partition in HFS+ format using either the APM or GPT format. Creates a single primary partition. Uploads the hardware inventory and displays the list of incompatible devices on the client console. Formats the C drive and sets it as an NTFS file system. Installs the master boot record for Windows 2000, Windows XP, or Windows Server 2003. Installs the master boot record for Windows Vista, Windows Server 2008, and Windows 7. Captures the user state and allows you to migrate the user with the Deploy User State postinstallation task. Uploads hardware inventory.

Collect Mac OS X Computer Name Shell Script

Create Single HFS+ partition on disk0 Create Single Partition Display Device Compatibility

Shell Script

DISKPART script BAT script

Format C: as NTFS Install 2000/XP/2003 MBR

BAT script BAT script

Install Vista/2008/7/MBR

BAT script

Scan User States Offline

USMT

Upload Hardware Inventory

BAT script

74

K2000 Deployment Appliance v3.3, Administrator's Guide

Cleaning the hard drive or partitions


Create a DISKPART Preinstallation Task to erase all the data on the hard drive or partition, create new partitions, and assign letter drives. DISKPART is a Windows utility that runs on a Windows computer that is booted into the K2000 Boot Environment (KBE). This section walks you through the process of adding a task that cleans all the partitions and creates a single boot partition, C. Use these instructions guideline for creating a more advanced cleanup task. When assigning the task to a Scripted Installation or System Image, run the DISKPART task after the tasks that collect and back up the data you want to save from the computer. Note: DISKPART supports NTFS drives only. 1. Click Library > Preinstallation Tasks. The Preinstallation Tasks page appears. 2. In Choose Action, click Add New DISKPART. The Preinstallation Task Detail page appears. 3. In Name, type a name that distinguishes this task from other similar tasks. For example, name this task Single NTFS Partition C. The name is the only identifier displayed when selecting the task on the Scripted Installation Details and System Image Details pages. 4. In DISKPART Script, enter the following: clean all create partition primary active 5. Click Save. The preinstallation task is available to assign to Scripted Installations and System Images Deployments.

Creating an application task


Provides an application or file, such as an installation file, that the appliance runs using the specified command-line either after the installation/deployment of the OS in the KBE or after the first reboot. Use application tasks to name the computer, install and configuration software, or perform any set up task that requires additional files. 1. Click Library > Preinstallation Tasks. The Preinstallation Tasks page appears. 2. In Choose Action, click Add New Application. The Preinstallation Task Detail page appears. 3. In Name, enter a name that distinguishes this task; for example Mac OS X 4. In Runtime Environment, click the target platform (Windows or Mac OS X). 5. In Upload File, enter the full path to the file or click Browse and select the file. Upload file size limit is 2 GB; use the appliance Restore share to upload large files. 6. Click Save. The task is now available for assignment in Scripted Installations and Windows System Image Deployments.

K2000 Deployment Appliance v3.3, Administrator's Guide

75

Running a Batch Script


Contains a batch script that appliance runs in the K2000 Boot Environment before installing the operating system or reimaging a target. 1. Click Library > Preinstallation Tasks. The Preinstallation Tasks page appears. 2. In Choose Action, click Add New BAT Script . The Preinstallation Task Detail page appears. 3. In Name, enter a name that distinguishes this task. 4. In BAT Script, enter the script you want to run. 5. Click Save. The task is now available for assignment in Scripted Installations and Windows System Image Deployments.

Postinstallation Tasks: Customizing the installation


Configure Postinstallation Tasks to finalize the set up after a clean installation of an operating system, either a clean installation (Scripted Installation) or reimaging (System Image).

Create a task that installs a driver


Many hardware drivers can be installed as part of the regular operating system installation or image however some drivers, especially video card, that have complex configuration or dependencies should be installed using the driver installation file provided by the manufacturer. Assign driver installation tasks, after the operating system or image installation completes, while the system is still booted into the Boot Environment. Get the driver installation file before creating the task. 1. Click Library > Postinstallation Tasks. 2. In Choose Action, click Add New Application. The Postinstallation Task Detail page appears. 3. In Name, enter a logical name for the task, such Install Dell E6410 Chipset Drivers. 4. In Type, choose the Windows. 5. In Runtime Environment, choose K2000 Boot Environment (Windows). 6. Next to Upload File, click Browse and select the installer. 7. In Command Line, enter the filename and the installation switches you want to use. 8. Click Save. The task is now available for assignment in Scripted Installations and Windows System Image Deployments.

Creating a Batch Script Task


Contains a batch script that appliance runs either in the KBE after installing/deploying the operating system or from Windows after the first reboot. Get the driver installation file before creating the task. 1. Click Library > Postinstallation Tasks.

76

K2000 Deployment Appliance v3.3, Administrator's Guide

2. In Choose Action, click Add New BAT Script. The Preinstallation Task Detail page appears. 3. In Name, enter a logical name for the task. 4. In Type, choose the target platform. 5. In Runtime Environment, choose K2000 Boot Environment (Windows) to run the script before the first reboot and Windows to run from OS after reboot. 6. In BAT Script, enter the script. 7. Click Save. The task is now available for assignment in Scripted Installations and Windows System Image Deployments.

Naming the target


Renames the target PC after the first reboot using a Workstation Name Changer compatible text file. For detailed information, see the WSName.exe web site. The appliance renames the computer using the command-line parameters that you specify in this task. Set up a naming database as described in the sidebar help. 1. Click Library > Postinstallation Tasks. 2. In Choose Action, click Add New Naming Rule. The Postinstallation Task Detail page appears. 3. In Name, enter a logical name for the task, such K1000 Agent for Windows with .Net. 4. Next to Upload File, click Browse and select the naming database file. 5. In Command line, change the name mapping in the command line if required. 6. Click Save. The task is now available for assignment in Scripted Installations and Windows System Image Deployments.

Installing the K1000 Agent


In environments that have a K1000 System Management Appliance, you may want to install the agent as a Postinstallation Task. Note: To install and run K1000 Agents for Windows v5.1 and lower the computer must have .Net v1.1 or higher. The K1000 appliance share \\K1000_hostname\client\agent_provisioning provides the following agent installation files:
Operating System Mac OS X File Description

\mac_platform \KBOX Agent 5.1.33710.dmg

Installs the K1000 Agent for Mac OS X.

Windows 2000 and higher Windows 2000 and higher

\windows_platform\KInstallerSetup.exe

Installs only the K1000 Agent for Windows on a computer that already has .Net.

\windows_platform\KInstallerSetupSilent.msi Silently installs the K1000 Agent for Windows on a computer that already has .Net. \windows_platform\KNISetup_v11Silent.msi Silently installs the K1000 Agent for Windows and .Net.

Windows 2000 and higher

K2000 Deployment Appliance v3.3, Administrator's Guide

77

1. Click Library > Postinstallation Tasks. 2. In Choose Action, click Add New K1000 Agent . The Postinstallation Task Detail page appears. 3. In Name, enter a logical name for the task, such K1000 Agent for Windows with .Net. 4. In Type, choose the platform. 5. Next to Upload File, click Browse and select the installer file. 6. In Command Line, ensure that the filename matches the one you uploaded and you specify your K1000 host name in the installation switches. For an explanation of available command line switches and agent configuration properties, see the K1000 System Management Appliance Administrator Guide Addendix E: Manually Deploying Agents. 7. Click Save. The task is now available for assignment in Scripted Installations and Windows System Image Deployments.

Installing applications
Provides an application or file, such as an installation file, that the appliance runs using the specified command-line either after the installation/deployment of the OS in the KBE or after the first reboot. Use application tasks to name the computer, install and configuration software, or perform any set up task that requires additional files. Note: In environments with K1000 System Management Appliance, use Post Installation Tasks to perform required one time installation, such as hardware drivers. Install and patch other software from the K1000 System Management Appliance. 1. Click Library > Postinstallation Tasks. 2. In Choose Action, click Add New Application. The Postinstallation Task Detail page appears. 3. In Name, enter a logical name for the task, such Install Adobe Reader 9. 4. In Type, choose the platform. 5. In Runtime Environment, choose whether to install the application before or after the first reboot. 6. Next to Upload File, click Browse and select the application installer. 7. In Command Line, enter the filename and the installation switches you want to use. 8. Click Save. The task is now available for assignment in Scripted Installations and Windows System Image Deployments.

Joining the domain


Once the computer is configured and named, you can automatically join it to the domain using a script. Dell KACE recommends customizing the Example: Join Domain Post Installation Task provided with your appliance. Note: The join_domain.vbs joins Windows 2000 and higher computers only. For information on automatically joining other types of systems refer to the Dell KACE Support Knowledge Base.

78

K2000 Deployment Appliance v3.3, Administrator's Guide

The preconfigured Example: Join Domain Post Installation Task is an application task that has a Visual Basic script, join_domain.vbs, attached. Customize the task using the command line parameters, as follows: join_domain.vbs my_domain admin_user admin_password primary_dns_IP
Parameter Name Description The name of the domain to which the script joins the computer. The UID of the domain administrator with permission to join the computer to the domain. The password of the domain administrator account. Optional, the IP address of the primary DNS server.

my domain
admin user admin password primary dns IP

1. Click Library > Postinstallation Tasks. 2. Click Example: Join Domain. The Postinstallation Task Detail page appears. 3. Click Duplicate. A new task named Copy of Example: Join Domain is created and the Postinstallation Task Detail edit page appears. 4. In Name, enter a logical name for the task, such Join MyCompany Domain. 5. In Command Line, change my_domain , and admin_user admin_password . 6. Click Save. The task is now available for assignment in Scripted Installations and Windows System Image Deployments.

Installing a service pack


Installs the service pack that you selected or uploaded after the first reboot using the command-line parameters you specify. 1. Click Library > Postinstallation Tasks. 2. In Choose Action, click Add New Service Pack. The Postinstallation Task Detail page appears. 3. In Name, enter a unique name that identifies the service pack. 4. Load the service pack onto the appliance: Automatically: In Select Service Pack, choose a pack and click Download Service Pack Automatically. Manually: Click Upload Service Pack Manually and then Browse. Select the service pack file.

5. In Command line, verify that the command line options match the ones you want to use. 6. Click Save. The task is now available for assignment in Scripted Installations and Windows System Image Deployments.

Capturing a system image


The Image Capture process starts by booting a source computer to the deployment environment, KBE. Once in the deployment environment, the image capture takes place from the source computer using the client side

K2000 Deployment Appliance v3.3, Administrator's Guide

79

Main Menu. KBE also has VNC remote control software built into the boot environment so that administrators can remotely capture images. Sysprep based images are most widely used when deploying the same image to a large numbers of computers. The hard drive is built with the operating system and any other settings the IT staffer sees fit. Next the image is generalized with sysprep to remove the Security ID (SID) and any other operating system specific information such as computer name and network settings. Once sysprep is complete, the image can be captured. This can be considered a "clean" image since none of the unique identifiers are present in the image at the time of capture. When this image is deployed, it starts a "mini-setup" where all the identifiers removed in the previous step are returned to the computer. For Windows computers you must run the Microsoft Sysprep Tool before capturing a system image. The capturing process uploads the image to the System Images page. Note: Use the Dell KACE Knowledge base for instructions and examples on preparing and capturing images of Windows and Mac OS X systems. The Sysprep Training Bundle (http://www.kace.com/support/downloads/sysprep/SysprepBundle.zip) contains examples for most Windows systems. PXE boot the target system, to display the Boot Manager. Note: Once the system boots, you can access the Boot Manager remotely using a VNC-Java Remote Control session. 1. On the target system Boot Manager, choose the KBE that supports the target hardware.

In a lab environment, you could increase the Boot Manager Timeout period on the Settings & Maintenance > General Settings page up to 15 minutes (900 seconds) to allow you to connect to the target and interrupt

80

K2000 Deployment Appliance v3.3, Administrator's Guide

the boot sequence. In a production environment, 15 seconds is the default and in most cases increasing the time out could impact user productivity. The Deployment and Recovery Console appears.

2. 3. 4. 5. 6.

Click Imaging. Click Capture image of this machine. In Image Name, enter a name that identifies the image on the appliance. In Image Source, ensure that all the drives you want to capture appear in the list. Click Force continue on errors to continue the capture and upload process even if warnings and fatal error occur. 7. Click Include debug output in log to turn on debugging level logging and upload the log to the Appliance Logs page. Turning on debugging may increase the time it takes to capture and upload the image. 8. Click Start capture. The K2000 Client dialog opens and connects to the appliance. The dialog remains open and shows the progress. The name of the image also appears on the System Images page and the Status column indicates the progress (for example Uploading). Depending on the bandwidth of your network, the number of tasks, and the size of the image you are deploying, and whether or not you turned on debugging the process may take several minutes to a few hours to complete.

Configuring System Images


After you capture an image from a reference system using the Deployment and Recovery console, the System Image appears in on the System Images page.

K2000 Deployment Appliance v3.3, Administrator's Guide

81

In most cases you will want to add tasks that automate the process of preparing the target computer for the image, such as reformatting and partitioning the hard drive, and tasks that customize the deployment, such as naming the computer and joining it to the domain. You can also add, remove, and modify files, directories, and other items in the image.

Capturing a system image


The Image Capture process starts by booting a source computer to the deployment environment, KBE. Once in the deployment environment, the image capture takes place from the source computer using the client side Main Menu. KBE also has VNC remote control software built into the boot environment so that administrators can remotely capture images. Sysprep based images are most widely used when deploying the same image to a large numbers of computers. The hard drive is built with the operating system and any other settings the IT staffer sees fit. Next the image is generalized with sysprep to remove the Security ID (SID) and any other operating system specific information such as computer name and network settings. Once sysprep is complete, the image can be captured. This can be considered a "clean" image since none of the unique identifiers are present in the image at the time of capture. When this image is deployed, it starts a "mini-setup" where all the identifiers removed in the previous step are returned to the computer. For Windows computers you must run the Microsoft Sysprep Tool before capturing a system image. The capturing process uploads the image to the System Images page. Note: Use the Dell KACE Knowledge base for instructions and examples on preparing and capturing images of Windows and Mac OS X systems. The Sysprep Training Bundle (http://www.kace.com/support/downloads/sysprep/SysprepBundle.zip) contains examples for most Windows systems. PXE boot the target system, to display the Boot Manager. Note: Once the system boots, you can access the Boot Manager remotely using a VNC-Java Remote Control session. 1. On the target system Boot Manager, choose the KBE that supports the target hardware.

82

K2000 Deployment Appliance v3.3, Administrator's Guide

In a lab environment, you could increase the Boot Manager Timeout period on the Settings & Maintenance > General Settings page up to 15 minutes (900 seconds) to allow you to connect to the target and interrupt the boot sequence. In a production environment, 15 seconds is the default and in most cases increasing the time out could impact user productivity. The Deployment and Recovery Console appears.

2. Click Imaging.

K2000 Deployment Appliance v3.3, Administrator's Guide

83

3. 4. 5. 6.

Click Capture image of this machine. In Image Name, enter a name that identifies the image on the appliance. In Image Source, ensure that all the drives you want to capture appear in the list. Click Force continue on errors to continue the capture and upload process even if warnings and fatal error occur. 7. Click Include debug output in log to turn on debugging level logging and upload the log to the Appliance Logs page. Turning on debugging may increase the time it takes to capture and upload the image. 8. Click Start capture. The K2000 Client dialog opens and connects to the appliance. The dialog remains open and shows the progress. The name of the image also appears on the System Images page and the Status column indicates the progress (for example Uploading). Depending on the bandwidth of your network, the number of tasks, and the size of the image you are deploying, and whether or not you turned on debugging the process may take several minutes to a few hours to complete.

Setting up the Pre- and Postinstallation Tasks


Pre- and Postinstallation Tasks allow you automate the tasks that prepare the computer for the operating system and complete (customize) the set up after deployment. System Images: Configure the Pre- and Postinstallation Tasks after capturing and uploading the image from the reference machine. Scripted Installations: Configure the Pre- and Postinstallation Tasks after setting up the answer file or after choosing a server-based attended installation. Note: You can also modify which Pre- and Postinstallation Tasks are assigned to an existing deployment configuration by viewing the details. The New Scripted Installation wizard displays the Scripted Installation Details page after you set up the answer file. 1. To modify the Pre- or Postinstallation tasks of an existing Scripted Installation, click Deployments > Scripted Installations and then click on the name. The Scripted Installation Details page appears. 2. Click Setup Configuration to display the answer file in XML. You can change the settings by editing the XML. 3. In Preinstallation Task Error Handling, choose the script behavior when an error occurs: Continue on Errors: Ignore failures and continue without prompting. Prompt on Errors: Prompts with an option to abort or continue. Halt on Errors: Aborts if an error occurs.

4. In Installation Plan, configure the actions to run before and after the operating installation: a) Drag Pre- and Postinstallation Tasks from Available to Run. b) Put the tasks in the order you want them to be executed. 5. Click Save. If you click Cancel when using the Scripted Installation Wizard, the Scripted Installation is created without Pre- or Postinstallation Tasks assigned and manual changes to the configuration file are discarded.

84

K2000 Deployment Appliance v3.3, Administrator's Guide

The Scripted Installation is now available from the Boot Manager window on computers that PXE booted to the appliance and can be assigned to a computer on the Boot Action Setup page.

Editing System Images


Captured images are fully editable from the appliance. You can rename, replace, remove, or edit image files from the Administrative Console. Empty directories can also be added to the image for later population. Making a backup copy of an image prior to modification takes seconds and requires no additional storage. 1. Click Deployments > System Images. 2. Click the name of the image. The System Image Details page appears. 3. Click Browse Files. The File Browser window opens. 4. Click the drive letter to expand the partition and view the files in the image, you can rename, remove, and replace files. Click Submit after each change. 5. Click Add Drive to add a partition. Click Submit after each change. Once you submit a change it is committed even if you close the File Browser window and click Cancel on the System Image Details page.

Deploying a System Image


Deploy System Images from the appliance using Boot Actions (installs on next network boot) or from the system using the Deployment and Recovery console.

Reimaging from the Recovery Console


You can deploy a System Image from the Deployment and Recovery console on a target system. PXE boot the target system, to display the Boot Manager. Note: Once the system boots, you can access the Boot Manager remotely using a VNC-Java Remote Control session. 1. On the target system Boot Manager, choose the KBE that supports the target hardware.

K2000 Deployment Appliance v3.3, Administrator's Guide

85

In a lab environment, you could increase the Boot Manager Timeout period on the Settings & Maintenance > General Settings page up to 15 minutes (900 seconds) to allow you to connect to the target and interrupt the boot sequence. In a production environment, 15 seconds is the default and in most cases increasing the time out could impact user productivity. The Deployment and Recovery Console appears.

2. Click Imaging.

86

K2000 Deployment Appliance v3.3, Administrator's Guide

3. Click Deploy image to this machine. 4. In Image Name, click the name of the image you want to install on this machine. Only System Images for the platform and architecture appear in the list. 5. Click Restart Automatically after deployment to reboot the system after the last Postinstallation Task is performed. 6. Click Start deploy. The VNC-Java Remote Control session remains open while the tasks performed in KBE are executed; from the session you can watch the progress of the Preinstallation and Image installation tasks, as well as any Postinstallation Tasks that are performed in KBE by re-establishing a connection. Depending on the bandwidth of your network, the number of tasks, and the size of the image you are deploying, the process may take several minutes to a few hours to complete.

Deploying on the next network boot


These instructions explain how deploy a Scripted Installation or a System Image on one or more target computers from the appliance the next time the computers network boot. Access the Boot Action Setup from the System Details, Scripted Installation Details, and System Image Details to populate fields with related options (such as the MAC address of the target machine). This tasks walks you through the process when assigning the boot action from scratch. Note: A target can only have one Boot Action assigned. When you assign a machine to a new boot action, the existing boot action is automatically deleted. 1. Click Systems > Boot Actions. 2. In Choose Action, click Add Boot Action. Choosing systems from the Boot Action list and clicking Set Boot Action populates the machines field with the MAC addresses of the selected systems. If you do not know the MAC address of the system, it is possible to assign the boot action to the IP address (not recommended) using this option. Saving a Boot Action replaces the existing one. The Boot Action Setup page appears. 3. In First Boot Action , click the type of the action (Show Boot Manager or Boot from Local Hard drive) or the name of the Scripted Installation or System Image you want to deploy. 4. In Number of Boots, enter the number of times you want this action to occur before executing the Next Boot Action. 5. In Next Boot Action, click the name of the Scripted Installation or System Image you want to deploy. 6. In Number of Boots, enter the number of times you want this action to occur before displaying the Boot Manager. 7. If you choose a System Image or Scripted Installation that has the Scan Users States Offline Preinstallation Task, the Scan User States Offline page appears. Select the USMT Scan Template and click Save. 8. If you choose a System Image or Scripted Installation that has only the Deploy User State Postinstallation Task, the Deploy User States page appears. Select the USMT version, the users you want to deploy, and click Save. The next time the targets boot from the appliance, the Boot Manager launches the action without displaying the Boot Manager menu.

K2000 Deployment Appliance v3.3, Administrator's Guide

87

Maintaining the appliance

Updating appliance software


Your appliance automatically checks for updates nightly. Use the instructions in this section to get and install updates during normal business hours or to manually update an appliance that does not have direct access to the Dell KACE Support site.

Displaying the appliance version


There are two ways to display the appliance version. You can click the About link in the lower left corner or use the instructions in this section. 1. Click Settings & Maintenance > Appliance Maintenance. The Appliance Maintenance page appears. 2. Under K2000 Appliance Updates, the Current Version field displays the software version number.

Checking for updates


The appliance checks for updates from the Dell KACE Customer Support Portal nightly. To check for a newer version, the appliance requires access to the internet. This section explains how to manually check for updates and automatically install them. 1. Click Settings & Maintenance > Appliance Maintenance. The Appliance Maintenance page appears. 2. Click Edit next to Check for Server Updates. The Update Status and Last Check show the progress. The appliance is updated with the latest software. Some updates take an hour or more to apply and require a reboot to complete.

Updating the appliance directly from KACE


Software updates are available from the Dell KACE Customer Support Site or by contacting Dell KACE Technical Support directly.

88

K2000 Deployment Appliance v3.3, Administrator's Guide

1. Click Settings & Maintenance > Appliance Maintenance. The Appliance Maintenance page appears. 2. Under K2000 Appliance Updates, click Edit. 3. Click Check for Server Updates. If an update is available, a confirmation message appears. 4. Click Apply Updates. Some updates take a few hours to apply and may require the appliance to reboot.

Manually updating the appliance


Apply patches and updates to the appliance software and database from a file you previously downloaded to a local machine. Manually apply patches and updates to the appliance from the Administrative Console. 1. Click Settings & Maintenance > Appliance Maintenance. The Appliance Maintenance page appears. 2. Next to Manually Update K2000, click Edit. 3. Click Browse, select the update file, and then click Open. 4. Click Update K2000. The update is applied. Some updates take a few hours to complete and may require the appliance to reboot.

Updating RSA software


When your environment uses the Remote Site Appliance (RSA) to distribute components from a remote share, you must also update the RSA OVF images each time you update the K2000 Appliance software. The updates are available from the Dell KACE Customer Support Site or by contacting Dell KACE Technical Support directly. 1. Click Settings & Maintenance > Appliance Maintenance. The Appliance Maintenance page appears. 2. Scroll down to Remote Sits Appliance (RSA) OVF Image Updates and click Edit. 3. Click Check for RSA OVF Image Updates. The Update Status displays the results of the process. Is an update is available it is automatically downloaded and applied. The connected RSAs now have the latest software. Some updates take a few hours to complete and may require the appliance to reboot.

Viewing and downloading log files


You can display the appliance logs, including the mail server and access logs, or save them to another computer from the Appliance Maintenance page.

K2000 Deployment Appliance v3.3, Administrator's Guide

89

Displaying log files


The Dell KACE K2000 appliance log files are available from the Administrative Console. This section explains how to display the log as a text. 1. Click Settings & Maintenance > Logs. The Appliance Logs page appears. 2. Click the name of the log. The log contents displays on the page with the latest entry first.

Downloading all logs


The Dell KACE K2000 appliance allows you to compress and download all logs in a single .tgz file. 1. Click Settings & Maintenance > Logs. The Appliance Logs page appears. 2. Scroll to the bottom of the page. 3. Below the last log file, click Download Logs. The Opening Log Files window appears. 4. Click Open with or Save, and then click OK.

Managing drivers
Manage supplemental drivers on the Library > Drivers page, that is drivers for peripherals and hardware which are not included in the Source Media and boot environments you uploaded or the appliance default KBEs. Note: Manage drivers in system images on the reference computer using system tools. To update the currently cached drivers, use one of the following methods: Driver Feed, Download and Install Packages: Automatically puts a copy of the drivers on the share and recaches the Drivers list. Package Management > Import List, import BE type package: Automatically puts a copy of the drivers on the share and recaches the Drivers list. Driver share: Copy driver files to the share. You must manually recache the KBE folder on Managing Drivers page. Driver Harvest Utility: Automatically uploads selected drivers from a Windows computer to the driver share. You must manually recache the KBE folder from the Managing Drivers page The following diagram shows the resources required to build a KBE:

90

K2000 Deployment Appliance v3.3, Administrator's Guide

Note: Using hardware specific KBEs reduce the amount of time it takes to load drivers and network boot. To exclude drivers from a KBE build, remove them from the Driver cache.

Managing the drivers share files


The driver share directory is organized into subdirectories, two boot environments and one for each of the supported operating systems. The share uses this organization because each KBE and operating system type requires its own versions of a driver. This is especially true for the more recent operating systems. The UNC path to the driver share \\K2000_hostname\drivers. Under each directory you can create subfolders to organize the drivers you add. The path to the driver, including the driver name, cannot exceed 255 characters, the directories and driver names do not support special characters.

Manually adding drivers


After downloading and uncompressing drivers from the manufacturer web site or other resource, upload the driver files to the appliance and recache the corresponding driver folder. Recaching a KBE folder from the Managing Drivers page makes the drivers available to Media Manager when building a KBE. Recaching an operating system folder makes the drivers available to Scripted Installations (Windows only).

K2000 Deployment Appliance v3.3, Administrator's Guide

91

Note: Leave the drivers in the corresponding folder, even after recaching, to make it available to the appliance processes. The system compatibility report shows cached driver availability. Removing a driver without recaching may cause booting, installation, and recovery errors that result in system failure and compromise the issues shown in the compatibility report. The UNC path to the driver share \\K2000_hostname\drivers. Under each directory you can create subfolders to organize the drivers you add. The path to the driver, including the driver name, cannot exceed 255 characters, the directories and driver names do not support special characters. 1. Download and uncompress the drivers to a computer that can access the appliance drivers share. 2. Open the driver share. You set the share password in Driver/Restore Share Password on the Settings & Maintenance > General Settings page. 3. Put the driver files in a folder that corresponds to the process to which you want to make the drivers available. For example, to make drivers available to Media Manager for a 32 bit KBE build, put the drivers to kbe_windows_x86. 4. Go to Library > Drivers, and then in Choose Action click Recache Drivers. The Managing Drivers page appears. 5. Click the button that corresponds to the driver share folder. Recache All Drivers updates the every cache and can take a long time to execute. Only recache the folders that changed. For example, Recache K2000 Boot Environment (Windows x86) updates the drivers from kbe_windows_x86. 6. Click the Drivers tab. The Drivers list appears. 7. Using the View by menu, filter the driver list and verify that the drivers you added are now cached. For example, click View by > KBE (Windows x86) to show the drivers you added to kbe_windows_x86.

92

K2000 Deployment Appliance v3.3, Administrator's Guide

Getting drivers from Dell KACE


Dell KACE Support gathers drivers and provides packages that you can download and install on the Library > Driver Feed page. The model specific packages contain drivers for Scripted Installations (Windows only) and System Images. The Windows KBE packages contain drivers contained in the Windows Automated Installation Kit (WAIK). Note: The KBE packages are the same as the prebuilt KBEs shipped with the Dell KACE Deployment Appliance. You must enable the driver feed to populate the available driver package list, see Enabling the Driver Feed on page 16 for details. 1. Click Library > Driver Feed. 2. Click the driver package you want to add to the appliance cache. If the drivers are required for network booting, add the Windows PE package. 3. In Choose Action, click Download and Install Packages. The process begins. The Status column changes to Installed into driver share when the process completes. The drivers are automatically recached and appear in the driver list. The drivers are now available for Scripted Installations and System Images or KBE (if you installed a Windows PE pack).

Managing Disk Space


Running out of disk space may cause the appliance to stop functioning. Be sure to free disk space by backing up data and removing any unused items from the appliance. After backing up the data on your system, remove the following items to free disk space:
Type Unused system image files Description Purge files captured during a system image that are not currently referenced by any of System Images in a Deployment configuration. Typically these files were replaced after the capture, or shared by System Images that have been removed from the appliance. When machines become obsolete and you most likely will not need to reimage or recover them, delete the images from the Deployment configurations and run a purge. Once you end of life an operating system, delete the Source Media from the library and the corresponding Scripted Installations from the Deployment configurations. Delete unused tasks from the Library, particularly those that are large. For example, application tasks. After deploying User States to all the required targets, delete those that you do not plan to deploy again. When you rebuild KBE it creates a new KBE in both the Source Media and Boot Environments libraries. Delete any that do not contain the drivers required by your endpoints to network boot.

System Images OS Installation Pre- and Postinstallation Tasks User States KBEs

K2000 Deployment Appliance v3.3, Administrator's Guide

93

Type Restore Share

Description Store backup packages in another location. Offload and delete exported packages automatically or manually. Manually delete packages added to the Restore directory that were too large to import from another location.

Verifying available disk space


Confirm the available disk space on the Disk Usage chart. For optimal performance the Dell KACE K2000 appliance requires about 20% free disk space. This allows you to stage or restore backup files as required. Click Home. The Dashboard page appears with the Disk Usage chart on the lower right.

Removing unused image files


To free disk space, remove all unused K-Image files from the hash store. 1. Click Settings & Maintenance > Appliance Maintenance. The Appliance Maintenance page appears. 2. Scroll down to Purged unused K-image files, and click Edit. 3. Click Purge. The Dell KACE K2000 appliance deletes all unused K-Image files from hash store. After the process of deleting unused image files completes, view the remaining disk space on the Home page.

Deleting System Images


System Images can be very large and generally use the most disk space. Whenever an image becomes out-of-date or the system type becomes obsolete, be sure to remove the images from the appliance. Note: You can only delete unassigned System Images. System Images can be assigned to a system as a boot action. 1. Click Deployments > System Images. The System Images page appears. 2. Select the items you want to remove. 3. In Choose Action, click Delete Selected. The items are permanently removed from the appliance. View the disk storage on the Home page.

Deleting Scripted Installations and OS Source


When an operating system type is obsolete or otherwise unused in your environment, remove the Scripted Installation and OS source media. Note: Only unassigned items can be deleted. Therefore, you must remove the Scripted Installations before removing the Source Media.

94

K2000 Deployment Appliance v3.3, Administrator's Guide

1. Click Deployments > Scripted Installations. The Scripted Installations page appears. 2. Select the items you want to remove. 3. In Choose Action, click Delete Selected. 4. Click Library > Source Media. The Source Media page appears. 5. Select the items you want to remove. 6. In Choose Action, click Delete Selected. The items are permanently removed from the appliance. View the disk storage on the Home page.

Deleting KBEs and NetBoot Environments


When you build and upload a new network boot environment, two copies are created. Remove the boot environment from both the Source Media and Boot Environments pages. Note: You can only delete unassigned network boot environments from the Boot Environments page. Boot environments can be assigned as the Default Boot Environment on the General Settings page or to a system as a Boot Action. 1. Click Library > Boot Environments. The Boot Environments page appears. 2. Select the items you want to remove. 3. In Choose Action, click Delete Selected. 4. Click Library > Source Media. The Source Media page appears. 5. Select the items you want to remove. 6. In Choose Action, click Delete Selected. The items are permanently removed from the appliance. View the disk storage on the Home page.

Deleting Preinstallation Tasks


Remove unused Preinstallation Tasks after backing it up as required. Note: You can only delete unassigned tasks. Tasks can be assigned to a Scripted Installation or System Image Deployment configuration. 1. Click Library > Preinstallation Tasks. The Preinstallation Tasks page appears. 2. Select the items you want to remove. 3. In Choose Action, click Delete Selected. The items are permanently removed from the appliance. View the disk storage on the Home page.

Deleting Postinstallation Tasks


Remove unused Postinstallation Tasks after backing it up as required.

K2000 Deployment Appliance v3.3, Administrator's Guide

95

Note: You can only delete unassigned tasks. Tasks can be assigned to a Scripted Installation or System Image Deployment configuration. 1. Click Library > Postinstallation Tasks. The Postinstallation Tasks page appears. 2. Select the items you want to remove. 3. In Choose Action, click Delete Selected. The items are permanently removed from the appliance. View the disk storage on the Home page.

Backing up and restoring data


Use the Package Management Export K2000 Packages feature to back up data to either the Restore share on the appliance or another location. And use the Import K2000 Packages to restore items you backed up or share the data between K2000 appliances.

Exporting library components to packages


The Export feature generates a package (.PKG) file that contains the data you want to backup or share and an index (.XML) file that contains meta data about the package for each of the selected components. The appliance saves the files in the K2000 Restore directory, \\K2000_hostname\Restore. Store and move the files together, each package with its complementary index file. Note: Often Package files are very large because they may contain full disk images or entire operating systems. Use care when storing and copying these files from the K2000 to other network locations. 1. Click Settings & Maintenance > Package Management > Export K2000 Packages. 2. Click the components that you want to package. A separate package is created for each item you select. 3. In Choose Action, click Export Selected . The packaging process begins, it may take a few minutes to several hours to complete depending on the size and number of the packages. The status column indicates when each export completes.

Scheduling backups
You can schedule components you want to export at regular intervals. The export creates a new package each time it is exported, so back up files that you think will change. 1. Click Settings & Maintenance > Package Management > Export K2000 Packages. The Export List page appears. 2. Select the items you want to export at a regular interval. 3. In Choose Action, click Schedule Export for Selected. The Schedule Export page appears. 4. Set the interval that the items are exported into packages and saved in a folder on the Restore share.

96

K2000 Deployment Appliance v3.3, Administrator's Guide

5. Click Save. At the next specified time the item is exported. The job appears in the Package Management Queue. Note: Removing a job from the Queue also removes the schedule on the Export page.

Automatically transferring packages


Copies exported packages from the K2000 restore directory to a remote location. Use the Off-Board Package Transfer feature to automatically backup exported packages from the appliance restore directory to a remote FTP/SFTP server or Samba file share. The backup process creates a new directory on the remote server, copies all .xml and .pkg files to that location, and optionally deletes the transferred files from the restore directory. 1. Click Settings & Maintenance > Package Management > Off-Board Package Transfer. The Off-Board Package Transfer page appears. 2. Click Enable Backup. The Backup form appears. 3. Set the transfer details as follows: Schedule Run: Select the interval and set the time when you want to run the backup. Backup Protocol: Select which file transfer protocol is used to put files on the remote site. Backup Server Host Name or IP: Host name or IP address of the computer to which the files are transferred. Path or Share Name: Enter the path to the directory or share name for the backups. User Name: Enter the user name for the appliance to use, requires write access the remote location. User Password: Enter the password name required to access the remote location. Cleanup Restore: Click to enable. Deletes files from the restore directory on the K2000 appliance after the transfer completes.

4. Click Save. At the next specified time the items are transferred to the location you specified. The job appears in the Package Management Queue. Note: Removing this job from the Queue also removes the Offboard Transfer configuration.

Restoring Library components


The Import feature allows you to share data between K2000 Deployment appliances and to restore data from backup.

Restoring components from a remote share


Use the Import and Upload Package to restore or share library components, such as drivers, pre and post-installation scripts, and user states and templates, from Dell KACE K2000 appliance packages. Note: After importing a driver package, you must recache the drivers on the Managing Drivers page.

K2000 Deployment Appliance v3.3, Administrator's Guide

97

To import both the package and corresponding index file is required. For example, if you import windowsdriverxyz.pkg, windowsdriverxyz.xml is also required. You can upload and import packages smaller than 2 GB from an external computer or file share. However, you must move larger packages to the Dell KACE K2000 appliance Restore directory and use import. 1. Click Settings & Maintenance > Package Management. The Package Management page appears. 2. Click Import K2000 Packages. The Import List page appears with a list of packages in the restore share. 3. Import packages: Select the items in the list, and then in Choose Action, click Import K2000 Packages. In Choose Action, click Upload Package for Import.

4. Click Browse. The file selector window appears. 5. Locate and select the .pkg file you want to import, then click Open. The Dell KACE K2000 appliance adds a copy of the component to the library.

Restoring components from a local share


The Import feature adds components from packages to the library. Importing packages adds only new or updated items, such as drivers and user states. You must upload packages before you can import the contents, see Restoring components from a remote share on page 97. 1. Click Settings & Maintenance > Package Management > Import K2000 Packages. The Settings: Import List page appears. 2. Click the check box next to the package you want to import. 3. In Choose Action, click Import Selected. The import process begins. Depending on the size and number of components in the package, the process can take several minutes to several hours. The new components appear in the library.

Installing tools required to build KBE


To build a K2000 Boot Environment (KBE), Media Manager and Windows Automated Installation Kit are required. To build and upload new KBEs: WinPE v3.0Windows requires the Media Manager and the Windows AIK NetBootMac OS X requires the K2000 Image Utility and the Mac OS X installation disk

98

K2000 Deployment Appliance v3.3, Administrator's Guide

Downloading and installing Media Manager


Media Manager is available for both Mac OS X and Windows.

Installing Media Manager for MAC OS X


K2000 Media Manager builds NetBoot network booting environments and uploads system image captures. Perform these steps on the Mac OS X computer with an administrator account. Note: The installation disk for the computer is required to build a network booting environment. 1. Log in to the Dell KACE K2000 Appliance Administrative Console. 2. Click Library > Media Manager. The Media Manager page appears. 3. Click Download for Mac OS X. The File Download window appears. The Media Manager is installed. Click the Media Manager application to run it.

Installing Media Manager on Windows


Media Manager builds and rebuilds boot environments, uploads operating system source, and Windows User States to the Dell KACE K2000 Appliance. Download and install the Media Manager from the K2000 appliance. Media Manager requires Microsoft .NET 2.0. Before you install Media Manager, download and install .NET 2.0 from the Microsoft Download Center. Search this web site for NET and the computer operating system name to find the files you need. Perform these steps on the computer where you installed .NET. 1. Log in to the Dell KACE K2000 Appliance Administrative Console. 2. Click Library > Media Manager. The Media Manager page appears. 3. Click Download for Windows (Requires .Net 2.0). The File Download window appears. 4. Click Run or Save to download the installation file to the computer and then double-click it to begin installation. The Welcome window appears. 5. Click Next. The Select Installation Folder window appears. 6. (Optional) In Folder, click Browse and select a folder. 7. Click Next. The Confirm Installation window appears. 8. Click Next. After a few moments the Installation Complete window appears. 9. Click Close. The Media Manager is now installed on the computer. To start Media Manager, go to Start > Programs > KACE > K2000 Media Manager.

K2000 Deployment Appliance v3.3, Administrator's Guide

99

Installing Windows Automated Installation Kit (AIK)


Before you can build the K2000 Boot Environment (KBE) you must install the Windows AIK for Windows 7 on either a Windows 7 computer or Windows 2008 Server. During the Windows AIK installation process you accept the EULA terms and conditions that gives the user permission to use WinPE 3.0 and USMT 4.0. And the WAIK ISO for Windows 7 contain most of the mass storage and Network card drivers that are required to boot computers using KBE (WinPE3.0). This task requires an ISO mounting software or a blank DVD, a Windows 7 computer or Windows 2000 server with an account on the machine with elevated privileges such as an administrator account. Log in to a Windows 7 computer or Windows 2008 Server using an account that has permission to install software, such as an administrator account. 1. Download the Windows AIK for Windows 7 from the Microsoft web site to the computer. Ensure that you get correct package. The WAIK for Windows 7 download takes a minimum of 2.5 hours to complete. 2. Install the Media Manager application while the WAIK ISO downloads, see Installing Media Manager on Windows on page 99. 3. To access the installation files, either burn the WAIK ISO file to a DVD or mount the ISO to the computer using an ISO mounting utility. 4. Run the WAIK installer, by double-clicking StartCD.exe. Once the Media Manager and Windows AIK are installed, you are ready to capture an image and build the K2000 Boot Environment.

Understanding Action Icons


The Action Icon menu on the General Settings page provides buttons on the System Inventory, Network Inventory, and Boot Actions pages that allow you to access remote nodes from the Dell KACE K2000 appliance.

Programming remote access icons


Remote Access icons appear on the System Inventory, Network Inventory, and Boot Actions pages. You can configure the icons to launch an application, such as CRT secure shell, VNC, Putty and so forth, or open an HTML supported link, such as a VNC-Java Remote Control session to a target that has network booted. When launching applications, the Remote Action runs as an unsigned scripted ActiveX control and opens the application you specified on the browser host. You can only run these types of Remote Actions using Internet Explorer. Note: Only Remote Actions that open a browser session, such as VNC-Java Remote Control, work with Safari, Firefox, and so forth. The Dell KACE K2000 appliance provides the following preprogrammed options for remote access. The table below describes the corresponding requirements:

100

K2000 Deployment Appliance v3.3, Administrator's Guide

Software

Browser Host Requirements crt.exe

Client-side Requirements SSH client

Description

SecureCRT

The appliance launches SecureCRT and connects to node using SSH on port 8443 by default. Most operating systems come with a standard SSH client. DMRC client is automatically installed on the client the first time a connection is opened. You can use any DMRC supported cli options. Displays the nodes shared folders. Note that the full path of the executable is typically required; for example: C:\Windows\explorer.exe. Opens a remote desktop session with the node. If the node is online it responds to the ping. Opens an SSH connection from the browser host to the target node. Opens a session from the browser host to target node. Opens a session from the browser host to the target node. Opens a session from the browser host to the target node. The KBE has the client side software, therefore you can VNC in a browser session to a client that has network booted into KBE to access the targets Boot Manager.

Dameware Mini Remote Control Explorer

dwrcc.exe

DMRC client

explorer.exe

Windows/ SMB share

Microsoft Remote Desktop Ping Putty Telnet Tight VNC VNC-Java Remote Control

mstsc.exe ping.exe putty.exe telnet.exe vncviewer.exe None

Remote Desktop None None None None VNC Java Client

To program an Action Icon: 1. Click Settings & Maintenance > Control Panel > General Settings. The General Settings page appears. 2. Click Edit. 3. In Action Icon #1 or Action Icon #2, set up one of the default actions or configure your own action. 4. Click Save. The action icon button now runs the action you configured when you click the icon on the System Inventory, Network Inventory, and Boot Actions pages.

Opening a VNC session to a target in the Boot Environment


The K2000 Boot Environments (KBE) and NetBoot Environments for Mac OS X have a built-in VNC-Java Remote Control application that allows you to connect to the target once it has network booted. Remote access to the target allows you to select boot options in the Boot Manager, such as launching a Scripted Installation or System Image deployment, or using the Hardware Inventory upload tool to gather information about the system. This task requires Action Icon #1 or Action Icon #2 configured for VNC-Java Remote Control with the KACE_HOST_IP or KACE_HOST_NAME variable on the General Settings page. You must also know the VNC-Java Remote Control password. 1. Boot the target computer into the default Boot Environment. For computers connected to the network on that same subnet as the appliance with the first boot sequence option set to NIC, send a wake-on-land from the System Inventory or Network Inventory page. 2. Log in to the K2000 Administrative Console. 3. Click Systems > System Inventory.

K2000 Deployment Appliance v3.3, Administrator's Guide

101

The System appears in the inventory list if it has network booted. 4. In the Host/IP Address column, click the Remote Action icon configured for VNC-Java Remote Control. A new browser tab appears with the hostname or IP address of the system you are accessing. If the target is available, a password prompt appears. 5. Enter the VNC password and click OK. The targets Boot Manager displays.

Using the Deployment and Recovery Console


The KACE K2000 Appliance enables remote emergency recovery of systems that are unable to boot to their local hard drives. Network boot these systems to a K2000 Boot Environments (KBE). You can boot an unresponsive system from the appliance, an RSA, a USB drive, or a bootable ISO file on a CD in the systems CD drive. Once in a boot environment, you use the Deployment Client > Recovery GUI and shell tools available to edit or replace files including the registry, and run commands. The agent-less, PXE-based design allows you to remotely recover any LAN-connected desktop, laptop, or server.

Opening the Recovery Console


The Recovery Console is built into the K2000 Boot Environment. Therefore to access the console you must network boot the computer from the appliance. This section explains how to open the console from the Boot Manager on a Windows system. 1. Network boot the system by restarting it or powering it on. From the Systems > System Inventory page, select the system and then in Choose Action, click Send Wake-on-LAN. The Boot Manager loads on the target. 2. (Optional) If the computer is in another location, access the Boot Manager by connecting to the target using one of the following methods: Action Icon for VNC-Java Remote Control: Click the Icon next to the system row on the Systems > System Inventory, Systems > Network Inventory, or Systems > Boot Actionspage. VNC-Java Remote Control from your browser: In the address bar, enter the host name or IP address followed by port 5800. For example: 198.168.80.129:5800.

Set the VNC password on the Settings & Maintenance > General Settings page. If you forget the password, reset it and then reboot the target system. A new tab opens and displays the VNC Authentication page. Enter the password. The Boot Manager appears.

102

K2000 Deployment Appliance v3.3, Administrator's Guide

3. Select the boot environment that has the drivers that the target requires: Graphical Interface and Text Menu: Use the arrow keys and enter/return to select. Basic: Type the name of the KBE.

The system boots from the appliance and the Recovery and Deployment Console appears.

K2000 Deployment Appliance v3.3, Administrator's Guide

103

From the Deployment and Recovery console you can gather information about the computer and upload it to the appliance, modify data stored on the computer (for example the registery keys and files), perform a clean installation of the operating system, and reimage the system.

Uploading Hardware Inventory


From the Deployment and Recovery console, you can capture the hardware inventory of the system and upload the details to the System Image Details page of the appliance. Note: Uploading the inventory allows you to run a hardware compatibility report on the System Image Details page that shows whether the drivers required by the hardware are available in the driver cache for Scripted Installations. PXE boot the target system, to display the Boot Manager. Note: Once the system boots, you can access the Boot Manager remotely using a VNC-Java Remote Control session. 1. On the target system Boot Manager, choose the KBE that supports the target hardware.

In a lab environment, you could increase the Boot Manager Timeout period on the Settings & Maintenance > General Settings page up to 15 minutes (900 seconds) to allow you to connect to the target and interrupt the boot sequence. In a production environment, 15 seconds is the default and in most cases increasing the time out could impact user productivity. The Deployment and Recovery Console appears.

104

K2000 Deployment Appliance v3.3, Administrator's Guide

2. Click Imaging. 3. Click Deploy image to this machine. 4. In Image Name, click the name of the image you want to install on this machine. Only System Images for the platform and architecture appear in the list. 5. Click Restart Automatically after deployment to reboot the system after the last Postinstallation Task is performed. 6. Click Start deploy. The VNC-Java Remote Control session remains open while the tasks performed in KBE are executed; from the session you can watch the progress of the Preinstallation and Image installation tasks, as well as any Postinstallation Tasks that are performed in KBE by re-establishing a connection. Depending on the bandwidth of your network, the number of tasks, and the size of the image you are deploying, the process may take several minutes to a few hours to complete.

Capturing a system image


The Image Capture process starts by booting a source computer to the deployment environment, KBE. Once in the deployment environment, the image capture takes place from the source computer using the client side Main Menu. KBE also has VNC remote control software built into the boot environment so that administrators can remotely capture images. Sysprep based images are most widely used when deploying the same image to a large numbers of computers. The hard drive is built with the operating system and any other settings the IT staffer sees fit. Next the image is generalized with sysprep to remove the Security ID (SID) and any other operating system specific information such as computer name and network settings. Once sysprep is complete, the image can be captured. This can be considered a "clean" image since none of the unique identifiers are present in the image at the time of capture. When this image is deployed, it starts a "mini-setup" where all the identifiers removed in the previous step are returned to the computer. For Windows computers you must run the Microsoft Sysprep Tool before capturing a system image. The capturing process uploads the image to the System Images page.

K2000 Deployment Appliance v3.3, Administrator's Guide

105

Note: Use the Dell KACE Knowledge base for instructions and examples on preparing and capturing images of Windows and Mac OS X systems. The Sysprep Training Bundle (http://www.kace.com/support/downloads/sysprep/SysprepBundle.zip) contains examples for most Windows systems. PXE boot the target system, to display the Boot Manager. Note: Once the system boots, you can access the Boot Manager remotely using a VNC-Java Remote Control session. 1. On the target system Boot Manager, choose the KBE that supports the target hardware.

In a lab environment, you could increase the Boot Manager Timeout period on the Settings & Maintenance > General Settings page up to 15 minutes (900 seconds) to allow you to connect to the target and interrupt the boot sequence. In a production environment, 15 seconds is the default and in most cases increasing the time out could impact user productivity. The Deployment and Recovery Console appears.

106

K2000 Deployment Appliance v3.3, Administrator's Guide

2. 3. 4. 5. 6.

Click Imaging. Click Capture image of this machine. In Image Name, enter a name that identifies the image on the appliance. In Image Source, ensure that all the drives you want to capture appear in the list. Click Force continue on errors to continue the capture and upload process even if warnings and fatal error occur. 7. Click Include debug output in log to turn on debugging level logging and upload the log to the Appliance Logs page. Turning on debugging may increase the time it takes to capture and upload the image. 8. Click Start capture. The K2000 Client dialog opens and connects to the appliance. The dialog remains open and shows the progress. The name of the image also appears on the System Images page and the Status column indicates the progress (for example Uploading). Depending on the bandwidth of your network, the number of tasks, and the size of the image you are deploying, and whether or not you turned on debugging the process may take several minutes to a few hours to complete.

Reimaging from the Recovery Console


You can deploy a System Image from the Deployment and Recovery console on a target system. PXE boot the target system, to display the Boot Manager. Note: Once the system boots, you can access the Boot Manager remotely using a VNC-Java Remote Control session. 1. On the target system Boot Manager, choose the KBE that supports the target hardware.

K2000 Deployment Appliance v3.3, Administrator's Guide

107

In a lab environment, you could increase the Boot Manager Timeout period on the Settings & Maintenance > General Settings page up to 15 minutes (900 seconds) to allow you to connect to the target and interrupt the boot sequence. In a production environment, 15 seconds is the default and in most cases increasing the time out could impact user productivity. The Deployment and Recovery Console appears.

2. Click Imaging.

108

K2000 Deployment Appliance v3.3, Administrator's Guide

3. Click Deploy image to this machine. 4. In Image Name, click the name of the image you want to install on this machine. Only System Images for the platform and architecture appear in the list. 5. Click Restart Automatically after deployment to reboot the system after the last Postinstallation Task is performed. 6. Click Start deploy. The VNC-Java Remote Control session remains open while the tasks performed in KBE are executed; from the session you can watch the progress of the Preinstallation and Image installation tasks, as well as any Postinstallation Tasks that are performed in KBE by re-establishing a connection. Depending on the bandwidth of your network, the number of tasks, and the size of the image you are deploying, the process may take several minutes to a few hours to complete.

Performing a clean OS installation


You can initiate the clean installation of an operating system, Scripted Installation, from the Deployment and Recovery Console on a target system. PXE boot the target system, to display the Boot Manager. Note: Once the system boots, you can access the Boot Manager remotely using a VNC-Java Remote Control session. 1. On the target system Boot Manager, choose the KBE that supports the target hardware.

In a lab environment, you could increase the Boot Manager Timeout period on the Settings & Maintenance > General Settings page up to 15 minutes (900 seconds) to allow you to connect to the target and interrupt
K2000 Deployment Appliance v3.3, Administrator's Guide 109

the boot sequence. In a production environment, 15 seconds is the default and in most cases increasing the time out could impact user productivity. The Deployment and Recovery Console appears.

2. Click Scripted Installation. 3. In Scripted Installation Name, click the one you want to install on this system. 4. Click Start installation. The process launches in a command prompt window. The VNC-Java Connection remains open until after the OS installation completes. The connection is dropped on the reboot. Depending on the bandwidth of your network, the number of tasks, and the size of the image you are deploying, and whether or not you turned on debugging the process may take several minutes to a few hours to complete.

Accessing information on a corrupted node from KBE


The Recovery option on the Deployment and Recovery console allows you to access, back up and modify information from a target that cannot boot from its own hard drive. The following options are available:
Option Command Prompt Edit File in Notepad Edit the Registry Edit the User Registry Description Run MS-DOS commands to access and modify the target system. Open and modify any file supported by Notepad on the target systems hard drive. This allows you to change Change the system registry keys. Change the user registry keys.

PXE boot the target system, to display the Boot Manager.

110

K2000 Deployment Appliance v3.3, Administrator's Guide

Note: Once the system boots, you can access the Boot Manager remotely using a VNC-Java Remote Control session. 1. On the target system Boot Manager, choose the KBE that supports the target hardware.

In a lab environment, you could increase the Boot Manager Timeout period on the Settings & Maintenance > General Settings page up to 15 minutes (900 seconds) to allow you to connect to the target and interrupt the boot sequence. In a production environment, 15 seconds is the default and in most cases increasing the time out could impact user productivity. The Deployment and Recovery Console appears.

K2000 Deployment Appliance v3.3, Administrator's Guide

111

2. Click Recovery. The Recovery Tools appear. 3. Click the recovery tool you want to run. Closing the registry editing window saves the changes you made. When you are done, click Back to Main Menu to exit the tools.

112

K2000 Deployment Appliance v3.3, Administrator's Guide

Administrative Console

The Administrative Console is a web-based interface. This guide provides detailed information on the user interface pages.

Home
Provides quick access to frequently performed tasks, latest support news and FAQs, appliance alerts, tutorials, and the global search function.

Tasks
Administrator dashboard page that provides links to tasks you may need to perform, appliance statistical data, and the latest information from Dell KACE. Alerts Displays appliance state messages that may require action, including warnings when you are approaching your appliance capacity, configuration, and so forth. Common Tasks Displays a list of the most frequently used appliance tasks. Library Summary Displays total number of components in the appliance library areas. Support News RSA news feed that links to the latest articles from Dell KACE and the top 5 FAQs from the Support Portal. Deployment Statistics Displays deployment summary information.

K2000 Deployment Appliance v3.3, Administrator's Guide

113

Network Utilization Displays current statistical information on the network traffic over the two appliance NICs. System Health Displays critical information about the appliance hardware, such as RAID health. Disk Usage Provides current disk space information. The appliance requires about 20% free space.

Guided Tour
Provides tutorials that lead you through the process of setting up your appliance and allow you to quickly learn the main features.

Search (Global Search)


Search all library components, tasks, and other appliance items for specific terms or phrases. For example, searching for Windows returns all Windows source media, systems, preinstallation and postinstallation tasks, deployment scripts, boot actions, and so on. Search field Type the word or phrase that you want to match and click Search. Global Search field Type the word or phrase that you want to match, and then press Enter or Return.

Library
Manages all the components used by the boot environments, scripted installations, and system images.

Overview
Displays library component summary data with links to menus and management utilities.

Source Media
Displays a list of the available operating systems installation source and K2000 Boot Environments. Source Media allows you to install a clean version of the operating system using the Deployments > Scripted Installations feature and create hardware specific boot environments and create a copy of the KBE using the Deployments > Boot Environments. Choose Action Manage components using the following options:

114

K2000 Deployment Appliance v3.3, Administrator's Guide

Download Media Manager

Opens the Media Manager page where you can download the utility that is required for uploading OS Installation files, K2000 Boot Environments, and Windows User State Migration Tools. Removes the selected items from the appliance. Note: You can only remove unassigned source media. Before you can delete media assigned to a Scripted Installation, assign a different source media item or delete the Scripted Installation.

Delete Selected

Source Media List Each row shows a source media component uploaded using the Media Manager or imported from a package.
Name Operating System Size Type the display name of the source. Operating systems to which the source applies. Set during upload from Media Manager. The footprint of the operating system installation files contained in the source media item, not the actual physical space required to store the source on the appliance.

Source Media Details


Displays details of the source uploaded from a node using the Media Manager utility. From this page you can modify the source name and add notes. Source Detail Fields Most of the source details are read only.
Name Operating System Total Disks Type the display name of the source. Operating systems to which the source applies. Set during upload from Media Manager. Number of disks in the set that contained the all operating system installation files. A single disk is indicated as 1 of 1. Footprint of the installation files contained on all disks in the set to which this source belongs, not the actual physical disk space of storing this disk on the appliance. Date that the first disk in the set was uploaded. Date that any disk in the set was modified. Source media version, which is the number of times the source media has been modified since it was uploaded. Field for administrators to write information about the source media item. Only visible on this page.

Total Size

Created Modified Version

Notes

K2000 Deployment Appliance v3.3, Administrator's Guide

115

Installation Disk X of Y Created Modified Status Size

Indicates the disk number out of the total number of disks the operating system. The date this disk was uploaded. The date this disk was modified. The upload status of this disk. The footprint of the operating system installation files contained in the source media item, not the actual physical space required to store the source on the appliance. The MD5 checksum of the disk. The SHA-1 checksum of the disk.

MD5 Checksum SHA-1 Checksum

Media Manager
Navigation title: Download Media Manager Utility that allows you to upload Source Media, Windows User State Migration Tools, and K2000 Boot Environment (KBE) from a computer to the appliance. Download the Media Manager installation file to a networked node. Note: You must upload resources from a node with the same operating systems, that is only Media Manager for Windows installed on a Windows node can upload Windows resources.

Drivers
Displays a list of drivers added to a K2000 Boot Environment (KBE), K-image, or for scripted installations from source media. Choose Action Manage components using the following options:
Add Drivers & Recache Drivers Opens the Managing Drivers page where you can recache drivers you manually added to the appliance. Opens the Driver Harvesting page where you can download the Driver Harvesting Utility to capture drivers on a node and upload them to the appliance.

Download Driver Harvesting Utility

Driver List Each row shows a driver added to the appliance.


Description Type Descriptive name of the drivers referenced in the .inf file. The category of hardware for which the driver is used.

116

K2000 Deployment Appliance v3.3, Administrator's Guide

Hardware ID .inf File

Identifies the driver hardware. The full path to the driver setup file on the appliance.

Driver Details
Displays information about the driver. Note: Only delete drivers that are not being used and recache the driver share on the Managing Drivers page. Driver Set Up Shows detailed information gathered from the driver and other resources.
INF File Hardware Class Operating System or KBE (link) The full path to the driver setup file on the appliance. The category of hardware for which the driver is used. The name of the Operating System the driver is for or the KBE driver folder that include the drivers. Note: Click the name to show the supported driver configurations.

Name of Operating System or KBE Driver share folder Shows specific driver configurations used by the Deployment or Boot Environment.
Driver descriptive name Driver Hardware ID Service Name The name of the driver configuration. The driver details display below this heading. Path to the driver configuration file. Specific identifier of the hardware to which the driver configuration applies. Name the driver registers as when installed.

Managing Drivers
Navigation title: Add Drivers Recache Drivers Recache drivers from the \\K2000_hostname\drivers share directory.

K2000 Deployment Appliance v3.3, Administrator's Guide

117

The appliance caches the drivers for K2000 Boot Environment (KBE) and Scripted Installations. To add drivers, copy the driver into the folder for the operating system type and into the KBE folder of the chipset type (if it is required for booting), and then click the corresponding folder button on this page.

Driver Harvesting
Navigation title: Download Driver Harvesting Utility Provides links to download a utility you can use on a node that already has drivers that you want to add to Scripted Installations or KBE. The Driver Harvesting Utility only detects certain driver files and cannot be used for drivers that require an executable to install or have a large number of unusual or complex dependencies.

Driver Feed
Provides driver packs for computer models gathered by Dell KACE support. The appliance downloads the packs directly from the Dell KACE Support Site and recaches the appliance driver store. Choose Action Manage driver packs using the following options:
Manage Driver Feed Settings Opens the Driver Feed Settings where you can enable/disable the feed from Dell KACE and check for new packs. Downloads packages from Dell KACE, puts them in the

Download and Install Packages

\\K2000_hostname\drivers share, and then automatically recaches the


appliance driver store. Uninstall Packages Removes the package from the \\K2000_hostname\drivers share and then automatically recaches the appliance driver store.

Driver Package List Each row shows a driver package available from Dell KACE.
Model Manufacturer Operating System Last Driver Update Download Size Status Computer model to which the drivers apply. Company that makes the computer. OS and chipset of the computer. Last time the package was updated by Dell KACE. The package size. State of the package; when blank, indicates that the package is not downloaded or installed.

118

K2000 Deployment Appliance v3.3, Administrator's Guide

Driver Feed Settings


Navigation title: Manage Driver Feed Settings Dell KACE Support provides drivers for various computer models. When you check Enable Driver Feed a list of the available packages from Dell displays on the Driver Feed page.

Driver Feed Package Details


Shows information about the driver packages available from the Dell KACE Support site.
Manufacturer Model Operating System Package Type Created Modified Last Driver Update Package Status Install Location Download Filename Download Size Company that makes the computer. Computer model to which the drivers apply. OS and chipset of the computer. Describes the content of the package. Only drivers are available at this time. Date and time when Dell KACE first made the package. Date and time when drivers were added or removed by Dell KACE from the package. Last time the package was updated by Dell KACE. State of the package; when blank, indicates that the package is not downloaded or installed. Path where the drivers are installed in the driver share. File name of the package. The package size.

Preinstallation Tasks
Preinstallation Tasks are assigned to a Scripted Installation or System Image. The appliance executes these tasks after the computer network boots, while the computer is still in the K2000 Boot Environment, and before installing the operating system or reimaging the computer. Use these tasks to prepare and configure system hardware, map network drives, back up data, and so on. For example, you can make a preinstallation task that reformats the hard drive, configures a RAID device, creates partitions, or captures a computer name. Choose Action Manage tasks using the following options:
Add New Application Provides a script or program, such as an executable, and the corresponding command line parameters that the appliance executes in the K2000 Boot Environment before installing the operating systems or reimaging the target.

K2000 Deployment Appliance v3.3, Administrator's Guide

119

Add New BAT Script

Contains a batch script that appliance runs in the K2000 Boot Environment before installing the operating system or reimaging a target. Contains a batch script that appliance runs in the K2000 Boot Environment before installing the operating system or reimaging a target. Provides a Diskpart script that the appliance runs using the Windows Diskpart Command-line Utility in the K2000 Boot Environment before installing the operating system or reimaging the target. Removes the tasks that you selected from the appliance. Note: You can only remove unassigned tasks.

Add New Shell Script

Add New DISKPART

Delete Selected

Default Tasks The appliance comes with the following set of default Preinstallation Tasks that you can customize for your environment.
Name Collect Computer Name Type Application Description Captures the name of a Windows computer for reuse in the Apply Computer Name postinstallation task. Only for System Image deployments. Captures the name of a Mac OS X computer for reuse in the Apply Mac OS X Computer name postinstallation task. Only for System Image deployments. Mac OS X only. Creates a single partition in HFS+ format using either the APM or GPT format. Creates a single primary partition. Uploads the hardware inventory and displays the list of incompatible devices on the client console. Formats the C drive and sets it as an NTFS file system. Installs the master boot record for Windows 2000, Windows XP, or Windows Server 2003. Installs the master boot record for Windows Vista, Windows Server 2008, and Windows 7. Captures the user state and allows you to migrate the user with the Deploy User State postinstallation task. Uploads hardware inventory.

Collect Mac OS X Computer Name Shell Script

Create Single HFS+ partition on disk0 Create Single Partition Display Device Compatibility

Shell Script

DISKPART script BAT script

Format C: as NTFS Install 2000/XP/2003 MBR

BAT script BAT script

Install Vista/2008/7/MBR

BAT script

Scan User States Offline

USMT

Upload Hardware Inventory

BAT script

120

K2000 Deployment Appliance v3.3, Administrator's Guide

Preinstallation Task List The following table describes the Preinstallation Task columns.
Name Type Runtime Environment Size Identifies the Preinstallation Task on the appliance. Read only Application, the type of task. Select the boot environment of the target nodes, either Windows or Mac OS X. Total size of the task.

Preinstallation Task Detail


Navigation title: Add New Application Displays detailed information for an application preinstallation task. From this page you can create, modify, or duplicate a preinstallation task. Provides a script or program, such as an executable, and the corresponding command line parameters that the appliance executes in the K2000 Boot Environment before installing the operating systems or reimaging the target. Note: If you attach a Zip or Tar file, the appliance uncompresses the file and runs the command you specified. Set up the compressed file without a top level folder.
Name Type Runtime Environment Created Modified Version Identifies the Preinstallation Task on the appliance. Read only Application, the type of task. Select the boot environment of the target nodes, either Windows or Mac OS X. Date and time the task was first created. Date and time that the last change was made to the task. Indicates the number of times that the task has been modified. Each saved change adds an increment of one, where one is the first saved version. Displays the name of an attached file or application. Zip files are uncompressed on the appliance before being downloaded onto the target computer. Size of the file. Command line arguments and parameters that the appliance executes to run the task. Note: Use the call command to run a batch script.

File

File Size Command Line

Notes Scripted Installations

Information about the task that appears on this page only. Displays the names of the Scripted Installations to which the task is assigned.

K2000 Deployment Appliance v3.3, Administrator's Guide

121

Note: You can only delete unassigned tasks.

System Images

Displays the names of the System Images to which this task is assigned. Note: You can only delete unassigned tasks.

Preinstallation Task Detail


Navigation title: Add New BAT Script Displays the details of a Batch Script Preinstallation Task. From this page, you can create, modify, or duplicate this preinstallation task. Contains a batch script that appliance runs in the K2000 Boot Environment before installing the operating system or reimaging a target.
Name Type Runtime Environment Created Modified Version Identifies the task. Read only, BAT Script. Read only, Windows. Date and time the task was made. Date and time that the last change was made to the task. Indicates the number of times that the task has been modified. Each saved change adds an increment of one, where one is the first saved version. Series of commands executed by the command line interpreter; the available commands depend on the targets environment. Note: Use the call command to run another batch script.

BAT Script

Notes Scripted Installations

Information about the task that appears on the page only. Displays the names of the Scripted Installations to which the task is assigned. Note: You can only delete unassigned tasks.

System Images

Displays the names of the System Images to which this task is assigned. Note: You can only delete unassigned tasks.

Preinstallation Task Detail


Navigation title: Add New Shell Script

122

K2000 Deployment Appliance v3.3, Administrator's Guide

Displays detailed information for an Shell Script preinstallation task for Mac OS X computers only. From this page, you create, modify, delete, and duplicate the task. Contains a bash shell script that the appliance runs in the K2000 Boot Environment before installing the operating system or reimaging the target.
Name Type Runtime Environment Created Modified Version Identifies the Preinstallation Task on the appliance. Read only, Shell Script. Read only, Mac OS X. Date and time the task was first created. Date and time that the last change was made to the task. Indicates the number of times that the task has been modified. Each saved change adds an increment of one, where one is the first saved version. Series of commands executed by the command line interpreter; the available commands depend on the targets environment. Information about the task that appears on this page only. Displays the names of the Scripted Installations to which the task is assigned. Note: You can only delete unassigned tasks.

Shell Script

Notes Scripted Installations

System Images

Displays the names of the System Images to which this task is assigned. Note: You can only delete unassigned tasks.

Preinstallation Task Detail


Navigation title: Add New DISKPART Displays the details of a DISKPART script Preinstallation Task for Windows only. From this page you can create, modify, or duplicate a preinstallation task. Provides a Diskpart script that the appliance runs using the Windows Diskpart Command-line Utility in the K2000 Boot Environment before installing the operating system or reimaging the target.
Name Type Runtime Environment Created Modified Version Identifies the Preinstallation Task on the appliance. Read only, DISKPART Script. Read only, Windows. Date and time the task was first created. Date and time that the last change was made to the task. Indicates the number of times that the task has been modified. Each saved change adds an increment of one, where one is the first saved version.

K2000 Deployment Appliance v3.3, Administrator's Guide

123

DISKPART Script

Diskpart script that the appliance executes. Note: You must select the disk, volume, or partition.

Notes Scripted Installations

Information about the task that appears on this page only. Displays the names of the Scripted Installations to which the task is assigned. Note: You can only delete unassigned tasks.

System Images

Displays the names of the System Images to which this task is assigned. Note: You can only delete unassigned tasks.

Diskpart commands The following table describes the most typical actions you may want to perform using a Diskpart script:
Action (Mandatory) Selecting objects Command Description You must select a disk, partition, or volume before to operate on with one of these commands. Where number is the disk, partition, or volume number.

select disk=[number] select partition=[number] select volume=[{number\drive_letter}] clean [ all ]

Cleaning partitions

This command quickly removes all partitions from a disk. The all option zeros all sectors on the disk. 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 available space for it. The currently selected partition is marked as an active, or bootable partition. 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 partitions

create partition [ primary | extended | logical ] [ size=number | offset=number ]

Marking the boot partition Assigning a drive letter to a partition

active

assign letter=[letter]

Postinstallation Tasks
Actions you can assign to Scripted Installations and System Images that run after the OS installation. You can create a task that runs either in the K2000 Boot Environment before rebooting or locally after the first reboot. Choose Action Manage tasks using the following options:

124

K2000 Deployment Appliance v3.3, Administrator's Guide

Add New Application

Provides an application or file, such as an installation file, that the appliance runs using the specified command-line either after the installation/deployment of the OS in the KBE or after the first reboot. Use application tasks to name the computer, install and configuration software, or perform any set up task that requires additional files. Contains a batch script that appliance runs either in the KBE after installing/deploying the operating system or from Windows after the first reboot. Contains a bash shell script that the appliance runs in the K2000 Boot Environment after installing the operating system or from the Mac OS after the first reboot. Provides a K1000 Agent installer that the appliance runs from the operating system after the first reboot. Renames the target PC after the first reboot using a Workstation Name Changer compatible text file. For detailed information, see the WSName.exe web site. The appliance renames the computer using the command-line parameters that you specify in this task. Installs the service pack that you selected or uploaded after the first reboot using the command-line parameters you specify. Replaces the targets HAL with the hal.dll, ntkrnlpa.exe, and

Add New BAT Script

Add New Shell Script

Add New K1000 Agent

Add New Naming Rule

Add New Service Pack

Add Custom HAL Replacement

ntoskrnl.exe files you uploaded. The process runs after the image deployment, while
still in the KBE, and before the first boot. Custom HAL Replacement is supported for 32-bit versions (x86) of Windows 2000, Windows XP, and Windows 2003 operating systems only. Thoroughly test the HAL replacement before deployment; a faulty HAL may prevent the computer from rebooting. Delete Selected Removes the tasks you selected from the appliance. Note: You can only remove unassigned items.

Postinstallation Task List The following table describes the Preinstallation Task columns.
Name Type Runtime Environment Identifies the task on the appliance. The type of task. Indicates the environment the appliance runs the task in during a Scripted Installation or System Image. KBE tasks run after installing/deploying the OS while still in the boot environment; Windows/Mac tasks run after first reboot. Indicates the total size of the task.

Size

Postinstallation Task Detail


Navigation title: Add New Application

K2000 Deployment Appliance v3.3, Administrator's Guide

125

Displays the Postinstallation Task details of an application task you can assign to a Scripted Installation or System Image deployment. From this page you can create, duplicate, modify, and delete the task. Provides an application or file, such as an installation file, that the appliance runs using the specified command-line either after the installation/deployment of the OS in the KBE or after the first reboot. Use application tasks to name the computer, install and configuration software, or perform any set up task that requires additional files.
Name Type Runtime Environment Identifies the task on the appliance. Read only. Application, the type of task. Select the environment in which the appliance runs the application. Note: This option determines when you can assign the Postinstallation Task to a Scripted Installation or System Image. KBE tasks run in the boot environment and Windows/Mac tasks run after first reboot list. Created Modified Version

Date and time the task was first created. Date and time of the last change was made to the task. Indicates the number of times that the task has been modified. Each saved change adds an increment of one, where one is the first saved version. Displays the name of an attached file or application. Zip files are uncompressed on the appliance before being downloaded onto the target computer. Size of the file. Command line arguments and parameters that the appliance executes to run the task. Note: Use the call command to run a batch script.

File

File Size Command Line

Notes Scripted Installations

Information about the task that appears on this page only. Displays the names of the Scripted Installations to which the task is assigned. Note: You can only delete unassigned tasks.

System Images

Displays the names of the System Images to which this task is assigned. Note: You can only delete unassigned tasks.

Postinstallation Task Detail


Navigation title: Add New BAT Script Displays the Postinstallation Task details of an Batch Script task you can assign to a Scripted Installation or System Image deployment. From this page you can create, duplicate, modify, and delete the task. Contains a batch script that appliance runs either in the KBE after installing/deploying the operating system or from Windows after the first reboot.

126

K2000 Deployment Appliance v3.3, Administrator's Guide

Name Type Runtime Environment

Identifies the task. Read only, BAT Script. Choose Windows to run the script on the target OS after the first reboot or K2000 Boot Environment (Windows) to run the script before the first reboot while still in the KBE. Date and time the task was made. Date and time that the last change was made to the task. Indicates the number of times that the task has been modified. Each saved change adds an increment of one, where one is the first saved version. Series of commands executed by the command line interpreter; the available commands depend on the runtime environment. Note: Use the call command to run another batch script.

Created Modified Version

Batch Script

Notes Scripted Installations

Information about the task that appears on the page only. Displays the names of the Scripted Installations to which the task is assigned. Note: You can only delete unassigned tasks.

System Images

Displays the names of the System Images to which this task is assigned. Note: You can only delete unassigned tasks.

Postinstallation Task Detail


Navigation title: Add New Shell Script Displays detailed information for a Shell Script postinstallation task (Mac OS X only). From this page you create, modify, delete, and duplicate the task. Contains a bash shell script that the appliance runs in the K2000 Boot Environment after installing the operating system or from the Mac OS after the first reboot.
Name Type Runtime Environment Identifies the task. Read only, Shell Script. Choose the environment that the appliance runs the script. K2000 Boot Environment (Mac OS X) runs the script after the OS installation and before the first reboot. Mac OS X runs the script after the first reboot from the target OS. Date and time the task was first created. Date and time that the last change was made to the task. Indicates the number of times that the task has been modified. Each saved change adds an increment of one, where one is the first saved version.

Created Modified Version

K2000 Deployment Appliance v3.3, Administrator's Guide

127

Shell Script

Series of commands executed by the command line interpreter; the available commands depend on the runtime environment. Information about the task that appears on this page only. Displays the names of the Scripted Installations to which the task is assigned. Note: You can only delete unassigned tasks.

Notes Scripted Installations

System Images

Displays the names of the System Images to which this task is assigned. Note: You can only delete unassigned tasks.

Postinstallation Task Detail


Navigation title: Add New K1000 Agent Installer Displays detailed information for a K1000 Agent Postinstallation Task. From this page you create, modify, delete, and duplicate the task. Provides a K1000 Agent installer that the appliance runs from the operating system after the first reboot. Note: Requires .Net 1.1 or 2.0 Framework. Dell KACE recommends setting up a .Net (application) Postinstallation Task and assigning it to run before the agent installer task.
Name Type Runtime Environment Created Modified Version Identifies the task. Read only, K1000 Agent. Choose the operating system. Date and time the task was first created. Date and time that the last change was made to the task. Indicates the number of times that the task has been modified. Each saved change adds an increment of one, where one is the first saved version. Browse to and select the K1000 Agent installation file; you can download the agent from the Support Portal or from the K1000 appliance. Enter the installation command-line parameters. Information about the task that appears on this page only. Displays the names of the Scripted Installations to which the task is assigned. Note: You can only delete unassigned tasks.

Upload File

Command Line Notes Scripted Installations

System Images

Displays the names of the System Images to which this task is assigned.

128

K2000 Deployment Appliance v3.3, Administrator's Guide

Note: You can only delete unassigned tasks.

About the installer The KACE K1000 Appliance agent is available in two configurations: K1000 Appliance agent with .NET Framework: Installs both the agent and the .NET Framework. K1000 Appliance agent without .NET Framework: Installs the agent only, for use on nodes that already have .NET Framework installed.

Postinstallation Task Detail


Navigation title: Add New Naming Rule Displays the Postinstallation Task details of Naming Rule task you can assign to a Scripted Installation or System Image deployment. From this page you can create, duplicate, modify, and delete the task. Renames the target PC after the first reboot using a Workstation Name Changer compatible text file. For detailed information, see the WSName.exe web site. The appliance renames the computer using the command-line parameters that you specify in this task.
Name Type Runtime Environment File Created Modified Version Identifies the task. Read only, BAT Script. Read only, Windows. The naming database that contains the targets name. Date and time the task was made. Date and time that the last change was made to the task. Indicates the number of times that the task has been modified. Each saved change adds an increment of one, where one is the first saved version. Enter the wsname.exe command line parameters, such as

Command line

wsname.exe /RDF: namedb.dat /DFK:$MAC


where namedb.dat is the name of the text file that you uploaded and $MAC is a K2000 variable that the appliance replaces with the targets actual MAC address during look up.

Note: Use the call command to run another batch script.

Notes Scripted Installations

Information about the task that appears on the page only. Displays the names of the Scripted Installations to which the task is assigned. Note: You can only delete unassigned tasks.

System Images

Displays the names of the System Images to which this task is assigned.

K2000 Deployment Appliance v3.3, Administrator's Guide

129

Note: You can only delete unassigned tasks.

Postinstallation Task Detail


Navigation title: Add Custom HAL Replacement Displays the Postinstallation Task details of a HAL (Hardware Abstraction Layer) Replacement task you can assign to a System Image deployment. From this page you can create, duplicate, modify, and delete the task. Replaces the targets HAL with the hal.dll, ntkrnlpa.exe, and ntoskrnl.exe files you uploaded. The process runs after the image deployment, while still in the KBE, and before the first boot. Custom HAL Replacement is supported for 32-bit versions (x86) of Windows 2000, Windows XP, and Windows 2003 operating systems only. Thoroughly test the HAL replacement before deployment; a faulty HAL may prevent the computer from rebooting. Note: Do not use the K2000 Custom HAL Replacement with image deployment to 64-bit systems or other unsupported operating systems.
Name Type Runtime Environment Created Modified Version Identifies the Preinstallation Task on the appliance. Read only Custom HAL Replacement, the type of task. Read only, K2000 Boot Environment (Windows). Date and time the task was first created. Date and time that the last change was made to the task. Indicates the number of times that the task has been modified. Each saved change adds an increment of one, where one is the first saved version. Displays the name of an attached file or application. Zip files are uncompressed on the appliance before being downloaded onto the target computer. Size of the file. Displays the name of an attached file or application. Zip files are uncompressed on the appliance before being downloaded onto the target computer. Size of the file. Displays the name of an attached file or application. Zip files are uncompressed on the appliance before being downloaded onto the target computer. Size of the file. Information about the task that appears on this page only. Displays the names of the Scripted Installations to which the task is assigned. Note: You can only delete unassigned tasks.

Custom HAL DLL

HAL.DLL Size NTKRNLPA.EXE

NTKRNLPA.EXE Size NTOSKRNL.EXE

NTOSKRNL.EXE Size Notes Scripted Installations

130

K2000 Deployment Appliance v3.3, Administrator's Guide

System Images

Displays the names of the System Images to which this task is assigned. Note: You can only delete unassigned tasks.

Postinstallation Task Detail


Navigation title: Add New Service Pack Displays the Postinstallation Task details of Service Pack task, you can assign it to a Scripted Installation or System Image deployment. From this page, you can create, duplicate, modify, and delete the task. Installs the service pack that you selected or uploaded after the first reboot using the command-line parameters you specify.
Name Type Runtime Environment Created Modified Version Identifies the task. Read only, Service Pack. Read only, Windows. Date and time the task was made. Date and time that the last change was made to the task. Indicates the number of times that the task has been modified. Each saved change adds an increment of one, where one is the first saved version. Click the name of the service pack that you want to install. The service packs shown are automatically downloaded. URL to the service pack you selected. Browse to the service pack that you want to use for this task and then select it. Enter the command that the appliance uses to install the service pack. You must include the service pack filename, whether you selected one to automatically download or manually uploaded. Information about the task that appears on the page only. Displays the names of the Scripted Installations to which the task is assigned. Note: You can only delete unassigned tasks.

Select Service Pack

Download Service Pack Automatically Upload Service Pack Manually Command line

Notes Scripted Installations

System Images

Displays the names of the System Images to which this task is assigned. Note: You can only delete unassigned tasks.

User States
Displays user states captured by a scan of a target.

K2000 Deployment Appliance v3.3, Administrator's Guide

131

Scanning requires the Microsoft Windows User State Migration Tool software included in the Windows AIK (Automated Installation Kit). Upload USMT before performing a scan. K2000 captures user states by running the Scan State utility on the target. You can run the scan with the default settings or customize the capture using a USMT Scan Template. Migration saves the user state on the appliance and allows you to put it on any number of targets during a Scripted Installation or System Image deployment. This preserves the users files, profile, and preferences while you change, fix, or replace their computer or operating system. Users are then able to access their files and settings are just as they remember. Online user states can also be exported, that is backed up or shared with another appliance using the Package Manager. Choose Action Manage User States captures using the following options:
Scan New User State Scans a target for user states and select which users to capture for online migration. From this page, you identify the target of the scan. Installs the Windows User State Migration Tool (USMT) version 3.0.1 and/or 4.0 on the appliance. This software is required to capture user states for online and offline user migrations. Removes the user states that you selected from the appliance. Note: You can only remove unassigned items.

Upload USMT Software

Delete Selected

Apply Label

Applies a label to the selected user states. The available labels display under the option and allow you to filter the user state list. Unlabels the selected user states.

Remove Label

Scan New User State


Navigation title: Scan New User State Scans a target for user states and select which users to capture for online migration. From this page, you identify the target of the scan. Scanning requires USMT, an administrator account, and that the target is powered on and connected to the network. The target must have the following settings: All Windows systems using a firewall: File and Print Sharing is enabled. This setting is on the Exceptions list of the Firewall Configuration. Windows XP systems: Simple File Sharing is off. Windows 2000 SP4 systems: The Windows installer version (C:\WINDOWS\system32\msi.dll) is 3.0.1 or later. Windows 7 and Windows Server 2008: The Network Security LAN Manager Authentication Level is set to Send LM and NTLM responses.

132

K2000 Deployment Appliance v3.3, Administrator's Guide

Host Name/IP

Enter the fully qualified hostname or IP address for the target system or enter a range of computers using a Comma, semicolon, and newline separated list. Optional, unless the authenticating user is a domain user. Note: When blank, the username syntax on the target is hostname\username.

Domain

User Name

Enter a user that has administrator privileges on the target system. Note: This account must have already logged on to the target at least once.

Password USMT Version to be used

Password of the user. Select the User State Migration Tool version compatible with the operating system you are scanning. (Only available when using USMT v4.0 or higher) Select the name of USMT Scan Template that you want to use for the capture. A template determines which items to capture.

USMT Template

Select Profiles
Displays the user states that the scan found on the target. To capture the user states, select the users and click Next.

Upload User State Migration Tool


Navigation title: Upload USMT Software Displays options for uploading the User State Migration Tool. From this page you can open the Media Manager page where you can download the a utility to a node that has Windows Automated Installation Kit (AIK) and upload the USMT v4.0, download the USMT v3.0.1 software directly from Microsoft, manually upload the v3.0.1 installers, or manually upload a Zip file that contains the USMT v4.0. Installs the Windows User State Migration Tool (USMT) version 3.0.1 and/or 4.0 on the appliance. This software is required to capture user states for online and offline user migrations. Download Microsoft User State Migration Tool 3.0.1 installer automatically Downloads the USMT v3.0.1 for x86 and x64 directly from the Microsoft website and installs both on the appliance.
Download Status Last Update Indicates the tool has been downloaded. Shows the date that the USMT was last downloaded.

Upload Microsoft User State Migration Tool 3.0.1 installer manually Provides links for you to download the USMT v3.0.1 installers from Microsoft and then manually upload and install on the appliance.

K2000 Deployment Appliance v3.3, Administrator's Guide

133

Download URL for x86 version Download URL for x64 version USMT MSI (x86) USMT MSI (x64) Last Update

Links to the USMT on the Microsoft website.

Links to the USMT on the Microsoft website.

Browse to and then select the USMT installer file that you want to upload. Browse to and then select the USMT installer file that you want to upload. Indicates the last time that the installer was uploaded using this method.

Upload ZIP archive of Microsoft User State Migration Tool 4.0 After archiving (zipping) the User State Migration Tools included in the Windows Automated Installation Kit, this option allows you to upload the package.
Download URL for WAIK ZIP archive of USMT Last Update Links to the WAIK on the Microsoft website that includes USMT v4.0. Browse to and then select the USMT that you archived in the WAIK. Indicates the last time that an archive of the USMT v4.0 was uploaded.

USMT Scan Template


Controls the behavior of the Scan State tool when performing online and offline user state migrations from the appliance. Allows you to exclude user profiles, Windows and Document components, file types, and specific files. Choose Action Manage USMT Templates using the following options:
Add New Scan Template Defines which user states, Windows Components, and files or file formats to exclude from scans. For use with USMT v4.0 only. Removes the selected USMT Templates. You can only remove items that are not assigned to User State scans. Applies the label to the selected USMT Template. Removes the label from the selected USMT Template.

Delete Selected

Add Label Remove Label

USMT Scan Template Details


Navigation title: Add New Scan Template Displays the details of a scan template. From this page you can configure a new template and modify or delete an existing one.

134

K2000 Deployment Appliance v3.3, Administrator's Guide

Defines which user states, Windows Components, and files or file formats to exclude from scans. For use with USMT v4.0 only.
Name Created Modified Notes Identifies the template on the appliance. Date and time that the template was first created. Date and time that the last change saved. Describes the template, only appears on this page.

User selection options Controls the user included in the scan. To limit the user states, click Scan all available user states and specify which users to exclude by entering them into the user list field.
Scan all available user states Specify users to be excluded Gets all user states on the system except the ones you exclude (optional). Displays the Comma separated user list field where you enter the UIDs of the users that you do not want to scan.

Command line options Provides a list of options that describe the corresponding scanstate.exe switches the appliance uses to run the scan. For details on switches, see http://technet.microsoft.com/en-us/library/cc749015(WS.10).aspx.
Optimize ScanState when the destination computer is running Windows Vista Save only files that are stored on the local computer Runs the scan with the /targetvista switch. Optimizes the configuration file and cli for Microsoft Windows Vista operating systems.

Runs the scan with the /localonly switch. Excludes data from external and mapped network drives. When not selected, copies files stored locally as well as those stored on all other connected drives.

Enables volume shadow copy when Runs the scan with the /vsc switch. Captures files that are locked for editing by other a file is in use applications. Ignore non-fatal errors when scanning user state Runs the scan with the /c switch. Continues the scan, even when non-fatal errors occur such as a file cannot be migrated. When this option is not selected, the scan fails on the first error.

Specify the number of times to retry Runs the scan with the /r:n switch, where n is the number of retries. Determines how when an error occurs many times the network file saving process tries to save the user state data. The default is 3. Note: Increase the number of times in high latency networks.

Specify the time to wait, in seconds, Runs the scan with the /w:n switch, where n is the seconds to wait before a retry. before retrying a failed attempt Determines how long the network file saving process waits before trying to save the user state data again. The default setting is 1. Control Encrypting File System (EFS) Runs the scan with the /efs:option switch.

K2000 Deployment Appliance v3.3, Administrator's Guide

135

Note: If you choose to migrate encrypted files, you must also migrate the Certificate using a utility, such as Cipher.exe. Migrate the certificate using an application Preinstallation Task and Postinstallation Task.

Content configuration options Controls which data is captured and migrated using a customized configuration file. Use this feature to exclude Windows and Document components only. Generate the configuration file on a workstation that has the same files and folders, applications, and component setup as the scan targets. The ScanState command-line syntax to create a configuration file you can modify is: scanstate /genconfig:filename /I:MigApp.xml /I:MigUser.xml where filename is the name of the configuration file. Specifying a manifest ensures that the settings you want to modify are included in the configuration file. For items missing from the configuration file, the default settings are used. Note: Only excluding items from the WindowsComponents and Documents is supported. Modifying the default settings from other manifests, such as MigUser.xml and MigApp.xml, is not supported.
Exclude Files In the input field, enter a comma separated list of file types, or in the drop-down, select the types of files that you do not want to migrate. To select multiple files, use CTL + click. Browse to, and then select the configuration file that was created using the USMT v4.0 ScanState Tool.

Specify config file

When Specify config file is cleared, the Documents to be scanned (config file component) and Windows Components to be scanned (config file component) display. The appliance captures the items that you selected in those sections. Documents to be scanned (config file component) Captures the selected documents and files in the corresponding Windows folder. Windows Components to be scanned (config file component) Captures the selected items.

Deployments
Manages the Scripted Installations, System Images, and Boot Environments that you assign to Systems as a Boot Action and allows you to manage the Deployment and Library components on Remote Site Appliances (RSAs).

Scripted Installations
Displays a list of the Scripted Installations. From this page, you can create new Scripted Installations, modify, label, or delete existing ones.

136

K2000 Deployment Appliance v3.3, Administrator's Guide

Use Scripted Installations to remotely perform a clean installation of Windows operating systems on a networked computer. Scripted Installations can prepare the computer for a new operating system: install the operating system and drivers; and complete the setup by installing applications, migrating user states, and so on. Choose Action Manage scripted installations using the following options:
Add New Scripted Installation Delete Selected Opens a wizard that guides you through the steps of configuring a Scripted Installation. Removes the Scripted Installations from the appliance. Note: When you remove an assigned Scripted Installation, the corresponding Boot Action is also removed.

Apply Label Remove Label

Adds the label to the selected items. Removes the label from the selected items.

Create a Scripted Installation


Navigation title: Add New Scripted Installation Displays the first screen of the Scripted Installation wizard. From this page, you can set the name and select the source media.
Name Source Media Identifies the Scripted Installation on the appliance and deployment client. Select the name of the source media to install.

Create a Scripted Installation (Windows)


Displays the options for creating a new Windows operating system installation.
Walk me through creating an answer file for unattended setup Creates a configuration file using the Unattended Installation Wizard.

Upload an existing answer file for unattended Uploads a configuration file for unattended installation. setup No answer file; This will be a server-based attended setup Creates a basic configuration file that requires user input to complete the installation.

Create Scripted Installation This section shows the tasks you can use to prepare the computer for the OS and customize the computer after the OS is installed. Manage the tasks by dragging and dropping between the following columns: Run (the left side): Shows assigned tasks. Tasks are executed in the order listed. Available (the right side): Shows unassigned tasks that are available for the platform (Windows or Mac).

K2000 Deployment Appliance v3.3, Administrator's Guide

137

Create a Scripted Installation Navigation title:Walk me through creating an answer file for unattended setup Displays the configuration options for an unattended installation. The appliance generates the unattended installation configuration file. Leaving fields blank on this page will require users to make selections during installation. Note: Once you save the Scripted Installation you can only modify the unattended installation settings directly in XML format. Registration Data These settings vary depending on the operating system, that is Source Media.
Name Organization Product Key Identifies the user to which the license is assigned. Identifies the company or organization. Enter the product activation key. Note: For Volume licenses, enter the MAK (Multiple Activation Key) or KMS (Key Mgt System) setup key.

Use KMS Client Setup Key

Windows 7 and Windows Server 2008 only. Click the type of OS you want to install, this automatically inserts a KMS key in the product key field. Windows 7 and Windows Server 2008 only. Automatically detects the installation image using the product key.

Install Image

General Settings Sets the regional and locale of the computer as well as the screen options.
Time Zone Regional and Language Option Screen colors Select the computers time zone. Select the computers default operating system language. Select the computers screen colors. The recommended setting is Windows default, unless you know that all the target computers require the same setting. Select the computers screen area. The recommended setting is Windows default, unless you know that all the target computers require the same setting. Select the computers screen refresh rate. The recommended setting is Windows default, unless you know that all the target computers require the same setting.

Screen area

Refresh Frequency

Administrator Account Creates the local administrator account during the installation process and sets whether or not the computer automatically logs into the account after it reboots. Postinstallation Tasks, such as renaming the computer

138

K2000 Deployment Appliance v3.3, Administrator's Guide

and installing software, require the script to automatically log back into the computer with an account that has administrative privileges.
Username Enter the user name for the administrator account. This account is created during the installation process. Enter the password for the administrator account. Leave the field blank for no password. Automatically logs the administrator account in to the target computer after booting.

Password Automatically log computer into the Administrator account Disable automatic login after n system boots

Disables the automatic login of the administrator account after the specified number of boots.

Networking Controls initial network related settings. The recommended setup is to leave the computer name field blank (to generate a random name) and join it to a workgroup instead of the domain. This allows you to use this Scripted Installation for more targets. Then use Postinstallation Tasks to rename computer and join it to the domain.
Computer Name Workgroup Domain Create a computer account in the domain Domain Administrator Enter a computer name or leave the field blank to generate a name automatically. Join the computer to a workgroup. Select the check box if the Target Machine is a part of a domain. Select the check box to create a new computer account in the domain. 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 Components Clicking Enable Automatic Updates turns on the Windows automatic update feature during installation. Create a Scripted Installation Select an answer (configuration) file that the appliance uses to install the operating system. Note: To allow Postinstallation Task to run, set OemPreinstall ="yes" in the answer file.

Scripted Installation Details


Displays the settings. From this page you can change the installation configuration, add/remove Pre- and Postinstallation Tasks, delete, and duplicate this Scripted Installation.

K2000 Deployment Appliance v3.3, Administrator's Guide

139

Name Type Source Media Created Modified Version Status Notes Label Setup Configuration

Identifies the Scripted Installation. Method used to create the Scripted Installation. Installation files used to install the operating system. Date and time the Installation Script was created. Date and time of the last change was made to the Scripted Installation. Number of times the Scripted Installation was modified. State of the Scripted Installation. Description that only appears in this page. Shows the labels applied. Displays the installation configuration file used to install the operating system. To modify the file, click Show, and then enter your changes. Sets the behavior if an error occurs when running a Preinstallation Task: Continue on Errors: Ignore failures and continue without prompting. Prompt on Errors: Prompts with an option to abort or continue. Halt on Errors: Aborts if an error occurs.

Preinstallation Task Error Handling

Installation Plan This section shows the tasks you can use to prepare the computer for the OS and customize the computer after the OS is installed. Manage the tasks by dragging and dropping between the following columns: Run (the left side): Shows assigned tasks. Tasks are executed in the order listed. Available (the right side): Shows unassigned tasks that are available for the platform (Windows or Mac). The tasks are grouped by the runtime environments that were selected in the task configuration. You can only move the tasks between the corresponding area.
Preinstallation Tasks Postinstallation Tasks Postinstallation Tasks Green Green Blue Runs in the K2000 Boot Environment (KBE) before the image is deployed. Runs in the KBE after the image is deployed, but before the first reboot. Runs from the operating system, such as Windows, after the first reboot using the logon specified in the Boot Action.

System Images
Displays system images uploaded to the appliance for deployment and recovery. From this page, you can open the image for editing, label, and remove images.

140

K2000 Deployment Appliance v3.3, Administrator's Guide

Note: Uploading Mac OS X System Images requires K2000 Image Utility. To download this utility, go to Library > Overview > Download Media Manager and then click the Download for Mac OS X link. After adding an image, you can set up Pre- and Postinstallation Tasks, change (replace, add, and remove) files on the image, set up offline and online user migration, by editing the image details. Choose Action Manage system images using the following options:
Delete Selected Removes the selected items from the appliance. Note: Removing a System Image assigned to a Boot Action, also removes the Boot Action.

Apply Label Remove Label

Adds the label to the selected items. Removes the label from the selected items.

System Image Details


Displays the image settings. From this page, you can change the files in the image, add/remove Pre- and Postinstallation Tasks, delete, and copy the image.
Image Name Image Type Browse Files Identifies the image. K2000 image type. Displays the image files and allows you to modify the image. You can add, remove, rearrange, and replace files, plus remove, and rename the drives. Footprint of the total image size, not the actual physical disk space of storing the image on the appliance. Number of times that the image has been modified since it was uploaded. Shows the current state of the image. Large images take some time to upload, duplicate, or rebuild. Date and time that the System Image was first created. Date and time that the last change was made to the System Image. Opens the Boot Action Setup page where you can assign the Deployment to a target computer. Opens the USB Flash Driver Installer page, and starts building it. Follow the instructions on this page to download and use the USB Image. Download the image log to review deployment history.

Total Size

Version Image Status

Created Modified Deploy this System Image to a System Create bootable USB flash drive image for this System Image Download the log for this System Image

K2000 Deployment Appliance v3.3, Administrator's Guide

141

Harvested From

MAC address of the computer, in hexadecimal format, the image was captured on. Click the address to open the system details. Note: Only displays if the image was captured from a managed system.

Harvest Started Harvest Completed Manufacturer Model Notes Labels Preinstallation Task Error Handling

Date and time that the image capture process began. Date and time that the image capture finished. Name of the computer manufacturer the image is from. Model of the computer that the image is from. Description that only appears in this page. Applied labels are highlighted. CTL + click to add/remove labels. Sets the deployment behavior if an error occurs while running a Preinstallation Task: Continue on Errors: Ignore failures and continue without prompting. Prompt on Errors: Prompts with an option to abort or continue. Halt on Errors: Aborts if an error occurs.

Deploy Options

Sets the behavior while deploying the system image: Remove local files not in image: (Fastest deployment option.) Detects the deltas between the image and the current state of the target computer, removes files that are not in the image, and replaces modified files. Force Continue on errors: Continues the deployment even if there are errors deploying the system image. Include debug output in log: Creates and uploads debug log to the appliance.

Installation Plan This section shows the tasks you can use to prepare the computer for the image and customize the computer after the image is installed. Manage the tasks by dragging and dropping between the following columns: Run (the left side): Shows assigned tasks. Tasks are executed in the order listed. Available (the right side): Shows unassigned tasks that are available for the platform (Windows or Mac). The tasks are grouped by the runtime environments that were selected in the task configuration. You can only move the tasks between the corresponding areas.
Preinstallation Tasks Postinstallation Tasks Postinstallation Tasks Green Green Blue Runs in the K2000 Boot Environment (KBE) before the image is deployed. Runs in the KBE after the image is deployed, but before the first reboot. Runs from the operating system, such as Windows, after the first reboot using the logon specified in the Boot Action.

142

K2000 Deployment Appliance v3.3, Administrator's Guide

Boot Environments
Displays a list of all K2000 Boot Environments (KBE) and NetBoot Boot Environments. From this page, you can copy KBEs from source, delete existing builds, and apply/remove labels. Boot Environments provide the drivers and other resources that a target computer requires to network boot from the appliance. KBEs are built on a client node or imported using the Package Management feature. Building a Boot Environment with Media Manager creates two independent components, an item you can use for booting on the Boot Environment page and a copy on the Source Media page. Note: The only way to add drivers to a Boot Environment is to build it as new using Media Manager. Media Manager adds all the currently cached drivers of the platform type (x86, x64, or Mac) during the build process on the client node. Choose Action Manage Boot Environments using the following options:
Add New Boot Environment Copies an existing KBE from the selected Source Media. Once the KBE is copied, add notes, download it to an ISO or as a USB flash, and set it as Boot Action from the Boot Environment Details page. No drivers are added when you create a new KBE. Removes the KBE build. You can no longer set it as the default KBE, choose it on the node console for a network boot, or set it as a Boot Action. To completely remove it, you must also delete it from the Source Media page. Note: You cannot remove a default KBE. If the KBE is assigned as a Boot Action, the Boot Action is also deleted.

Delete Selected

Apply Label Remove Label

Adds a label to the selected items. Removes the label from the selected items.

Create a Boot Environment


Navigation title: Add New Boot Environment Copies an existing KBE from the selected Source Media. Once the KBE is copied, add notes, download it to an ISO or as a USB flash, and set it as Boot Action from the Boot Environment Details page. No drivers are added when you create a new KBE. Note: You must use Media Manager for Windows or for Mac, to rebuild the boot file with drivers in the cache.
Name Source Media

Enter a unique name for the KBE. Select the KBE you want to build.

K2000 Deployment Appliance v3.3, Administrator's Guide

143

Boot Environment Details


Displays the boot environment settings. From this page, you can see which drivers the boot environment includes, modify settings, make a copy, or delete the Boot Environment.
Name Type Source Media Created Modified Version Status Identifies the Boot Environment. Type of KBE (Windows or Mac). Name and type of the Source Media that was used to create the Boot Environment. Date and time the Boot Environment was first created. Date and time the Boot Environment was last changed. Number of times the Boot Environment was modified. State of the Boot Environment. Indicates whether processes, such as copying, uploading, and building, are in progress. Description that only appears on this page. Applied labels are highlighted. To apply or remove labels, use CTL+click. Open the Boot Action Setup with this KBE selected as the First Boot Action. Saves the Boot Environment in an ISO file.

Notes Labels Set up a System to load this Boot Environment Download bootable ISO for this Boot Environment View third party driver report for this Boot Environment View complete driver report for this Boot Environment Create bootable USB flash drive image for this Boot Environment

Saves a list of the third party drivers included in the KBE in a text file.

Saves a list of all the drivers included in the KBE in a text file.

Downloads a copy of the boot environment that you can save directly onto USB flash drive.

Remote Site Appliances


Navigation title: Remote Sites Displays a list of the Remote Site Appliances (RSAs) linked to the K2000 appliance. From this page, you can add linked RSAs to manage, distribute Library and Deployment components, and remove (but not unlink) RSAs. Choose Action Manage RSAs using the following options:

144

K2000 Deployment Appliance v3.3, Administrator's Guide

Add New Remote Site Appliance Download Remote Site Appliance OVF Refresh Version Sync Selected Delete Selected

Displays a list of linked RSAs. From the Remote Site Appliance list, you choose an appliance that has nodes you want to manage from this appliance, and then click Next. Provides a link to the zip file that contains the RSA Virtual Appliance OVF that you can import in to a virtual machine. Download the RSA OVF image to the host computer at the remote site. Select an RSA and click to verify the software version. Select RSAs and click to push the components selected for synchronization to the remote site. Removes the RSA from the inventory. Note: An RSA can only connect to one K2000 appliance; to allow the RSA to connect to another K2000 appliance you must also delete it from Settings & Maintenance

Add a Remote Site Appliance


Displays a list of linked RSAs. From the Remote Site Appliance list, you choose an appliance that has nodes you want to manage from this appliance, and then click Next. The RSA is added to this appliance and displays in the Remote Site list.

Remote Site Details


Displays the settings of a RSA that extends the K2000 appliance.
Host Name Created Modified Last Sync Status Progress DNS host name of the Remote Site Appliance. Date and time the RSA was linked. Date and time of the last RSA configuration change or software upgrade. Date and time the components were replicated. Synchronization state. Shows the amount of data to be replicated to the RSA if a synchronization is in progress. Otherwise shows the amount of data and length of time the last replication took. Shows the size of all the components selected. However when you synchronize only components that changed are replicated, that is if the component versions are the same no data is replicated. Check the version of the RSA and/or apply an available upgrade. Applying an upgrade may reboot the RSA. Limits the amount of bandwidth the replication can use, where 0 indicates unlimited. Sets the synchronization method (manual or scheduled).

Selected for Sync

Upgrade Remote Site

Transfer Rate Limit Update Scheduling

K2000 Deployment Appliance v3.3, Administrator's Guide

145

Scripted Installations

Enable synchronization of Scripted Installations you want to deploy in the remote location. Enabling a component also enables the corresponding items under Dependencies. Enable synchronization of the System Images you want to deploy in the remote location. Enabling a component also enables the corresponding items under Dependencies. Enable synchronization of the Boot Environments you want to use for network booting in the remote location. Always replicate the default Boot Environments set on the General Settings page. Enable synchronization of the user states you want to deploy to targets at the remote site. Click Show/Hide toggle the list of the items required by the selected Scripted Installations, System Images, Boot Environments and User States that are selected for replication.

System Images

Boot Environments

User States Dependencies

Download Remote Site Appliance OVF Image


Provides a link to the zip file that contains the RSA Virtual Appliance OVF that you can import in to a virtual machine. Download the RSA OVF image to the host computer at the remote site.

Systems
Manage licenced sets (System Inventory) and locate computers on your network, and set the Boot Actions of those computers for Deployment configurations.

System Inventory
Displays a list of computers that booted into the K2000 Boot Environment (KBE). Each computers represents a used seat. The appliance identifies the systems by their MAC address and updates the detailed information, such as IP address, each time the node boots from the KBE. Note: Systems that boot into KBE appear in both the System Inventory and Network Inventory lists.

Choose Action Manage systems using the following options:


Set Boot Actions Send Wake-on-LAN Delete Selected Opens the Set Boot Action where you can specify the next network boot action for the selected computers. Wakes the computer if it is connected to the network. Removes the computer from the inventory, which frees a licensed seat. Note: Removing the computer from System Inventory, removes the corresponding Network Inventory and Boot Action items.

146

K2000 Deployment Appliance v3.3, Administrator's Guide

Apply Label Remove Label

Adds the label to the selected items. Removes the label from the selected items (but not the appliance).

System Details
Displays detailed information about a system that booted into a Boot Environment on the K2000. From this page you can modify system settings, run a driver compatibility report, and set the systems next network boot action.
IP Address MAC Address Platform Host Name Created Modified Set Boot Actions for this System Current IP address of the system. MAC address of the system in hexadecimal format: xx:xx:xx:xx:xx:xx. Type of platform of the system, such as Mac OS X or Windows. Enter the host name of the node. Click Save to update this value in the DNS Lookup field. Date and time that the record was created. Data and time of the last change to the record. Opens the Set Boot Action page where you can set the actions for the next network boot of this system. Results of appliance pinging this system, such as Succeeded or Failed. Indicates whether this system, identified by the MAC Address, has ever requested a network boot from the appliance. State of TCP ports scanned by the last Network Scan that included this computer. Note: On most networks, the Network scans can only detect port status when the computer is on the same subnet as the appliance.

Ping Status PXE Status

TCP Port Status

UDP Port Status

State of the UDP ports scanned by the last Network Scan that included this computer. Note: On most networks, the Network scans can only detect port status when the computer is on the same subnet as the appliance.

Set Boot Action

Opens the Boot Action Setup page, where you can specify the next network boot action for the system. Select the name of the driver cache to use for a compatibility report, these drivers are only available to Scripted Installations. Compares the selected driver cache to the computer hardware to determine if the drivers available and are compatible for a Scripted Installation.

Select Operating System

Show Compatibility

K2000 Deployment Appliance v3.3, Administrator's Guide

147

K1000 Inventory
When the K2000 Deployment Appliance is linked to one or more K1000 System Management v5.2 and higher appliances, the K1000 systems are listed. Select systems, and then in Choose Action, click Set Boot Actions to deploy Scripted Installation or System Image to the machine on the next network boot.

Network Inventory
Displays a list of all known systems. The inventory consists of nodes detected using a Network Scan, systems booted into KBE, uploaded from an inventory file, or for which a boot action was added by specifying the MAC address. Note: Running a network scan with the General Settings > Display Empty Scan Results in Inventory enabled, creates an record for every IP address in the range even if no system is assigned to that address. Choose Action Manage systems using the following options:
Set Boot Actions Upload Network Inventory Send Wake-on-LAN Delete Selected Opens the Set Boot Action where you can specify the next network boot action for the selected computers. Opens the Upload Network Inventory where you can import a list of computers from a CSV file. Wakes the computer if it is connected to the network. Removes the computer from the inventory, which frees a licensed seat. Note: Removing the computer from Network Inventory, removes the corresponding System Inventory and Boot Action items.

Apply Label Remove Label

Adds the label to the selected items. Removes the label from the selected items (but not the appliance).

Network Inventory Detail


Displays the system information.
IP Address MAC Address IP address assigned to the system. When a system network boots in KBE, this field is updated. MAC address of the system in hexadecimal format: xx:xx:xx:xx:xx:xx. This field identifies the system on the appliance. Type of platform the system is running on, such as Mac OS X or Windows. Host name of the node. Network Scans can set this field automatically using reverse DNS lookup.

Platform Host Name

148

K2000 Deployment Appliance v3.3, Administrator's Guide

Created Modified Last Boot Ping Status PXE Status

Date and time that this record was created. Date and time of the last change to the record. Date and time of the last system boot. Results of appliance ping to the system, such as Succeeded or Failed. Indicates whether this system, identified by the MAC Address, has ever requested a network boot from the appliance. State of TCP ports scanned by the last Network Scan that included this computer. Note: On most networks, the Network scans can only detect port status when the computer is on the same subnet as the appliance.

TCP Port Status

UDP Port Status

State of the UDP ports scanned by the last Network Scan that included this computer. Note: On most networks, the Network scans can only detect port status when the computer is on the same subnet as the appliance.

Set Boot Action for this system

Opens the Boot Action Setup page where you can specify the next network boot action for the system. Information about the system that only appears on this page.

Notes

Upload Network Inventory


Navigation title: Upload Network Inventory Select the comma separated file that contains inventory you want to upload to the appliance. The appliance identifies computers by their MAC address. Once systems are in inventory you can send a Wake-on-LAN command and set their boot actions. Inventory File Click Browse and select the file that contains a comma separated list, in the order of IP address, MAC address, host name .

Network Scans
Displays configured network scans, which you can run to detect systems on the network. Note: Only use this feature in environments to scan for computers that are on the same subnet as the appliance. Network Scans overwrite existing records on the System Inventory and Network Inventory pages with the data collected by the scan. Detailed information, such as MAC address and port status, can only be gathered

K2000 Deployment Appliance v3.3, Administrator's Guide

149

from systems on the same subnet as the appliance. When the MAC address is removed by a Network Scan, the record is removed from the System Inventory page and any corresponding Boot Actions are also deleted. Note: Enabling the General Settings > Display Empty Scan Results in Inventory creates an item in the Network Inventory for each address in the range. Choose Action Manage network scans using the following options:
Add New Network Scan Run Scan Delete Selected Opens the Network Scan page where you can configure a new scan. Scans the configured IP range and creates a Network Inventory item for each address in the range. Removes configuration for the network scan. Removing the computer from Network Inventory also removes it from System Inventory.

Network Scan Details


Navigation title: Add New Network Scan Displays the form where you configure the a Network Scan to detect systems in the specified IP range. Some details, such as MAC address port status, can only be detected if the node is on the same subnet as the appliance. Note: Running a network scan with the General Settings > Display Empty Scan Results in Inventory enabled, creates an item for each IP address in the range even if no computer is assigned to that address. Complete the form to configure a network scan:
Name Notes IP Range Enable Ping Test Ping Timeout Enable Port Test Port Timeout Identifies the network scan. Information that appears only on this page. Enter the beginning range to the end range, such as 10.100.0.1 to 10.100.100.20. Run ping from the appliance to each address in the range. Sets the ping timeout period in seconds. Gets the port status. Sets the port status timeout period in seconds. Note: Generally, port tests only work on the same subnet as the appliance.

TCP Port Configuration

Enter a comma separated list of ports. For example, the appliance requires 135 and 80 to install software or deploy images to Windows systems.

150

K2000 Deployment Appliance v3.3, Administrator's Guide

UDP Port Configuration

Enter a comma separated list of ports. For example, the appliance requires port 7 to gather information about the status of an installation or deployment. Use reverse lookup to determine the host name of the computer. Enter the interval in seconds. If a secondary DNS is configured, the reverse look up is then performed on that server. Runs the network scan automatically at the set interval.

Enable DNS Lookup DNS Lookup Timeout

Enable Scheduled Run

Boot Actions
Displays a list of systems to which Boot Actions have been assigned. From this page you can send a Wake-on-LAN command, delete boot actions, and open the Boot Action Setup page. Boot Actions configure the behavior of a computer that boots into KBE. Use Boot Actions to assign install operating systems (Scripted Installation) and deploy captured images (System Images) to managed computers (System Inventory), scanned or imported computers (Network Inventory), or to any other computer with a known MAC address. Choose Action Manage Boot Actions using the following options:
Add Boot Actions Opens the Set Boot Action where you can select Boot Actions for any computer in Inventory or enter a MAC address of a none-inventory computer. Opens the Set Boot Action where you can change the Boot Actions for the selected computers. Wakes the computer if it is connected to the network. Removes the Boot Action. Note: Removing the computer from System Inventory, automatically removes the corresponding Network Inventory and Boot Action items.

Set Boot Actions Send Wake-on-LAN Delete Selected

Boot Action Setup


Navigation title: Add Boot Action Set Boot Action Displays the Boot Action settings. From this page, you can set up new boot actions or change existing ones. Controls the actions that the selected computer takes the next time the computer network boots into the K2000 Boot Environment. A computer can have only one boot action. When you set up a boot action for a computer that already has one, the appliance overwrites the older boot action. Setting for selected system When viewing the Boot Actions of a system the following fields display:

K2000 Deployment Appliance v3.3, Administrator's Guide

151

Host Name

Optional. Shows the name of the computer. Identifies the computer on the appliance. When this field is blank, the IP address displays in the host name field. Shows the IP address of the computer the last time the computer was scanned or booted from the KBE. MAC address of the selected systems. Note: When viewing or setting the boot actions, only the address of a single computer displays. When adding a new boot action, the MAC addresses of all the selected systems display and you can manually add a new address on a new line by typing the address in hexadecimal format.

IP Address MAC Address

First Boot Action Number of Boots

Select the action you want the computer to take the next time it network boots from KBE. Enter the number of times that you want the computer to repeat the First Action before taking the Next Boot Action. Where zero is infinite. Select the action you want the computer to take after it has repeated the First Boot Action the number of times you specified. Enter the number of times that you want the computer to repeat the Next Boot Action.

Next Boot Action

Number of Boots

Adding new (without select systems) When creating a new boot action (Add Boot Action) or setting up the boot action (Set Boot Action), the option to select systems displays:
Systems Displays a list of systems that booted into KBE or were detected using a network scan. Note: Creates a separate items for each computer you select.

MAC Address

MAC address of the selected systems. Note: When viewing or setting the boot actions, only the address of a single computer displays. When adding a new boot action, the MAC addresses of all the selected systems display and you can manually add a new address on a new line by typing the address in hexadecimal format.

First Boot Action Number of Boots

Select the action you want the computer to take the next time it network boots from KBE. Enter the number of times that you want the computer to repeat the First Action before taking the Next Boot Action. Where zero is infinite. Select the action you want the computer to take after it has repeated the First Boot Action the number of times you specified. Enter the number of times that you want the computer to repeat the Next Boot Action.

Next Boot Action

Number of Boots

152

K2000 Deployment Appliance v3.3, Administrator's Guide

Boot Action Setup


Displays settings for migrating user states. This page only appears if migration Pre- and/or Postinstallation Tasks were assigned to the deployment that you selected as the First or Next boot options. Scan User States Offline These options display for offline migrations, that is deployments that have the Scan User States Offline Preinstallation Task. Offline migration captures all the user states (not excluded from the template) with USMT v4.0 and uploads them to the appliance. If a user on the target matches one of the existing User State records, the process overwrites the existing record. Note: When migrating users from Vista computers, only use templates that are optimized for Vista.
USMT Scan Template

Select the name of the template that you want to use to run the Scan State Utility before the operating system is installed or deployed. Note: If you leave this field blank or no templates exist, the scan runs with the default settings and all the user states on the target are captured.

Deploy all the user states scanned as part of Must be enabled to migrate users from the previous version of the target; otherwise, user the offline scan states are captured but not deployed.

Deploy User States Note: These options display when the Deploy User State Postinstallation Task is assigned to the deployment. You can migrate online user states, even when you are also performing an offline scan. For online migrations, that is, to deploy a user state captured from the appliance, select the users that you want to install on the systems:
User states scanned with User State List Select the USMT version to filter the user list. Displays a list of user states available on the appliance. Click the check box, to deploy the user state.

Reports
View K2000 Deployment and System Performance reports.

Reports
Displays a list of Reports created by Dell KACE that you can display in HTML or save to a comma separated value (CSV) file.

K2000 Deployment Appliance v3.3, Administrator's Guide

153

To create your own reports using a third-party tool, enable Allow Offboard Database Access on the Security page.

System Performance
This page contains graphs for statistical data, such as activity, CPU usage, and network traffic.

Settings & Maintenance


Manage and administer the appliance. Configure network settings, manage users, link appliances, view logs, back and restore data.

Control Panel
Displays appliance configuration menus.

General Settings
The General Settings page controls the K2000 Boot Environment (KBE) default bootstrap, Boot Manager, boot loader, and remote access settings. Modified (Read only) Displays the date and time when the settings on this page were modified. Remote and Local Actions (Windows with IE only) For Action Icon #1 and Action Icon #2, choose the action you use most frequently. This feature only works when browsing to the Administrative Console from a Windows computer using Internet Explorer. And then customize the action as follows:

executable_name KACE_HOST_name | KACE_HOST_IP where K2000_Host_name and K2000_Host_IP are K2000 variables that the appliance replaces with the corresponding node host name or IP address. If you specify a static host name/IP the icon only launches a session with the specified address. Note: Some programs require a protocol, port, or URL, for example Explorer requires leading slashes to indicate a network address \\KACE_HOST_NAME. The executable_name is the full path to the program executable on the browser host including the command-line parameters that the appliance Active X controls runs to open the session. The software must be present on the browser host, and if required the node, to successful launch the session. The Dell KACE K2000 appliance provides the following preprogrammed options for remote access. The table below describes the corresponding requirements:

154

K2000 Deployment Appliance v3.3, Administrator's Guide

Software

Browser Host Requirements crt.exe

Client-side Requirements SSH client

Description

SecureCRT

The appliance launches SecureCRT and connects to node using SSH on port 8443 by default. Most operating systems come with a standard SSH client. DMRC client is automatically installed on the client the first time a connection is opened. You can use any DMRC supported cli options. Displays the nodes shared folders. Note that the full path of the executable is typically required; for example:

Dameware Mini Remote Control

dwrcc.exe

DMRC client

Explorer

explorer.exe

Windows/ SMB share

C:\Windows\explorer.exe.
Microsoft Remote Desktop Ping Putty mstsc.exe Remote Desktop Opens a remote desktop session with the node.

ping.exe putty.exe

None None

If the node is online it responds to the ping. Opens an SSH connection from the browser host to the target node. Opens a session from the browser host to target node. Opens a session from the browser host to the target node. Opens a session from the browser host to the target node. The KBE has the client side software, therefore you can VNC in a browser session to a client that has network booted into KBE to access the targets Boot Manager.

Telnet Tight VNC VNC-Java Remote Control

telnet.exe vncviewer.exe None

None None VNC Java Client

After you associate an action with the icon, you can launch the action using the icon on the System Inventory, Network Inventory, and Boot Actions pages. Display Empty Scan Results in Inventory Click the check box to show all IP addresses scanned, including null entries, on the Network Inventory page. The Network Scan feature scans a range of IP addresses and displays the scan results on the Network Inventory page. By default only nodes connected to the network that respond to the scan are shown. Driver/Restore Share Password Enter a password for accessing the drivers and restore shares using the account, admin; the default is admin. Boot Manager Timeout Enter the timeout interval in seconds. You can extend or shorten the timeout value. When the value is 0, select an option for the boot to continue. The boot manager time-out determines the length of time that the boot menu stays active on the computer. Boot Manager Style Select the type of interface (Graphical Menu | Text Menu | Basic) that the users sees on start up.

K2000 Deployment Appliance v3.3, Administrator's Guide

155

Local Hard Disk Boot Method Select the boot loader method: Chain Boot (default) loads the KBE second stage boot loader and continues to boot from the network. Local Boot exits the KBE first stage boot loader and returns control back to the BIOS to continue the boot from the local hard drive. Note: Only change this setting to Local Boot when recommended by Dell KACE support.

Boot Manager Password Enter the password for Boot Manager. KBE Bring up Network Delay Enter the number of seconds to wait for the DHCP server response after the network drive is mounted before proceeding with the boot process when booting from KBE. Note: On low bandwidth or high latency networks, increase the delay.

VNC Password Enter a password for the VNC server. The default user name and password is admin/admin. The Dell KACE K2000 appliance comes with a built-in VNC server. Default K2000 Deployment and Recovery Environment Select default environments for each platform. The appliance displays the available boot environments. Note: The list is populated after you create and import the KBEs for each type of system.

Date & Time Settings


Displays the system date and time settings. Set the appliance allows you to manually set the time or synchronize with an NTP or NIST server. To modify the settings, scroll down to the bottom, click Edit, change the settings, and then click Save.
Modified Current Time Time Zone Automatically synchronize with Internet time server (Read only.) Displays the date and time the system date and time settings were last modified. Time that of the appliance system clock. Displays time zone of the appliance. Click to configure a time server. In the Time Server field, enter either the host name or IP address of an NTP or NIST server, and then click Save.

156

K2000 Deployment Appliance v3.3, Administrator's Guide

Set the clock on the K2000 manually

Click to display hour, minute, and second and month, day, and year fields. In the fields enter the correct date and time and then click Save. The clock begins tracking time.

Network Settings
The Network Settings control the appliance to network connection, the built-in DHCP addressing and network booting redirection services, and the external SMTP server configuration. The appliance automatically restarts after you save changes. Modified (Read only) Displays the date and time when the settings on this page were modified. Host Name Enter the host name of your Dell KACE K2000 Appliance. Domain Name Enter the domain name of your Dell KACE K2000 Appliance. For example: kace.com IP Address Enter a static IP address. Note: When you modify the IP address, be extremely careful setting the new address. Ensure you use the correct new address, or it will be difficult to locate the appliance on your network without knowing the exact IP address. Network Speed Select the network speed from the drop-down list. Default Gateway Enter the default gateway. Subnet Mask Enter the subnet mask. Secondary IP Address Enter the IP address of the additional NIC card after connecting it to the network. Traffic on this NIC includes RSA synchronization, Offboard Package Transfers, and so forth. Note: Client-Server operations, such as network booting and deployments, occur on the primary NIC.

Secondary Network Speed Select the network speed for the additional NIC card.

K2000 Deployment Appliance v3.3, Administrator's Guide

157

Primary DNS Enter the primary DNS. The appliance uses reverse DNS lookup to determine the hostname of a computer during a Network Scan. Secondary DNS Enter the secondary DNS. If the connection to the primary DNS times out or fails, the appliance attempts to lookup the computers hostname on the secondary DNS. Enable On-Board DHCP Server Click to use the built-in DHCP (Dynamic Host Configuration Protocol Server) to assign network IP addresses and enable network booting redirects from the appliance. Then enter the IP range: DHCP Pool Start: Enter the first IP address in the range. DHCP Pool End: Enter the last IP address in the range. Note: Only use the built-in DHCP server, when your environment does not already have one.

Enable NetBoot Server (for Mac OS X client) Click to use the built-in NetBoot server to redirect Mac clients to the KBE for network booting.
BSDP Server Priority BSDP Image Index Use the default, for example 32768. Use the default setting, for example 52230.

Use Proxy Server Click when the appliance must use a proxy server to access the Internet. Then complete the proxy form: Note: The appliance requires Internet access to connect to www.kace.com to download software updates and check license information.
Proxy Type Proxy Server Proxy Port Proxy (Basic) Auth Click the protocol, HTTP or SOCKS5. Enter the host name or IP address of the proxy server. Enter the port for the proxy server; the default HTTP port is 8080 and SOCKS5 is 1080. Click to enable authentication using a domain account. The appliance does not join the domain and therefore you must enter the following to authenticate on the domain Enter the appliance domain account username. Enter the appliance domain account password.

Proxy Username Proxy Password

Use SMTP Server Click to use an external SMTP server and then enter the SMTP host name or IP address in the form. Note: Configure the external SMTP Server to allow anonymous login for outbound mail transport.

158

K2000 Deployment Appliance v3.3, Administrator's Guide

Language Settings
Displays the current appliance Administrative Console language and regional settings. To modify the settings, at the bottom of the page click Edit, change the settings, and then click Save. Regional Preferences Sets the language and region for the Administrative Console, Media Manager, Driver Utility, Boot Manager, and Recovery Console interfaces.
Option Language Description Select the language the Administrative Console, Media Manager, Driver Harvesting Utility, Boot Manager, and Recovery Console interfaces. Select the region.

Region

KBE Optional Font Support Adds support for double-character sets to the K2000 Boot Environment.

Security
Controls settings that allow external resources to access the appliance. Click to enable/disable the following external access security settings.
Allow SSH Root Login (Kace Support) Enabling Allow SSH Root Login (Kace Support) on the Security page provides remote access to Dell KACE Support personnel. Dell KACE recommends enabling this feature before you begin to use the appliance. SSH remote access is the only method that support personnel can use to diagnose and fix problems if the appliance becomes unresponsive. For example, the recommended free disk space is not available. Enabling Allow Offboard Database Access on the Security page, makes the Dell KACE K2000 Appliance database available to external programs, such as Crystal Reports, for reporting. By default, the appliance does not allow external connections to the database. The Enable SNMP Monitoring setting allows clients to monitor the Dell KACE K2000 Deployment appliance. Once enabled, the appliance SNMP agent authorizes read-only access for all MIBs to any client querying the community string. Dell recommends creating a unique string; Public is the default.

Allow Offboard Database Access

Enable SNMP Monitoring

Users
Displays a list of all users, local and LDAP. When LDAP is enabled, all local users are disabled. Choose Action Manage users using the following option:
Add New User Displays the user information. From this page you can complete the new user form, reset a users password, and modify their information. Removes the users that you selected from the appliance.

Delete Selected

K2000 Deployment Appliance v3.3, Administrator's Guide

159

Apply Label

Applies a label to the selected users. The available labels display under the option and allow you to filter the user list. Unlabels the selected users.

Remove Label

Edit User Details


Navigation title: Add New User Displays the user information. From this page you can complete the new user form, reset a users password, and modify their information. Only change the users details for local users.
User Name The login name. Note: You cannot modify the admin user account login name.

Full Name Email Domain Budget Code Location Password Confirm Password Permissions

First and last name of the user. Email address of the user. Name of the domain the user is in. (Optional) Budget code of the department the user is in. (Optional) Site or location of the user. Enter a password for the user. This field is required to activate the user. Reenter the password. Role of the user on this appliance. Administrators have full read/write access, Read only admins can log in and view settings and run reports, and users cannot access the administrative console.

User Authentication
Server Friendly Name Server Hostname (or IP) Enter a name for the server that identifies it in the list of external LDAP servers. Enter LDAP server IP address or host name. The appliance uses this address to authenticate users. Enter the LDAP Port number, the default is 389. Note: Contact Dell KACE support if you are using LDAPS, default port 636.

LDAP Port Number

160

K2000 Deployment Appliance v3.3, Administrator's Guide

Search Base DN

Specify which area of the LDAP tree the appliance should begin to search for users. For example, specify OU=it,

DC=kace, DC=com to search the IT group.

Note: Searching the entire directory may cause lag time during login. Limiting the search base decreases these delays.

Search Filter

Enter (LDAP_attribute=KBOX_USER) where the LDAP_attribute is the name of the attribute that contains a unique user ID and KBOX_USER is a variable the appliance replaces at runtime with the Login ID the user enters. For example for Active Directory enter(samaccountname=KBOX_USER)and for most other LDAP servers enter (UID=KBOX_USER).

LDAP Login

Enter the bind DN; that is the user account with permission to query the search base. Use either the DN format: CN=username,DC=company, user principal name format username@company.com. Note: If the field is left blank the appliance connects to the LDAP server using an anonymous bind.

DC=com or the

LDAP Password (if required) User Permissions

Enter the LDAP account password. Choose the permissions to assign to a user the first time they successfully log in: Admin: Read/write access. ReadOnly Admin: View all pages, no change access. User: No access.

Test LDAP Password

Change the KBOX_USER variable in the Search Filter to a valid Login ID, for example (samaccountname=jsmith) and enter the corresponding password for the LDAP account and click Test LDAP Settings. Note: Be sure to change the user name in the Search Filter back to the system variable KBOX_USER.

Labels
Creating and applying labels allows you to organize System Images, User States, User State Templates, Scripted Installations, System Images, Boot Environments, and Systems when reviewing the items on the list pages. K2000 provides manual labels, which are unrestricted. You can apply labels to any of the supported components, that is a user state template and a system image can have the same label. Deleted Selected Deletes the label from the appliance and automatically removes it from any components to which it was applied.

Edit Label Details


Create new and modify or delete existing manual labels.
K2000 Deployment Appliance v3.3, Administrator's Guide 161

Label Name Enter the display name of the label. If you modify the name of an existing label, the appliance automatically updates the label for all the components to which it has been applied. Label Type (Read only.) Displays manual label, the only type available on the K2000. Notes Enter information about label. Appears on this page only.

Registration & Licensing


Displays the current registration and licensing information. To change this information scroll to the bottom of the page and click Edit, after modifying the settings click Save to apply your changes. Registration Displays registration details.
Company-Institution Name Organization Name Administrator Email Send Crash Reports to KACE The name of organization to which this product is registered. (Optional) The name of the division or organization. The email address of the appliance administrator to whom daily status emails are sent. Send crash reports to KACE.

Licensing Licensing Summary displays read only information and statical data of your keys. License Key shows the last four digits of the current keys.
Product Version Serial Number Status Expires Activation Status Modules Model number of the appliance. Software version. Appliance serial number. Shows whether the license is valid or invalid. Shows the license key expiration date. Date and time the appliance was first activated. Features activated on the appliance. Currently only the full product is available, Deployment Appliance. Number of client seats licensed for use with this appliance. To unregister clients use the System Inventory page.

Seats

162

K2000 Deployment Appliance v3.3, Administrator's Guide

Used Seats

Number of clients currently registered in System Inventory.

KACE Linking
Displays the key required to link this appliance to another Dell KACE appliance. From this page, you can enable or disable the ability to link this appliance to another, set the display name for this appliance on the remote appliance, and set the timeout interval for sessions connecting to this appliance from a remote site. Linking allows you to switch back and forth between the administration consoles of the appliances using the same log-in session. Use K1000 Computer Inventory details, including MAC address, to assign Boot Actions. And record a history of K2000 deployment and recovery activity of the computer in the K1000 Computer Inventory details. To link appliances, configure the following settings on both appliances: Enable KACE Linking Add a remote appliance configuration with the appliance key

Enable KACE Linking K2000 Friendly Name (this server) Remote Login Expiration Request Timeout

Allows this appliance to be linked to another appliance. Unique name that displays in the system list for single sign-on. Duration of a single sign-on session in minutes. Number of seconds the remote appliance should wait before timing out while this appliance authenticates the login credentials from the remote appliance.

K2000 Deployment Appliance v3.3, Administrator's Guide

163

KACE Linking Key Fingerprint KACE Linking Key (this server)

Read only. Copy and paste this key to Linked Appliances > Edit Linked Appliance Detail page on the remote appliance.

Linked Appliances
Navigation title: Manage Linked Appliances Displays a list of remote appliances with links configured on this appliance. To establish a link, you must configure an appliance link configuration on both appliances (local and remote). The K2000 appliance allows you to link:
Type K2000 RSA K2000 Deployment Appliance Description

To recover and reimage computers at a remote site that have a weak connection to the K2000 appliance. For single-sign on, to allow administrators to access multiple appliances from the a single Administration Console session. Note: Requires the LDAP configuration and permissions or that the same local user accounts (with matching passwords) exists on both appliances.

K1000 System Management Appliance

Imports system information from the K1000 appliance and allows K2000 administrators to assign Boot Actions and perform other related tasks on those systems.

Choose Action Manage linked appliance settings using the following options:
Add New Linked Appliance Displays the settings of a remote appliance linked to this appliance. From this page, you can modify the settings, test the link connection, and delete the configuration. Removes the link. Note: You must also remove the Linked Appliance configuration to this appliance on the remote appliance. Otherwise when a user logs into the remote appliance it attempts to establish a link to this appliance, which may cause delays logging in.

Delete Selected

Edit Linked Appliance Detail


Navigation title: Add Linked Appliance Displays the settings of a remote appliance linked to this appliance. From this page, you can modify the settings, test the link connection, and delete the configuration. Using the key from the remote appliance, you add K1000, K2000, and RSA link configurations. Setting up a link allows you to sign into all the appliances from a single centralized session. Switch between consoles using the drop-down list in the upper right corner.

164

K2000 Deployment Appliance v3.3, Administrator's Guide

Note: When you configure a K1000 link, the Inventory > K1000 Inventory tab appears populated with the Computers from the K1000. You can use the K1000 Inventory information to set Boot Actions.
Created Modified Host Name Port 80 access to this server is disabled by its configuration Model Key Fingerprint Linking Key Status Message

Date and time the item was created. Date and time of the last change. Identifies the remote appliance, must match the DNS name. Only use this setting when directed by Dell KACE support

Model of the remote appliance. Automatically updates after link is established. Remote appliance key. Automatically updates after the link is established, Pasted from the Settings & Maintenance > KACE Linking of the remote appliance. Connection test results.

Appliance Logs
The Dell KACE K2000 appliance provides the following log files.
Type System System Log name System Messages Outgoing Mail Log Description Displays miscellaneous information about the server's operation and execution. Displays information about the informational email messages that the KACE K2000 Appliance has sent. Displays HTTP Server access information. Displays HTTP Server error information. Displays miscellaneous information about KACE K2000 Appliance Server operation and execution. Displays errors or server warnings regarding KACE K2000 Appliance onboard server processes. Displays messages from the process that handles network drivers for Scripted Installations.

Web Server Web Server K2000 Server

Access Log Error Log Output Log

K2000 Server

Error Log

Network Driver Server Network Driver Server File Servers

Output Log

Error Log

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

TFTP Transfer Log Displays TFTP Server access information.

K2000 Deployment Appliance v3.3, Administrator's Guide

165

Type File Servers

Log name NETBIOS Name Server Windows File Server Output Log

Description Displays miscellaneous Windows File Server information.

File Servers

Displays Windows File Server access information.

Task Processor

Displays information about the KACE K2000 Appliance background processes. These processes are listed in the Currently: field in the upper right corner of the user interface. Displays errors or server warnings resulting from KACE K2000 Appliance background processes. These processes are listed in the Currently: field in the upper right corner of the user interface. Displays miscellaneous information about the application's operation and execution.

Task Processor

Error Log

Privileged Action Server Privileged Action Server Scheduled Action Server Scheduled Action Server

Output Log

Error Log

Displays errors or server warnings regarding KACE K2000 Appliance onboard server processes. Displays miscellaneous information about Scheduled Action Server operation and execution.

Output Log

Error Log

Displays errors or server warnings regarding KACE K2000 Appliance onboard server processes. Displays error that occured while capturing and deploying user profiles during deployments.

User State Migration

Failed Error Log

RAID
The appliance automatically checks the RAID disk array status every few minutes and updates this page. The K2000 appliance have RAID database protection on all physical devices, not RSA (Remote Sites Appliances) or K2000 running on a Virtual Machine. Use this page to confirm that the RAID disks are functioning correctly. The K2000 Appliance administrator automatically receives an email message indicating that a disk has failed and instructs you to call Dell KACE Customer Support immediately. Check the RAID status if you experience a sudden unexplained drop in system performance. The appliance uses these RAID levels to protect your data: KACE K2100 Deployment Appliance - RAID level 1. KACE K2200 Deployment Appliance - RAID level 5.

Package Management
Backs up and restores components, such as drivers, system images, scripted installations. You can also share components between K2000 appliances.

Export List
Navigation title: Export K2000 Packages

166

K2000 Deployment Appliance v3.3, Administrator's Guide

The Export feature generates a package (.PKG) file that contains the data you want to backup or share and an index (.XML) file that contains meta data about the package for each of the selected components. The appliance saves the files in the K2000 Restore directory, \\K2000_hostname\Restore. Store and move the files together, each package with its complementary index file. Choose Action Manage components using the following options:
Export Selected Schedule Export for Selected Creates a package for each of the selected components. Opens Schedule Export where you set the interval and time you want to automatically package the selected components.

Schedule Export
Sets the interval and time that the appliance begins packaging the items you selected. Note: The process may take several hours to complete, depending on the number of packages you selected and the size of the items.

Package Management Queue


Displays a list of import and export jobs in the order that they will be executed. The appliance runs one import/export operation at a time. Scheduled exports appear in the queue. Choose Action Manage packages jobs using the following option:
Delete Selected Stops a job that is in progress or removes the job from the queue. Deleting a scheduled export, permanently unschedules the export.

Import List
Navigation title: Import K2000 Packages Displays a list of components available to Import from the K2000 Restore directory. You can also import packages from another location if the package is smaller than 2 GB. In order to import larger packages you must first move them to the Restore share. Choose Action Manage packages available for import using the following options:
Upload Package for Import Allows you to browse to another computer or networked location to select a package that you want to import. The package you select is copied to the restore share and automatically imported. Components in the package that are already on the appliance get overwritten on import. Imports the selected packages from the restore share. It replaces components on the appliance with the ones from the package.

Import Selected

K2000 Deployment Appliance v3.3, Administrator's Guide

167

Delete Selected

Removes the package (both the index and package files) from the Restore share.

Import Package
Navigation title: Upload Package for Import Allows you to browse to another computer or networked location to select a package that you want to import. The package you select is copied to the restore share and automatically imported. Components in the package that are already on the appliance get overwritten on import.

Off-Board Package Transfer


Copies exported packages from the K2000 restore directory to a remote location. Use the Off-Board Package Transfer feature to automatically backup exported packages from the appliance restore directory to a remote FTP/SFTP server or Samba file share. The backup process creates a new directory on the remote server, copies all .xml and .pkg files to that location, and optionally deletes the transferred files from the restore directory. Click Edit and then Enable Backup to turn on the off-board transfer feature and display the scheduling and remote host form.
Modified Enable Backup Schedule Run Backup Protocol Backup Server Host Name or IP Path or Share Name Displays the date and time that the record was last updated. Click to enable/disable. Select the interval and set the time when you want to run the backup. Select which file transfer protocol is used to put files on the remote site. Host name or IP address of the computer to which the files are transferred. Enter the path to the directory or share name for the backups. Note: The backup creates a new directory in the location you specified. The naming convention is datatype_timestamp.

User Name User Password Cleanup Restore

Enter the user name for the appliance to use, requires write access the remote location. Enter the password name required to access the remote location. Click to enable. Deletes files from the restore directory on the K2000 appliance after the transfer completes.

168

K2000 Deployment Appliance v3.3, Administrator's Guide

Appliance Maintenance
K2000 Appliance Updates Software updates are available from the Dell KACE Customer Support Site or by contacting Dell KACE Technical Support directly. Automatic Updates: Appliance gets and installs Dell KACE K2000 appliance software patches and updates directly from Dell.
Update Status Read only. Displays a message that indicates the status of the appliance software and database versions. Indicates if the appliance can connect to Dell, whether your appliance software is up-to-date or needs an update, or if an error occurred while applying an update. (Read only) Displays the date and time the appliance last connected to the Dell Support site to check for an update package. Current Version Check for Server Updates Apply Updates (Read only) Displays the current appliance version. Click to download and install latest patches and updates. Appears if an update is available.

Last Check

Manual Updates: Install the update from a file that you downloaded from the Dell KACE Support site.
K2000 Update File Update K2000 Click Browse and select the file that you downloaded from KACE. Install the update using the file you selected.

Remote Sits Appliance (RSA) OVF Image Updates When your environment uses the Remote Site Appliance (RSA) to distribute components from a remote share, you must also update the RSA OVF images each time you update the K2000 Appliance software. The updates are available from the Dell KACE Customer Support Site or by contacting Dell KACE Technical Support directly. Automatic Updates: Appliance gets the update from Dell directly and automatically installs RSA software patches on the Virtual Machine at the remote site.
Update Status Read only. Displays a message that indicates the status of the linked RSA software and database versions. Indicates if the appliance can connect to Dell, whether your appliance software is up-to-date or needs an update, or if an error occurred while applying an update. MD5 checksum of the RSA software. Date and time the update was installed.

Checksum Last Update

Check for RSA OVF Image Click to download and install latest patches and updates. Updates

Manual Updates: Install the update from a file that you downloaded from the Dell KACE Support site.

K2000 Deployment Appliance v3.3, Administrator's Guide

169

RSA Update File Update RSA OVF Image

Click Browse and select the file that you downloaded from KACE. Install the update using the file you selected.

Utilities Driver Recache: Updates the appliance driver cache for the boot environments and scripted installations from the driver share directory. Only manually added drivers require recaching.
Update Status Last Recache Read only. Displays a message that indicates the status of the last recache request. Date and time the drivers were successfully recached from the driver share. Note that you can recache the predefined directories individually from the Driver Management page. Recaches all directories on the drivers share.

Recache All Drivers

Purge unused K-image files: The Purge button removes system image files that are not associated with an image of an licensed client, that is a node which has booted from the K2000. Client nodes display on the Systems Inventory page. Power Management: Allows you to reboot or power off the appliance.

170

K2000 Deployment Appliance v3.3, Administrator's Guide