hit counter code
Compaq 238618-001 - Evo Thin Client Quick Setup Manual
Compaq 238618-001 - Evo Thin Client Quick Setup Manual

Compaq 238618-001 - Evo Thin Client Quick Setup Manual

Hp image manager 5.0: quick setup guide
Hide thumbs Also See for 238618-001 - Evo Thin Client:

Advertisement

HP Image Manager 5.0
Quick Setup Guide

Advertisement

Table of Contents
loading

Summary of Contents for Compaq 238618-001 - Evo Thin Client

  • Page 1 HP Image Manager 5.0 Quick Setup Guide...
  • Page 2 © Copyright 2009 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Internet Explorer is either a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries.
  • Page 3: Table Of Contents

    Table of contents 1 Introduction What is HP Image Manager? ....................... 1 About This Manual ..........................2 Conventions ......................... 2 2 Installing Image Manager Components Server Requirements ........................... 3 Running the Installer Wizard ........................ 3 Completing the Server Installation ..................... 18 HP Image Manager Server Configuration ..................
  • Page 4 Appendix A Appendix A: Troubleshooting Unpacking and Installing/Rebooting ....................30 Booting the Thin Clients ........................31 Glossary ................................32 Index ................................... 35...
  • Page 5: Introduction

    Introduction What is HP Image Manager? HP Image Manager delivers operating systems and applications on-demand from your server to PCs or thin clients. The server is used as a virtual disk drive, so clients do not require a hard disk or flash memory.
  • Page 6: About This Manual

    The client requests a boot loader program to be downloaded from the tftp server. The client executes the boot loader program which requests an virtual operating system to be downloaded from the NVDD server. All of the server-based services required (licensing, PXE, tftp, DHCP and NVDD) can be provided by a single server hardware platform, multiple server platforms with a single service per platform, or with multiple services distributed over multiple platforms for fault tolerance.
  • Page 7: Installing Image Manager Components

    Installing Image Manager Components Server Requirements ● Operating system: Windows 2003, 2008, Linux x86 (kernel 2.6) NOTE: Only the x86/32–bit versions of Windows server-based components are provided. They will run in compatibility mode on the 64–bit editions of Windows 2003 and Windows 2008 servers. ●...
  • Page 8 NOTE: If you want to install HP Image Manager on a server running Linux, you will need to run the Installer Wizard on a PC running a Windows operating system, select Decompress as the Setup type, then copy the server software component files installed on the PC to the server. Run the HP Image Manager Installer Wizard.
  • Page 9 Click Next > to display the License Agreement screen. Running the Installer Wizard...
  • Page 10 Read the License Agreement and, if you agree to the terms, select the I accept the agreement option then click Next >. This dialog box provides instructions on how to install the software. Chapter 2 Installing Image Manager Components...
  • Page 11 Click Next > to continue. Specify the directory where the software components will be installed. Click Next > then select the type of installation required from the following options: Running the Installer Wizard...
  • Page 12 You might need to run the installation wizard several times, depending upon your network configuration. The most basic installation is a single machine serving the PXE, TFTP, and Flexnet License server services. To perform this kind of installation, you would select Server Installation (for Windows) and follow the prompts.
  • Page 13 ● Web Console Allows the web-console to be retro-fitted to an Image Manager installation. Although the web-console can be accessed from any machine connected to the same network as the server, the server side of the web-console must execute on the same machine as the Image Manager server that it is controlling ●...
  • Page 14 NOTE: To have the installer install the FLEXnet License server service, you must have the license file available on your server. This can either be the IMTRIAL license file in order to trial the software for 90 days, or it could be the full Image Manager license obtained during the product download sequence.
  • Page 15 Click Next > to continue. If you have selected Server installation (for Windows) or if Server components/Components for Windows is selected on a Custom installation, the Server Folders Paths page is displayed. This page is not displayed if Decompress All is selected. NOTE: The figure shows the dialog with the Custom option selected.
  • Page 16 You can browse for other paths and create other folders on your Windows system. If you have selected Server installation (for Windows) or if the component Server components/ Components for Windows is selected on a Custom installation, the Image Manager Service Installation page is displayed.
  • Page 17 If you have selected Server installation (for Windows) or if the component Web Console is selected on a Custom installation, the Web Console Installation page is displayed. This page is not displayed if Decompress All is selected. Choose to Full install or Partial install the Web Console. Full install may require the Windows installation disk.
  • Page 18 Click Next > to continue. The Select Start Menu Folder page appears. Accept or change the name of the Start Menu folder. Chapter 2 Installing Image Manager Components...
  • Page 19 Click Next > to review the settings before continuing. Running the Installer Wizard...
  • Page 20 If the settings are correct, click Next > to begin installing the files to the specified location. A progress bar will indicate the current status of the installation. NOTE: If the destination device does not have enough disk space for the software to be installed, a message will be displayed and the Installer Wizard will fail.
  • Page 21 When the installation has been completed, click Finish. Running the Installer Wizard...
  • Page 22: Completing The Server Installation

    Completing the Server Installation If you chose to install and start all the services automatically, the server installation has been completed. The server will now be running Image Manager, PXE server and the FLEXnet license server, waiting for the first client to connect. However, the clients will need a virtual disk from which to boot. The creation of this virtual disk is covered in the chapter Initial Client Configuration.
  • Page 23: Hp Image Manager Server Configuration

    HP Image Manager Server Configuration Disk Storage Required on the Server The Image Manager server must have a partition containing enough free space to contain all the virtual hard disks required by clients. A virtual hard disk consists of a hard disk image file plus a CVOL (Client Volume Overlay) write cache file that will contain all data written by the clients.
  • Page 24: Installing And Configuring Image Manager Desktop Management Web Console

    Installing and Configuring Image Manager Desktop Management Web Console Introduction The Desktop Manager Console provides a simpler way for a user to administer the Image Manager on a day-to-day basis. It does not provide the more complex settings of the full Image Manager console, but it allows a non-technical user to perform simple operations, such as changing the image streamed to Thin Clients, rebooting Thin Clients, and viewing activity information about the Thin Clients (who is logged in, IP address, computer name).
  • Page 25 From the Select Components screen, choose Web Console. Select this option if you would like to install only the HP Image Manager Web Console on a computer running a Windows operating system. To use the Web console on a server that doesn’t currently have a Web-server, select Full Install, and click Next >.
  • Page 26: Configuring Image Manager For Use With The Desktop Manager Console

    Configuring Image Manager for use with the Desktop Manager Console The Desktop Manager Console is designed to serve a selected image from a predefined group of images to a set of identical access devices, such as thin clients. The access devices will then boot from the selected image.
  • Page 27: Modifying The Client Image To Support Desktop Manager Console

    Modifying the client image to support Desktop Manager Console Within the client image, you should create a Client Sign-in desktop icon that opens a browser with the URL <Server name>/client. You can then drag this icon also to the Startup folder for Windows, so that each time the client machine(s) power on, the desktop sign-in dialog is displayed.
  • Page 28: Supported Browsers For The Desktop Manager Console

    Supported browsers for the Desktop Manager Console Supported browsers include all Web standards-compliant browsers, such as Internet Explorer version 7 and beyond, Firefox, Google Chrome, and Apple Safari. Web standards are defined by the World Wide Web consortium (W3C). Chapter 3 Installing and Configuring Image Manager Desktop Management Web Console...
  • Page 29: Enabling Clients To Access Images

    Enabling Clients to Access Images TFTP and DHCP Server Configuration The Image Manager technology relies upon the industry standard PXE and TFTP technologies to provide the initial connection to the Thin Client endpoint device. Before clients can access and boot from images on the HP Image Manager server, you must have a DHCP, PXE and TFTP server configured to serve the HP Primary Bootstrap Loader file mPXELdr.bin to clients.
  • Page 30: Testing The Tftp Service

    Copy the file mPXELdr.bin from the Server directory of the HP Image Manager distribution package into the relevant directory where files served by TFTP are stored. Make sure that the TFTPD daemon is configured correctly and working. Testing the TFTP Service You can test the TFTP service from a PC running a standard Windows Vista/Windows XP/Windows 2003/Windows 2008 operating system by typing the following at the command prompt: tftp -i host_ip_address get mPXELdr.bin %TEMP%\mPXELdr.bin...
  • Page 31: Initial Client Configuration

    Initial Client Configuration Introduction So far in this guide we have configured the Image Manager server components, setup the other network services required to support virtual disk sharing, and (if required) enabled the desktop manager console to easily manage the Image Manager operation. Before we can actually boot a Thin Client, however, we need to have a virtualized image of the disk for that client.
  • Page 32: Using A Pre-Built Microsoft Windows Image

    Using a Pre-Built Microsoft Windows Image There are two after-market kits for HP Image Manager, one contains a pre-built Microsoft Windows XP® image; the other contains a Microsoft Windows Vista® image, with all the Image Manager drivers pre- installed and ready to serve from the server. The use of these kits requires that the customer have a volume licensing key (available from Microsoft).
  • Page 33 into CVol - volatile mode. Then boot each of the other Thin Clients from the image, logging in one time to each Thin Client to set the computer name and add the client to the domain if desired. Your HP Image Manager system is ready for use. Using a Pre-Built Microsoft Windows Image...
  • Page 34: Appendix A Appendix A: Troubleshooting

    Appendix A: Troubleshooting Unpacking and Installing/Rebooting I always get a “Service had trouble starting” message when rebooting the Server and also at the end of the HP IM installer. This problem typically occurs because of a conflict between the HP IM PXE Server and the existing DHCP services on the machine.
  • Page 35: Booting The Thin Clients

    Booting the Thin Clients When a Thin Client is initially powered-on, it should perform a PXE boot in order to receive the Image Manager network boot loader from the IM TFTP server. When I power on the Thin Client, it doesn’t attempt the PXE boot process. Make sure that there isn’t a Flash boot device connected to the Thin Client Ensure that the BIOS settings have a first boot device of Network I see a message indicating that the client is trying to PXE boot, but it doesn’t get a DHCP address...
  • Page 36: Glossary

    Glossary ACPI Advanced Configuration and Power Interface blue screen A blue screen (or BSOD, Blue Screen Of Death) is a screen with a blue background that appears when a Windows- based computer crashes boot loader The first program to execute when a system is booted. BOOTP Bootstrap Protocol CVOL...
  • Page 37 Microsoft SysPrep The Microsoft System Preparation Utility for Microsoft Windows operating system deployment. Microsoft VirtualPC A Microsoft software product that emulates a PC in software. mPXELdr mPXELdr.BIN is a Network Boot Program network address translator NTLDR a Windows 2000/Windows XP/Windows 2003 operating system loader Network Virtual Disk.
  • Page 38 VMWare A software product that emulates a PC in software. Glossary...
  • Page 39: Index

    Index Linux client TFTP directory 25 access image 25 configuration 27 server image access 25 configuration 19 configuration DHCP configuration 25 client 27 disk storage required 19 configuration, server 19 file locations 18 configuring TFTP configuration 25 license server 19 server requirements conventions 2 Image Manager installation 3...

Table of Contents