Home » HP Manuals » Desktops » HP Neoware e90 » Manual Viewer

HP Neoware e90 ezRemote Manager 3.0 User Manual - Page 112

Step 4. Update the Update Version File name, Step 5. Apply the initial update

Add to My Manuals
Save this manual to your list of manuals

Page 112 highlights

• Copy the cloned image to the FTP server and rename the image: "image.dd" (\\10.10.80.10\c_drive\Inetpub\ftproot\neoware\xpe\192\factory\image.dd) Step 4. Update the Update Version File name • Rename the version file name to: "2" Note: This is to match the Update Version set in Step 2, above. If the version file name does not match the Update Version setting that is contained in image.dd, then the XPe appliances will reboot and run ezUpdate image update continuously. The default Update Version setting in software update packages distributed by Neoware is "1." Step 5. Apply the initial update • Reboot the thin client appliances XPe ezUpdate Advanced Topics Profiles for XPe ezUpdate Profiles are a mechanism for maintaining separate configurations for otherwise identical Neoware XPe thin client appliances. You can add as many profiles as you like, but should always leave the \factory profile intact. Once configured to use a specific profile, at boot-up the XPe appliance looks to the profile folder for a new image file, and for new or updated snap-ins. To create a new profile, add a folder at the same level as the appropriate \factory folder and name the new folder the name of the profile. For example: A profile for call-center XPe thin client appliances (256 MB Flash disk models) might be "callcenter." The full pathname to the folder would thus be: ftp://servername/neoware/xpe/ 256/callcenter The \callcenter folder should contain these files: 1 (or other update version file name), snapins.txt, and optionally image.dd. The version file should be named the same as the Update Version setting in the 112 XPe ezUpdate Advanced Topics

