Neoware Image Manager 4.
© 2007 by Neoware, Inc. 3200 Horizon Drive, King of Prussia, PA 19406 USA Tel.: +1-610-277-8300 Fax: +1-610-771-4200 Email: info@neoware.com Web: http://www.neoware.com This manual is copyrighted by Neoware, Inc. All rights are reserved. This document may not, in whole or in part, be copied, photocopied, reproduced, translated, or reduced to any electronic medium or machine-readable form without prior consent, in writing, from Neoware, Inc.
Neoware Image Manager User Manual Table of Contents CHAPTER 1 Introduction 1 What is Neoware Image Manager? About This Manual 2 Conventions 2 Overview of Contents 3 CHAPTER 2 1 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 12 Normal Mode 12 Volatile Mode 12 Persistent Mode 13 Administrator Mode 13 High Availability & Fast System Recovery 13 Stateles
Table of Contents Using a Cluster of Servers 14 Technical Notes 14 Neoware Image Manager Licenses 15 Server Licenses 16 Client Package Licenses 16 Licenses Explained 16 Evaluation Version 17 CHAPTER 3 Installing Image Manager Components 19 System Requirements 19 Client Requirements 19 Server Requirements 20 Network Requirements 22 Installation Summary 23 Running the InstallShield Wizard 24 Image Manager Server Configuration 32 Disk Storage Required on Server 32 File Locations on the Server 32 Uninstalling
Table of Contents DHCP Server Configuration Client Configuration 62 Troubleshooting 63 CHAPTER 6 61 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 Adding a Volume from Another Configuration File 73 Changing a Volume’s Write Mode 75 Modifying a Configuration File Currently Running 75 CHAPTER 7 Controlling the Use of Images & Volumes 79 The Image Configuratio
Table of Contents CHAPTER 9 Building a Virtual Hard Disk to Boot any PC or TC 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 Devices 112 Additional Uses for Neoware UbiBoot 113 Creating a Windows Installation that can Run Unknown Hardware 113 Creating a Windo
Table of Contents CHAPTER 11 Windows Product Activation 127 Introduction 127 Product Activation Procedure CHAPTER 12 128 Windows User Profiles 131 Domain Roaming Profiles 131 "Local" Roaming Profiles 132 Folders Redirection 134 CHAPTER 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
Table of Contents Adding a New Client to the Domain 168 Do I Need to Reboot? 169 Storing Domain Credentials in the System Partition 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 Image Manager Console 181 The Toolbar 183 The File Menu 184 The Edit Menu 184 The Tools Menu 185 The View Menu 186 The Help Menu 18
Table of Contents The Network Tab 205 The Authorized Subnets Tab 206 The Nvdd Manager 207 Merging Configuration Files 209 Password for Remote Administration 210 CHAPTER 17 The NVDD Configuration File 213 Introduction 213 The nvdd.smalldisk.vol.
Table of Contents Client Naming 233 Setting Client Name using NVD Protocol 233 Updating Client Name from Client 234 Enabling Client MultiBoot 235 Example nvdd.
Table of Contents Cloning a Partition 272 Example Cloning Procedures 273 Cloning Directly to an Attached Hard Disk 273 Cloning to a Network Shared Hard Disk 274 Cloning to Another Image Manager Virtual Hard Disk 275 Expert Options 276 Disable Options 276 Boot Options 277 Command Line Options 277 Error Messages 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 Machin
Table of Contents Troubleshooting APPENDIX B 291 The TFTPD Installer 293 Introduction 293 Using the TFTPD Installer 294 Managing the TFTPD Service 295 APPENDIX C Configuring the DHCP Server 297 Introduction 297 Before Installing DHCP Server Configuring the Server 298 Configuring DHCP 301 DHCP Reservations 312 Related Resources 315 APPENDIX D 297 DHCP Reference 317 How Clients Locate the Image Manager Server dhcpd.
Table of Contents APPENDIX F NVDD Reference 337 Introduction 337 Command Syntax 337 Verbose Mode 337 Port Number 338 Configuration File 338 Log File 338 No Lock File Check 338 APPENDIX G NVD.SYS Reference 341 Introduction 341 Parameters 341 IP Address 341 APPENDIX H File Transfer 345 Introduction 345 Root Folder for File Transfers APPENDIX I 345 NVDD Temporary Files 347 The NVDD Configuration File 347 The nvdd.conf.
Table of Contents Issues 357 Network Adapters 358 VIA Rhine Family 358 Servers with Several Network Adapters 359 Volumes 359 Multi-Volume Windows 2000 Clients 359 ACPI 360 Stand By & Hibernation 360 Shutdown & Reboot 360 NVD.
Table of Contents Maximum Number 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 Software Copyrighted by Lukas Gebauer 377 Software Copyrighted by Jordan Russell 379 Index 381 xv
Table of Contents xvi
Neoware Image Manager User Manual CHAPTER 1 Introduction This chapter introduces Neoware Image Manager and describes the scope of this User Manual. What is Neoware 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.
Introduction You can think of Neoware Image Manager as a network storage product (a SAN product) that makes it possible to boot several clients off a single virtual drive hosted on the server. About This Manual This manual describes how to install and use Neoware Image Manager version 4.6. It assumes that you are familiar with Windows and server operating system administration, as well as DHCP/BOOTP and TFTP server configuration.
Introduction Overview of Contents This manual is divided into the following chapters and appendices: Chapter 1: Introduction Introduces Neoware Image Manager and describes the scope of this User 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.
Introduction Chapter 10: Managing Local Hard Disk Access Describes how to enable or disable client access to local hard disks. Chapter 11: Windows Product Activation Describes how to activate Windows products for Image Manager clients. Chapter 12: Windows User Profiles Describes how to configure your Neoware Image Manager system so that clients can use Windows user profiles.
Introduction Chapter 19: The mPXELdr Configuration File Describes the mPXELdr configuration file and the settings that can be specified in it. Chapter 20: Neoware Active Cloner Describes how to use Neoware Active Cloner to clone the current system partition to another partition. Chapter 21: Virtualized Environments Describes how to use Neoware Image Manager with virtual machines, which can run Image Manager clients or server.
Introduction Appendix H: File Transfer Describes issues relating to the file transfer capabilities of Image Manager. Appendix I: NVDD Temporary Files Describes issues relating to temporary files created by the nvdd process. Appendix J: Boot Process Comparison Provides a side-by-side comparison between a HDDbased boot process and the Neoware Image Manager based boot process. Appendix K: Troubleshooting Provides help on how to overcome problems when using Neoware Image Manager with various systems.
Neoware Image Manager User Manual CHAPTER 2 Overview of Neoware Image Manager This chapter provides a brief description of how Neoware Image Manager works. Software Suite Components Neoware Image Manager consists of the following main components: • Neoware Image Manager Server - Allows the remote boot and central management of Windows 2000, XP, XP Embedded, XP Home, XP Pro desktops (diskless PCs or flashless thin clients) from Windows/Linux/FreeBSD servers.
Overview of Neoware Image Manager How Neoware Image Manager Works Neoware Image Manager enables you to quickly build and distribute virtual hard disk images (volumes) to diskless PCs and clients. The procedure is very straightforward and can be summarized as follows. First of all you would install then run Neoware Image Manager Server on a server, then, on another PC (a "client" PC), install and run Client Builder on a hard disk containing the required Windows operating system and software configuration.
Overview of Neoware Image Manager always boot from the originally defined configuration. User profiles (desktop, shortcuts, favourites, bookmarks, application settings, etc.) may be stored on a remote server and presented according to which user logs into the desktop device. This enables user personalization based on Windows User Profiles while desktops are not dedicated to any one user.
Overview of Neoware Image Manager mPXELdr sends an “init” packet to the server to retrieve information about the bootable virtual drives available to the client that runs mPXELdr. If several bootable virtual drives are available, mPXELdr displays a boot menu. The users can then choose the drive to be used as the system (boot) drive. mPXELdr then loads and runs the MBR (Master Boot Record) of the virtual system drive, just as the BIOS loads and runs the MBR of an actual HDD.
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 UbiBoot utilities are used whenever you want to add a new desktop or upgrade hardware.
Overview of Neoware Image Manager Client Writing Modes Image Manager allows administrators to customize how clients write data to virtual volumes. The main writing modes are described below. Refer to the chapter “Controlling the Use of Images & Volumes” on page 79 for a complete description of all the modes available. Normal Mode Normal mode enables a client user to install applications and make system changes without modifying the original hard disk image file.
Overview of Neoware Image Manager Persistent Mode Persistent mode is similar to Volatile mode except it enables you to retain some customization of the volume for each client, separate from the hard disk image. For example, to retain Windows XP activation data customized for each computer. Note: Persistent mode uses the same CVol files as in Normal mode, so if the common hard disk image file is modified, all per-client customizations will be discarded.
Overview of Neoware Image Manager Servers List Neoware Image Manager clients use an initialization file that the Image Manager boot loader loads and interprets to determine the server to contact from a list of servers. Neoware Image Manager clients can also use a specific DHCP option (DHCP Option 132) to determine the server to contact from a list of servers. Neoware Image Manager boot loader builds a list of the servers to contact from the initialization file and from DHCP Option 132.
Overview of Neoware Image Manager • There is no theoretical limitation to the number of clients that can be connected to a single Neoware Image Manager server, as long as 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 perfor- mance requirements of software applications running on the clients.
Overview of Neoware Image Manager Server Licenses A Server License file is required. There can be only one server license file and the server license file must be named lanpcsrv.lic. Server license files contain the number of clients and the expiration date(s). Client Package Licenses Client Package License files are optional. There can be up to 99 Client Package License files. Client Package License files must be named lanpccltNN.lic (where NN is a number between 01 and 99).
Overview of Neoware Image Manager Evaluation Version If you use an evaluation version of Neoware Image Manager, there are some limitations with the product. • It is limited to a certain date. The expiration date is displayed in Neoware Image Manager Server logs when the server module starts. The evaluation product cannot be used legally after this date without Neoware’s written consent. • It is limited to a certain maximum number of client computers.
Overview of Neoware Image Manager 18 Evaluation Version
Neoware Image Manager User Manual CHAPTER 3 Installing Image Manager Components This chapter describes how to install Neoware Image Manager components on the server and client computers. System Requirements Client Requirements • PXE 2.x enabled. • Any CPU supported by the operating system to be downloaded from the Neoware Image Manager server. • Main memory: 128 MB minimum, 256+ MB recommended. • Network card (100 Mb/s recommended).
Installing Image Manager Components partition on the server, the partition size cannot be larger than 4 GB because FAT32 does not support files larger than 4 GB. Listed below are the typical maximum file sizes for common file systems. NTFS File size limited only by size of server volume. FAT Maximum file size is 2 GB. FAT 32 Maximum file size is 4 GB. Ext-2 Maximum file size is 2 GB Ext-3 Maximum file size is 2 TeraBytes (if LFS support is completely implemented).
Installing Image Manager Components • Hard drive capacity: 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 have such a version and you need Linux/FreeBSD server support, contact your Neoware representative.
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 server, which are usually available from the NIC manufacturer web site. These drivers are usually more efficient than the drivers shipped with Windows XP/2000.
Installing Image Manager Components you are using a Microsoft DHCP server, refer to the appendix “Configuring the DHCP Server” on page 297 for a step-by-step installation procedure. A configurable TFTP service must be installed and properly configured to serve boot files to PXE PROM. For example, MSTFTPD for Windows 2000/2003 Server, 3Com freeware tftp server for Windows systems, tftpd daemons shipped with Linux and Unix, freeware TFTPD32. A Samba server can be useful if you use Linux/ FreeBSD server.
Installing Image Manager Components Running the InstallShield Wizard You will need to run the InstallShield Wizard on the server (or a Windows PC if the server is running Linux or FreeBSD - see note below) and then again on the client computer to install the relevant Neoware Image Manager software components.
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.
Installing Image Manager Components 26 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.
Installing Image Manager Components 7 Enter the User Name and Company Name and specify if the application is to be installed for 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.
Installing Image Manager Components 8 Select the type of installation required from the following options: Server Installation (Windows) Select this option if you are installing Neoware Image Manager on the Windows server that will host your images.
Installing Image Manager Components Console Select this option if you would like to install only the Neoware Image Manager Console on a computer running a Windows OS. UbiBoot Extractor Select this option if you are installing UbiBoot Extractor on a client machine that needs to be added to the current capabilities of existing images.
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.
Installing Image Manager Components Note that if the destination device does 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 Configuration” on page 32.
Installing Image Manager Components Image Manager Server Configuration Disk Storage Required on Server The Image Manager server must have a partition containing enough free space to contain all the virtual hard disks required by clients. A virtual hard disk consists of a hard disk image file plus a CVol (Client Volume OverLay) write cache file that will contain all data written by the clients. The contents of the CVol files can be retained or deleted when the clients reboot.
Installing Image Manager Components C:\Program Files\Neoware\Image_Manager_4.6 If your server runs Linux or FreeBSD OS, the required server module and server tools are stored in the following subdirectory of the target directory in which the Neoware Image Manager archive was decompressed: Server\Linux or Server\FreeBSD Server or Server with Console installation: Only Windows versions of the server module (NVDD.
Installing Image Manager Components This completes 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 system: ./nvdd -c nvdd.smalldisk.vol.conf You should see various messages similar to that shown in the illustration below.
Installing Image Manager Components Uninstalling Neoware Image 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 uninstall the components and configuration performed during Image Creation.
Installing Image Manager Components 36 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.
Installing Image Manager Components 5 When the InstallShield Wizard has completed removing the software, click Finish.
Installing Image Manager Components Undoing Client Builder Changes on an HDD-based Configuration It is possible to undo the changes that Neoware Image Manager Client Builder has performed on an HDD based configuration, in case the creation process did not complete smoothly or was not closed neatly. To undo changes: 1 Open a command prompt and navigate to the folder where the file NeowareIMClientBuilder.exe is installed (usually C:\Program Files\Neoware\Image Manager 4.6\Client.
Neoware Image Manager User Manual CHAPTER 4 Creating a Client Image This chapter describes how to use Client Builder to create a client image on the Image Manager server. Introduction The Client Builder component of Neoware Image Manager makes a complete image of a system partition (hard disk) based on the size of the partition, not its contents. It is recommended that the size of the partition is adjusted once all software has been installed (using PowerQuest Partition Magic, for example).
Creating a Client Image Using Client Builder The following procedure assumes that you have already installed the Client components of the Neoware Image Manager on the hard disk drive that will be used to create the client image. You must be logged on as a user with administrator privileges. 1 Before running Client Builder you must 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.
Creating a Client Image The Client Builder dialog will be displayed. 6 If your server’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 packets.
Creating 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. Clicking the Find NVD servers button will enable you to search for the required server (using broadcast packets). Clicking the Advanced settings button will display additional options.
Creating a Client Image 9 Read the license agreement then click Accept to continue. 10 A list of available network interface cards (NICs) will be dis- played. This enables you to specify which NIC(s) to use to boot the client on Neoware Image Manager. All the available NICs are selected by default. Check the Expert box to enable the tick box settings next to the listed NICs to be changed.
Creating a Client Image If your client OS is Windows XP SP2 and you have Windows XP Security Center enabled, you may be prompted that Automatic Windows Updates have been disabled. This is normal if you did not change Advanced Settings in the first step. You should not restore Automatic Windows Update (or any other Windows settings) before the image has been created. Client Builder will restore the original settings after it has completed.
Creating a Client Image Using Client Builder 45
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.
Creating a Client Image You can also right-click on My Computer and select Manage/ 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). Disk management Wait for the Found New Hardware wizard to finish the installation, then click Next.
Creating a Client Image 14 The Client Builder dialog is displayed with the volume name and server address automatically set by the system. If you need to change the entries in this dialog, check the Expert box to enable the options. Note that the settings in the right half of the dialog use the internal protocol between Client Builder and the NVDD server module to create the image.
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 as the source of the image. Administrators using XP Pro booted from an actual hard disk drive will then, usually, create an image of their system (first) partition.
Creating a Client Image Important: When you create the image file on the server, if the image creation takes more than 5 minutes per gigabyte of partition, this implies that the global performance of your system is not adequate. You may then have problems when using diskless clients, especially when using several clients at the same 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.
Creating a Client Image Client Builder has created an image that contains exactly the same data as stored on your original hard disk drive, including the disk signature. Windows may not be able to reliably handle two drives that have the same signature, nor detect such a situation in a manner that suits your requirements.
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 signature: Click Yes if you want to change the signature on the local drive.
Creating a Client Image 19 Click OK. In order to restore the original configuration of your client OS, Windows needs to be stopped. This is required in order to completely remove all the drivers installed previously. 20 Click Yes to shutdown the client computer. 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.
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.vol.conf 2 54 Testing the Image Check that the messages displayed are OK. If any error messages are displayed, relaunch NVDD with the extra parameter -vall to generate a complete log.
Creating a Client Image Advanced Client Builder Options The Client Builder includes additional options for more advanced control over its operation. You can display these options by clicking the Advanced settings button in the initial dialog displayed when you run Client Builder. You should not change the default settings in this dialog, except for the Virtual Memory settings, unless you are fully aware of the effect the changes will have.
Creating a Client Image Disable Windows Updates Default: Checked This option prevents Windows from using the Automatic Updates features. You should NOT uncheck this option unless you only use volumes mounted in Admin mode (i.e. a unique volume for each client computer). If Automatic Updates are allowed when volumes are not mounted in Admin mode, they could make too many changes to the volume and cause the CVol write cache files on the server to become too big.
Creating a Client Image system, such as an NTP server. For example, you can tweak the W32Time service according to the following document: 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.
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 the system volume is opened in a protected mode, writes to this volume are not kept after a reboot.
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 Before clients can access and boot from images on the Neoware Image Manager server, your TFTP and DHCP server must be configured to serve the Neoware Primary Bootstrap Loader file mPXELdr.bin to clients.
Enabling Clients to Access Images 4 Copy the file mPXELdr.bin from the Server directory of the Neoware Image Manager distribution package, into the directory specified by the registry entry above. (Neoware Image Manager includes a utility called TFTPD Installer that helps you to do this. Refer to the appendix “The TFTPD Installer” on page 293 for details.) Note: You can use any standard RFC compliant TFTP service. The freeware TFTPD32 (http://www.jounin.
Enabling Clients to Access Images DHCP Server Configuration Configure your DHCP server so that it serves the file mPXELdr.bin to the clients. (Refer to the DHCP , TFTP and PXE documentation for details.) If you use Microsoft Windows DHCP Server on a Windows 2000/ 2003 server, refer to the appendix “Configuring the DHCP Server” on page 297. The DHCP/BOOTP next-server entry must be set to the TFTP server’s IP address.
Enabling Clients to Access 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 Primary Bootstrap Loader file mPXELdr.bin is served to the client. The client then executes Neoware Primary Bootstrap Loader.
Enabling Clients to Access Images Troubleshooting If you experience any problems when the client boots, such as a blue screen or the client freezing, please do the following: 1 Power off the client. Wait for 1 minute. Power on the client again. 2 Check the NVDD server messages. 3 Power Off the client. Open its case and reconnect the original system boot drive to the IDE or SCSI and power cables, then boot the client from it.
Enabling Clients to Access Images 64 Troubleshooting
Neoware Image Manager User Manual CHAPTER 6 Assigning Volumes to Clients This chapter describes how to use the Image Manager Console to assign volumes to clients. Introduction This chapter describes how to use the Image Manager Console to assign volumes to clients. "Volume" is the name of the Virtual Disk Drive logical object. For a complete description of all the options available using the Console, refer to the chapter “The Image Manager Console” on page 181.
Assigning Volumes to Clients To open a Neoware Image Manager Server configuration file in the Console, display the File menu and select Open. Neoware Image Manager Server configuration files have the file extension .conf. You can also open a configuration file actually in use on a remote server by clicking the nvdd button in the tool bar. Refer to the chapter “The Image Manager Console” on page 181 for details.
Assigning Volumes to Clients its group. You can easily select or deselect volumes 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 Console can refer to a collection of computers on a subnet, not just a single workstation, connected to the Image Manager server.
Assigning Volumes to Clients Typical subnet masks are: 32 This is the subnet mask 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.168.0.1 and 192.168.0.254. 16 65534 IP addresses (a complete class B). For example, 172.16.0.0/16 means all the IP addresses between 172.16.0.0 and 172.16.254.254. 0 Is usually only used with IP address 0.
Assigning Volumes to Clients The drop-down list box will list all the bootable volumes currently associated with the group. Select the name of the default volume to boot from then click OK. Note that if there are two or more bootable volumes associated with a group, when you switch on a client that belongs to that group, it will display a list of the volumes available to boot from.
Assigning Volumes to Clients Creating or Modifying a Volume You can create a new volume by right-clicking in the Volume panel and selecting Create Volume in the pop-up menu. You can modify an existing volume by double-clicking on the Volume item in the Volume panel, or by right-clicking on this item and selecting Properties. A dialog consisting of several tabs is displayed. The General tab enables you to specify a name for the volume that will be used to identify it in the Console.
Assigning Volumes to Clients Cylinders: (size of volume image (bytes) / (512 * heads * sectors)) + 1 Note that Client 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.
Assigning Volumes to Clients The CVOL tab enables you to specify a different directory for this volume’s CVol files if they are not to be stored in the general CVol directory. Note that the file paths are relative to the location of the running nvdd server. This is particularly important to remember when you modify the configuration of a remote Image Manager server (then using the browse button is irrelevant).
Assigning Volumes to Clients The Allowed Computers tab enables you to specify which computers are allowed to access this volume, and which computers are allowed in Admin mode. When you have finished specifying volume settings, click the OK button and the new volume name will appear in the Console Volumes list. You can now assign this volume to groups of computers.
Assigning Volumes to Clients Load volumes from file button to list the names of the volumes defined in the configuration file. Select the volume you want to copy to the current configuration file then click Add. The volume will appear in the Console Volumes list. Repeat for each volume you want to 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.
Assigning Volumes to Clients Changing a Volume’s Write Mode You can quickly change the write mode of a volume. Just doubleclick on the name of the volume to display the Volume Properties dialog, then click on the Parameters tab. Change the Volume Mode (or Special clients) settings as required and click OK. (For a description of the writing modes, refer to the section “Volume Write Modes” on page 82.
Assigning Volumes to Clients To connect to an Image Manager server, enter the server’s IP address, port number (leave 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 runs on the same PC that runs the Console, you can enter 127.0.0.
Assigning Volumes to Clients The name of the configuration file currently being used by the remote server is also displayed. You can edit this configuration file within the Nvdd Manager dialog by clicking the Open conf file from server button. When you have finished, Save the file. A message should indicate that the 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.
Assigning Volumes to Clients 78 Modifying a Configuration File Currently Running
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 corresponding configuration file that allows you to control how the image is used by clients. The configuration file is stored in the same directory as the image file and has the name nvdd..conf.
Controlling the 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 based on settings in the hard disk image configuration file.
Controlling the Use of Images & Volumes Location of CVol Files CVol files are stored in the same directory as the NVDD server module by 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 volume, thus on a "per-volume" basis. This will take precedence over the general CVol directory setting.
Controlling the Use of Images & Volumes CVol file created for this volume can grow to using the Image Manager Console. Right-click on the Volume name, select Properties in the pop-up menu, then click the CVOL tab in the dialog. The CVOL Size setting determines the total number of megabytes that can be used by each CVol data file. For more information on setting the CVol maximum size and what happens when the file becomes full, refer to the section “Maximum Size of CVol Files” on page 221.
Controlling the Use of Images & Volumes The Volume Mode settings enable you to specify the standard writing mode to be used when a client mounts the volume, while the Special Clients options enable you to specify a different writing mode for individual clients. You can also specify a unique Volume ID number, but you should let Image Manager generate it automatically. There are two main write modes called Admin and CVolwrite. The CVolwrite mode consists of three submodes: Normal, Volatile and Persistent.
Controlling the Use of Images & Volumes write cache file and will not be lost when the volume is re-mounted. This enables clients to have different configurations while sharing the same image file. The CVol files can be sent to remote sites where an identical reference hard disk image file exists. This makes deployment of updated images to remote sites easier because you 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.
Controlling the Use of Images & Volumes Note that if 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.
Controlling the Use of Images & Volumes 86 Volume Write Modes
Neoware Image Manager User Manual CHAPTER 8 Adding Network Boot Devices to an Image This chapter describes how to add bootable network card details to an image so it can be remote booted on different machines. Overview Neoware UbiBoot is a suite of tools that enable you to reduce the number of images required for a fleet of heterogeneous client hardware, making image management easier.
Adding Network Boot Devices to an Image ‘Normal’ (an image with a CVol file that will still be accessible at the next reboot - the common image file itself must then be modified using the CVolMerge tool), or ‘Admin’ (we recommend that you create a backup copy of the image before making changes to it in Admin mode). The UbiBoot Inserter dialog lists the descriptions of any bootable NIC data files stored in the UbiBootData directory to enable you to select the one to insert in the image.
Adding Network Boot Devices to an Image Before Using the UbiBoot Extractor & UbiBoot Inserter Tools The data file created by UbiBoot Extractor must be stored in a workspace that is accessible by both source and destination machines. The workspace can be a USB key, a share on a networked machine, or any other storage that can be accessed by both machines. The user must have enough rights to create both directories and files. We recommend leaving the UBExtract.exe and UBInsert.
Adding Network Boot Devices to an Image Extracting Boot Device Details 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 store the data in a file. 1 Select Start > Neoware > Image Manager > Tools > UbiBoot Extractor, or run the UBExtract.
Adding Network Boot Devices to an Image Clicking on a device in the list will display a summary of its technical characteristics, such as its descriptive name and manufacturer, the OS of the machine containing the device (in this case, the OS currently running on the machine), 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 where UBExtract.
Adding Network Boot Devices to an Image Note that if the device details have already stored as a file in the UbiBoot Extractor directory, the following dialog will be displayed. Clicking Cancel will cancel the export operation. Clicking OK will overwrite the information currently stored for this NIC with the latest information. This could be useful if a more recent revision of the NIC drivers have been installed, and the user wants to ensure that the latest version is inserted in the destination image.
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&REV_11-4&111a1fd8&0&00E0.Dev. You can rename this file but you must keep the .DEV extension. 6 The following dialog will be displayed when the operation has been completed successfully.
Adding Network Boot Devices to an Image IMPORTANT NOTE Starting with version 1.2 of the UbiBoot Extractor/Inserter programs, the original date and time of the driver files (typically the .INF and .SYS files) are preserved across extraction and insertion. Previous versions did not preserve the original date and time, and the files were marked as last modified at the time they were inserted. The .DEV files stored in the UbiBoot Extractor/Inserter repository are fully compatible between the 1.2 and pre-1.
Adding Network Boot Devices to an Image Inserting Boot Device Details into an Image The following procedure will insert the details of a bootable network device in a 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 in which the bootable NIC data is to be inserted. You must use an account that provides full administrative rights.
Adding Network Boot Devices to an Image is too long for it to be displayed entirely, just leave your mouse pointer on it for a few seconds. A ’hint’ box will be displayed with the complete path. In the device list, any device that was extracted from a machine environment that is not strictly compatible with that of the current machine will appear in red letters.
Adding Network Boot Devices to an Image 3 Click the Insert button.
Adding Network 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.
Adding Network Boot Devices to an Image If the device files that you are about to insert into the NVD image are older than the device files in the current (destination) machine, warning and confirmation messages similar to the following will appear: This message might be displayed twice, once for the device file and once for the device .SYS file. Note that if the device already in the machine was created using a version of UbiBoot Extractor/Inserter earlier than 1.
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 processor. 6 Click the Exit button to leave the program. Note: It is possible (although completely useless and strongly discouraged) to inject the same NIC information multiple times on the same machine. This only results in filling the system configuration of the destination machine with unnecessary data.
Adding Network Boot Devices to an Image Testing the 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: 1 If you were using CVolwrite/Normal mode on the destination machine, you might: • rename or copy the CVol files to associate them with the source machine.
Adding Network Boot Devices to an Image itself using the CVolMerge tool and, optionally, the CVolComtool (if you intend to deploy the CVol file to remote locations, for instance). pactor The image has now been enhanced and you can now switch back to CVolwrite/Volatile mode.
Neoware Image Manager User Manual CHAPTER 9 Building a Virtual Hard Disk to Boot any PC or TC This chapter describes how to use Neoware UbiBoot to build a virtual hard disk that can boot a range of PC and TC configurations. What is Neoware UbiBoot? Neoware UbiBoot is a suite of tools that enable you to reduce the number of images required for a fleet of heterogeneous client hardware, making image management easier.
Building a Virtual Hard Disk to Boot any PC or TC • Create a hardware-independent Windows installation containing operating system, hardware drivers and applications which can be used on any hardware configuration. The hardware will be detected and configured when Windows boots. • Create a Windows installation containing all the hardware drivers for a variety of PC configurations, then build a master hard disk image for deployment.
Building a Virtual Hard Disk to Boot any PC or TC • Start with a freshly formatted hard disk containing a clean instal- lation of Windows. Note that Pre-installed Windows setups often embed proprietary components that may not be compatible with all the hardware configurations your Windows installation may need to run on. Pre-installed Windows setup should not be used as the base for a Neoware UbiBoot-enabled configuration.
Building a Virtual Hard Disk to Boot any PC or TC Running Neoware UbiBoot The following basic 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 C: (partition size should not exceed 10 GB), and an image of that partition has been created using Client Builder.
Building a Virtual Hard Disk to Boot any PC or TC 5 Click the Go! button. 6 An end-user License Agreement dialog will be displayed. Read the agreement and, if you agree to the terms, select I accept then click the Go On button. UbiBoot will install and 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.
Building a Virtual Hard Disk to Boot any PC or TC Note that you can also run the executable file (NIMClonerGUI.exe) “directly” as long as the required files (NIMCloner.exe, NRdmpSvc.exe and VVSAToolsDll.dll) are stored in the same directory as the executable file. Select as the target the hard disk drive that you will be using to detect the new hardware whose support is to be added to the operating system on the virtual disk drive. Keep the default settings in Active Cloner.
Building a Virtual Hard Disk to Boot any PC or TC HDD now has a UbiBoot-enabled Windows installation in its system partition. 9 Connect the target HDD to the platform whose hardware is to be detected in order to add support for it. 10 Switch on the PC or TC so that it boots off the target HDD. Win- dows will automatically detect the new hardware configuration and may ask you to provide driver media (CD-ROM) or reboot the PC or TC - do so when prompted.
Building a Virtual Hard Disk to Boot any PC or TC A hard disk image is created by running Client Builder on any of the clients that can be booted from the target HDD, as described in the chapter “Creating a Client Image” on page 39. If in the future you need to add or change a client configuration in the hard disk image, you may need to transfer the image to an actual IDE hard disk to enable Windows to recognise the new client hardware configuration.
Building a Virtual Hard Disk to Boot any PC or TC Detecting New Hardware You must run Neoware UbiBoot each time you want to detect new hardware. If you don’t run Neoware UbiBoot just before connecting the UbiBoot enabled HD to the new hardware, Windows may not be able to start correctly (BSOD, reboot…) and then it won’t be able to detect the new hardware.
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 cases you can perform the following procedure: 1 Right-click on My Computer and select Properties. 2 Click on the Advanced tab. 3 Click on Environment Variables.
Building a Virtual Hard Disk to Boot any PC or TC Additional Uses for Neoware UbiBoot Creating a Windows Installation that can Run Unknown Hardware Neoware UbiBoot enables you to create a Windows installation that can be run on unknown hardware. This can then be used as a hardware independent pre-installed and preconfigured Windows installation (containing Windows System and applications). The hardware will be detected and configured when Windows boots on each different hardware.
Building a Virtual Hard Disk to Boot any PC or TC • Advanced Configuration and Power Interface (ACPI) PC HAL, ACPI PIC (HALACPI.DLL) • ACPI Uniprocessor PC HAL, ACPI APIC UP (HALAACPI.DLL) • ACPI Multiprocessor PC HAL, ACPI APIC MP (HALMACPI.DLL) Usually there is an ascending compatibility between HALs. For instance, Standard PC HAL is the most compatible HAL. If your Windows installation uses Standard PC HAL, when it is UbiBootenabled it should be able to boot ACPI computers etc.
Building a Virtual Hard Disk to Boot any PC or TC Mixing ACPI & Non-ACPI Computers Advanced Control and Power Interface (ACPI) is considered by Windows 2000/XP/2003 OS as the root-most device in a PC architecture. A Windows 2000/XP/2003 installation that was made for an ACPI enabled computer will not be able to boot a non-ACPI computer, even if Neoware UbiBoot has been applied to the system HD.
Building a Virtual Hard Disk to Boot any PC or TC Windows, you can disable ACPI in your PC BIOS setup before you install Windows. You can also press the F5 key during the first part of the Windows installation (when you can see Press F6 if you need to install a SCSI or RAID controller). Then select Standard PC as the PC type for your Windows installation, or the specific HAL you want to use. Note: Non-ACPI installations of Windows can boot ACPI computers. The opposite is not true.
Building a Virtual Hard Disk to Boot any PC or TC 11 Click Finish then Close. 12 Reboot the computer. 13 Let Windows re-detect the hardware (detection may not occur). The HAL used by the Windows installation on the system drive (either HDD or virtual drive) is now the one you just selected.
Building a Virtual Hard Disk to Boot any PC or TC Windows Product Activation When changing the hardware of a Windows system that needs to be activated (Windows XP, Microsoft Office XP, etc.), you may need to re-activate the product. It is recommended that you use VLA (Volume License Agreement) editions of the products. VLA editions do not need to be activated. If VLA editions are not available, you may have to enter each PC’s own product serial key in order to re-activate.
Building a Virtual Hard 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 UbiBoot and Microsoft SysPrep may be used together. SysPrep will not overwrite what UbiBoot has done. UbiBoot Expiry Date The UbiBoot expiry date, if any, only affects the GUI application that runs when you apply Neoware UbiBoot. It has no effect on the Windows installations you have created using UbiBoot.
Building a Virtual Hard Disk to Boot any PC or TC • Your client can use at least one of the following protocols: HTTP protocol using port 80, either directly or through a proxy server. SNTP protocol to connect to NTP servers outside your LAN. This protocol uses UDP port 123. If you are behind a network address translator, you may need to configure your network address translator ports redirection for this purpose.
Building a Virtual Hard Disk to Boot any PC or TC After I applied Neoware UbiBoot successfully, Windows detected my new hardware and is running correctly but is very slow and reacts as if it was overloaded. There might be a process that is using a lot of system resources. Open the Task Manager, click on the Process tab, check the box Show processes from all users, sort the process by CPU occupation and check if there is a process other than System Idle Process that is using the CPU intensively.
Building a Virtual Hard Disk to Boot any PC or TC After moving an UbiBooted HDD that was made for an AMDbased Windows installation to an Intel-based computer, the Intelbased computer cannot boot. The computer 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.
Neoware Image Manager User Manual CHAPTER 10 Managing Local Hard Disk Access This chapter describes how to enable or disable client access to local hard disks. Introduction Neoware Image Manager clients can be customized in order to enable or disable access to local hard disks. This is achieved using the Local HD Manager wizard LocalHDManager.exe.
Managing Local Hard Disk Access 2 Backup the HD image on the server. 3 Modify the relevant nvdd configuration (using Neoware Image Manager Console or a text editor) so that the virtual volume will be opened in Admin mode. 4 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). 5 Boot ONE client. 6 Log on this client using an Administrator Account.
Managing Local Hard Disk Access Enable delayed (or late) local HDs detection - Windows will detect the local disk drives in the second (or third) part of the boot process (not as boot devices). This is useful when there are issues accessing certain local disk drives.
Managing Local Hard Disk Access 14 Start at least one client computer and check that access to the local HDs meet your requirements. NOTES • Note that the Local HDs Detection setting will apply to all local HDs. If you need more detailed options, such as 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.
Neoware Image Manager User Manual CHAPTER 11 Windows Product Activation This chapter describes how to activate Windows products for Image Manager clients. Introduction Windows XP and some other products edited by Microsoft need to be activated. This activation is made through a link between a unique Product Key and data that are specific to each computer.
Windows Product Activation CVolwrite/Persistent (or CVolwrite/Normal) client writing mode so that each client machine would have its own activation link. Product Activation Procedure The administrator can use the following procedure to activate products. 1 Modify the nvdd configuration file (using Neoware Image Manager Console or a text editor) so that the system volume will be opened in CVolwrite/Persistent write mode (or in CVolwrite/ Normal mode).
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 clientspecific differences (deltas) to the HD image file).
Windows Product Activation 130 Product Activation Procedure
Neoware Image Manager User 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 client like” usage.
Windows User Profiles "Local" Roaming Profiles You can use an original setup where all the users are created only on the reference local shared configuration (in fact in the local system users accounts database). Users are created on a client computer booted from an actual HD or from a remote 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 reference installation.
Windows User Profiles 7 Boot only ONE client. 8 On the client computer, issue the following command at the command prompt for each user created earlier: net user /profilepath:\\\\PROFILE 9 Log on successively with each user login name and password and check that everything is running correctly. (This step is recommended because it will create the appropriate “local profile folders” for every user.) 10 Shutdown the client station.
Windows User Profiles ing documentation). Local Settings may contain, typically, Outlook files, WallPaper etc. The directories Local Settings and History should not be in this list. The directory Local Settings\Application Data\ Microsoft\Windows may be in this list, though it is not in this list by default. This setting can be applied to HKEY_USERS\.Default before the users are created. Then, this setting does not need to be applied individually for all users after they have been created.
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 drives, its hardware must be 100% identical to the clients that can boot off that virtual drive. In particular, the network card must be in the same PCI slot for both clients.
Adding Clients & New Software Modifying an HD Image to be Used by Several Clients Using Admin Mode The following procedure enables you to make changes to a hard disk image that is used by several clients. For example, to add a new application so that it is available to all the clients. This must be done each time you want to modify the reference configuration so that every client can benefit from the changes you make.
Adding Clients & New Software Using the CVolMerge Tool 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 changes. 5 Log on to this client with a user that has enough rights to perform the desired changes on the volume. 6 Install the new application(s), patches, and modify the configuration.
Adding Clients & New Software 1 Make sure your NVDD server module runs so that the system volume you want to modify is mounted in CVolwrite/Normal mode by the client used to perform the changes on the HD image file. Let us assume that the volume you want to modify is named MyDisk and that the corresponding image file path is /HDImages/ MyDisk.vol. Let’s also assume that the CVol files for this volume are stored in /CVols on your server.
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 boot from the new one, or (2) let the clients run the old image and make the NVDD server give them the new one the next time they reboot. These methods are as follows: First Method: 1.
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 files: MyImage1.vol and MyImage2.vol, and the corresponding volumes in the configuration file (MyImage1 and MyImage2). MyImage1 is your current production image.
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 require a mirrored copy of the same image at each location. In this case the original mirrored copies of the image can be created at each location using a DVD-based or HD-based copy of the original Master image.
Adding Clients & New 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 file. (The nvddadmin tool can remotely launch CVolMerge on the remote server. CVolMerge will actually run on the remote server.
Adding Clients & New Software Rem file on the Master server. Rem %3 is the image filename on the servers. Rem Rem Rem %4 is the UNC Path of the remote server folder in which the CVol File is to be copied and where the Image to be modified resides. CVolCompactor %1 %2\%3 New%1 gzip New%1 gzip New%1.dat copy New%1.gz %4 /y copy New%1.dat.gz %4 /y echo echo echo echo echo echo echo echo echo echo gzip –d New%1.gz > %4\RemoteJob.bat gzip –d New%1.dat.gz >> %4\RemoteJob.bat move New%1 %1 >> %4\RemoteJob.
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 existing volume to be used on new hardware and you cannot use the UbiBoot Extractor and Inserter tools.
Adding Clients & New Software the primary partition in the local hard drive can be different from the filesystem of the current system volume (for instance, the system volume can use FAT32 filesystem and the target partition can be formatted with NTFS filesystem). Use the computer to which the actual HD is physically connected to perform these operations. 6 Stop as many processes as possible on the Neoware Image Manager client.
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 source and the target partition are not actually copied. This makes upgrades to the target partition very efficient and fast.
Neoware Image Manager User Manual CHAPTER 14 Adding Clients to Windows Domains This chapter describes how to add Neoware Image Manager clients to a Windows domain using the Neoware Domain Wizard. Introduction The Neoware Domain Wizard NeoDomain.exe enables you to add Image Manager clients to a Windows domain. This wizard modifies the disk image so that domain membership is available for multiple computers using the same image as their system virtual hard disk.
Adding Clients to Windows Domains Domain Credentials are stored when the client computer shuts down. When a client computer boots off a shared virtual HD it will use its own personalized Domain Credentials. Repository for Domain Credentials The Neoware Domain Wizard can store the domain credentials for each member either in a directory on the server (default), the system partition, or in another partition.
Adding Clients to Windows Domains will not be saved with the domain credentials because the system Virtual HD is mounted in CVolwrite/Volatile mode. The domain controllers will assume that the client knows its new password when this password has actually been forgotten by the client when it rebooted. The Neoware Domain Wizard will automatically disable Machine Accounts Passwords changes when the Repository in System Partition option is selected.
Adding Clients to Windows Domains Same Repository used by Different Shared System HD Images When the repository is stored on a Neoware Image Manager server or in a separate drive, the domain credentials can be associated with different shared system HD images that have been created from a common "strain" image. This is because the domain credentials depend on data contained in the image itself.
Adding Clients to Windows Domains client computer can still be a member of the domain and use the same domain credentials no matter which HD image was used to boot up the computer. Another application of this unique feature is when the Administrator changes the unique HD image that is assigned to a client computer as its system image. For example, the system image is changed from WindowsXP-Pro-Diag.vol to WindowsXP-Pro-Office.vol.
Adding Clients to Windows Domains 2 Shutdown all the clients that are using the image you will be modifying. If you will be working on a copy of an image created in the previous step, make 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.
Adding Clients to Windows Domains 9 Click Next to continue.
Adding 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 Domain Wizard window. 13 Make sure that the client preferred DNS IP address is set to a Domain Controller IP address.
Adding Clients to Windows Domains Storing Domain Credentials in an NVDD Server Directory 155
Adding Clients to Windows Domains 156 Storing Domain Credentials in an NVDD Server Directory
Adding Clients to Windows Domains Storing Domain Credentials in an NVDD Server Directory 157
Adding Clients to Windows Domains 16 When needed, provide 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. 17 Reboot the computer. 18 Log on to the client 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.
Adding Clients to Windows Domains Windows 2000 Professional Clients The procedure is the same as for Windows XP Professional clients described in the previous section, except that there is no Network ID wizard in Windows 2000. Instead, you have to do the following to replace Network ID wizard operations: 1 Run the Control Panel > System applet. 2 Select the Computer Name tab. 3 Click the Change button. 4 If the client is indicated to be a member of a domain, make it a member of a workgroup.
Adding Clients to Windows Domains It is possible to use automated scripts that use the Microsoft netdom utility in order to 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 for Windows XP sp2 clients is available at the following Internet address: Netdom http://www.microsoft.com/downloads/details.
Adding Clients to Windows Domains In order for such a script to work, you have to make sure that: • netdom.exe is in the system search path (for example, copy it in c:\windows\system32). • the Environment variables DomainName, UserName and UserPass are consistent. (UserName must be the name of a user account in the domain specified by DomainName. UserName must have the right to add and remove computers in DomainName.
Adding Clients to Windows Domains Storing Domain Credentials on a Non-Volatile Drive The following procedure requires that you use the Windows 2000 Professional or Windows XP Professional operating system. Before you perform the following procedure, make sure that the client computer is not a member of a domain. If it is a member of a domain, you must remove it before you continue.
Adding Clients to Windows Domains 5 Save the nvdd configuration file in Neoware Image Manager Console. 6 Reload the nvdd configuration file in Neoware Image Manager Console so that the writing mode changes are taken into account. 7 Boot ONE client. 8 Log on this client using an Administrator Local User Account (a user account local to this client user’s database with administrative rights). You cannot use a domain user account because the client is not a member of a domain.
Adding Clients to Windows Domains 13 Click Next to continue. 14 Select the option Repository in non-system Partition.
Adding Clients to Windows Domains (e.g. D:\). Note that you can only choose a directory on an existing drive as the path to repository folder. If you check the option Hide repository drive in Windows the drive on which the repository is housed will not appear in Windows explorer. This uses the NoDrive registry feature of Windows. For more details about NoDrive, refer to: Explorer, http://www.windowsitpro.com/Article/ArticleID/37880/ 37880.html?Ad=1 16 Click Next to continue.
Adding Clients to Windows Domains You will see the message Operation completed in the Neoware Domain Wizard window. 19 Make sure that the client preferred DNS IP address is set to a Domain Controller IP address. You may need to tune your DHCP server options in order to set the preferred DNS server for your clients. If you are told that there are several network cards with the same IP address in the client computer, click the No button and leave the system as it is.
Adding Clients to Windows Domains 28 Reload the nvdd configuration file in the Image Manager Con- sole 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 user’s database with administrative rights). Do not use a domain user account. 31 On the client, open System Properties (Control Panel > Sys- Click on the Computer Name tab then click the Change button. tem).
Adding Clients to Windows Domains 39 Optional, depending on the "no-need for reboot" validation (refer to the section “Do I Need to Reboot?” 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.
Adding Clients to Windows Domains add to domain again using scripts run by the clients when they boot- up. It is possible to use automated scripts that use the Microsoft netdom utility in order to perform the "leave domain" and "join domain" tasks. Netdom can even be configured to reboot the computer after it has performed "leave domain" or "join domain" tasks, if you validated that this step is needed. Netdom for Windows 2000 sp4 clients is available at the following Internet address: http://www.
Adding Clients to Windows Domains • Try to log on to each of these client computers with Domain User credentials. If you can log on these clients using Domain User name and password, you do not need to reboot between removing and joining each client to the domain again. Storing Domain Credentials in the System Partition The following procedure requires that you use the Windows 2000 Professional or Windows XP Professional operating system.
Adding Clients to Windows Domains 7 Log on this client using an Administrator Local User Account (a user account local to this client user’s database with administrative rights). Do not use a domain user account. 8 On this client, launch the Neoware Domain Wizard either from the Start menu by selecting Programs > Neoware > Image Manager > Tools > Neoware Domain Wizard, or by running the executable file NeoDomain.
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.
Adding Clients to Windows Domains Refer to the following web sites for information on the Foreground Policy option: http://support.microsoft.com/kb/q305293/ http://www.microsoft.com/technet/prodtechnol/ windowsserver2003/library/ServerHelp/274e614e-f5154b80-b794-fe09b5c21bad.mspx 12 Click Apply to continue. You will see the message Operation completed in the Neoware Domain Wizard window. 13 Make sure that the client preferred DNS IP address is set to a Domain Controller IP address.
Adding Clients to Windows Domains 20 Log on this client using an Administrator Local User Account (a user account local to this client users database with administrative rights), not a domain user account. 21 Repeat steps 13-20 until all the required client computers’ accounts are created. 22 Shutdown 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).
Adding Clients to Windows Domains 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. You can just use one client PC to add all the clients into the domain. All that is required is that the clients’ computer names are added to the domain.
Adding Clients to Windows Domains 176 Storing Domain Credentials in the System Partition
Neoware Image Manager User Manual CHAPTER 15 Merging Image & CVol Files This chapter describes how to use the CVolMerge tool to create a new hard disk image from an existing image and a CVol file. Introduction The CVolMerge tool enables you to create a new hard disk image file from an existing image and a CVol file, or update an existing image with the content of a CVol file.
Merging Image & CVol Files C:\Program Files\Neoware\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 in the CVol file and compare them with the sectors in the image file. If the sectors are the same, they are removed from the CVol file.
Merging Image & CVol Files Please note that CVolMerge does not check if the parameter 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: CVolMerge \HDimages\big2k.vol \cvols\big2k@00E0C554E700 \HDImages\NewBig2K.vol Linux/Unix example: .
Merging Image & CVol Files 180 Using the CVolMerge Tool
Neoware Image Manager User Manual CHAPTER 16 The Image Manager Console This chapter describes how to use the Image Manager Console to change settings in an nvdd configuration file. Introduction The Image 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.
The Image Manager Console .conf. (See later in this chapter for how to open a server configuration file of a server that is actually running, and how to 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 panel on the left displays the names of computers (i.e. subnets) and groups of computers.
The Image Manager Console The Toolbar The toolbar provides a quick way of accessing menu options just by clicking a button. New To create a new configuration file. Open To open an existing configuration file. Save To save the currently opened configuration file. New Group To define a new group of computers. New Client To define a new computer or subnet of computers. New Volume To define a new volume.
The Image Manager Console Search To search an object. About To open the About dialog. The File Menu The File menu provides standard functions for opening and saving files, and exiting the Image Manager Console. The Edit Menu The Edit menu enables you to create clients and volumes, and view and edit their properties.
The Image Manager Console Selecting Create will display a menu enabling you to create a new Computer, Group or Volume. Note that you must select a corresponding object in the relevant Console panel in order to create a new version of that object. The dialogs displayed when you select these options are the same as those when you select Properties. Selecting Properties will display a Properties dialog for the currently selected Computer, Group, or Volume.
The Image Manager Console Selecting Nvdd Manager will display a dialog enabling you to connect to a running Image Manager server and open and edit configuration files on it. Selecting Merge conf file will display a dialog that enables you to open another configuration file in order to copy volume settings from it into the currently open configuration file. The View Menu The View menu enables you enable or disable display of the Toolbar and Status bar.
The Image Manager Console ing the Edit menu and selecting Properties. A Properties dialog is displayed when you create a Computer, Group or Volume. Client Properties The Client Properties dialog enables you to specify the properties of a client Object. These properties contain the name assigned to the client object, whether this object is a collection of workstations or a subnet (or a single workstation), or an individual client identified by its IP address or MAC address.
The Image Manager Console or specifying a unique MAC Address, 188 Displaying & Changing Properties
The Image Manager Console or specifying an IP subnet. When idenfified as a subnet, the identification is made of two fields. The IP address (address of the “network”) and the subnet mask. Typical subnet masks are: 32 This is the subnet mask for a single IP 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 and it will be treated accordingly.
The Image Manager Console If several definitions exist that match the same client, the priorities are as follows (highest priority first): 1 MAC address, 2 Unique IP address (actually IP subnet with subnet mask of 32 bits), 3 IP subnet with subnet mask of 31 bits, 4 IP subnet with subnet mask of 30 bits, ... 33 IP subnet with subnet mask of 1 bit, 34 IP subnet with subnet mask of 0 bit (actually 0.0.0.0/0, the “everybody” group in the default nvdd.conf file).
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). For more information on client naming, refer to the section “Client Naming” on page 233. Group Properties The Group Properties dialog specifies the name of a collection of computers (i.e. subnets).
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.
The Image Manager Console Creating a Volume You can create a new volume either by right-clicking in the Volume panel and selecting Create Volume in the pop-up menu, or by displaying the Edit menu and selecting Create then Volume. A dialog consisting of several tabs is displayed. This dialog is also displayed when you view the Properties of a selected volume.
The Image Manager Console names of the CVol files are directly derived from the related Volume name and changing this name while the volume is mounted by Neoware Image Manager client will crash the clients. The Console will display a warning when you want to change an existing volume name Specify the name of the hard disk image file to use in the File name box (click the ...
The Image Manager Console The Parameters Tab 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 writing mode to be used, while the Special clients options enable you to specify a different writing mode for individual clients. (For a description of the writing modes, refer to the section “Volume Write Modes” on page 82.
The Image Manager Console The CVol Tab The CVOL tab enables you to specify a different directory for this volume’s CVol files if they are not to be stored in the general CVol directory (specified in the General tab of the Generic Properties dialog). You can also specify the maximum size that the CVol data file for this volume can grow to. Note that you can change this maximum size even when there are existing CVol files related to this volume, even if some have reached the current maximum size.
The Image Manager Console The Computers tab The Computers tab will display the names of all the computers that can share this volume. (This is not where you specify which computers share the volume.) Double-clicking on a group or computer name will display the relevant Properties dialog. We highly recommend that you set Admin computers according to your requirements and do not leave the client object "everybody" in this field.
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 which computers or subnets are allowed in Admin mode. To add a computer to the Allowed computers or Admin computers list, select the computer name in the central list box then click the + (plus) button under the relevant list box to add it to that list.
The Image Manager Console Generic Options The General Tab 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 specifies the maximum size that CVol data files can grow to. Note that you can change this maximum size even when there are existing CVol files, even if some have reached the current maximum size.
The Image Manager Console The Flush disk data on write operation option is used when you want to make 100% sure that when a client sends a request to write some data, it gets an acknowledgement that the write operation succeeded when the data have actually been written on the disk drive. This option is usually set when you have a cluster of servers that use a shared storage.
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 Client Object “everybody” (IP range:0.0.0.
The Image Manager Console directory for a volume’s CVol files on the CVOL tab of the Volume dialog. Properties The Client files folder setting specifies the root directory for file transfer. Files transferred by a client will be placed in a subdirectory within this directory. The name of each subdirectory will consist of the MAC address of the client initiating the file transfer. Any file transferred to or from the admin client (nvddadmin) must be based on this directory, or a subdirectory of it.
The Image Manager Console The Executable Paths Tab The Binary files folder setting specifies the path to the tools that can be launched by the server during a remote session from nvddadmin. MD5 Executable and Archiver Executable enable you to specify different executable files to the default ones used for these operations. MD5 Parameters and Archiver Parameters allow you to set custom parameters for the defined executables.
The Image Manager Console Archiver Executable default: gunzip.exe (Windows) or gunzip (Linux/FreeBSD). Archiver Parameters default: the only parameter given to the executable file will be the filename given by the administrator through nvddadmin. If Archiver Parameters is set, the parameters will be given first, followed by the filename. For example: [] Note that you can use batch file (.bat or .
The Image Manager Console The Network Tab The Network tab specifies 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 address of 0.0.0.0 means all the IP addresses assigned to the server.
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.
The Image Manager Console The Nvdd Manager One of the most useful features of the Console is the ability to manage running Image Manager servers. Display the Nvdd Manager dialog by selecting Nvdd Manager in the Tools 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.
The Image Manager Console When the Console runs on a computer that also runs the 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 a modified configuration file, as long as the file has been opened by clicking the Open conf file from server button. Note: This method is the only one that can be used to actually modify a configuration file currently running.
The Image Manager Console Merging Configuration Files The Console enables you to import volume details stored in another configuration file, especially single-volume configuration files created using Client Builder. The merge command enables you to copy volume definitions from another configuration file into the current configuration file. Display the Merge Information dialog by selecting Merge conf file in the Tools menu or by clicking the corresponding icon.
The Image Manager Console then change the path specified in File name, or browse to find the image file. Click OK to finish. Volume IDs for imported volumes may also have to be tuned manually so that they do not use an existing ID. Password for Remote Administration You can configure an NVDD server module so that a password is required in order to control it remotely using the Image Manager Console or Client Builder. This is achieved using the NvddPasswd utility.
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.
The Image Manager Console 212 Password for Remote Administration
Neoware Image Manager User Manual CHAPTER 17 The NVDD Configuration File This chapter describes the nvdd configuration file and the settings that can be specified in it. Introduction The nvdd configuration file is used to define virtual hard disk volumes and specify which clients can access them. Every hard disk image that Client Builder creates will have an associated configuration file called nvdd..conf.
The NVDD Configuration File The nvdd.smalldisk.vol.conf File The nvdd.smalldisk.vol.conf file 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 to access. The following shows the initial contents of the configuration file nvdd.smalldisk.vol.conf. These settings enable you to start using Image Manager to create images and volumes straight away.
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 # #volumes = vol0, vol1 volumes=SmallDisk SmallDisk.id=1 SmallDisk.file=smalldisk.vol SmallDisk.desc=Small 8MB Virtual Volume SmallDisk.cylinders=1 SmallDisk.heads=255 SmallDisk.sectors=63 SmallDisk.
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.vols=SmallDisk group0.unicast=true group0.read_only=false group0.users=everybody, admin 216 The nvdd.smalldisk.vol.
The NVDD Configuration File Configuration File Settings The following configuration file setting descriptions generally follow the order shown in the example nvdd.smalldisk.vol.conf file shown in the previous section. Comments can be specified in the configuration file by beginning the line with the # character. Caution: Neoware Image Manager will erase existing comments when it modifies a configuration file.
The NVDD Configuration File authorized_subnets (optional – default: all subnets) If this setting is present, nvdd will deny access to clients whose IP addresses do not match the comma-separated list of subnets. A subnet definition is of the form: a.b.c.d[/bits|:netmask] where a, b, c, and d must be fully specified. Timing max_idle_time (optional – default: 120) Clients that have not communicated with nvdd during this time (in seconds) will be automatically deleted.
The NVDD Configuration File Directories for File Transfer client_files_dir = ./files/ This option specifies the root directory for file transfer. Files transferred by a client will be placed in a subdirectory within this directory. The name of each subdirectory will consist of the MAC address of the client initiating the file transfer. Any file transferred to or from the admin client (nvddadmin) must be based on this directory, or a subdirectory of it.
The NVDD Configuration File Md5_params = [] (optional) If md5_file is set, this option is used to give the executable file its command line. By default, the only parameter given to the executable file will be the filename given by the administrator through nvddadmin. If md5_params is set, the parameters will be given first, followed by the filename. For example: [] unzip_file = (optional – default: gunzip.
The NVDD Configuration File Certificate File certificate_file=./Certificates/cacert.pem This specifies the name of the SSL certificate that the server is to use for admin connection. Although SSL encryption is disabled in Neoware Image Manager 4.5, the certificate file must still be present and the parameter that specifies its path must be correctly set. certificate_passwd=[] (optional) This gives the server the password used to encrypt the certificate file (if any).
The NVDD Configuration File have to respond to many Delayed Write Failed messages by clicking the OK button). You can then increase the sector map size value so that when the server is restarted the client can continue its write operations. If the CVol file becomes full and the sector map size for a volume is the same as the total number of sectors in the volume, a "Disk Full" or "Delayed Write Failed" error message will be issued.
The NVDD Configuration File This option is intended to be used in a high-availability environment when there are several servers that can write to the same shared storage. Number of Processing Units disk_thread (optional – default: 1) Specifies the number of processing units dedicated to disk operations. This value can be tuned depending on the server resources to enhance performance.
The NVDD Configuration File A station is identified 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 identification to a unique computer (bits=32), then the client will be able to receive its name from the NVDD server. Client MAC Address .
The NVDD Configuration File Computer Name Change .save_name=[true¦false] This option defines the 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. When defined for a subnet, this parameter is applied to all the clients that belong to this subnet and do not belong to a more precise subnet or are not defined by MAC address.
The NVDD Configuration File choose from (i.e. if several bootable volumes are available to this client). For example: disk0.desc=Windows XP sp2 (Back Office) Volume Geometry The following parameters are created by Client Builder when it creates the image file and associated configuration file. .cylinders Specifies the number of cylinders for the virtual disk. .heads Specifies the number of heads for the virtual disk. .
The NVDD Configuration File This parameter is now obsolete and performs no function. It is retained only for compatibility with earlier versions of Neoware Image Manager. Volume Integrity .check_cvol (optional – default: false) This parameter is used to make nvdd check the integrity of CVol files before opening them. Integrity is checked by the comparing the CVol file date with the image file date.
The NVDD Configuration File If the write mode is set to cvolwrite, then the cvol_mode command specifies the submode. You can also specify different write modes for specific clients using the same volume, so the default write mode is ignored. The following commands would be used to indicate which clients are to use which mode: .admin_mode_users= .normal_mode_users= #(CVolWrite/Normal) .
The NVDD Configuration File will have the same name plus the extension .ref for the header, and for the data file. If this reference CVol does not exist, it will be copied from the existing CVol file for this client. This means that the first time a volume is opened by a client in Persistent mode, the reference CVol file is automatically copied from the existing CVol file.
The NVDD Configuration File CVol file folder and will be treated as a normal CVol. Note that in this case, when the client reboots, the reference CVol file will be created from the current CVol file for this client (file vol0@00E0C554E700) as described in Case 2 above.
The NVDD Configuration File Allowed Clients .users Comma separated list of clients allowed to access this volume. .admin_users (optional) Comma separated list of clients allowed to access this volume as administrators. Note that only one administrator client is allowed at the same time. When an administrator is accessing the disk, all other clients are refused. An administrator client cannot access specified volumes when some other (non-Admin) clients are still present.
The NVDD Configuration File .unicast (optional – default: false) This specifies if the stations should mount volumes in unicast or not. Values: true or false. .read_only (optional – default: false) This specifies if the station should mount volumes in read only mode or not. If so, all write requests will be discarded. .users This is a comma separated list of users in group. The best matching user subnet is chosen to specify if a client uses the group parameters.
The NVDD Configuration File Client Naming 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 on DHCP option 12 (client host name) or, if no DHCP option 12 was set for this client, a name consisting of the letter H + the client MAC address.
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 not exist, the NVDD server can then record this name in the nvdd configuration file.
The NVDD Configuration File Enabling Client MultiBoot 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 10 seconds, the client will boot using the default volume. The names of the boot volumes are specified together with any other volumes using the parameter .
The NVDD Configuration File mPXELdr gets the parameter .desc of each bootable volume. mPXELdr displays this description after the number assigned to the corresponding volume. If there is no .desc parameter for a specific volume, mPXELdr will not not display anything after HD,. The first volume in the list is assigned the number 1, the second volume is assigned number 2 etc. The user can press 1 to boot from volume number 1, 2 to boot from volume number 2, etc.
The NVDD Configuration File inition to be non-bootable. For example, you could have the following entries in the nvdd configuration file: ... volumes= VolXPHE, VolXP, VolXPNoBoot VolXPHE.file=VolXPHE.vol VolXPHE.desc="Windows XP HOME Edition" VolXPHE.boot_device=true ... VolXP.file=VolXP.vol VolXP.desc="Windows XP PRO" VolXP.boot_device=true ... VolXPNoBoot.file=VolXP.vol VolXPNoBoot.desc="Windows XP PRO Non Bootable" VolXPNoBoot.boot_device=false ... groups= group0, group1 group0.vols=VolXPHE, VolXP ...
The NVDD Configuration File Example nvdd.conf with Multi-Volume Support The following example nvdd configuration file shows typical settings for multi-volume support. # nvdd.conf generated by Neoware Image Manager Console #Network Settings address=0.0.0.0 port=2184 admin_addr=0.0.0.0 admin_port=29035 authorized_subnets= #Server settings max_idle_time=3600 sectors_map_size=2000000 default_save_name=true disk_threads=1 recv_buf=131072 send_buf=131072 #Directories client_volumes_dir=./ client_files_dir=.
The NVDD Configuration File # # VOLUME definitions # volumes=disk2, disk1 disk2.id=1 disk2.file=./disk2.vol disk2.desc=disk2 disk2.cylinders=447 disk2.heads=255 disk2.sectors=63 disk2.floppy=false disk2.boot_device=true disk2.check_cvol=true disk2.no_admin_cvol=true disk2.write_mode=cvolwrite disk2.cvol_mode=normal disk2.sectors_map_size=0 disk2.client_volumes_dir= disk2.cache_size=0 disk2.type=0 disk2.users=admin, everybody disk2.unicast_users=admin, everybody disk2.admin_users=admin disk2.
The NVDD Configuration File disk1.users=admin, everybody disk1.unicast_users=admin, everybody disk1.admin_users=admin, everybody disk1.admin_mode_users= disk1.normal_mode_users= disk1.volatile_mode_users= # # GROUP definitions # groups=group0 group0.vols=disk1, disk2 group0.unicast=true group0.max_ram_sectors=102400 group0.read_only=false group0.users=admin, everybody 240 Example nvdd.
Neoware Image Manager User Manual CHAPTER 18 NVDD Server Administration This chapter describes the NVDDAdmin tool and NVDAdmin protocol commands for administering a remote NVDD server. Introduction The NVDAdmin protocol is used to communicate with a running nvdd program.
NVDD Server Administration Secured NVDAdmin Protocol Neoware Image Manager server and the clients that use NVDAdmin protocol can use SSL (OpenSSL) to encrypt communications. This is mainly dedicated to configurations where a console controls a remote server through WAN. 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.
NVDD Server Administration -c The default certificates 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 server running on the same machine. Nvddadmin –h Server64.paris.texas.Company28.
NVDD Server Administration parameter: ‘name’. This is the name of the file after it has been transferred. If this second parameter is not specified, the file keeps its original name after the transfer. The put and get commands exist in several flavors: secured (prefix s) or non secured, with resume (prefix r). "With resume" means that the command will append the rest of the file to be transferred to the data already transferred (if any).
NVDD Server Administration nopwd Switch to AUTH mode when the password on the server side has not been set. exit Exit this utility. help Display basic help text. admin [P] Use single admin mode (aka exclusive admin mode, exclusive admin connection). This mode is used to make sure that the NVDAdmin connection to the remote server is the only connection of this kind that exists. The connection is then an NVDAdmin Exclusive connection.
NVDD Server Administration get [] [P] Gets filename from server without resume mode on nonsecured socket. rget [] [P] Gets filename from server with resume mode on non-secured socket. sput [] [P] Copies filename to server without resume mode on secured socket. srput [] [P] Copies filename to server with resume mode on secured socket. sget [] [P] Gets filename from server without resume mode on secured socket.
NVDD Server Administration remote 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 defined in a conf file will not be disrupted. In particular, in case the volume(s) they mounted do not exist anymore or are not shared with the same ID or volume name.
NVDD Server Administration rm [P] Removes the specified regular file on the server side. get_users [P] Prints a list of IP addresses and port numbers of clients that are currently connected to nvdd server. get_volumes [P] Prints a list of volumes on nvdd. info_user : [P] Prints information about a user (a client). (One from a list exactly as reported by the get_users command. This means that the port must also be specified).
NVDD Server Administration unzip [P] unzip remote file. The gunzip.exe file (or gunzip executable for Linux/FreeBSD) must be present in bin_directory on the server. bin_directory is specified in the nvdd configuration file. Another "decompressor" executable and optional parameters can be specified through the use of the appropriate settings in the conf file.
NVDD Server Administration 250 NVDDAdmin Commands
Neoware Image Manager User Manual CHAPTER 19 The mPXELdr Configuration File This chapter describes the mPXELdr configuration file and the settings that can be specified in it. Introduction mPXELdr can use a configuration file to set the list of NVD servers that it will try to communicate with, in addition to DHCP Option 132. This configuration file also allows the setting of several boottime options which are described later in this chapter.
The mPXELdr Configuration File 3 ip1_ip2_ip3.ini Search for an .ini file common to all IP addresses starting with ip1.ip2.ip3. 4 ip1_ip2.ini Search for an .ini file common to all IP addresses starting with ip1.ip2. 5 ip1.ini Search for an .ini file common to all IP addresses starting with ip1. 6 m1_m2_m3.ini Search for an .ini file common to all the machines with this 3byte MAC address prefix, i.e. belonging to the same “Ethernet MAC address block”.
The mPXELdr Configuration File This search mechanism can be used to organize a multi-level hierarchy of configuration files, from the most specific (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.
The mPXELdr Configuration File • The value ends either with a standard value terminator or with a keyword-specific terminator. Because the end of line control characters are standard value terminators, values usually do not extend across lines unless otherwise specified (keyword-specific syntax). • Unless specified otherwise, a keyword followed by an invalid value for that keyword will cause the keyword to be ignored, and the default value (if any) for that keyword to be applied.
The mPXELdr Configuration File Example mPXELdr .ini File # Comments are allowed in the .ini file. # Blank lines are allowed too. # # # # A ‘whitespace’ is either a space or a TAB character. Whitespaces may appear before the # sign. Whitespaces may appear before keywords (such as NVDServers) too. Comments extend to the end of line. # Examples of keyword use and syntax: # Vanilla example: # NVDServers = 192.168.0.
The mPXELdr Configuration File Keywords The Include Keyword Syntax: Include = Examples: 1 2 3 4 Include Include Include Include = = = = MyIncludeFile.ininc /MyIncludeFile.ininc SomeRelativePath/MyIncludeFile.ininc /SomeAbsolutePath/MyIncludeFile.ininc Default value: None The is either absolute (expressed starting relative to the TFTP root directory) or relative (to the directory where the mPXELdr boot program resides).
The mPXELdr Configuration File from the PXE TFTP file path and the .ini file. This is important because mPXELdr has no idea whether the TFPT server is talking to a Windows, Linux or UNIX server. Even if the TFTP specification allowed such information to be known, the PXE specification is not designed to relay such information to mPXELdr. It is the user’s responsibility to use the correct separator in the DHCP parameters and .ini file.
The mPXELdr Configuration File An Include file may include other files. This is one of the ways to build structured configurations. Include files can only be nested four levels deep. The NVDServers Keyword Syntax: NVDServers = Examples: NVDServers = 192.168.0.209,192.168.0.161:2300,111.111.111.111:111; NVDServers = 192.168.0.209,192.168.0.161:2300,111.111.111.111:111 NVDServers = 192.168.0.209,192.168.0.161:2300,111.111.111.
The mPXELdr Configuration File boot file (and its .ini file) to the list of potential NVD servers. This is the default option. If the terminating character is a ‘!’, the PXE boot loader will not add the TFTP server to the list of NVD servers. If multiple NVDServers keywords are found by mPXELdr during .
The mPXELdr Configuration File Include directive documented in this chapter. This capability allows the administrator to create a few number of NVDServers sublists as independent files, and assemble them in different configuration files through the use of Includes in the various .ini files. This way, the whole hierarchy of server lists can be modified for large number of stations or groups of stations by simply changing a few Include files.
The mPXELdr Configuration File • Answers its connection request • Has a bootable volume this station can see and reach. The first bootable volume on the server that the station can see will be used for booting. The order of volumes on the server are defined by the server configuration. Servers are searched in the order defined by the NVDServers keyword(s) (as well as Option 132), in the order specified.
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 Volume Selection screen. The following illustration shows a typical log screen display immediately before a volume is booted.
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, with one entry per server found. Server selection is achieved using the Up and Down arrow keys then pressing the Enter key.
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 attempt to boot that volume. You can return to the server selection screen by pressing the Escape key. Note: The VolSelectionTO parameters described later in this chapter have NO EFFECT in interactive mode.
The mPXELdr Configuration File Pressing the F1 key from the Boot Volume Selection 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 Volume Selection screen. The following illustration shows a typical log screen display immediately before a volume is booted. Note that this can normally only be seen if the PreBootPause keyword is specified and set to Y.
The mPXELdr Configuration File umes available on the server. If the user does not touch the keyboard during this time period, mPXELdr will automatically select the first volume in the list and attempt to boot. Valid values are 1 to 60 seconds. Values larger than 60 seconds are reduced to 60 seconds. A value of 0 effectively disables the time out, and will let mPXELdr wait infinitely for user interaction. The default value is 10 (10 seconds timeout).
The mPXELdr Configuration File The ReQueryDHCPOptions Keyword Syntax: ReQueryDHCPOptions = Examples: ReQueryDHCPOptions = Discover ReQueryDHCPOptions = None ReQueryDHCPOptions = Inform Default value: ReQueryDHCPOptions = I Warning: This option implements a work around for a few and limited number of technical issues related to very specific DHCP implementations. It should only be used when such a case has been clearly and unambiguously identified.
The mPXELdr Configuration File server returned to the station in its DHCPACK reply to the DHCP request emitted by the PXE boot prom. If set to I, the regular DHCPINFORM method is used. This is the default. The NICRxTxQs Keyword Syntax: NICRxTxQs = Examples: NICRxTxQs = 8/4 NICRxTxQs = 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 implementations.
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.
The mPXELdr Configuration File 270 Keywords
Neoware Image Manager User Manual CHAPTER 20 Neoware Active Cloner This chapter describes how to use Neoware Active Cloner to clone the current system partition to another partition. Introduction Neoware Active Cloner is a partition duplicator that works on a file by file basis and enables differential cloning and duplication of the current system partition to another partition while Windows is running.
Neoware 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) or through a graphical user interface called NimClonerGUI.exe. The following procedure describes the basic user interface operation.
Neoware Active Cloner 2 The Source Drive is the partition to be 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 a drive shared on the network, etc. The additional options in this dialog are accessed by clicking the Expert button.
Neoware Active Cloner Cloning to a Network Shared Hard Disk 274 2 Make sure the partition you want to make bootable on the attached hard disk is activated and is the first partition on the hard disk. 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 launch any applications on this computer while Neoware Active Cloner is running. 4 Start Neoware Active Cloner.
Neoware Active Cloner 7 Specify the Target Drive in the Neoware Active Cloner as the drive letter associated with the shared hard disk. 8 Click the Clone button. When the target drive is a network share, Neoware Active Cloner does not have physical access to the target hard drive and then it cannot check that the partition is activated nor can it dump the MBR of the source drive to the MBR of the target drive.
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 you to modify the cloning process so that certain steps are not included. Selecting Disable Files Cloning will prevent file processing. To prevent any files or directories on the target partition that are not on the source partition from being deleted, select Disable Files Cleaning.
Neoware Active Cloner Boot Options The Target Type option can be set 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.
Neoware Active Cloner /NoFiles Using this option will prevent file processing. /NoCleanFiles This option will prevent any files or directories on the target partition that are not on the source partition from being deleted. It will have no effect if /NoFiles is specified. /NoReg This option will prevent the full set of registry files from being created on the target drive. /NoHDDBoot If you do not use this option NimCloner.
Neoware Active Cloner Error Messages Could Not Copy a File If the message Could not copy a file is displayed, try manually copying the file from the source drive to the target drive. Some files (such as log files, temporary files) may not actually be needed for the Windows operating system on the target drive in order to boot off the target drive. If the file cannot be copied, check if the file is actually required. You may need to run disk checking/repairing tools if some files are corrupted.
Neoware Active Cloner 280 Client-Specific Settings on the Target System
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 Neoware Image Manager integrates perfectly well in VMWare environments. It can be used to stream OS and applications (actually disks) to Virtual Machines, making it very useful in VDI (Virtual Desktop Infrastructure) environments.
Virtualized Environments In particular, you should make sure that the latest VMWare Network Interface Card driver (VmxNet driver) is actually installed and working. Using this driver will actually improve performance and failing to use it may result in creating an image that will not be bootable by Image Manager Clients. Adding VM Support to Existing Images You can modify an existing Image Manager virtual drive so that it can be used to boot VMs.
Virtualized Environments When the drivers are completely installed in the image, that image can be used to boot all the machines it previously supported, including the Physical machines, and also the VMWare VMs. Having such an image may be very convenient as you can boot it in any VMware VM and then be able to reproduce what users experimence on their machines, even if you do not have to hand any client machine compatible with the image.
Virtualized Environments If you are using VMWare Workstation or VMWare server, this is achieved by using the menu Edit > Virtual Network Settings then selecting 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.
Virtualized Environments Setting a routing service or a NAT service on the guest that runs Image Manager server would then enable it to be the gateway between the private network and public network, and machines in the private network would potentially have access to all the network resources available to the public network (internet access, network file servers etc).
Virtualized Environments The server named saruman runs the DHCP service for Private Network. It is also configured to route IP packets between the private and public network. When setting such a dual network configuration, administrators should be careful to configure their DHCP service so that it does not interfere with the public network if this is not desired. Usually, an administrator would create a DHCP scope or subnet that would only server the IP addresses in the private network.
Virtualized Environments Microsoft VirtualPC Virtual Server Environments Most of what is mentioned in the previous section for VMware environments is also true in Microsoft VirtualPC/Virtual server environments. Refer to the VMware section earlier for more details about general operations with virtual machines. In this section we will focus on Microsoft VirtualPC/VirtualServer specifics.
Virtualized Environments Other Virtualized Environments There are other virtualized environments than VMWare 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 able to successfully PXE-boot off Neoware Image Manager.
Neoware Image Manager User Manual APPENDIX A Upgrading Image Manager This appendix describes how to upgrade from earlier versions of Neoware Image Manager. Important The components in a specific release of Neoware Image Manager must not be mixed with components from other releases. Components in 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 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, CVolCompactor, NvddPasswd, NvddAdmin) on the server side. You can perform a Server installation after having uninstalled the previous version, or you can use Decompress installation to get the files you need.
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 in Admin mode so that the new hardware is detected once for all and does not have to be redetected every time a client boots up.
Upgrading Image Manager 292 Upgrading from Previous Versions of Neoware Image Manager 4
Neoware Image Manager User Manual APPENDIX B The TFTPD Installer This appendix describes how to use the TFTPD Installer to configure Windows 2000/2003/XP TFTP Server for Image Manager clients. Introduction The TFTPD Installer is a tool for helping you to install the TFTP server (TFTPD) that is shipped with Microsoft Windows 2000/ 2003 Server, so that it can be used with Neoware Image Manager clients.
The TFTPD Installer Using the TFTPD Installer The following procedure assumes that the Microsoft TFTPD service is not yet installed. If the service is already installed, the TFTPD Installer will behave slightly differently to what is described here. However, the messages and hints displayed by the TFTPD Installer should still enable you to use it easily.
The TFTPD Installer 4 It is recommended that you check the Run TFTPD Service at boot time box so that TFTP Server will be launched automatically when the server boots. 5 If you want the TFTPD Service to be run when the TFTPD Installer is exited or when you click the Apply button, check the Run TFTPD Service now box. 6 Click the Apply button. 7 Click OK to exit the TFTPD Installer. 8 Make sure that the file mPXELdr.bin (or mPXELdr..
The TFTPD Installer 296 Managing the TFTPD Service
Neoware Image Manager User Manual APPENDIX C Configuring the DHCP Server This appendix describes how to configure the Windows 2000/2003 DHCP server. Introduction This appendix describes how to install and configure Microsoft DHCP Server, supplied with Windows 2000/2003 Server, for use with Neoware Image Manager. Before Installing DHCP Server IMPORTANT: The system on which DHCP server is to be installed must use a static (i.e.
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. 298 1 From the Start menu, select Programs > Administrative Tools > Configure Your Server to display the following dialog: 2 In the left-hand panel, click on Networking, select DHCP, and then start the Windows Component Wizard.
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 DHCP Server 5 Click Next in the Windows Components dialog. A progress bar will be displayed while the system configures the network components. 6 300 When the Windows Components Wizard has successfully completed, click the Finish button.
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 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. A definition of a range of IP addresses (with or without additional options) is called a scope.
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 the DHCP Server 5 Specify the range of IP addresses and the subnet mask. The range must not include the IP address of the DHCP server itself, or any other device with a manually 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 304 Configuring DHCP Click Next to continue.
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 this Add Exclusions dialog. Click Next to continue. 8 Typically, an IP address is assigned (i.e. leased) for a limited period of time. This avoids the situation where you run out of available addresses when visitors connect to the network and gat an IP address assigned.
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.
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 to communicate with systems on the WAN. Enter the IP address then click Add to enter the address to the list of Gateways. 12 Click Next to continue.
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 activate this scope now then clicking Next. (You can Activate/Deactivate the scope later with a right-click on the scope and selecting Activate or Deactivate.
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 win- dow, select the DHCP server and either right-click or from the Action menu select Authorize. 18 You may now have to close the DHCP window then open it again to see that the DHCP server is now running.
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 menu) and selecting Configure Options. Action 20 Scroll through the list box and check the option 066 Boot Server Host Name check box. Enter your server’s String Value field.
Configuring the DHCP Server 21 Scroll through the list and check the option 067 Bootfile Name check box. Enter mPXELdr.bin in the String value field. 22 Click OK to accept the settings. IMPORTANT: Make sure that option 060 Class ID is not present, or not checked, in Scope 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 (Intel PXE PDK for example) on your server.
Configuring the DHCP Server DHCP Reservations Even though 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 allows each client to have a DHCP-provided specific host name.
Configuring the DHCP Server 2 Enter a name for the reservation (just a “nickname”), the IP address you want to be assigned to the client, 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 Reservain the tree-view pane. tions If you want to add a specific option to a reservation, for example a host name, you need to configure the options for that reservation.
Configuring the DHCP Server 4 Scroll down to the particular option you want 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.
Configuring the DHCP Server Related Resources Documents relating to MS Windows® DHCP server can be found at the following address: http://technet2.microsoft.com/windowsserver2008/en/ servermanager/dhcpserver.mspx You can also refer to the following RFCs related to DHCP. RFCs can be browsed on the RFC web site: http://www.rfc-editor.org.
Configuring the DHCP Server 316 Related Resources
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 to boot from. There are two ways to configure the server(s) that mPXELdr will attempt to contact.
DHCP Reference virtual disk to the client, the client tries to locate a running Neoware Image Manager server module by scanning the next IP address and port in the list sent in DHCP option #132. If the last server in the list does not answer (or if this list is empty), the client tries to connect to the IP address that is sent in next-server DHCP option #66 (field siaddrr of DHCP answer), using the default NVDD port UDP 2184.
DHCP Reference default-lease-time -1; max-lease-time 43200; subnet 192.168.0.0 netmask 255.255.255.0 { host e100-01 { next-server 192.168.0.23; hardware ethernet 00:00:39:3C:10:AB; fixed-address 192.168.0.75; filename "mPXELdr.bin"; option option-132 "192.168.0.4:10000,192.168.0.9;" ; } host e100-02 { next-server 192.168.0.23; hardware ethernet 00:00:39:18:01:AB; fixed-address 192.168.0.70; filename "mPXELdr.bin"; option option-132 "192.168.0.4,192.168.0.
DHCP Reference Option #6: Domain Name Server (DNS). Option #12: Computer host name. This value is used by Neoware Image Manager as the TCP/IP host name and also as the NetBIOS computer name (Windows computer name). Option #44: WINS Server. Option #132: Used by mPXELdr to get a list of server IP addresses (optionally followed by a colon (:) and a port number. If no colon and port number is specified, standard NVD port UDP 2184 is used) that can respond to NVDD requests.
DHCP Reference 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 BDRUPD.
DHCP Reference perform before continuing the process. The actual value is useless, BDRUPD uses the type of the RegType value as the type of the value(s) it will write to the keys. Target : REG_MULTI_SZ. Contains couples of path + value to modify. The data given by the DHCP option value will be set at each path / value set in this list. The Target value must contain an even number of strings. The first string is a path to a key in the registry.
DHCP Reference If REG_SZ. Contains a registry path to a DWORD value. This value is read by BDRUPD. If it is not zero the option is processed: the Target is written with the value of the option or emptied if Type=4. Otherwise this key is ignored. IfNot REG_SZ. Contains a registry path to a DWORD value. This value is read by BDRUPD. If it is zero the option is processed: the Target is written with the value of the option or emptied if Type=4. Otherwise this key is ignored.
DHCP Reference Examples The DHCP option 1 provides the client’s subnet mask. This information must be set in the active network card’s TCP/IP configuration, under the "SubnetMask" value. Also, if MS DHCP client is enabled by BDRUPD, this option must also be set as "DhcpSubnetMask".
DHCP Reference Removing a Value The DHCP option 6 is used to set the DNS list. These 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 set to an empty string, and the data must be set to the DhcpNameServer value instead.
DHCP Reference NetBIOS Name for Clients The NetBIOS name of a Neoware Image Manager client is set to Client Host Name, as set by NVD name (see the Client Naming section), or by DHCP replies. This section deals only with the case when the client name is set only by DHCP option #12. The host name can be set with DHCP option #12, also known as or Host Name.
DHCP Reference Windows DHCP Client In previous versions of Neoware Image Manager, the client’s IP settings were set as "statically assigned address" (even if the address was provided by the DHCP server), and set by the Neoware Image Manager integrated DHCP client. This behaviour could lead to issues with some DHCP servers where the lease was not regularly renewed. To prevent this situation from occurring, the Windows DHCP client is now used by default.
DHCP Reference 328 Windows DHCP Client
Neoware Image Manager User Manual APPENDIX E Configuring NVDD as a Windows Service This appendix describes how to configure the Image Manager server as a Windows service. Introduction The Neoware Service Loader is a utility that enables execution of the Image Manager server as a service on Windows NT/2000/XP/ 2003 boxes that run the Image Manager server module nvdd.
Configuring NVDD as a Windows Service 3 In the Executable file field, enter the directory path and filename of the Neoware Image Manager server module (usually nvdd.exe). You can click the ... button to browse for the file. 4 The Command line field enables you to specify arguments that are to be sent to the Image Manager server module. These are usually in the form: -c nvdd..conf -n For example: -c nvdd.disk.bin.
Configuring NVDD as a Windows Service The following illustration shows the typical entries for configuring the Image Manager server to be run 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 server’s hard disk.
Configuring NVDD as a Windows Service 7 When all the required settings have 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.
Configuring NVDD as a Windows Service Using NVDD as a 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 the file system: Program Files/Neoware/Image_Manager_4.6/Server/Windows/SrvcLoaderSetup.exe. 2 Click the Start button to start the service.
Configuring 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 server box is switched on, even if no user actually launched the nvdd server module. You can also configure the Recovery options for the service.
Configuring NVDD as a Windows Service Uninstalling the Service To uninstall the NVDD service, just click the Uninstall button in the Neoware Service Loader Setup dialog. This will stop the service if it is running, and uninstall it from the system.
Configuring NVDD as a Windows Service 336 Using NVDD as a Service
Neoware Image Manager User Manual APPENDIX F NVDD Reference This appendix describes the command line options that can be used when launching the nvdd server module. Introduction 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 command line options that can be used when launching the nvdd server module.
NVDD Reference io Print messages relating to network and disk inputs/outputs. conf Print messages relating to initialization and configuration file parsing. timo Print messages relating to timeouts. Note that if all or timo is specified, nvdd will display all time-out messages, including those indicating that nvdd is waiting for communication. The message checking for idle clients will be displayed frequently.
NVDD Reference scripts or processes. In the case of a server having a power failure, nvdd will not be shutdown cleanly and the .LOCK file will remain, preventing nvdd from being launched automatically, at least while the .LOCK file has not been removed. Users should use this option only in startup 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 .
NVDD Reference 340 Command Syntax
Neoware Image Manager User Manual APPENDIX G NVD.SYS Reference This appendix describes the parameters that can be set in the registry entry for the NVD.SYS driver. Introduction At the client side, NVD.SYS is the Neoware Image Manager driver in charge of communications with the Image Manager server.
NVD.SYS Reference Sectors Per Request sector_per_request This DWORD value defines the maximum number of 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 less than 128 to fine tune the flow of data transmission between client and server. This has been proven to be useful (rarely) with some GigaEthernet/100BaseT switches for which the buffers dedicated to GigaEthernet packets were too small.
NVD.SYS Reference Network Interfaces Binding nic_list This REG_MULTI_SZ value contains indexes of network cards that are used by Image Manager as Virtual Drive controllers. The 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.
NVD.
Neoware Image Manager User Manual APPENDIX H File Transfer This appendix describes issues relating to the file transfer capabilities of Image Manager. Introduction Image Manager uses two file transfer protocols: • The file transfer protocol NVDFTP is integrated in the NVD protocol (the HDD emulation protocol), and is used in particular to transfer the Domain Credentials at boot and shutdown time.
File Transfer anyone who knows how to transfer files using NVDFTP or NVDAdmin could copy or replace the files in this folder, in particular your license file, your configuration files, your images etc. In order to add some security to NVDAdmin protocol, we recommend that you set a password on the server side (using the NvddPasswd tool - refer to the section “Password for Remote Administration” on page 210 for details).
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 it creates a temporary copy of the configuration file in the directory specified by the client_files_dir parameter in the nvdd configuration file, and uses this copy to work with. The temporary configuration file copy has the same name as the original configuration file but has the prefix current.
NVDD Temporary Files If the NVDD server crashes, due to a power failure for example, the temporary file current.nvdd.conf will still remain in the directory specified by client_files_dir. The next time nvdd is launched it will copy any files prefixed with current. into a subdirectory of the client_files_dir called restoredfiles, and add a timestamp to the end of each filename. This makes it possible for an administrator to recover configuration files that include changes that have not yet been applied.
NVDD Temporary Files named USER_REP.. This file is located in the directory where the NVDD server resides. You can also specify the directory in the Neoware Image Manager Console using the Client files folder option (select Generic options in the Tools menu, then click the Directories tab). When nvdd is stopped or restarted, or when the configuration file is reloaded (through the console or NVDDAdmin for instance), the USER_REP.
NVDD Temporary 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 deleted. The configuration will then contain the updated information.
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 the Neoware Image Manager-based boot process.
Boot Process Comparison 352
Boot Process Comparison 353
Boot Process Comparison 354
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 You can view our on-line support pages at the following Internet address: http://www.neoware.com/support.php Neoware offers various Technical Support programs. Check with your Neoware representative.
Troubleshooting In order to check versions, you can refer to the Release Notes document, or you can perform a “decompress” installation of Neoware Image Manager and check that the files you are using are actually the same as the ones in the “decompressed” folder. File version information may be embedded in files made for Windows (.EXE, .SYS, .DLL etc.) or may be displayed on screen when they are run. You can also refer to file dates and size, and you can use any file comparison tool.
Troubleshooting If your adapter or PXE implementation is not listed here, it does not mean that it will not work with Neoware Image Manager. In case it does not work as expected at the very beginning of the Windows 2K/XP boot process (e.g. you cannot see the first black and white character mode boot progress bar or Windows coloured splash screens, or the boot process is very slow), ask for an upgraded PXE code from the manufacturer of your NIC, motherboard or PXE code provider.
Troubleshooting Cause Certain types of DHCP servers, especially MS DHCP Server, may supply boot file names that are not terminated in a null character. Intel Architecture Labs PXE 2.1 addresses the null terminated boot file names, but fails to work correctly if the DHCP boot file size option is not present when using Intel Boot Agent 4.0.19. Solution This issue has been corrected in Intel Boot Agent 4.0.22. Update Intel Boot Agent to version 4.0.22 or above. Customers using IBA 4.0.
Troubleshooting Servers with Several Network Adapters If the server response to the client is unexpectedly slow and the server has several network card adapters, the Neoware Image Manager server module should be configured so that it is using only one of the server assigned IP addresses. Use the parameter address in the nvdd configuration file or use the Neoware Image Manager Console (Tools > Generic Options > Network) to specify which NIC to use.
Troubleshooting \SYSTEM32\DRIVERS (usually C:\WINNT\SYSTEM32\DRIVERS or C:\WINDOWS\SYSTEM32\DRIVERS). ACPI Stand By & Hibernation Stand By and Hibernation are currently not supported on Windows systems that run with Neoware Image Manager. NVD.SYS driver version 1.0.0.5 and after implements a mechanism that prevents Stand By or Hibernation to occur in most cases. If the system emits a request to enter into Stand By or Hibernation mode, NVD.
Troubleshooting value of 10 (10 seconds) is usually enough to let all the system component that still need to access the virtual disks. On the other hand, if the shutdown time seems too long, you can reduce this parameter value. Please refer to the appendix “NVD.SYS Reference” on page 341 for more details about this parameter.
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 protocol v1 when the server module is using NVD protocol v2. Make sure that the mPXELdr.BIN file that your TFTP servers are sending out comes from the same software package as your NVDD server software.
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 booted, it is recommended that you try setting this parameter to 32. If this gives better result, try 64 afterwards, and keep tuning until you have worse results. Values under 32 are usually not better. Tip: Test these setting changes within CVolwrite/Normal mode. Once you are happy with the setting, use Admin mode to make the final change. Refer to the appendix “NVD.
Troubleshooting ets. This results in lots of packets sent by the server being overwritten before they are dispatched to the 100BT ports. You should also enable flow control on the client and server NICs, and on the Ethernet switches if available. Please also refer to the section “Number of Sectors Per Read/Write Request” on page 362 for information on reducing the number of sectors in a single Neoware Image Manager request.
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 that are never restarted or that are up and running for long periods of time is very likely to lead to a "CVol file full" error.
Troubleshooting This will also make sure the logical volume is always clean at boot time. When CVolwrite/Volatile mode is not acceptable, you may schedule deletions of the CVol files on an acceptable basis (every night, every 3 days, every weekend etc…). A deletion batch file should: 1 CD to the directory where the CVol files are stored. 2 Shutdown all the clients that may have mounted a virtual drive off that server. 3 Stop the Neoware Image Manager server module. 4 Delete all the CVol files.
Troubleshooting by 8 (or the maximum CVol data size expressed in Kilobytes divided by 4). For example, if the maximum number of sectors in a CVol is 1048576 (the maximum size of a CVol is then 512MB), the maximum size of Virtual Memory file should be 128MB.
Troubleshooting Large File Support on Linux 2.2 Error When Opening a Large Volume On some Linux servers you may encounter a File Too Large error when NVDD starts and tries to open a volume file that is larger than 2GB. This is caused by the lack of Large File Support in some Linux systems. Without Large File Support, Linux cannot handle file sizes bigger than 2GB. Resolution: 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.
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 to have different SIDs.
Troubleshooting A large number of stations on one single server MAY be supported, with no warranty, with a configuration in which the following recommendations are met: 1 The server should have at least 2 Ethernet 1000 NICs teamed as a single network adapter so that the server theoretical bandwidth is 2Gb/s or more. 2 The Ethernet switches should have 1000-100Mb/s capabilities and should be able to handle correctly large amounts of buffered packets, WITHOUT DROPPING THEM.
Troubleshooting 6 The clients should have enough memory for the Page File (swap file) to be disabled or reduced to its minimum (around 20MB). 7 The clients should only run useful applications, not any Network/HardDisk consuming application such as video streaming, games... etc.. When designing a fleet of Neoware Image Manager stations, you should keep in mind that each client needs to have enough of the global bandwidth, and server disk access should be designed in consequence.
Troubleshooting Recommended Network Configuration The following network configuration recommendations should help you to achieve better performances and avoid congestion. • Never use uplinked Ethernet switches. • Use good quality Ethernet controllers on the server and the clients. • You can use teamed network adapters on the server to increase server network bandwidth. • Use fast HDs on the server. The fastest the server HDs, the better performances.
Troubleshooting • If local Hard Drives are available to the clients, configure Win- dows 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.
Troubleshooting 374 Recommended Network Configuration
Neoware Image Manager User Manual APPENDIX L Copyright Notices & License Terms This appendix provides the copyright notices and license terms for software embedded in Neoware Image Manager components. Patents Neoware Image Manager software suite is protected by a number of patents: EP1808763, EP1728164, WO2007006960, WO0193016. Patents pending. Third Parties Copyrights Neoware Image Manager embeds software codes that are copyrighted by third parties.
Copyright Notices & License Terms Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1 The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.
Copyright Notices & License Terms Software Copyrighted by Lukas Gebauer Project: Delphree - Synapse 003.006.004 Content: HTTP client Copyright (c)1999-2003, Lukas Gebauer. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1 Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Copyright Notices & License Terms The Initial Developer of the Original Code is Lukas Gebauer (Czech Republic). Portions created by Lukas Gebauer are Copyright (c) 1999-2003. All Rights Reserved. Contributor(s): History: see HISTORY.HTM from distribution package (Found at URL: http://www.ararat.cz/synapse/) _________________________________________________ Project: Delphree - Synapse 002.002.003 Content: SNTP client Copyright (c)1999-2003, Lukas Gebauer. All rights reserved.
Copyright Notices & License Terms OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The Initial Developer of the Original Code is Lukas Gebauer (Czech Republic). Portions created by Lukas Gebauer are Copyright (c)2000-2003. All Rights Reserved.
Copyright Notices & License Terms 380 Third Parties Copyrights
Neoware Image Manager User Manual Index 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 277 error messages 279 Expert options 276 NimCloner.exe 277 NimClonerGUI.
Index accessing images 59 activating Windows products 127 adding new 135 adding to Windows domain 147 assigning volumes to 65, 69 boot volume 68, 191, 235 changing name 234 configuring for images 62 display shared volumes 197 image creation 39 testing 54 installation requirements 19 license file 16 local HD access 123 locating Image Manager server 317 MAC address 224 maximum attached to server 369 mPXELdr.
Index introduction 39 using Client Builder 40 volume 193 current configuration file 347 CVol files description 80 location 81, 196, 201, 218, 230 maximum size 81, 196, 199, 221 merging with image file 137, 177 reducing size before merging 177 size of 32 storage requirements 32 CVolCompactor 177 CVolMerge 137, 177 CVolwrite mode 83, 227 domain adding clients to 147, 159, 168, 174 client IP addresses 168 client names 159, 174 credentials 148 management 147 roaming profiles 131 storing credentials in server d
Index building procedure 106 cloning 271 for booting any PC 103 local client access 123 partition size 19 use unknown hardware 110 using when UbiBoot-enabled 110 hard drive SATA 104 SCSI 104 hardware 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 Builder 39
Index Volume Properties Allowed Computers 198 Computers 197 CVol 196 General 193 Parameters 195 Image Manager 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 63 updating multiple remote servers 141 using Client Builder 40 installing Image Manager 19 InstallShiel
Index VolSelectionTO 265 mPXELdr.bin 9, 59, 295, 311, 318, 320, 357 MS-TFTP Server Helper 294 multiboot selection 68, 191, 235 multicore computers 115 multi-CPU computers 115 N NeoDomain.exe 147 Neoware Virtual Disk 9 Neoware Virtual Disk Daemon 9 NeowareIMClientBuilder.
Index nvdd.current.conf 346 nvdd.exe 33 nvdd.smalldisk.vol.conf 214 NVDDAdmin 242 command examples 243 command syntax 242 commands 243 NvddPasswd.
Index installation 19 system restore 58 system virtual volume restoring to actual HD 144 T technical support 355 temporary NVDD files 347 testing client images 54 TFTP server configuration 59 TFTPD managing 295 TFTPD Installer 293 TFTPDInstall.
Index allowed clients 231 allowed users 198 assigning to clients 65, 69 boot from 191 cache size 230 changing write mode 75 creating 193 creating new 70 CVol files 80 defining 193, 225 directory for 193, 218, 230 display 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.
Index 390
