HP Neoware e90 ezRemote Manager 3.0 User Manual - Page 91

config.txt, The Create Auto Update Configuration dialog will open.

Get HP Neoware e90 - Thin Client PDF manuals and user guides View all HP Neoware e90 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 91 highlights

config.txt nections button in the ezRemote Manager toolbar, or select Connections from the Actions menu bar item. 3 When the Neoware Appliance Connection Manager appears, select the template appliance from the list of appliances on the left-hand side. 4 Click the Get button. When ezRemote Manager finishes uploading the appliance's connections, the Save As button will become active. 5 Click the Save As button. The Save As dialog will open. 6 Browse to either the FTP directory or a temporary directory and click the Save button. For ezUpdate to function properly, this file must be placed in the FTP directory the DHCP tag 137 specifies. This file describes the software, connection, and property configuration versions available on the FTP server for appliances to download. To create the config.txt file: 1 Select Auto Update from the Actions menu. The Create Auto Update Configuration dialog will open. 2 In the Enter Auto Update Directory field, specify the FTP directory to which DHCP tag 137 points (the URL path as it appears in the DHCP tag). This entry must include the full path on the FTP server specified. 3 In the Software Version field, specify the name of the folder containing the Neoware Windows CE software. "3000" is the default name for this folder. 4 In the Properties Registry File field specify both the name of the properties.rgy file located in the FTP directory (by default, "properties.rgy"), and the version in the accompanying Version field. Creating ezUpdate files 91 List View

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
Creating ezUpdate files
91
List View
nections button in the ezRemote Manager toolbar, or select Con-
nections from the Actions menu bar item.
3
When the Neoware Appliance Connection Manager appears,
select the template appliance from the list of appliances on the
left-hand side.
4
Click the Get button.
When ezRemote Manager finishes uploading the appliance’s con-
nections, the Save As button will become active.
5
Click the Save As button.
The Save As dialog will open.
6
Browse to either the FTP directory or a temporary directory and
click the Save button.
For ezUpdate to function properly, this file must be placed in the
FTP directory the DHCP tag 137 specifies.
config.txt
This file describes the software, connection, and property configura-
tion versions available on the FTP server for appliances to down-
load. To create the
config.txt
file:
1
Select Auto Update from the Actions menu.
The Create Auto Update Configuration dialog will open.
2
In the Enter Auto Update Directory field, specify the FTP direc-
tory to which DHCP tag 137 points (the URL path as it appears in
the DHCP tag).
This entry must include the full path on the FTP server specified.
3
In the Software Version field, specify the name of the folder con-
taining the Neoware Windows CE software. “3000” is the default
name for this folder.
4
In the Properties Registry File field specify both the name of the
properties.rgy
file located in the FTP directory (by default, “prop-
erties.rgy”), and the version in the accompanying Version field.