HP Neoware e140 Neoware Image Manager 4.6 User Manual - Page 156
you commit the changes to, which is now your production image
View all HP Neoware e140 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 156 highlights
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. When you update it, you must commit the changes into the file MyImage2.vol. Then you configure the clients to boot off MyImage2. Later, when you want to update MyImage2 (which is now your production image), you commit the changes to MyImage1.vol and set the clients to boot off MyImage1. Using this method is very efficient and secure, as you always have a backup copy of the unmodified image. 9 Start or reload the NVDD server module with its new configuration. Now when the clients boot, they can use the new application, the new system settings are applied to them, etc. 140 Modifying an HD Image to be Used by Several Clients