Professional Documents
Culture Documents
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
Contents
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
Managing drivers...................................................................................................90
Managing the drivers share files..................................................................................91 Getting drivers from Dell KACE...................................................................................93
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
iv
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).
Create the K2000 Boot Environment that allows targets to boot from the appliance. Direct PXE boot requests to the appliance.
Description Verify that the target can boot from the appliance.
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
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.
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
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.
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).
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.
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.
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.
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.
10
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.
12
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.
13
14
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.
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.
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.
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.
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.
17
18
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
19
Boot Manager timesout to default boot sequence (local driver) Fails to boot into KBE
20
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.
21
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
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
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.
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.
26
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.
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.
28
When the NetBoot Environment upload completes, the NetBoot Environment appears on the Source Media and Boot Environments pages.
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
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.
31
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.
32
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.
33
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
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.
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.
Primary DNS
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).
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.
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.
Confirm Password
38
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.
39
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
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.
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
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.
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.
42
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.
43
44
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.
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.
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.
47
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
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.
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
50
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.
51
The Source Media page appears. 2. Click the name of the source. The details page of the selected source appears.
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
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.
54
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.
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
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.
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
Create Single HFS+ partition on disk0 Create Single Partition Display Device Compatibility
Shell Script
Install Vista/2008/7/MBR
BAT script
USMT
BAT script
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.
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.
61
\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.
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
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.
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.
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.
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.
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.
65
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.
66
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.
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
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.
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.
70
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.
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.
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
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.
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.
Create Single HFS+ partition on disk0 Create Single Partition Display Device Compatibility
Shell Script
Install Vista/2008/7/MBR
BAT script
USMT
BAT script
74
75
76
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.
\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.
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.
78
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.
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.
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
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.
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.
82
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.
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.
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
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.
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
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.
87
88
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.
89
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
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.
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
System Images OS Installation Pre- and Postinstallation Tasks User States KBEs
93
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.
94
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.
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.
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
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.
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.
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.
98
99
100
Software
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.
dwrcc.exe
DMRC client
explorer.exe
Microsoft Remote Desktop Ping Putty Telnet Tight VNC VNC-Java Remote Control
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.
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.
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
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.
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.
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
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.
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
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.
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
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.
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.
110
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.
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
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.
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.
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
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.
Total Size
Notes
115
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.
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.
116
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.
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
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
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.
119
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.
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.
Create Single HFS+ partition on disk0 Create Single Partition Display Device Compatibility
Shell Script
Install Vista/2008/7/MBR
BAT script
USMT
BAT script
120
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.
File
Information about the task that appears on this page only. Displays the names of the Scripted Installations to which the task is assigned.
121
System Images
Displays the names of the System Images to which this task is assigned. Note: You can only delete unassigned tasks.
BAT Script
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.
122
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
System Images
Displays the names of the System Images to which this task is assigned. Note: You can only delete unassigned tasks.
123
DISKPART Script
Diskpart script that the appliance executes. Note: You must select the disk, volume, or partition.
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.
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
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
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
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
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
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.
126
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.
Batch Script
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.
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.
System Images
Displays the names of the System Images to which this task is assigned. Note: You can only delete unassigned tasks.
Upload File
System Images
Displays the names of the System Images to which this task is assigned.
128
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.
Command line
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.
129
130
System Images
Displays the names of the System Images to which this task is assigned. Note: You can only delete unassigned tasks.
Download Service Pack Automatically Upload Service Pack Manually Command line
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.
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.
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
132
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 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 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.
133
Download URL for x86 version Download URL for x64 version USMT MSI (x86) USMT MSI (x64) Last Update
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.
Delete Selected
134
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.
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.
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
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.
Adds the label to the selected items. Removes the label from the selected items.
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).
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.
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
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
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.
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.
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
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.
Adds the label to the selected items. Removes the label from the selected items.
Total Size
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
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
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
Adds a label to the selected items. Removes the label from the selected items.
Enter a unique name for the KBE. Select the KBE you want to build.
143
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.
144
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
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
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.
146
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.
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.
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.
Show Compatibility
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.
Adds the label to the selected items. Removes the label from the selected items (but not the appliance).
148
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.
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.
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
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
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.
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
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.
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.
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.
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.
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.
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.
Number of Boots
152
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.
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.
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
Software
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:
dwrcc.exe
DMRC client
Explorer
explorer.exe
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.
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.
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.
156
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.
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.
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
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.
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
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
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.
160
Search Base DN
Specify which area of the LDAP tree the appliance should begin to search for users. For example, specify OU=it,
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
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.
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.
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.
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
Used Seats
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.
163
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.
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
164
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.
K2000 Server
Error Log
Output Log
Error Log
Displays errors or server warnings for the process that handles network drivers for Scripted Installations.
165
Log name NETBIOS Name Server Windows File Server Output Log
File Servers
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.
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
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.
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
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.
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
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.
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.
169
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.
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