Section	Page
Table of Contents	3
CHAPTER 1 Introduction	7
Overview	7
Complete remote management of Neoware thin client appliances	7
ezRemote Manager distribution	8
Getting More Information	9
The Internet	9
Technical support	9
CHAPTER 2 Installing ezRemote Manager	11
Installing ezRemote Manager	11
Installing ezRemote Manager	11
Uninstalling ezRemote Manager	12
CHAPTER 3 Asset Manager	13
Asset Manager functions not available in Support Mode	13
Building an asset database	13
Locating thin client appliances	13
List view	16
List view thin client appliance information	16
Sorting the list view	17
Renaming thin client appliances	17
Adding one or more thin client appliances to the list view	19
Adding a single thin client appliance	20
Adding multiple thin client appliances using a range of IP addresses	20
Adding thin client appliances using a list of IP addresses	21
Grouping in asset lists	22
Creating a new group	22
Printing list views	23
Switching to the task view	23
Adjusting the list view	23
Saving and automatically retrieving asset lists	24
Apply Database Access password	24
Exporting asset list data to other applications	25
File \| Export Database	25
Data exported	26
CHAPTER 4 Database Access Modes	27
Administrator and Support modes	27
Administrator mode functions	27
Support mode functions	28
Two database access passwords	28
Administrator mode access password	28
Enable Support Mode Access	29
Support Mode password	29
Retrieving ezRemote Manager asset list databases	30
Retrieving an asset list database	30
Using the proper database access password	31
Access mode indicators	31
Administrator access mode indicators	31
Support access mode indicators	32
CHAPTER 5 Updating Appliance Software	33
Software updates	33
Getting software updates	33
Accessing the Software Update Manager	33
XPe/NTe software cloning	35
Preparing the template or source appliance	36
Preparing the target appliances	36
Start the cloning process	36
Copying the cloned image to other XPe / NTe appliances	38
CHAPTER 6 Connection Manager	39
Connection Manager not available in Support Mode	39
Connections in thin client appliances	39
What are “connections”?	39
Connection cloning supported models	40
Cloned connection settings	41
What about other configuration settings?	41
Why clone connections?	41
Save time configuring thin client appliances	41
Create “standard desktops” using ezUpdate server configuration files	42
Setting up the template appliance	42
Creating connections	42
Cloning connections to other appliances	43
“Cloning” or copying connections from one thin client appliance directly to others	43
Loading connection configurations from a file	45
Saving connection configurations to file	46
CHAPTER 7 Properties Manager	49
Properties Manager not available in Support Mode	49
Device properties in thin client appliances	49
What are “properties”?	49
Which thin client appliances support property cloning?	50
Which appliance configuration items are not cloned using Properties Manager?	51
Which appliance configuration items are cloned using Properties Manager?	51
Why clone properties?	52
Save time configuring thin client appliances	52
Save standard configurations as backups	52
Create ezUpdate server configuration files	52
Setting appliance properties using ezAnywhere shadowing	53
Loading property settings from a file	55
Saving properties configurations to file	57
CHAPTER 8 Snap-In Manager	59
What is a Snap-In?	59
ezSnap Technology	59
Snap-In Manager	60
Apply snap-ins and more	60
Using the Snap-In Manager	60
CHAPTER 9 ezAnywhere Shadowing	63
What is shadowing?	63
Remote viewing and control	63
Underlying protocol	63
What is required to shadow a remote appliance	64
Client configuration	64
ezAnywhere shadowing and passwords	65
Initiating an ezAnywhere shadowing session	65
Error messages during ezAnywhere session initiation	66
CHAPTER 10 Sessions	69
Setting Session Parameters	69
Using the Set Session Parameters Dialog	70
Task view	72
Task view actions	73
Switching to the list view	74
Adjusting the task view	74
CHAPTER 11 Wake on LAN Operations	75
Wake on LAN and ezRemote Manager	75
What is Wake on LAN?	75
What does Wake on LAN do in ezRemote Manager?	75
Wake on LAN on demand	76
Automatic Wake on LAN (Auto Wake on LAN)	76
ezRemote Manager tasks that work with by Auto Wake on LAN	77
Configuring automatic Wake on LAN (Auto WOL)	77
Appendix A: Broadcast SNMP and Router Configuration	79
ezRemote Manager access to separate subnets through Cisco routers	79
Adding a route to your server	80
Configuring Router	80
Relevant Cisco Router Commands	82
Appendix B: ezUpdate for Windows CE Appliances	83
Windows CE ezUpdate	83
Requirements	83
Overview of procedure	84
FTP Server	84
DHCP Tag 137	84
Static IP Address	85
ezUpdate Server Configuration	86
Basic FTP server setup	86
Choosing the right instruction set	87
1Instruction Set A	87
Instruction Set B	88
Instruction Set C	89
Creating ezUpdate files	90
properties.rgy	90
connections.rgy	90
config.txt	91
Appendix C: ezUpdate for NeoLinux Appliances	93
ezUpdate and NeoLinux	93
Requirements	94
NeoLinux ezUpdate server package installation	94
Configuring ezUpdate via DHCP	95
Manually configuring ezUpdate on the client	95
Using ezUpdate to distribute NeoLinux software update packages	97
Using ezUpdate to distribute NeoLinux configurations	97
Updating connections and properties	97
install.nl	98
Version file	98
Configuration files	98
properties.rgy	98
connections.rgy	99
Setting the appliances for ezUpdate	100
ezUpdate Advanced Topics	102
Snap-ins	102
Appendix D: ezUpdate for Windows XPe Appliances	103
ezUpdate and Windows XPe	103
Suggested implementations	103
Requirements	104
Options	104
DHCP tag 137	104
FTP server setup	105
XPe ezUpdate server package	105
How XPe ezUpdate functions	109
Boot time check for updated software	109
Starting ezUpdate after the initial boot-up	110
Simple XPe ezUpdate example	110
Step 1. Install the XPe ezUpdate package	110
Step 2. Set up a “standard” XPe configuration	111
Step 3. Save the “standard” image to the ezUpdate server	111
Step 4. Update the Update Version File name	112
Step 5. Apply the initial update	112
XPe ezUpdate Advanced Topics	112
Profiles for XPe ezUpdate	112
Snap-ins for XPe ezUpdate	113