HP Neoware e140 Neoware Image Manager 4.6 User Manual
HP Neoware e140 - Thin Client Manual
 |
View all HP Neoware e140 manuals
Add to My Manuals
Save this manual to your list of manuals |
HP Neoware e140 manual content summary:
- HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 1
Neoware Image Manager 4.6 USER MANUAL - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 2
form without prior consent, in writing, from Neoware, Inc. Neoware, Neoware Image Manager, Neoware UbiBoot, Eon, Capio, ThinSTAR, TeemTalk and The information provided in this manual is intended for instructional purposes only and is subject to change without notice. Neoware, Inc. accepts no - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 3
is Neoware Image Manager? 1 About This Manual 2 Conventions 2 Overview of Contents 3 CHAPTER 2 Overview of Neoware Image Manager 7 Software Suite Components 7 How Neoware Image Manager Works 8 Neoware Image Manager Boot Process 9 Adding a New Desktop & Upgrading Hardware 11 Client Writing Modes - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 4
-based Configuration 38 CHAPTER 4 Creating a Client Image 39 Introduction 39 Using Client Builder 40 Testing the Image 54 Advanced Client Builder Options 55 CHAPTER 5 Enabling Clients to Access Images 59 TFTP & DHCP Server Configuration 59 Windows 59 Linux/FreeBSD 60 Testing the TFTP Service 60 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 5
Table of Contents DHCP Server Configuration 61 Client Configuration 62 Troubleshooting 63 CHAPTER 6 Assigning Volumes to Clients 65 Introduction 65 Running the Image Manager Console 65 Adding New Clients 67 Adding a New Group 68 Assigning a Volume to a Group 69 Creating or Modifying a Volume 70 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 6
103 What is Neoware UbiBoot? 103 Installing Neoware UbiBoot 104 Potential Incompatibilities 105 Running Neoware UbiBoot 106 Using a UbiBoot Enabled Hard Disk 110 Learn to Use Unknown Hardware 110 Master HD for Building Images 110 Detecting New Hardware 111 Updating or Removing Drivers for Off-line - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 7
13 Adding Clients & New Software 135 Adding a New Client 135 Modifying an HD Image to be Used by Several Clients 136 Using Admin Mode 136 Using the CVolMerge Tool 137 Managing & Updating Images Located at Multiple Remote Sites 141 Restoring a Virtual Volume to an Actual Hard Disk 144 CHAPTER - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 8
Domain Credentials in the System Partition 170 Client Names 174 Adding a New Client to the Domain 174 CHAPTER 15 Merging Image & CVol Files 177 Introduction 177 Using the CVolCompactor Tool 178 Using the CVolMerge Tool 178 CHAPTER 16 The Image Manager Console 181 Introduction 181 Running the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 9
Tab 206 The Nvdd Manager 207 Merging Configuration Files 209 Password for Remote Administration 210 CHAPTER 17 The NVDD Configuration File Computer Name Change Default 222 Flush Disk Buffers on Write 222 Number of Processing Units 223 Buffer Size 223 User Definitions 223 Client MAC Address 224 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 10
Client Naming 233 Setting Client Name using NVD Protocol 233 Updating Client Name from Client 234 Enabling Client MultiBoot 235 Example nvdd.conf with Multi-Volume Support Syntax 253 Example mPXELdr .ini File 255 Keywords 256 The Include Keyword 256 The NVDServers Keyword 258 The BootMode Keyword 260 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 11
279 Could Not Copy a File 279 Client-Specific Settings on the Target System 279 CHAPTER 21 Virtualized Environments 281 VMWare Environment 281 Introduction 281 Streaming Disk Images to Virtual Machines 281 Provisioning VMs with Image Manager 284 Running Image Manager Server in a VM 284 Using - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 12
DHCP Reference 317 How Clients Locate the Image Manager Server 317 dhcpd.conf File Example 318 Native DHCP Options 319 Optional Subkeys & Values 322 Examples 324 NetBIOS Name for Clients 326 Windows DHCP Client 327 APPENDIX E Configuring NVDD as a Windows Service 329 Introduction 329 Installation - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 13
Configuration File 347 The nvdd.conf.LOCK File 348 USER_REP Files 348 How to Retrieve Restored Files 349 APPENDIX J Boot Process Comparison 351 APPENDIX K Troubleshooting 355 Technical Support 355 Check Versions 355 PXE 356 PXE Implementations 356 Etherboot 357 PXE Error File Not Found 357 xiii - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 14
363 1000BT/100BT Ethernet Switches 363 Operations on Virtual Volumes 364 Delayed Write Failed or Disk Full Error in Client OS 364 Delayed Write Failed Warnings 365 Large File Support on Linux 2.2 368 Error When Opening a Large Volume 368 Computer SIDs 368 Limitations 369 Data Transfer During - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 15
of Applications Run from an Image 371 Recommended Network Configuration 372 APPENDIX L Copyright Notices & License Terms 375 Patents 375 Third Parties Copyrights 375 Software Copyrighted by Aladdin Enterprises 375 Software Copyrighted by Paul Kocher 376 Software Copyrighted by Brian Gladman 376 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 16
Table of Contents xvi - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 17
Image Manager? Neoware 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. All application processing is done by the client. A single software - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 18
be abbreviated to "UbiBoot". Neoware Image Manager Client Builder may be abbreviated to "Client Builder". Neoware Active Cloner may be abbreviated to "Active Cloner". The following abbreviations are also used: "HD" for Hard Disk. "HDD" for Hard Disk Drive. "TC" for Thin Client. 2 About This Manual - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 19
Manual. Chapter 2: Overview of Neoware Image Manager Provides a brief description of how Neoware Image Manager works. Chapter 3: Installing Image Manager Components Describes how to install Neoware Image Manager components on the server and client computers. Chapter 4: Creating a Client Image - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 20
Clients & New Software Describes how to add a new client, add new software, and restore a virtual hard disk volume to an actual hard disk. Chapter 14: Adding Clients to Windows Domains Describes how to add Neoware Image Manager clients for administering a remote NVDD server. 4 About This Manual - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 21
21: Virtualized Environments Describes how to use Neoware Image Manager with virtual machines, which can run Image Manager clients or server. Appendix A: Upgrading Image Manager Describes how to upgrade from earlier versions of Neoware Image Manager. Appendix B: The TFTPD Installer Describes how - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 22
Appendix K: Troubleshooting Provides help on how to overcome problems when using Neoware Image Manager with various systems. Appendix L: Copyright Notices & License Terms Provides the copyright notices and license terms for software embedded in Neoware Image Manager components. 6 About This Manual - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 23
PCs or flashless thin clients) from Windows/Linux/FreeBSD servers. • Neoware Image Manager Client Builder - Enables you to create a virtual disk off an existing hard disk drive. • Neoware Image Manager Console - Allows easy configuration of hard disk drive image servers and allocates configurations - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 24
Neoware Image Manager client desktops are then configured to use PXE-based remote boot to find the operating system, hardware drivers and applications they need to load from the Image Manager server, instead of loading them from their local hard drive or flash memory. When you turn on the PC or thin - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 25
in Neoware Image Manager clients boot process. It acts as a BIOS extension and provides a BIOS-based interface for the first step of the boot process (the step that experts call int13h based or "real mode" portion of the boot process). At first, mPXELdr.BIN is downloaded into the client memory using - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 26
boot process, NTLDR loads and runs BDruPD.SYS, NVD.SYS and DSKIMG.SYS, which are the Neoware Image Manager core client drivers. These drivers create a pseudo device that Windows considers as a disk drive. The operations on this pseudo device, especially read and write operations, are translated into - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 27
Overview of Neoware Image Manager Adding a New Desktop & Upgrading Hardware Neoware Image Manager provides a set of UbiBoot utilities that can enable you to modify a hard disk image so that it is able to serve a range of desktops (PCs and thin clients) with heterogeneous hardware configurations. The - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 28
of their desktops. Restoring a clean installation for a specific client is just a matter of deleting the write cache file on the server. Note: If the common hard disk image file is modified, all per-client customizations will be discarded. Volatile mode enables clients to use exactly the same volume - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 29
private volume on the server, making it a very private mode. High Availability & Fast System Recovery Stateless NVD Protocol The NVD (Neoware Virtual Disk) protocol used by the Neoware Image Manager client and server to access virtual drives is completely stateless. This means that even if the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 30
single IP address is a very good way to add fast recovery and high availability capabilities to the servers. Technical Notes • client and the files on the server (especially CVol files) are free from error loss. • Neoware Image Manager provides support for various storage options. Hard disk images - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 31
there are enough bandwidth and hard disk resources on the network and server to fulfill all the client requests in an acceptable time. • Neoware Image Manager has little effect on memory or performance requirements of software applications running on the clients. The number of applications that can - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 32
for 20 clients. lanpcclt04.lic is a Clients Package License file for 5 clients. The server can then serve 10 + 20 + 5 = 35 clients. Please note that if the Server License file embeds an expiration date, the server will cease to function after this date is reached. 16 Neoware Image Manager Licenses - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 33
Image Manager Server logs when the server module starts. The evaluation product cannot be used legally with more clients than the maximum number of clients. • It is limited to the default settings, specifically in terms of network settings and system settings. If available, Neoware technical support - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 34
Overview of Neoware Image Manager 18 Evaluation Version - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 35
to create a hard disk or "flash disk" image. This client station must have Windows XP, XPe or Windows 2000 properly installed and configured on a regular hard disk drive, and all the required software applications. It is recommended that the latest service packs, patches, updates and hotfixes are - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 36
size of 8K, default in FreeBSD). Windows and all the applications must be installed in C: drive. The C: drive should be the only hard disk partition available to the client workstation. Additional applications can be installed in the free space on the hard disk image after the image has been built - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 37
: 1.5 MB dedicated to Image Manager, plus disk space required to store the client hard disk image files and cache files (the default maximum cache file size is 512 MB per client). Note: Some releases of Neoware Image Manager do not include the latest version of Linux/FreeBSD components. If you - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 38
Installing Image Manager Components service packs, patches, updates and hotfixes are applied to the server operating system. A server class Network Adapter is recommended for the Image Manager server network card. You should install the latest NIC (Network Interface Card) drivers for the NICs in the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 39
will contain the hard disk images (if the default location does not suit your requirements due to not enough available storage space for example). The server will host the NVDD (Neoware Virtual Disk Daemon) server module and, eventually, the hard disk images that clients will access. This server - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 40
as the Setup type, then copy the server software component files installed on the Windows PC to the server. 1 Run the Neoware Image Manager InstallShield Wizard by inserting the Neoware Image Manager disk into your CD drive, or by starting the install using the download from Neoware.com. 24 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 41
Installing Image Manager Components 2 Click Next to begin the install process. 3 Type in your software License Key exactly as provided in your documentation, then click Next. 4 This and the following dialog provide instructions on how to install the software. Click Next to continue. Running the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 42
Installing Image Manager Components 5 Click Next to continue. 6 Read the License Agreement and, if you agree to the terms, select the I accept option then click Next. 26 Running the InstallShield Wizard - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 43
a single user or multiple users. It is usually recommended to install only for you (the administrator) so that users do not have easy access to Neoware Image Manager components that are usually reserved for administrators. Click Next to continue. Running the InstallShield Wizard 27 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 44
this option if you are installing Neoware Image Manager on the Windows server that will host your images. Decompress (required for Linux/FreeBSD server) Select this option if you plan to run Neoware Image Manager server on a Linux/FreeBSD server that will host your images (you will need to install - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 45
images. Neoware UbiBoot Select this option if you are installing Neoware UbiBoot on a client machine in order to enhance an existing Virtual Disk Drive so that it will support where the software components will be installed. The default directory is: C:\Program Files\Neoware\Image_Manager_4.6 Running - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 46
Installing Image Manager Components 11 Click Next to review the settings before continuing. 12 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. 30 Running the InstallShield Wizard - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 47
not have enough disk space for the software to be installed, the following message will be displayed: 13 When the installation has been completed, click Finish. 14 Now that the software components have been installed, you need to configure the server as described in the section "Image Manager Server - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 48
files could take up to the virtual hard disk image size. The average case would be when the virtual HD image is updated regularly (once per quarter). This would be approximately 2 GB for the HD and 800 MB per client. Some Windows settings, such as virtual memory settings, have an impact on the size - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 49
Image Manager archive was decompressed: Server\Linux or Server\FreeBSD Server or Server with Console installation: Only Windows versions of the server module (NVDD.EXE) and server tools are copied to the following default directory: C:\Program Files\Neoware\Image_Manager_4.6\Server Decompress - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 50
the Neoware Image Manager server initial configuration. You can test that the NVDD server module is installed correctly by navigating to the directory containing NVDD then typing one of the following at the command prompt to launch it: Windows system: nvdd -c nvdd.smalldisk.vol.conf Linux/FreeBSD - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 51
Manager This section describes how to remove Neoware Image Manager from your computer. Note that it is possible to uninstall the Image Manager software from an Image Manager bootable drive. It will just uninstall the components that have been copied during InstallShield installation, but will not - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 52
Installing Image Manager Components 3 Select Remove then click Next. 4 A warning message will be displayed to check whether you really want to remove the software. Click Yes to start the remove software process. 36 Uninstalling Neoware Image Manager - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 53
Installing Image Manager Components 5 When the InstallShield Wizard has completed removing the software, click Finish. Uninstalling Neoware Image Manager 37 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 54
.exe is installed (usually C:\Program Files\Neoware\Image Manager 4.6\Client.) 2 Enter the following command: NeowareIMClientBuilder.exe -r The last dialogs of Neoware Image Manager Client Builder will be displayed and when it exists, Neoware Image Manager will undo every change it may - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 55
Neoware Image Manager User Manual CHAPTER 4 Creating a Client Image Introduction This chapter describes how to use Client Builder to create a client image on the Image Manager server. The Client Builder component of Neoware Image Manager makes a complete image of a system partition (hard disk) - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 56
always make sure the NVDD server module is running on the Image Manager server, and is serving a non-bootable virtual disk to the client running Client Builder. A non-bootable virtual disk called SmallDisk is supplied with Neoware Image Manager. 2 To launch the NVDD server module so that it serves - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 57
's IP address does not appear in the dialog, please verify that your Image Manager server is running, shares a nonbootable virtual disk such as SmallDisk, and both client and server can access the network. Note that Client Builder finds the existing server on your network by sending server broadcast - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 58
a Client Image In order to enter the IP address manually, check the Expert box to access the options in the dialog. Enter the Server Address or Name of the server hosting Neoware Image Manager. Do not change the Server port default setting 2184 unless your server listens on a non-default port - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 59
to boot the client on Neoware Image Manager. All the available NICs are selected by default. Check the Expert supported. WiFi NICs are not supported. If you select a WiFi NIC, your image will not be bootable using this NIC. Tip: If you intend to have many hardware clients booting off the same image - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 60
should not restore Automatic Windows Update (or any other Windows settings) before the image has been created. Client Builder will restore the original in each window until the driver installation has been completed, then click Finish. Note: Two "Neoware Emulated Disk Drive" devices may be detected - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 61
Creating a Client Image Using Client Builder 45 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 62
Creating a Client Image Click the Continue Anyway button. 13 Right-click on My Computer and select Explore in the pop-up menu. An additional hard disk called SMALLDISK should now be listed in the My Computer list of hard disk drives. For example: 46 Using Client Builder - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 63
Creating a Client Image You can also right-click on My Computer and select Manage/ Disk management in the pop-up menu. If you do, do not do anything on this volume, even if Windows proposes actions to be performed on it (for example: Initialize and Convert Disk wizard). Wait for the Found New - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 64
will be automatically filled in by default using the information supplied earlier. A password may be needed if you have set one on the NVDD server using the NVDD Password utility. When the Whole disk image option is not selected, Client Builder will build an image based on the first partition of - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 65
Creating a Client Image ensures that when Client Builder creates an image from an existing Neoware or ThinTune XPe flash disk, it will create the correct type of image. If the system partition is the first partition, only the first partition (actually the MBR plus the first partition) will be used - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 66
time. You should investigate why the image creation is slow. Look for problems in the server hard disk, network, server resources and client network resources. You may increase performance with updated drivers for the server and client NIC and server HD controllers, and also with a defragmentation - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 67
. For example, you should not change the disk signature on a thin client using flash to boot from Windows XPe. If your client OS is XPe you MUST remove the local drive or flash before booting off the image created from the local hard disk drive or flash drive. In other cases there should be no - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 68
Creating a Client Image If you click No, the previous dialog will be displayed and you will be able to check the Expert box and configure Client Builder for it to change the local drive signature. The following dialog will be displayed if you configured Client Builder to change the local drive - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 69
If you click No, Neoware Image Manager Client drivers will not be completely removed from the local OS. They will be completely removed at Windows shutdown. 21 On the Neoware Image Manager server, shut down the NVDD server module: Windows system: Press the keys Ctrl + C Linux/FreeBSD system: Either - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 70
Creating a Client Image Testing the Image You can check that the image works correctly by running it on the Image Manager server as follows: 1 Run NVDD with the parameter: -c nvdd..conf For example: Windows: nvdd.exe -c nvdd.disk0.vol.conf Linux/FreeBSD: ./nvdd -c nvdd.disk0. - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 71
the default settings in this dialog, except for the Virtual Memory settings, unless you are fully aware of the effect the changes will have. All the settings in this dialog are only applied to the remote-booted operating system that will rely on the hard disk image to be created by Client Builder - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 72
Updates (or any other Windows settings) before the image has been created. Client Builder will restore the original settings after it has completed. Disable Daylight Saving Default time manually using BIOS settings, semi-manually using login scripts or startup scripts. With Image Manager client, it - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 73
: http://support.microsoft.com/default.aspx?scid=kb;EN-US;q223184 Disable Memory Dumps Default: Checked If Windows crashes, it tries by default to dump the crashed computer memory into a file that can be used later by experts to analyze the cause of the crash. With Neoware Image Manager clients, it - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 74
Creating a Client Image Disable System Restore Default: Checked The System Restore feature enables users to restore a previous state of their hard disk. With Neoware Image Manager clients, system restore is usually not needed. It would use up disk space unnecessarily. With Neoware Image Manager, if - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 75
Neoware Image Manager User Manual CHAPTER 5 Enabling Clients to Access Images This chapter describes how to configure the network and clients so that hard disk images can be accessed. TFTP & DHCP Server Configuration Windows Before clients can access and boot from images on the Neoware Image - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 76
" on page 293 for details.) Note: You can use any standard RFC compliant TFTP service. The freeware TFTPD32 (http://www.jounin.net/) for instance has been successfully tested with Neoware Image Manager. Linux/FreeBSD The directory where files served by TFTP are stored is usually /tftpboot or - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 77
" on page 317 for information on how clients locate the Neoware Image Manager server, and the DHCP options used. Neoware Image Manager. TFTPD32 should then provide the TFTP and DHCP services on the same computer. If the computer that runs TFTP and DHCP services also runs NVDD service (Neoware Image - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 78
Images Client Configuration 1 If the client contains a bootable hard disk drive or flash disk, either disable the disk or physically remove it. 2 Make sure the client is configured to boot with PXE (boot from LAN). 3 Start the client. The client's PXE PROM will display some messages. The Neoware - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 79
, copy the image file on the server (in the folder where NVDD is located). Make sure that NVDD configuration file (nvdd.conf by default) is OK for the image. Run nvdd again on the server. Remove the hard disk from the client. Start the client and boot it from LAN (PXE boot). Troubleshooting 63 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 80
Enabling Clients to Access Images 64 Troubleshooting - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 81
volumes and assign them to specific clients. The Console also provides a userfriendly way of accessing and changing the settings in a hard disk image's configuration file (nvdd..conf) without having to use a text editor to manually edit it. To run the Image Manager Console from the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 82
in the tool bar. Refer to the chapter "The Image Manager Console" on page 181 for details. When a Neoware Image Manager Server configuration file is opened in the Image Manager Console, the two panels will list the associated Clients and Volumes. The Clients panel on the left displays the names of - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 83
for a specific group by selecting the name of the group (or a computer within it) then clicking the relevant volume check boxes. If you want to make a computer a member of a group, just drag and drop the computer icon on the target group. Adding New Clients A Client object in the Image Manager - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 84
for a single IP address. For example, 194.199.93.24/32 means a range of 1 IP address (a single client computer). 24 254 IP addresses (a complete class C). For example, 192.168.0.0/24 means all the IP addresses between 192. the volume the group will use to boot from by default. 68 Adding a New Group - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 85
available to boot from. If you do not select a volume from the list, after ten seconds the client will automatically boot using the default volume specified here. (Refer to the section "Enabling Client MultiBoot" on page 235 for more details.) Assigning a Volume to a Group The name of each volume in - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 86
used to identify it in the Console. Specify the name of the hard disk image file to use in the File name box (click the ... button to to provide a brief description of the volume which will be displayed on the client screen when it starts. The Physical Parameters options enable you to specify the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 87
Builder will automatically provide the correct geometry parameters when it creates an image file and the associated configuration file. The Parameters tab enables you to specify the client writing mode for the volume and how it is shared. The Volume Mode settings enable you to specify the standard - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 88
to Clients The particularly important to remember when you modify the configuration of a remote Image Manager server (then using the browse button is irrelevant). You can size of the CVol files if this maximum size is not the default one. The Computers tab will display the names of all the computers - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 89
mode. Adding a Volume from Another Configuration File The Console enables you to open the configuration file of another hard disk image (i.e. a configuration file created using Client Builder) in order to copy volume definitions and parameters from it into the current configuration file. Display the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 90
Assigning Volumes to Clients Load volumes from file button to list the names of add. You must make sure that the properties of each copied volume specify the location of the hard disk image file associated with the configuration file currently being modified. To do this, double-click on the name of - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 91
82.) Note: If you select Admin for the Write mode, make sure the client computer you want to use in that mode is included in the list of Admin runs the Console (if this PC also acts as a Neoware Image Manager server) or on remote Image Manager servers. Selecting Nvdd Manager in the Tools menu will - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 92
as 0 if using default port number on server side), and password if required, then click the Connect button. Note that the drop-down list contains the server addresses that have been used previously, so you can quickly select one of these. If you want to connect to a Neoware Image Manager server that - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 93
Assigning Volumes to Clients The name of the configuration file currently being used by the remote file has been correctly saved back on the server. You should then click the Reload conf file button to make the remote server take the changes into account. Clicking the Refresh every button will - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 94
Assigning Volumes to Clients 78 Modifying a Configuration File Currently Running - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 95
Neoware Image Manager User Manual CHAPTER 7 Controlling the Use of Images & Volumes This chapter describes the image configuration file settings that determine how clients can use images and volumes. The Image Configuration File With each hard disk image it creates, Client Builder also creates a - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 96
Use of Images & Volumes Client Volume Overlay Files In the Image Manager system, a client mounts a server-based virtual disk drive (volume) consisting of a hard disk image file and a pair of Client Volume Overlay (CVol) files. The CVol files are created automatically by Neoware Image Manager Server - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 97
default. You can specify a different general directory using the Image Manager Console by displaying the menu Tools > Options > Generic Options, then clicking on the Directories tab. The CVol directory can be set relative to a specific Size of CVol Files The default maximum size for CVol files - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 98
file created for this volume can grow to using the Image Manager Console. Right-click on the Volume name, select saved or lost on re-boot. The mode to be used when a client mounts a volume is specified in the Image Manager Console Volume Properties dialog, on the Parameters tab. To display this tab - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 99
and Persistent. Admin mode is used when you want to install a new application or make permanent changes to the hard disk image file. In this mode the client will write directly to the image file, not the CVol write cache file. The write is permanent. Note the following: • A volume can be mounted by - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 100
do not need to send a fullsized hard disk image. Note that the remote hard disk image will need to be updated using the CVolMerge tool. The administrator can cancel all modifications made by the client user just by deleting the CVol files. The client will then mount the original unmodified volume - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 101
the hard disk image file is modified, the CVol files associated with it will be obsolete. Therefore Persistent mode should only be used when the original image file will not change often or when you can easily recreate persistent files after the image file has changed. Tip: As Neoware Image Manager - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 102
Controlling the Use of Images & Volumes 86 Volume Write Modes - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 103
client hardware, making image management easier. The UbiBoot Extractor and UbiBoot Inserter tools enable you to extract information about a bootable network interface card (NIC) and insert it into a Neoware Image Manager virtual disk. This allows the image named UbiBootData by default and is located - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 104
pre-extracted data for some Neoware thin clients, so that you do not even need to perform the extraction step to add hardware support for these devices into existing Neoware Image Manager virtual disks. Extra pre-extracted data may be available from Neoware technical support on request. 88 Overview - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 105
on the workspace storage, and running them from there. By default UbiBoot Extractor will create the data file in a subdirectory of Image Manager disk partition. There are two reasons for this restriction: • UbiBoot Inserter expects to modify certain Neoware Image Manager-specific settings - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 106
Note: Before you perform the actual extraction process, we recommend that you update the Network Card Drivers on the computer whose hardware support is to be added to an existing Neoware Image Manager virtual disk. The following procedure will extract the details of a bootable network device and - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 107
Adding Network Boot Devices to an Image Clicking on a device in the list will display a summary of ), and some file information that describes the device driver and environment. 2 If you wish to use another repository other than the default one (subdirectory UbiBootData, located in the same directory - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 108
of the NIC drivers have been installed, and the user wants to ensure that the latest version is inserted in the destination image. Note that if the manufacturer changed the internal code for the device from one revision to the next, UbiBoot Extractor will see the new NIC software - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 109
Adding Network Boot Devices to an Image All the information about the currently selected NIC will be saved in a file in the repository directory. By default the name of the file is the complete PCI ID of the network adapter with the .DEV extension. For example: VEN_14E4&DEV_167D&SUBSYS_ 05771014& - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 110
an Image IMPORTANT NOTE Starting with version 1.2 of the UbiBoot Extractor/Inserter programs, the original date and time of the driver files would have to recreate the .DEV files in your repository from the original driver files. In other words, extract all the devices using UbiBoot Extractor 1.2 or - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 111
Neoware Image Manager image. 1 Select Start > Neoware > Image Manager > Tools > UbiBoot Inserter, or run the UBInsert.exe program on a machine booting off the disk image directory. If you wish to use another repository other than the default one, press the ... button at the end of the Device data - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 112
service supported. If the operation is attempted anyway, UbiBoot Inserter will display a confirmation dialog and request user confirmation before actually inserting the device. Note: If you launch UbiBoot Inserter when the destination machine is not running from a Neoware Image Manager virtual disk - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 113
Adding Network Boot Devices to an Image 3 Click the Insert button. If the device was marked in red in the list (the OS or HAL (Hardware Abstraction Layer) of the source and - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 114
Boot Devices to an Image Even if the same NIC device drivers could be used on the source and destination machines, extracting and inserting are only supported on source and destination machines that: • run the same OS, service pack included. For example, extracting from Windows XPe (XP Embedded) and - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 115
files that you are about to insert into the NVD image are older than the device files in the current ( present in the machine might reflect the date of the latest insertion, rather than the actual driver file release date. In this case, it is probably safe to accept to overwrite the existing - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 116
Adding Network Boot Devices to an Image The log messages can be saved in a file by selecting Save Log in the File menu, or by copying and pasting them into a word up to the user of the UbiBoot Extractor and Inserter programs to use them appropriately. 100 Inserting Boot Device Details into an Image - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 117
Image When the Neoware Image Manager virtual disk on the destination machine has been correctly modified by UbiBoot Inserter, you must validate that the source machine can actually be booted off that image CVol file names. Refer to the section "Client Volume Overlay Files" on page 80 for details. • - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 118
Adding Network Boot Devices to an Image itself using the CVolMerge tool and, optionally, the CVolCompactor tool (if you intend to deploy the CVol file to remote locations, for instance). The image has now been enhanced and you can now switch back to CVolwrite/Volatile mode. 102 Testing the Image - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 119
a hard disk using Neoware Active Cloner) will cause Windows to boot using compatible drivers for core hardware components such as PCI bus, IDE drives, CPU, video, etc. Once booted using these drivers, Windows will then detect the actual hardware devices and install the specific drivers. An image of - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 120
the hardware drivers for a variety of PC configurations, then build a master hard disk image for deployment. • Configure Windows on a Neoware Image Manager Virtual HD to recognize unknown hardware. Installing Neoware UbiBoot Neoware UbiBoot is installed when you perform a Client installation using - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 121
the Plug'N'Play capabilities of Windows 2000/ XP/2003, a hardware driver specific to a device on one PC can be installed on the Neoware UbiBoot enabled hard disk even if another PC or TC which does not have that device will be using the hard disk image. The operating system of the PC or TC will not - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 122
procedure describes how to create a Windows system hard disk that can boot a variety of PC hardware configurations. It assumes that you have already installed the Client components of Neoware Image Manager on a regular IDE hard disk containing a correctly configured Windows installation in partition - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 123
configure the required drivers. An Operation Completed message will appear when successful. The virtual hard disk is now UbiBoot-enabled. 7 Run Neoware Active Cloner. To run Neoware Active Cloner from the Start menu, select Programs > Neoware > Image Manager > Tools > Neoware Active Cloner. Running - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 124
support is to be added to the operating system on the virtual disk drive. Keep the default settings in Active Cloner. The target HDD can be attached directly to the client content of the Virtual Disk Drive. Its main partition must have been activated. Refer to the chapter "Neoware Active Cloner" on - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 125
tab, then the Device Manager button.) 13 When all the hardware is working as expected, use Client Builder to create an image of the system partition. That image may now be used as a bootable virtual hard disk on any PC or TC of both hardware configurations. If you need to add another hardware - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 126
is the case, the UbiBoot-enabled HD can be used to boot any client in which hardware has been detected and related drivers have been installed. You can use a Neoware UbiBoot-enabled hard disk as a master HD for creating an image that can be used for cloning your systems. Make sure that the original - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 127
any patches, new drivers or chipset utilities that you need to apply. Now HD1 can be used to boot Client-A and Client-B, and any other clients that have the same hardware configuration. You can also boot Client-A or Client-B off HD1 and create a new image (virtual drive) with Client Builder. Using - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 128
Building a Virtual Hard Disk to Boot any PC or TC Updating or Removing Drivers for Off-line Devices You can update all the drivers for different clients on a single computer that boots a Neoware UbiBoot enabled system. You can also delete drivers for devices that will not be used anymore. In most - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 129
being used so that Windows recognises them and loads the required drivers. Then you can use this Windows installation to build a master image for deployment with cloning tools, or build a disk image for use with Neoware Image Manager or CD/DVD-Boot systems. HAL Considerations HAL (Hardware - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 130
ACPI-specific functions (such as ACPI power button setup (press the F5 key during the first part of Windows installation, then when you can see Press F6 if you need to install a SCSI or RAID controller, select Standard PC as the PC type for your Windows installation). Note that Neoware thin clients - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 131
with the appropriate HALs. Choosing a Specific HAL at Windows Installation You can specify the HAL to use when performing the Windows installation. If the Standard PC HAL is chosen, Windows will be installed with APM (Advanced Power Management) support, not ACPI. APM is the predecessor of ACPI - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 132
or specific location (Advanced), then click Next. 8 Select Don't Search, I will choose the driver to install, then click Next. 9 Make sure the Show compatible hardware check box is checked. 10 Select the desired HAL, then click Next. Note that if you plan to boot a Neoware thin client off the image - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 133
Server 2003 setup: http://support.microsoft.com/?kbid=309283 • How to force a HAL during an upgrade or an installation of Windows XP: http://support.microsoft.com/default.aspx?scid=kb;ENUS;299340 • How to troubleshoot Windows 2000 HAL issues: http://support.microsoft.com/default.aspx?kbid=237556 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 134
/evaluation/features/ activation.mspx http://www.microsoft.com/piracy/activation_faq.mspx http://support.microsoft.com/default.aspx?scid=kb;enus;328874 UbiBoot & Microsoft SysPrep Neoware UbiBoot and Neoware Image Manager can be used in conjunction with Microsoft SysPrep. In particular, a Windows - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 135
Disk to Boot any PC or TC after the image is enriched with new or modified hardware, necessitating the handling of multiple logical images. Note that both Neoware using UbiBoot. Troubleshooting I get a "Security Check Failed" error when running Neoware UbiBoot. Some versions of Neoware UbiBoot check - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 136
Disk to Boot any PC or TC • Your client Neoware Active Cloner. Shutdown the client, remove the HDD and connect it in the new client. Note that if the Windows installation was made with ACPI capabilities or HAL specific capabilities, the new client can boot Client-B, and use this on Client-A. If you - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 137
Disk to Boot any PC or TC After I applied Neoware CPU occupation and check if there is a process other than System Idle Process that is using the CPU by IntelPPM.SYS driver that cannot run on not usually cause any problem on the Intel or Services\IntelPPM] "Start"=dword:00000004 Troubleshooting 121 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 138
blue screens or reboots just before the desktop should be displayed. This is caused by AMD specific utilities that cannot run on Intel based computers. To rectify this, uninstall (or don't install) any AMD specific utility before cloning the virtual drive to the actual HDD. 122 Troubleshooting - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 139
Neoware Image Manager User Manual CHAPTER 10 Managing Local Hard Disk Access Introduction This chapter describes how to enable or disable client access to local hard disks. Neoware Image Manager clients can be customized in order to enable or disable access to local hard disks. This is achieved - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 140
configuration to the NVDD server module (either click the Reload conf file button in the Neoware Image Manager Console NVDD Manager dialog, or stop then restart the NVDD server module). 5 Boot ONE client. 6 Log on this client using an Administrator Account. (A user account with administrative rights - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 141
Default button then the Apply button will set the client operating system so that it behaves as if Local HD Manager had never been used. Local disk mode). 13 Reload the new configuration to the NVDD server module (either click the Reload conf file button in the Neoware Image Manager Console NVDD - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 142
preventing some specific drive letters to appear in Windows Explorer, you may want to use TweakUI. This free tool can be download from the following link: http://www.microsoft.com/ntworkstation/downloads/PowerToys/Networking/NTTweakUI.asp • When a new hard drive is detected while the HD image is not - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 143
Neoware Image Manager User Manual CHAPTER 11 Windows Product Activation Introduction This chapter describes how to activate Windows products for Image Manager clients. Windows XP and some other products edited by Microsoft need to be activated. This activation is made through a link between a - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 144
module (either click the Reload conf file button in the Neoware Image Manager Console NVDD Manager dialog, or stop then restart the NVDD server module). 3 Boot all the clients and activate them individually. Of course, you must follow the procedures that allow a specific Product Key to be entered - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 145
Windows Product Activation When you use this method to manage activations, you must re-activate each client computer every time the shared HD image file is modified. This is because the reference CVol files that contain the individual activation data are not valid anymore (they contain - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 146
Windows Product Activation 130 Product Activation Procedure - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 147
Manual CHAPTER 12 Windows User Profiles This chapter describes how to configure your Neoware Image Manager system so that clients can use Windows user profiles. Domain Roaming Profiles Neoware Image Manager can be used to set up a system in which user profiles are kept persistent. This is a "thin - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 148
HD Image in Admin mode. Here are some tips for this kind of setup: 1 Create the required user accounts on the Windows XP/2000 client Admin mode. 6 Reload the new configuration to the NVDD server module (either click the Reload conf file button in the Neoware Image Manager Console NVDD Manager - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 149
Neoware Image Manager client computers and log on with any of the user names and passwords used in step 9. 13 Log off this user. 14 On another Neoware Image Manager client station, log on with the user name and password in the key: HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\ - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 150
is not in this list by default. This setting can be applied to HKEY_USERS\.Default before the users are created. Then following documents for more details: http://support.microsoft.com/kb/232692 http://www Each roaming profile is copied "locally" on the client local volumes when the user logs on, so - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 151
Neoware Image Manager User Manual CHAPTER 13 Adding Clients & New Software This chapter describes how to add a new client, add new software, and restore a virtual hard disk volume to an actual hard disk. Adding a New Client When you add a new client so that it boots off one of the existing virtual - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 152
that will store some of the files that are part of the new application). In order to update a volume currently used by clients, you may also copy the HD image file you want to modify and configure Neoware Image Manager so that the client used to perform the changes will mount the copy of the HD - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 153
the CVolMerge Tool Adding Clients & New Software 3 Reload the new configuration to the NVDD server module (either click the Reload conf file button in the Neoware Image Manager Console NVDD Manager dialog, or stop then restart the NVDD server module). 4 Boot only the client that will perform the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 154
as you need to. 4 Once the reference configuration suits your requirements, shutdown the client. 5 Locate the file CVolMerge (or CVolMerge.exe) in the Neoware Image Manager Distribution software (usually in SERVER/ LINUX/TOOLS or SERVER\WINDOWS\TOOLS folder). Copy this file on your server HD. Let - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 155
Adding Clients & New Software 8 When CVolMerge completes, you have two images: the original unchanged image on which clients are still running, and the new updated image. To make your clients boot from the new image, you can either (1) stop all clients and change the configuration file so that they - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 156
Adding Clients & New Software You can keep the old image definition in the configuration file. Then, when you update the new image using the CVolMerge tool, you can commit the changes to update the old image file which will become your newest image. For example, let us assume you have two image - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 157
Adding Clients & New Software Managing & Updating Images Located at Multiple Remote Sites Neoware Image Manager servers are usually located on the same LAN as the clients that mount the virtual volumes. If you have several servers at different locations (at different branches for example), you may - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 158
Software On the Remote NVDD server(s) (the server(s) containing the mirrored copy of the same image that is mounted by local clients): 7 Decompress (unzip) the CVol file. (You can use the nvddadmin tool to do this.) 8 Use CVolMerge to merge the CVol file and the image file into a new updated image - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 159
Clients & New Software Rem file on the Master server. Rem %3 is the image filename on the servers. Rem %4 is the UNC Path of the remote server folder in Rem which the CVol File is to be copied and where the Rem Image call RemoteJob.bat Managing & Updating Images Located at Multiple Remote Sites 143 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 160
Adding Clients & New Software Restoring a Virtual Volume to an Actual Hard Disk It may sometimes be necessary to dump the current system volume that a Neoware Image Manager client used to boot from to an actual hard disk. This is necessary if you intend to use Neoware UbiBoot in order for an - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 161
Clients & New Software Stop as many processes as possible on the Neoware Image Manager client. In particular, try to exit or stop Neoware UbiBoot hardware detection, run Neoware UbiBoot now (assuming default installation, from the Start menu select Programs > Neoware > Image Manager > Tools > Neoware - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 162
Adding Clients & New Software \\MYSERVER\NIMCLONER\NIMCLONER E: Neoware Active Cloner will dump the contents of the actual system partition used to boot the client onto the target partition in the actual local hard disk. It uses an incremental cloning system so that files that are the same in the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 163
Neoware Image Manager User Manual CHAPTER 14 Adding Clients to Windows Domains Introduction This chapter describes how to add Neoware Image Manager clients to a Windows domain using the Neoware Domain Wizard. The Neoware Domain Wizard NeoDomain.exe enables you to add Image Manager clients to a - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 164
Neoware Image Manager Console using the Client files folder option (select Generic options in the Tools menu, then click the Directories tab). This parameter is set to "." by default you disable the password renewal policy. This is because if a new password is elected by the client and the server, - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 165
disk partition. If the partition used to store the domain credentials is in a Neoware Image Manager virtual volume, the recommended write mode for this volume is CVolwrite/Normal. This will allow each client password changes it will be retained by both the client (Machine Domain Account Password is - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 166
domain credentials are stored on the Neoware Image Manager server, it is recommended that the different hard disk images are shared using the same server configuration file. This will ensure that the client files directory and client names are consistent for each image. If you want to use several - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 167
remove it before you continue. Once the client computers boot correctly with Neoware Image Manager, do the following: 1 Backup the hard disk image on the server. You can copy the image to another image file that you will modify. You can copy an image currently used by clients as long as it is not - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 168
sure that no clients are using that image. 3 Use the Neoware Image Manager Console to change the default writing mode for the virtual system volume (the volume usually mounted as C: on your clients) to Admin mode. 4 Save the nvdd configuration file in the Image Manager Console. 5 Reload the nvdd - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 169
Adding Clients to Windows Domains 9 Click Next to continue. Storing Domain Credentials in an NVDD Server Directory 153 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 170
Clients to Windows Domains 10 Select the option Repository on Image Manager server (default) then click Next. 11 If you use CVolwrite/Volatile mode for your system Virtual HD, you should keep the default options. 12 Click Apply to continue. You will see the message Operation completed in the Neoware - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 171
Adding Clients to Windows Domains Storing Domain Credentials in an NVDD Server Directory 155 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 172
Adding Clients to Windows Domains 156 Storing Domain Credentials in an NVDD Server Directory - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 173
Adding Clients to Windows Domains Storing Domain Credentials in an NVDD Server Directory 157 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 174
computer using any Domain Account. 19 Shutdown the client computer. 20 Use the Image Manager Console to change the default writing mode for the virtual volume to CVolwrite/Volatile mode. Reload the nvdd configuration file in the Image Manager Console so that the writing mode changes are taken into - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 175
previously. Use the Network Identification Wizard, just as you did for the other clients. It is possible to add Neoware Image Manager clients to the domain without having to sit in front of each client to perform domain membership subscription. Storing Domain Credentials in an NVDD Server Directory - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 176
perform the "join domain" task. Netdom for Windows 2000 sp4 clients is available at the following Internet address: http://www.microsoft.com/windows2000/downloads/servicepacks/SP4/supporttools.asp Netdom for Windows XP sp2 clients is available at the following Internet address: http://www.microsoft - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 177
are such that the service NetLogon is started automatically. • this script is launched before the login dialog is displayed. To achieve this, use a computer startup script that you would set using the Group Policy editor (gpedit.msc) run on a client that had mounted the image in Admin mode. • there - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 178
it before you continue. Once the client computers boot correctly with Neoware Image Manager, do the following: 1 Backup the hard disk image on the server. You can copy the image to another image file that you will modify. You can copy an image currently used by clients as long as it is not currently - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 179
either from the Start menu by selecting Programs > Neoware > Image Manager > Tools > Neoware Domain Wizard, or by running the executable file NeoDomain.exe (usually stored in the subdirectory Client\NeoDomMgr of the Neoware software distribution package). The files NeoDomMgr.sys and License.txt - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 180
Adding Clients to Windows Domains 13 Click Next to continue. 14 Select the option Repository in non-system Partition. 15 In the field Path to repository folder, - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 181
Adding Clients to Windows Domains (e.g. D:\). Note that you can only choose a directory on an is used in production, you should keep the default options. Refer to the following web sites for information on the Foreground Policy option: http://support.microsoft.com/kb/q305293/ http://www.microsoft. - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 182
side. Reload the configuration file so that Neoware Image Manager server takes this new setting into account. 23 Reboot the computer. 24 Log on to the client computer using any Domain Account. 25 Shutdown the client computer. 26 Use the Neoware Image Manager Console to change the default writing - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 183
Clients to Windows Domains 28 Reload the nvdd configuration file in the Image Manager Console so that the writing mode changes are taken into account. 29 Boot one other client. 30 Log on this client using an Administrator Local User Account (a user account local to this client and password. Click - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 184
?" on page 169): Use the Neoware Image Manager Console to change the default writing mode for the virtual system volume (the volume usually mounted as C: on your clients) to CVolwrite/Volatile. Save the nvdd configuration file in the Image Manager Console. Reload the nvdd configuration file in the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 185
that this step is needed. Netdom for Windows 2000 sp4 clients is available at the following Internet address: http://www.microsoft.com/windows2000/downloads/servicepacks/SP4/supporttools.asp Netdom for Windows XP sp2 clients is available at the following Internet address: http://www.microsoft - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 186
sure that no clients are using that image. 3 Use the Neoware Image Manager Console to change the default writing mode for the virtual system volume (the volume usually mounted as C: on your clients) to Admin mode. 4 Save the nvdd configuration file in the Image Manager Console. 5 Reload the nvdd - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 187
either from the Start menu by selecting Programs > Neoware > Image Manager > Tools > Neoware Domain Wizard, or by running the executable file NeoDomain.exe (usually stored in the subdirectory Client\NeoDomMgr of the Neoware software distribution package). The files NeoDomMgr.sys and License.txt - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 188
Adding Clients to Windows Domains 9 Click Next to continue. 10 Select the option Repository in System Partition then click Next. 11 If you use CVolwrite/Volatile mode for your system Virtual HD, you should keep the default options. 172 Storing Domain Credentials in the System Partition - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 189
the domain administrative account user name and password. If a computer account already exists in the domain for the client, you can re-use this account. Neoware Image Manager configuration, or in DHCP settings, so that the computer name gets the new name when it boots. (Refer to the section "Client - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 190
the last client. 23 Use the Image Manager Console to change the default writing mode for the virtual volume to CVolwrite/Volatile mode (or CVolwrite/Normal mode if this suits your requirements). 24 Save the nvdd configuration file in the Image Manager Console. 25 Reload the nvdd configuration - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 191
into the domain. All that is required is that the clients' computer names are added to the domain. Then, using the same client PC, change its name in Neoware Image Manager server or DHCP configuration between each reboot and add the new client name to the domain as described earlier. You can use - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 192
Adding Clients to Windows Domains 176 Storing Domain Credentials in the System Partition - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 193
Neoware Image Manager User Manual CHAPTER 15 Merging Image & CVol Files Introduction This chapter describes how to use the CVolMerge tool to create a new hard disk image from an existing image and a CVol file. The CVolMerge tool enables you to create a new hard disk image file from an existing - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 194
\Image_Manager_4.6\Server\ FreeBSD\Dynamic\Tools C:\Program Files\Neoware\Image_Manager_4.6\Server\ FreeBSD\Static\Tools Using the CVolCompactor Tool The CVolCompactor tool is used to reduce the size of a CVol file before merging it with a hard disk image file. CVolCompactor will look at the sectors - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 195
path> actually refers to a CVol file relative to the hard disk image in . Also, remember that the [new HD image file] parameter is optional; if you do not specify it, CVolMerge will just update the existing image file with the content of the CVol file. Windows example - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 196
Merging Image & CVol Files 180 Using the CVolMerge Tool - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 197
Manager Console provides a graphical interface for editing an nvdd..conf configuration file. Each Neoware Image Manager Server module will use its own nvdd configuration file that defines virtual hard disk volumes and specifies which clients can access them. Refer to the chapter "The - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 198
reload a modified configuration file into a server that is running.) When an image configuration file is opened in the Image Manager Console, the two panels will list the associated Clients and Volumes. The Clients easily select or deselect volumes for a specific group by selecting the name of the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 199
one. Generic Properties To define various properties such as network access, client overlay file directories, etc. Nvdd Manager To control any running Neoware Image Manager, especially remote (access, load and reload configuration files). Properties To view the properties of the selected object - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 200
an object. About To open the About dialog. The Edit Menu The File menu provides standard functions for opening and saving files, and exiting the Image Manager Console. The Edit menu enables you to create clients and volumes, and view and edit their properties. 184 The File Menu - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 201
The Image Manager Console Selecting Create will display a menu enabling you to create set of tools for managing the Image Manager server, clients and volumes. Selecting Generic options will display a dialog enabling you to specify general settings such as the default maximum CVol size, network buffer - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 202
display of the Toolbar and Status bar. The Help Menu The Help menu enables you to display information about your version of the Neoware Image Manager Console. Displaying & Changing Properties The properties of a Computer, Group, or Volume can be displayed and changed either by right-clicking on its - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 203
. Name This field enables you to specify a name for the Client Object as it will appear in the Clients list. Client Identification The Client Identification property specifies how Neoware Image Manager identifies the Client Object: either by specifying a single IP address, Displaying & Changing - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 204
The Image Manager Console or specifying a unique MAC Address, 188 Displaying & Changing Properties - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 205
or specifying an IP subnet. The Image Manager Console When idenfified as a subnet, the address. For example, 194.599.93.24/32 means a range of 1 IP address (a single client computer). When a client object identified by subnet has a subnet mask of 32, it is in fact a unique IP address - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 206
name. The Neoware Image Manager configuration file contains a parameter that specifies the default behavior. This parameter is available in the Tools > Generic options dialog (see later in this section). If you would like a specific client object to be able to change and save the client name in the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 207
The Image Manager Console If you want this client to follow the default behaviour set in the Generic Properties dialog, check the Use Generic Option check box. Note that when Use Generic Option is checked, the greyed options will reflect the value of the default options (either Enabled or Disable). - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 208
The Image Manager Console Volume Properties The Volume Properties dialog provides a range of options for defining a volume that can be accessed by clients. It is divided into several tabs, with the General tab shown by default. Refer to the section "Creating a Volume" on page 193 for details. 192 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 209
for associated CVol files, and the physical parameters of the volume. CAUTION: You should not change the name of a volume currently in use by Neoware Image Manager client, nor should you change a volume name if there are CVol files related to this volume that you want to use. If you change the name - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 210
You can change the File name of a volume currently in use by Neoware Image Manager client only when the new file is a copy of the old file. If disk of your clients with another system disk! • If the volume is not currently mounted by Image Manager clients and you change the File name to an HDD image - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 211
. (For a description of the writing modes, refer to the section "Volume Write Modes" on page 82.) The clients listed in the Special clients mode tabs are defined in the Neoware Image Manager server configuration file. (Refer to the appropriate sections for details.) The Volume ID is the internal - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 212
The Image Manager Console The CVol Tab The CVOL tab enables you to specify a different size. All you would need to do would be to restart the server or reload the configuration file and, sometimes (when the clients are frozen because of "disk full" errors), reboot the clients. 196 Creating a Volume - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 213
We highly recommend that you set Admin computers according to your requirements and do not leave the client object "everybody" in this field. Only the actual clients allowed to perform administrative operations (changes in the image file itself) should be listed in this field. Creating a Volume 197 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 214
The Image Manager Console The Allowed Computers Tab The Allowed Computers tab enables you to specify which computers or subnets are allowed to access this volume, and - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 215
Generic Options The General Tab The Image Manager Console The General tab enables you to specify settings that affect network access, the directory to use for client volumes, and the default maximum size of the CVol file and the default Client-Driven name change behaviour. The CVOL Size setting - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 216
in potential data corruptions. The setting of the Client-Driven name change allowed (default behaviour) option determines the default action of the NVDD server when a computer name is changed by a client during a session, and a specific Client-Driven name change property is not defined for the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 217
The Image Manager Console allow specific clients to override this general setting. For more information on client naming, refer to the section "Client Naming" on page 233. Note: If you disable the parameter Client-Driven Name Change (default behavior) and you enable Client-Driven Name Change for the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 218
that the server is to use for admin connection. The Certificates pwd setting specifies the password used to encrypt the certificate file (if any). Note that even if SSL encryption is disabled in Neoware Image Manager, the certificate still has to be specified and valid. 202 Generic Options - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 219
parameters will be taken into account ONLY if you provide executable names in the corresponding fields. MD5 Executable default: md5sum.exe (Windows) or md5sum (Linux/ BSD). MD5 Parameters default: the only parameter given to the executable file will be the filename given by the administrator through - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 220
that you can use batch file (.bat or .cmd under windows, shell scripts under Linux/FreeBSD) as the executable. This may be useful when using executable files that do that when run as a service under Windows, Neoware Image Manager runs by default under the authority of "SYSTEM" account 204 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 221
the address and port to use for communicating with clients, and the Admin protocol address and port for communicating with the Image Manager server. Admin protocol is used by Client Builder to create the image file and by Neoware Image Manager Console to control running servers. Specifying an IP - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 222
The Image Manager Console The Authorized Subnets Tab The Authorized subnets tab is a security feature that allows you to configure the subnets the Image Manager server will accept. The server will accept requests from any IP address if no subnets are specified here. 206 Generic Options - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 223
menu. This enables you to connect to and manage Image Manager servers directly. To connect to a running Image Manager server, enter the server's IP address, port number (leave as 0 if using the default port number on the server side), and password if required, then click the Connect button. Note - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 224
Neoware Image Manager server module, you can use Nvdd Manager and connect to IP address 127.0.0.1 (local host) or to any of the server's assigned IP addresses. This makes it possible to reload of a client by clicking the Delete Client button. This will not remove the client from the configuration - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 225
Image Manager Console The Console enables you to import volume details stored in another configuration file, especially single-volume configuration files created using Client each copied volume specify the location of the hard disk image file associated with the configuration file currently being - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 226
.exe (Windows) or ./NvddPasswd (Linux/*BSD). 4 Type in the password to be used, press the Return key, then confirm the password by typing it again. The NvddPasswd utility must be launched whenever the administrator wants to set or change a password that Neoware Image Manager Console users must enter - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 227
The Image Manager Console Note: NvddPasswd can be used while nvdd is running. You do not need to restart nvdd for the new password to be taken into account for new connections. Password for Remote Administration 211 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 228
The Image Manager Console 212 Password for Remote Administration - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 229
Neoware Image Manager User Manual The NVDD CHAPTER 17 Configuration File Introduction This chapter describes the nvdd configuration file and the settings that can be specified in it. The nvdd configuration file is used to define virtual hard disk volumes and specify which clients can access them. - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 230
supplied in the Image Manager installation provides default configuration settings for the basic hard disk volume smalldisk.vol that is used as the foundation for creating hard disk images and volumes for clients stored in # /usr/local/lanpc3/cvol (Linux/Unix Style): # client_volumes_dir = /usr/local - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 231
The NVDD Configuration File disk_threads=1 recv_buf=131072 send_buf=131072 client_files_dir=./ bin_directory=./tools certificate_file=./nimcert.pem certificate_passwd=78gfd3sD # # USERS definitions # users=everybody, admin everybody.subnets=0.0.0.0/0 admin.subnets=127.0.0.1/32 # # VOLUME definitions - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 232
The NVDD Configuration File SmallDisk.users=admin, everybody SmallDisk.unicast_users=admin, everybody SmallDisk.admin_users=admin, everybody SmallDisk.admin_mode_users= SmallDisk.normal_mode_users= SmallDisk.volatile_mode_users= # # GROUP definitions # groups=group0 #group0.vols = vol0, vol1 group0. - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 233
Caution: Neoware Image Manager will erase existing comments when it modifies a configuration file. An example of a configuration file that supports multiple volumes port (optional - default: 2184) Specifies the port number used by the nvdd server. admin_addr (optional - default: same as address) - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 234
max_idle_time (optional - default: 120) Clients that have not communicated clients to communicate with the server again without any problems. Directory for Client Volumes client_volumes_dir=./ This specifies the directory where client client CVol files being stored in /usr/local/lanpc3/ cvol (Linux - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 235
client (nvddadmin) must be based on this directory, or a subdirectory of it. When NeoDomain has been run to enable Domain Credentials on Neoware Image experiences any problems, such as a power failure, filename>] (optional - default: md5sum.exe (Windows) or md5sum (Linux/BSD) This specifies the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 236
is to use when it receives an "UNZIP" command from nvddadmin. The specified executable file will be used instead of the default gunzip.exe (Windows) or gunzip (Linux/BSD). This executable MUST be placed in the directory pointed to by bin_directory. unzip_params = (optional) If unzip_file is - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 237
in Neoware Image Manager password used to encrypt the certificate file (if any). Maximum Size of CVol Files sectors_map_size (optional - default: 512) This specifies the maximum number of sectors that can be stored in each client the volume, Image Manager will issue a Disk Full error message - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 238
. For more information on client naming, refer to the section "Client Naming" on page 233. Flush Disk Buffers on Write do_flush_on_write=[true¦false] (optional - default: false) The setting of this option determines the default behaviour of the server when a client computer sends a write request - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 239
shared storage. disk_thread (optional - default: 1) Specifies the number of processing units dedicated to disk operations. This value can be to a number greater than the the number of CPU in your server added to the number of physical hard disk drives that are accessible in parallel at the same - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 240
by its IP address and given the name of the last matching subnet of different client (named "users") definitions. More details about IP addresses notation with slash can be found here: http://www.erg.abdn.ac.uk/users/gorry/course/inetpages/ip-address.html Note that if the subnets restrict the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 241
behavior of the server when the client changes its name during a session. If it is not specified, it defaults to the global value default_save_name. for this volume. .file Specifies the name of the hard disk image file to use. For example: SmallDisk.file=smalldisk.vol .desc - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 242
Specifies the number of heads for the virtual disk. .sectors Specifies the number of sectors for the virtual disk. Volume Type .floppy (optional - default: false) Specifies if this volume is a floppy image. Unit letters at DOS/BIOS level depend on this. Value: true or - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 243
with earlier versions of Neoware Image Manager. Volume Integrity .check_cvol (optional - default: false) This parameter client mounting the volume will be deleted before the client actually boots. All write operations will then be made on the hard disk image file itself. The default - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 244
write modes for specific clients using the same volume, so the default write mode is ignored. clients> #(CVolWrite/Volatile) If the writing mode is set to CVol write and the submode is normal, the following command will cause the Image Manager server to automatically check if the hard disk image - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 245
is copied to vol0@00E0C554E700 before vol0 is actually mounted by the client. The same is done for the data file [email protected] @00E0C554E700.ref and [email protected] replace vol0 CVol files for the client 00E0C554E700. In this case, the presence of a file named vol0@00E0C554E700 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 246
stored at the normal folder (see the section "Directory for Client Volumes" on page 218). Cache Size .cache_size (optional disk cache (Windows Servers, Linux/*BSD Servers). This option is currently unsupported and is present only for compatibility with earlier versions of Neoware Image - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 247
group definitions. A group is used at initialization time to determine which clients can access the shared drives. Depending on the client user name (see users), nvdd will tell the client which volumes it should mount and assign specific modes. Please note that this information is only general, real - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 248
in group. The best matching user subnet is chosen to specify if a client uses the group parameters. .wrappers (optional) This is a comma the default decimal base. This option is currently unsupported and is present only for compatibility with earlier versions of Neoware Image Manager - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 249
Naming The NVDD Configuration File Neoware Image Manager uses several methods to assign names to clients. You can either specify the name of a client directly in the nvdd configuration file using the NVD protocol (highest priority), or if no name is specified one will be assigned either based - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 250
The NVDD Configuration File Updating Client Name from Client When a client name has been set using the NVD protocol, it can be updated from the client side. At shutdown time the client sends a message to the NVDD server in which the client's name is embedded. If the client name has changed or does - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 251
MultiBoot The NVDD Configuration File Neoware Image Manager provides a MultiBoot feature. When two or more bootable volumes are associated with a client, the client will display the descriptions of these volumes so that the user can select the one to boot from. If no selection is made within - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 252
desc parameter for a specific volume, mPXELdr will not of Volume properties in the Neoware Image Manager Console) are displayed other bootable volumes are ignored. • The default boot volume (Virtual HD #1) is the first client(s). You could also copy a volume definition that uses the same disk image - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 253
VolXPHE and will see two volumes, their boot volume (VolXPHE, usually mounted on C:) and another volume, VolXPNoBoot, that may be mounted on D:. Clients in group0 and in group1 can be used at the same time with no problems, as long as no client mounts VolXPNoBoot or VolXP in Admin mode. Enabling - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 254
Volume Support The following example nvdd configuration file shows typical settings for multi-volume support. # nvdd.conf generated by Neoware Image Manager users=P640-149, e140-156, h00e0c5590bbf, admin, everybody, h00e0c559475a, e90-157 P640-149.mac=00E0C559316B e140-156.mac=00E0C554E700 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 255
.check_cvol=true disk1.no_admin_cvol=true disk1.write_mode=cvolwrite disk1.cvol_mode=normal disk1.sectors_map_size=0 disk1.client_volumes_dir= disk1.cache_size=0 disk1.type=0 Example nvdd.conf with Multi-Volume Support 239 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 256
=group0 group0.vols=disk1, disk2 group0.unicast=true group0.max_ram_sectors=102400 group0.read_only=false group0.users=admin, everybody 240 Example nvdd.conf with Multi-Volume Support - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 257
, to reload it after it has been modified, and also to get information about the clients currently attached to the server, etc. Client Builder can also use this protocol when it creates the image of the original hard disk. The NVDAdmin protocol uses TCP. The server listens on port 29035 by default - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 258
. The data sent between the console and the server are then encrypted. Note that SSL encryption has been disabled in Neoware Image Manager 4.5. If you actually want to encrypt the communication between NVDD server and NVDAdmin clients, you can set up an SSH tunnel. Note that the data sent by the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 259
path is /etc/ssl/certs/. -f The default filename is stdin. If this option is specified, NVDDAdmin will execute each of the commands in the specified file, making it possible to automate complex sets of instructions. Command Examples Nvddadmin -h 127.0.0.1 This communicates with the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 260
. All commands are case sensitive and must be in lowercase. Command Descriptions ping Ping the NVDD server. auth Authentification with password. The password is the one set by the NvddPasswd tool. It will be displayed in clear text on the screen when using this auth command. 244 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 261
NVDD Server Administration nopwd Switch to AUTH mode when the password on the server side has not been set. exit . Further exclusive NVDAdmin connection requests (either sent by NVDAdmin, by the Console or by Client Builder) will fail. connect [] Connect to the specified remote host. - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 262
with resume mode on secured socket. rput [P] Copies filename to server with name name with resume mode. reload [X] Reload nvdd server. This command actually performs the commands load_conf_current.get_conf_filename. This will load the configuration file named as current, followed - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 263
server as current. (using a put command), and send the reload command to the server. load_conf [X] Reload server with the specified configuration file. Caution: When using this command, you must make sure that existing clients that may be running and have mounted virtual volumes - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 264
connection) from nvdd. (Client identification obtained using the get_users command). md5 [P] Computes md5sum of the specified remote file. The Md5sum.exe file (or Md5sum executable for Linux/FreeBSD) must be present in bin_directory on the server. bin_directory is specified in the nvdd - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 265
remote file. The gunzip.exe file (or gunzip executable for Linux/FreeBSD) must be present in bin_directory on the server. bin_directory cvolmerge [P] Patch volume name (original image file) with CVolFile specified by CVolName to create destination name. CVolName - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 266
NVDD Server Administration 250 NVDDAdmin Commands - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 267
Neoware Image Manager User Manual CHAPTER described later in this chapter. mPXELdr will query the DHCP server that downloaded it for up to eight configuration files, in a fixed predefined order for an .ini file specific to the MAC address of the station. 2 ip1_ip2_ip3_ip4.ini Search for an .ini file - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 268
name, with this exact capitalization. If at this point, no .ini file has been found, mPXELdr will give an error message and merely use its default options and the server list provided in Option 132 of the DHCP (if any). 252 Introduction - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 269
(a specific piece of hardware) to the most general (all stations, for a common default) configuration. In order to be processed by mPXELdr, all the configuration files must be installed in the same directory as mPXELdr itself. Contents & Syntax • A whitespace is either a space or a TAB character - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 270
values usually do not extend across lines unless otherwise specified (keyword-specific syntax). • Unless specified otherwise, a keyword followed by an value for that keyword will cause the keyword to be ignored, and the default value (if any) for that keyword to be applied. • Unless specified - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 271
. # Blank lines are allowed too. # A 'whitespace' is either a space or a TAB character. # Whitespaces may appear before the # sign. # ) NVDServers = 192.168.0.9:256,192.168.0.209:2184,192.168.0.209:10000! ; BootMode = i # I: Interactive, A: Auto, S: Semi-auto (default) VolSelectionTO = 5 # - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 272
SomeAbsolutePath/MyIncludeFile.ininc As the TFTP OS can be hosted in either a Windows, Linux or UNIX server, mPXELdr will get the default .ini file path from the mPXELdr file path (that comes from the DHCP information removes any path separators. It merely uses those that it collects 256 Keywords - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 273
Linux or UNIX, and the TFTP client typically doesn't know either what OS and path separator convention the TFTP server is running. Finally, it should be noted that the above rules are applied to generate a filepath (which must be no more than the PXE specification , the TFTP software and/or launching - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 274
NVDServers = 192.168.0.209,192.168.0.161:2300,111.111.111.111:111! Default value: NVDServers = ; The use of this keyword can replace the need of a customized DHCP Option 132, making it easier to deploy Image Manager in existing networks where DHCP servers are already installed (and sometimes not - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 275
the TFTP server at the default NVD UDP port. This makes possible the use of Neoware Image Manager server running on the same server as the TFTP server without the use of an .ini file or DHCP Opt132. The use of multiple NVDServers lists is specifically - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 276
first non-whitespace character that follows the '=' sign. Thus Atomitoc, even though meaningless, will be accepted and processed just the same as Automatic. Default value: BootMode = S The BootMode keyword defines the behavior of the mPXELdr at boot time. It can take one of three values: A for - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 277
a successful connection, the search will be restarted from the first server in the list, then the second, etc. Semi-Automatic Mode (This is the default mode if the BootMode parameter is not specified.) Semi-Automatic mode is the same as Automatic mode with one exception. If the station mPXELdr is - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 278
The mPXELdr Configuration File The selection is achieved using the Up and Down arrow keys then pressing the Enter key. Pressing the F1 key from this screen will change the display to the log screen which shows messages printed by mPXELdr as it runs. Pressing the F2 key will return you to the Boot - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 279
The mPXELdr Configuration File Interactive Mode In this mode, the whole process of server and volume selection is done by the user through interactive menus. mPXELdr first displays a Boot Volume Selection screen containing the server list build using the NVDServers keywords and the Option132 servers - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 280
The mPXELdr Configuration File Volume selection is achieved using the Up and Down arrow keys then pressing the Enter key. Note that even if there is only one volume available for selection, the user still has to press Enter to continue. Once the user has selected and validated a volume, mPXELdr will - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 281
the PreBootPause keyword is specified and set to Y. The VolSelectionTO Keyword Syntax: VolSelectionTO = Examples: VolSelectionTO = 30 VolSelectionTO = 0 Default value: VolSelectionTO = 10 This keyword is only meaningful when associated with the BootMode = S option (see above). If the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 282
will be considered identical. This keyword accepts two values, Y and N. "N" is the default. If set to N, boot will immediately be attempted after a volume is selected by whatever of the boot sector from the selected image. Pressing any key will start the boot process from the selected server / - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 283
DHCP values in the client. This keyword accepts three values, D, N and I. "I" is the default. If set to D, specifications, but usually works and can be tried as an alternative method to the regular DHCPINFORM method. Note that versions of mPXELdr prior to the one shipped with Image Manager v4 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 284
1/1 Default value: None Warning: This option implements a work around for a few and limited number of technical issues related to very specific PXE unattended transmission and reception of data packets at times when the CPU is busy doing some other work. Upon initialization, mPXELoader queries - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 285
The mPXELdr Configuration File The NICRxTxQs parameters overrides the values that mPXELoader got from the PXE firmware with the values supplied. On a general basis, without specific knowledge about the NIC implementation, values above 48/1 are unsafe and should probably not be used. Keywords 269 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 286
The mPXELdr Configuration File 270 Keywords - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 287
optimized image update processes when used with Neoware UbiBoot. When you run Neoware Active Cloner the following steps occur by default, but Registry files are created on the target partition. 4 By default, Neoware Image Manager Client components are disabled on the target partition so that when the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 288
Active Cloner the target partition so that it stays bootable from an Image Manager server. 5 The Master Boot Record (MBR) of the source partition is duplicated to the target partition. Cloning a Partition Neoware Active Cloner can be run using command line options (described later in this chapter - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 289
cloned and is, by default, the partition running the operating system currently being used. 3 The Target Drive must be specified as a drive letter. It can be a hard disk partition attached to the Neoware Image Manager client, another Neoware Image Manager virtual hard disk, a bootable partition on - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 290
current Neoware Image Manager client to the shared hard disk. Make sure that you use connection credentials that give you full control permissions on the shared hard disk. 5 If the source hard disk is the system drive that will run Neoware Active Cloner, close as many applications and services as - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 291
target virtual drive to the client that will run Active Cloner, as a NONBOOTABLE drive. This target drive will then be mounted as an extra drive (D:, E:...). 3 If the source hard disk is the system drive that will run Neoware Active Cloner, close as many applications and services as possible. Do not - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 292
Neoware Active Cloner Expert Options Clicking the Expert button will enable you to access the additional options in the dialog. Disable Options The Disable options enable - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 293
to HDD Bootable (default) or NIM (Neoware Image Manager) Bootable. Selecting HDD Bootable will modify the Windows settings on the target partition so that it will not include Image Manager client specific settings that makes a Neoware Virtual Drive bootable with Neoware Image Manager. Selecting NIM - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 294
on the target drive so that it will not include Image Manager client specific settings that make a Neoware Virtual Drive bootable with Neoware Image Manager. Note that is possible that Windowsspecific settings used to boot with Neoware Image Manager would be incompatible with HDD bootability. If you - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 295
file is actually required. You may need to run disk checking/repairing tools if some files are corrupted. Client-Specific Settings on the Target System When you clone a Neoware Image Manager drive to a target drive, the current client-specific details are copied to the target system. In particular - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 296
Neoware Active Cloner 280 Client-Specific Settings on the Target System - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 297
Neoware Image Manager User Manual CHAPTER 21 Virtualized Environments This chapter describes how to use Neoware Image Manager with virtual machines, which can run Image Manager clients or server. VMWare Environment Introduction Streaming Disk Images to Virtual Machines Neoware Image Manager - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 298
in order to install the rest of the drivers for the VM. You would usually do this operation in Admin mode (or in CVolWrite/ Normal mode and then use CVolMerge to update the image). In order to boot your VM off a Neoware Image Manager virtual disk, you must enable the VM to boot from the network - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 299
what users experimence on their machines, even if you do not have to hand any client machine compatible with the image. Enabling PXE Boot in Your VMs In order for your VM to be able to boot of a Neoware Image Manager virtual drive, you have to enable PXE boot. This is usually done by - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 300
the tab DHCP Server and stopping the service. You must also make sure that the DHCP Service is not running by default. For instance, under Windows, you should open the "Services" management console. Provisioning VMs with Image Manager Neoware Image Manager is a perfect tool for provisioning - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 301
Environments Setting a routing service or a NAT service on the guest that runs Image Manager server would then enable In the example above, the two machines named saruman and rapetou are servers that run Neoware Image Manager server module. Both have two NICs, one connected to Private Network (172. - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 302
network configuration, administrators should be careful to configure their DHCP service so that it does not interfere with the public network a Neoware Image Manager virtual disk than when they boot off their own private VMware .vmdk disk. Yet, because you can use the very same Neoware Image Manager - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 303
about general operations with virtual machines. In this section we will focus on Microsoft VirtualPC/VirtualServer specifics. Enabling Network Boot To enable network boot, boot the VM, press the Del key to enter BIOS, go to the BOOT menu then enable network boot. For example: Note: The PXE code - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 304
and Microsoft VirtualPC/Virtual Server: Xen, Virtual Iron, VirtualBox, kvm etc. The VMs in these environments can usually be used to run Neoware Image Manager server module. However, all the "other virtualized environments" we could test implemented only partially the PXE standard and thus were not - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 305
a specific release of Neoware Image Manager are designed to work together and may not work if used with components that are not part of the same release. Upgrading from Previous Versions of Neoware Image Manager 4 Order of Upgrading Operations 1 Backup your hard disk image. 2 Boot one client with - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 306
Upgrading Image Manager If there are WiFi adapters in the list of supported Network cards, check the Expert option and make sure that no WiFi adapter is selected. 5 Shutdown the client. 6 Stop nvdd server. 7 Replace the server modules (nvdd.exe, mPXELdr.bin) and the server tools (CVolMerge, - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 307
Troubleshooting Upgrading Image Manager 14 Boot-up one client. It should boot with the new mPXELdr.bin and the new drivers from the updated image. 15 If new hardware is detected on the client (e.g. because of some changes in Neoware Image Manager client drivers), you may want to reboot the client - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 308
Upgrading Image Manager 292 Upgrading from Previous Versions of Neoware Image Manager 4 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 309
Neoware Image Manager User Manual APPENDIX B The TFTPD Installer Introduction This appendix describes how to use the TFTPD Installer to configure Windows 2000/2003/XP TFTP Server for Image Manager clients. The TFTPD Installer is a tool for helping you to install the TFTP server (TFTPD) that is - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 310
The following procedure assumes that the Microsoft TFTPD service is not yet installed. If the service is already installed, the TFTPD Installer will TFTPD Installer, either from the Start menu by select- ing Programs > Neoware > Image Manager > Tools > MS-TFTP Server Helper, or by navigating the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 311
to Windows 2000/2003 Server files field. You may need to copy the file from the Neoware Image Manager Server directory. 9 If the following information message is displayed, restart the server to run TFTPD. Managing the TFTPD Service Once Microsoft TFTP Server is installed, you can manage the TFTPD - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 312
The TFTPD Installer 296 Managing the TFTPD Service - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 313
Neoware Image Manager User Manual APPENDIX C Configuring the DHCP Server Introduction Before Installing DHCP Server This appendix describes how to configure the Windows 2000/2003 DHCP server. This appendix describes how to install and configure Microsoft DHCP Server, supplied with Windows 2000/ - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 314
Configuring the DHCP Server Configuring the Server Like with all other Server related components, you can start the setup of the DHCP server by selecting Configure Your Server from the Start/Programs/Administrative Tools menu. 1 From the Start menu, select Programs > Administrative Tools > Configure - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 315
Configuring the DHCP Server 3 Click on the line Networking Services and then click the Details... button. 4 Locate the line Dynamic Host Configuration Protocol (DHCP) in the list box and check the check box next to it. Click the OK button to continue. Configuring the Server 299 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 316
Configuring the DHCP Server 5 Click Next in the Windows Components dialog. A progress bar will be displayed while the system configures the network components. 6 When the Windows Components Wizard has successfully completed, click the Finish button. 300 Configuring the Server - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 317
Configuring the DHCP Server Configuring DHCP The DHCP server must be configured before it can be used. 1 From the Start menu, display the Administrative Tools menu and select DHCP. Configuring DHCP 301 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 318
Configuring the DHCP Server In the left pane of the DHCP window you will see the name and IP address of the DHCP server. After installation, a DHCP server is not authorized. Do not forget this later! 2 You need to define the range of IP addresses to be assigned (i.e. distributed) by the DHCP server. - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 319
Configuring the DHCP Server 3 Click Next to continue. 4 Enter a name and description for the scope you are about to create, then click Next. Configuring DHCP 303 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 320
assigned IP address (e.g. network printers). Although you could exclude them in the next step, usually a range is reserved for manually assigned addresses and then the rest (in this case 100 - 199) is given to the DHCP server for automatic distribution. 6 Click Next to continue. 304 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 321
Configuring the DHCP Server 7 If you could not define separate ranges for manually-assigned and DHCP-assigned IP addresses, then you can define the addresses to be excluded and not to be used by the DHCP server in - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 322
Configuring the DHCP Server 10 Additional DHCP options must be set when serving IP addresses to Neoware Image Manager clients in order for the system to work correctly. Select the option Yes, I want to configure these options now, then click Next. 306 Configuring DHCP - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 323
Configuring the DHCP Server 11 Is your Neoware Image Manager clients network part of a Wide Area Network? Do you want Neoware Image Manager clients to access the internet? If the answer is yes, you will need to configure the client computers with the IP address of the Gateway (or Router) to be able - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 324
Configuring the DHCP Server 14 Click Next to continue. 15 The WINS Servers dialog enables you to enter WINS server IP addresses that computers can use to convert NetBIOS computer names to IP addresses. Click Next to continue. 16 You now need to activate scope by selecting the option Yes, I want to - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 325
Configuring the DHCP Server The following dialog will be displayed when the New Scope Wizard has successfully completed. 17 You now have to authorize the DHCP server. In the DHCP window, select the DHCP server and either right-click or from the Action menu select Authorize. 18 You may now have to - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 326
Configuring the DHCP Server 19 Open the Scope Options dialog by selecting the Scope Options folder in the tree-view pane of the DHCP window (or display the Action menu) and selecting Configure Options. 20 Scroll through the list box and check the option 066 Boot Server Host Name check box. Enter - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 327
Options and in Server Options. Option 060 Class ID is not present by default, but may be set if you previously installed a third-party PXE Server -client configuration. In this case you may want to set option 60 to an empty string for the MAC addresses corresponding to Neoware Image Manager clients - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 328
DHCP assigns IP addresses dynamically on a first come, first served basis, using DHCP Reservations allows an IP address to be reserved for a specific client. An IP address can be matched with a MAC address to create a reservation. This allows DHCP to assign a "static" IP address. Furthermore, this - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 329
, the client's MAC address, and an optional description. 3 Keep the Supported types set to Both and click OK. The newly created reservation will then appear under Reservations in the tree-view pane. If you want to add a specific option to a reservation, for example a host name, you need to configure - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 330
to set. To set the host name, select option 012. Enter the desired value (TEST02-IP103 in the example above) then click OK. The option specific to that reservation will appear in the right pane when the reservation is selected in the tree-view pane. 314 DHCP Reservations - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 331
Interoperability between DHCP and BOOTP RFC 1542 Clarifications and extensions for Bootstrap protocol (BOOTP) RFC 2136 Dynamic Updates in the Domain Name System (DNS UPDATE) RFC 2241 DHCP Options for Novell Directory Services. RFC 2242 Netware/IP Domain Name and Information. Related Resources 315 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 332
Configuring the DHCP Server 316 Related Resources - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 333
Neoware Image Manager User Manual APPENDIX D DHCP Reference This appendix describes how clients locate the Neoware Image Manager server, and the DHCP options used. How Clients Locate the Image Manager Server At boot time, the Client station executes the mPXELdr code to locate an Image Manager Server - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 334
the default NVDD port UDP 2184. The next-server option is used by PXE to identify the TFTP server that should send the network boot program mPXELdr.bin to the client. Note: If you do not want the client to boot off Neoware Image Manager virtual HDs served by the server that runs TFTP service, you - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 335
configuration at boot time. The following DHCP options are read in DHCP answers and automatically set in Neoware Image Manager Clients' Windows TCP/IP configuration at boot time: Client IP Address: Assigned by DHCP. Option #1: Client subnet mask. Option #3: Default gateway. Native DHCP Options 319 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 336
to the client. This IP address (and optionally this port) is used afterwards as the IP address for the Neoware Image Manager server for this client. If virtual drives hosted on the server that provided TFTP service. By default, the BDRUPD.sys driver reads the DHCP options and tries to identify them. - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 337
corresponding information is set in Windows TCP/IP settings). In order for the BDRUPD.sys driver to handle new options, a registry key exists under BDRUPD as follows: HKLM\SYSTEM\CurrentControlSet\Services\BDRUPD\DHCPTags Note: NVDDTags (options sent by the NVDD server) are also processed by - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 338
the third string, etc. For example, if the first string contains \Registry\Machine\SOFTWARE\Neoware and the second string contains Test, BDRUPD will update the value named Test in the key: HKEY_LOCAL_MACHINE\SOFTWARE\Neoware. The process is as follows. BDRUPD gets a DHCP option value (or an NVDDTag - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 339
NICs have been defined, BDRUPD will update the settings for all of them. %ACTIVE_NIC% means the information will be set at two locations: %SERVICES%\Tcpip\Parameters\Interfaces\%INTERFACE_ID% %SERVICES%\%INTERFACE_ID%\Parameters\Tcpip %SERVICES% means the following location: \Registry\Machine - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 340
and optionally to the second one (DhcpSubnetMask) only if MS DHCP client is activated by BDRUPD (through the BDRUPD flag "SetDHCP"). Changing the Client's Name with NVDD Tags HKLM/System/CurrentControlSet/Services BDRUPD (key) NVDDTags (key) 1 (key) Type (REG_DWORD) : 1 RegType (REG_SZ) : "" Target - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 341
data must be set in the registry value "NameServer" if Microsoft Windows DHCP client is NOT activated. If it is activated, the "NameServer" entry must be Here is how BDRUPD is configured to achieve this: HKLM/System/CurrentControlSet/Services BDRUPD (key) DHCPTags (key) 6 (key) Type (REG_DWORD) : - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 342
can be set to on. The NetBIOS name cannot be set directly by DHCP. Neoware Image Manager client uses Internet Host Name (DHCP option #12) as the client NetBIOS name. Setting DHCP server to include the option Client Host Name in its answers usually implies that the DHCP server uses static entries - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 343
want to disable Windows DHCP and revert to the previous behaviour (to use the Neoware Image Manager integrated DHCP client instead), you can edit the following registry key: Key: HKLM/System/CurrentControlSet/Services/BDRUPD Value: SetDHCP (DWORD) Set it to "0" to disable DHCP, or "1" to enable it - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 344
DHCP Reference 328 Windows DHCP Client - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 345
the directory where the NVDD server module nvdd.exe is located. These files are usually found in the Server/Windows directory of the Neoware Image Manager software distribution package. 2 Launch Neoware Image Manager Server Service (SrvcLoaderSetup.exe). The following dialog will be displayed. 329 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 346
are usually in the form: -c nvdd..conf -n For example: -c nvdd.disk.bin.conf -n -n is usually specified when nvdd is run as a service, as it allows the service to be launched even if there is a .lock file (which can exist after a power failure, for example). Refer to the appendix - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 347
as a Windows service. 6 If you want Image Manager server messages to be stored in different log files, uncheck the Redirect to event log box and specify valid paths for the Standard output file (stdout) and Standard error file (stderr). Be aware that these files may use up a lot of disk space on the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 348
been specified, click the Install button. Neoware Service Loader will install and configure nvdd to work as a service. You can then Start and Stop the service using the Neoware Service Loader Setup dialog SrvcLoaderSetup.exe or the Windows Services applet in Administrative Tools. 332 Installation - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 349
NVDD as a Windows Service When nvdd is installed as a service, Neoware Service Loader Setup allows you to start or stop it. 1 Run Neoware Service Loader Setup, either from the Start menu by selecting Programs > Neoware > Image Manager > Tools > Neoware Image Manager Server Service, or by navigating - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 350
NVDD as a Windows Service 2 Double-click on the Neoware Image Manager Server entry to display the service properties. This dialog allows you to control the behaviour of the service. Usually you will select Automatic as the Startup type, so that the NVDD service runs automatically when the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 351
, and uninstall it from the system. Changing Service Settings To change the settings for the NVDD service: 1 Run Neoware Service Loader Setup, either from the Start menu by selecting Programs > Neoware > Image Manager > Tools > Neoware Image Manager Server Service, or by navigating the file system - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 352
Configuring NVDD as a Windows Service 336 Using NVDD as a Service - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 353
be used when launching the nvdd server module. The Neoware Image Manager server module nvdd is the main Network Virtual Disk (nvd) daemon. It reads a configuration file then shares hard disk images and virtual volumes among specified clients on the network using the nvd protocol. There are several - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 354
to network and disk inputs/outputs. The message checking for idle clients will be displayed frequently. This is not an error message, used again after that file has been reloaded by Neoware Image manager Console or the NVDDAdmin tool. support of power failures and startup 338 Command Syntax - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 355
or processes. In the case of a server having a power failure, nvdd will not be shutdown cleanly and the .LOCK scripts (i.e. scripts that are launched when the server computer is starting). Users that use Linux/FreeBSD servers are encouraged not to use this option but set scripts that would remove the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 356
NVDD Reference 340 Command Syntax - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 357
. At the client side, NVD.SYS is the Neoware Image Manager driver in charge of communications with the Image Manager server. This appendix describes the parameters that can be set in the registry entry for the driver, which is located in: HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/Nvd - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 358
sectors asked at one time by the client in each read/write operation. The allowed values are: 32, 64 or 128 (default). This value can be set to disk requests can be transmitted to Neoware Image Manager virtual disk drives after the shutdown order has been received by the drivers of the virtual disks - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 359
index numbers are set by Client Builder when the user selects the interfaces to be used as Virtual Disk controllers, or when UbiBoot Inserter adds the support for a network card into the image. Users should never edit this field manually as it could result in images becoming non-bootable. Domain - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 360
NVD.SYS Reference 344 Parameters - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 361
Neoware Image Manager User Manual APPENDIX H File Transfer Introduction This appendix describes issues relating to the file transfer capabilities of Image Manager. Image be set in the Image Manager Console, on the Directories tab of the Generic Properties dialog. By default, the root folder for - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 362
password before files can be transferred. The root folder has been set for security considerations. This has some implications. In particular, files created by NVDAdmin, such as the image files that client down (or when the configuration file is reloaded), the configuration file is copied back to - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 363
Neoware Image Manager User Manual APPENDIX I NVDD Temporary Files This appendix describes issues relating to temporary files created by the nvdd process. The NVDD Configuration File When nvdd is launched - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 364
If the NVDD server crashes, due to a power failure for example, the .LOCK file will still remain. You must manually delete or rename the .LOCK file in order to configuration file as well as your server execution. USER_REP Files Client names set by the NVD protocol are stored in the configuration - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 365
the directory in the Neoware Image Manager Console using the Client files folder option ( reloaded (through the console or NVDDAdmin for instance), the USER_REP. file is merged into the original configuration file and then deleted. If the NVDD server crashes, due to a power - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 366
Files • place (copy) the USER_REP file and give it the name USER_REP.. When you close or restart the server, or reload the configuration file using the appropriate Console button, the data inside the USER_REP file will be processed as usual, and the USER_REP file will be - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 367
Neoware Image Manager User Manual APPENDIX J Boot Process Comparison This appendix provides a side-by-side comparison between a HDD-based boot process and the Neoware Image Manager based boot process. The following illustrations contain a side-by-side comparison between a HDD-based boot process and - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 368
Boot Process Comparison 352 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 369
Boot Process Comparison 353 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 370
Boot Process Comparison 354 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 371
Neoware Image Manager User Manual APPENDIX K Troubleshooting This appendix provides help on how to overcome problems when using Neoware Image Manager with various systems. Technical Support Check Versions You can view our on-line support pages at the following Internet address: http://www.neoware - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 372
Troubleshooting PXE In order to check versions, you can refer to the Release Notes document, or you can perform a "decompress" installation of Neoware Image VT6102/VT6103 (PXE NIC driver v2.07 and above). • Broadcom NetXtreme Ethernet Boot Agent v 3.1.30 (also shipped as HP Boot Agent). • Marvell - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 373
server (and possibly other DHCP servers) and Intel Boot Agent v4.0.19 on the diskless client, please read the following. Issues Running Neoware Image Manager software while using Intel Boot Agent ver 4.0.19, the client aborts on downloading mPXELdr.bin. The error message is one of the following - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 374
VIA Rhine Family If the client computers use VIA Rhine family network adapters (or a compatible network adapter), then the Network Adapter driver may need to be updated. VIA Rhine family drivers shipped with Windows 2000/XP are not always compatible with the Neoware Image Manager system. If an - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 375
Adapters Volumes Troubleshooting If the server response to the client is unexpectedly slow and the server has several network card adapters, the Neoware Image configuration to a specific IP address instead of 0.0.0.0. Multi-Volume Windows 2000 Clients When Neoware Image Manager Clients running MS - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 376
tuned. This parameter is a registry value. By default, it has the value 3, which means that disks requests can be treated during 3 seconds after Neoware Image Manager virtual disks have received the system shutdown request to power off or re-start the Client. This grace delay may be needed by some - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 377
disk space on the client computer). Startup Clients Using Intel Clients using Intel i810 chipset under Windows 2000 may have i810 Chipset Under problems at startup such as system freezing, blue screens or unex- Windows 2000 pected reboots. Users are advised to update the Intel Display Driver - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 378
Troubleshooting Boot Process Stuck This problem is usually related to the Neoware Image Manager Client component not being able to communicate with the Neoware Image Manager server module. This can happen, for example, if the server module is not actually running or if client drivers are using NVD - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 379
Troubleshooting This parameter is a DWORD and can have a value in the range 2 to 128. If the client is acting slowly when remote configure them so that Neoware Image Manager packets can be sent and received by all the Neoware Image Manager clients and servers fast enough. Clients should be able to - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 380
Read/Write Request" on page 362 for information on reducing the number of sectors in a single Neoware Image Manager request. Operations on Virtual Volumes Delayed Write Failed or Disk Full Error in Client OS The error Delayed Write Failed may be raised by Windows when write operations on virtual - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 381
Troubleshooting you can also use the Neoware Image Manager Console to set this parameter (Tools > Generic Options, or the CVol tab in Volume Properties). Note that using any variant of CVolWrite mode with clients logical volume has more than 90% of free space. In order for logical volumes not to get - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 382
hard disk, before Neoware Image Manager Client Builder is run. To reduce the number of different sectors that are written during a user session, you should set the virtual memory of the clients to use a local hard disk, if any. If no local hard disks are present or available to store the Windows - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 383
size of Virtual Memory file should be 128MB. To reduce the number of different sectors that are written during a user session, you should make sure that the auto-defragmentation feature in Windows XP is disabled (it is disabled by default by Neoware Image Manager Client Builder when it builds - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 384
1 Make sure your Linux can handle files bigger than 2GB. If not, you may need to build a new kernel with Large File Support. 2 Make sure you use NVDD version 1.0.0.15 or later. All the versions of NVDD after 1.0.0.15 have complete Large File Support. Neoware Image Manager clients that boot from the - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 385
Troubleshooting CVol spaces will be discarded and your image should then run sysprep automatically. It is recommended that you completely understand what the potential problems of duplicated SIDs could be before you configure Neoware Image Manager clients booting from the same disk image - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 386
physical hard disk. The server hard disk and HD controllers should have large buffers and cache. If your server has a RAID controller, it is recommended that you use RAID1 instead of RAID5. 5 The server should not be running ANY additional application that consumes CPU power, memory, disk access or - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 387
Run from an Image The number of software applications that can be run at the same time on the same diskless client is related more to the client specification than to Neoware Image Manager. In particular it depends on client CPU power and client available memory. Neoware Image Manager has a side - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 388
disk caching on the server. • Use good quality Ethernet switches that can be configured to support flow control and that have enough buffers to hold large amount of data between 1000BT and 100BT networks. • Have enough RAM in the client (256MB or more). • Limit the client virtual memory size - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 389
Troubleshooting • If local Hard Drives are available to the clients, configure Windows so that its swap file is stored only on local HDs. Temporary folders can also be stored on local HDs. • Check that each client will have enough network bandwidth to transfer data from and to each server. - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 390
Troubleshooting 374 Recommended Network Configuration - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 391
Neoware Image Manager User Manual APPENDIX L Copyright Notices & License Terms Patents This appendix provides the copyright notices and license terms for software embedded in Neoware Image Manager components. Neoware Image Manager software suite is protected by a number of patents: EP1808763, - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 392
and/or other associated materials; 3 The copyright holder's name is not used to endorse products built using this software without specific written permission. DISCLAIMER This software is provided 'as is' with no explicit or implied warranties in respect of its properties, including, but not - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 393
Software Copyrighted by Lukas Gebauer Copyright Notices & License Terms Project: Delphree - Synapse 003.006.004 Content: HTTP client to endorse or promote products derived from this software without specific prior written permison. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 394
synapse/) Project: Delphree - Synapse 002.002.003 Content: SNTP client Copyright (c)1999-2003, Lukas Gebauer. All rights reserved. Redistribution endorse or promote products derived from this software without specific prior written permision. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 395
: See HISTORY.HTM from distribution package (Found at URL: http://www.ararat.cz/synapse/). Copyright (C) 1997-2003 Jordan Russell. All rights reserved. This software is provided "as-is," without any express or implied warranty. In no event shall the author be held liable for any damages arising from - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 396
Copyright Notices & License Terms 380 Third Parties Copyrights - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 397
Index Neoware Image Manager User Manual A access client images 59 ACPI considerations 115 troubleshooting 360 activating Windows products 118, 127 Active Cloner 271 clone directly to attached HD 273 clone to another Image Manager virtual HD 275 clone to network shared HD 274 command line options - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 398
16 local HD access 123 locating Image Manager server 317 MAC address 224 maximum attached to server 369 mPXELdr.bin 62 multiboot selection 68, 191, 235 naming 233 primary bootstrap loader file 62 renaming 348 server crash recovery 348 requirements 19 using Client Builder 40 volume use 79 writing - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 399
219 disable autocheck on startup 55 automatic updates 56 ChkDsk 55 daylight saving 56 Defrag 57 memory dumps 57 system restore 58 disk storage required on server 32 Index domain adding clients to 147, 159, 168, 174 client IP addresses 168 client names 159, 174 credentials 148 management 147 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 400
upgrade without re-installing software 113 I IEEE 1394 interface (FireWire) 360 image adding network boot device 87 Image Manager evaluation version 17 how it works 8 installing 19 licenses 15 limitations 369 overview 7 uninstalling 35 upgrading 289 Image Manager components Active Cloner 271 Client - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 401
Service Loader Setup 329 images accessing 59 adding new software 136 configuration file 65, 79 controlling use of 79 creating 39 CVol files 80 managing multiple remote servers 141 master HD for building 110 modifying configuration 136 nvdd configuration file 213 size 19 testing 54 troubleshooting - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 402
.exe 147 Neoware Virtual Disk 9 Neoware Virtual Disk Daemon 9 NeowareIMClientBuilder.exe 40 NetBIOS name 326 network adapters 358 adding boot device to an image 87 configuring for image access 59 installation requirements 19, 22 recommended configuration 372 requirements 22 troubleshooting 358, 363 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 403
drive support 104 server cluster of 14 DHCP 297 DHCP configuration 59 Image Manager configuration 32 disk storage required 32 file locations 32 how clients find 317 maximum attached clients 369 installation requirements 19, 20 license file 16 list of to contact 14 replacing 13 requirements 20 setup - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 404
Installer 293 TFTPDInstall.exe 293 third party software 375 timing 199, 218 troubleshooting 355 ACPI 360 booting 360 client accessing images 63 computer SIDs 368 global performances 362 IEEE 1394 interface (FireWire) 360 image access 63 NVDD server crash recovery 347 NVDD server temporary files 347 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 405
clients sharing 197 geometry 226 ID 195, 225 naming 193, 225 nvdd configuration file 213 properties 192, 193 restoring to actual HD 144 size of 194 smalldisk.vol 213, 214 storage 32 troubleshooting adding clients to 147 prefetcher 58 product activation 118, 127 user profiles 131 Windows service 329 - HP Neoware e140 | Neoware Image Manager 4.6 User Manual - Page 406
Index 390
-
1 -
2 -
3 -
4 -
5 -
6 -
7 -
8
-
9
-
10
-
11
-
12
-
13
-
14
-
15
-
16
-
17
-
18
-
19
-
20
-
21
-
22
-
23
-
24
-
25
-
26
-
27
-
28
-
29
-
30
-
31
-
32
-
33
-
34
-
35
-
36
-
37
-
38
-
39
-
40
-
41
-
42
-
43
-
44
-
45
-
46
-
47
-
48
-
49
-
50
-
51
-
52
-
53
-
54
-
55
-
56
-
57
-
58
-
59
-
60
-
61
-
62
-
63
-
64
-
65
-
66
-
67
-
68
-
69
-
70
-
71
-
72
-
73
-
74
-
75
-
76
-
77
-
78
-
79
-
80
-
81
-
82
-
83
-
84
-
85
-
86
-
87
-
88
-
89
-
90
-
91
-
92
-
93
-
94
-
95
-
96
-
97
-
98
-
99
-
100
-
101
-
102
-
103
-
104
-
105
-
106
-
107
-
108
-
109
-
110
-
111
-
112
-
113
-
114
-
115
-
116
-
117
-
118
-
119
-
120
-
121
-
122
-
123
-
124
-
125
-
126
-
127
-
128
-
129
-
130
-
131
-
132
-
133
-
134
-
135
-
136
-
137
-
138
-
139
-
140
-
141
-
142
-
143
-
144
-
145
-
146
-
147
-
148
-
149
-
150
-
151
-
152
-
153
-
154
-
155
-
156
-
157
-
158
-
159
-
160
-
161
-
162
-
163
-
164
-
165
-
166
-
167
-
168
-
169
-
170
-
171
-
172
-
173
-
174
-
175
-
176
-
177
-
178
-
179
-
180
-
181
-
182
-
183
-
184
-
185
-
186
-
187
-
188
-
189
-
190
-
191
-
192
-
193
-
194
-
195
-
196
-
197
-
198
-
199
-
200
-
201
-
202
-
203
-
204
-
205
-
206
-
207
-
208
-
209
-
210
-
211
-
212
-
213
-
214
-
215
-
216
-
217
-
218
-
219
-
220
-
221
-
222
-
223
-
224
-
225
-
226
-
227
-
228
-
229
-
230
-
231
-
232
-
233
-
234
-
235
-
236
-
237
-
238
-
239
-
240
-
241
-
242
-
243
-
244
-
245
-
246
-
247
-
248
-
249
-
250
-
251
-
252
-
253
-
254
-
255
-
256
-
257
-
258
-
259
-
260
-
261
-
262
-
263
-
264
-
265
-
266
-
267
-
268
-
269
-
270
-
271
-
272
-
273
-
274
-
275
-
276
-
277
-
278
-
279
-
280
-
281
-
282
-
283
-
284
-
285
-
286
-
287
-
288
-
289
-
290
-
291
-
292
-
293
-
294
-
295
-
296
-
297
-
298
-
299
-
300
-
301
-
302
-
303
-
304
-
305
-
306
-
307
-
308
-
309
-
310
-
311
-
312
-
313
-
314
-
315
-
316
-
317
-
318
-
319
-
320
-
321
-
322
-
323
-
324
-
325
-
326
-
327
-
328
-
329
-
330
-
331
-
332
-
333
-
334
-
335
-
336
-
337
-
338
-
339
-
340
-
341
-
342
-
343
-
344
-
345
-
346
-
347
-
348
-
349
-
350
-
351
-
352
-
353
-
354
-
355
-
356
-
357
-
358
-
359
-
360
-
361
-
362
-
363
-
364
-
365
-
366
-
367
-
368
-
369
-
370
-
371
-
372
-
373
-
374
-
375
-
376
-
377
-
378
-
379
-
380
-
381
-
382
-
383
-
384
-
385
-
386
-
387
-
388
-
389
-
390
-
391
-
392
-
393
-
394
-
395
-
396
-
397
-
398
-
399
-
400
-
401
-
402
-
403
-
404
-
405
-
406
 |
 |
Neoware Image Manager 4.6
USER MANUAL