HP Neoware e90 ezRemote Manager 3.0 User Manual - Page 95

Configuring ezUpdate via DHCP, Manually configuring ezUpdate on the client

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 95 highlights

List View Configuring ezUpdate via DHCP A Dynamic Host Configuration Protocol (DHCP) server may be configured to provide Neoware thin client appliances with the location (URL) of the ezUpdate server and files (the ezUpdate directory). Although ezUpdate can be configured to use any DHCP tag number, by default ezUpdate is configured to use DHCP tag 137. The ezUpdate DHCP tag (by default, tag 137) may be set on your DHCP server to specify the FTP or NFS location (URL) of configuration and/or software update files. If provided by DHCP, NeoLinux thin client appliances will use the URL to check for updated configuration files or updated software files at every bootup. The syntax of the URL address provided in the ezUpdate DHCP tag depends on the type and setup of the ezUpdate server you are using. For password-protected FTP, the URL should be in the following format: ftp://username:password@host/path_to_ezupdate_directory For anonymous FTP, the URL should be in the following format: ftp://host/path_to_ezupdate_directory If you are using anonymous FTP, and your FTP server resides on the same machine as your DHCP server, the URL should be in the following format: ftp://@DHCPSERVER/path_to_ezupdate_directory For an NFS server, the URL should be in the following format: nfs://host/path_to_ezupdate_directory On an NFS server, the ezUpdate directory should be shared for all users, read-only access. Manually configuring ezUpdate on the client If DHCP is not used to provide the path information to the ezUpdate directory, that information may be entered in the NeoLinux client setup interface. Even if DHCP is used, the NeoLinux client ezUpdate configuration may be set to ignore the DHCP setting. To manually configure ezUpdate on the NeoLinux thin client appliance: ezUpdate and NeoLinux 95

  • 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
ezUpdate and NeoLinux
95
List View
Configuring
ezUpdate via DHCP
A Dynamic Host Configuration Protocol (DHCP) server may be
configured to provide Neoware thin client appliances with the loca-
tion (URL) of the ezUpdate server and files (the ezUpdate direc-
tory). Although ezUpdate can be configured to use any DHCP tag
number, by default ezUpdate is configured to use DHCP tag 137.
The ezUpdate DHCP tag (by default, tag 137) may be set on your
DHCP server to specify the FTP or NFS location (URL) of configu-
ration and/or software update files. If provided by DHCP, NeoLinux
thin client appliances will use the URL to check for updated config-
uration files or updated software files at every bootup.
The syntax of the URL address provided in the ezUpdate DHCP tag
depends on the type and setup of the ezUpdate server you are using.
For password-protected FTP, the URL should be in the following
format:
ftp://username:password@host/path_to_ezupdate_directory
For anonymous FTP, the URL should be in the following format:
ftp://host/path_to_ezupdate_directory
If you are using anonymous FTP, and your FTP server resides on the
same machine as your DHCP server, the URL should be in the fol-
lowing format:
ftp://@DHCPSERVER/path_to_ezupdate_directory
For an NFS server, the URL should be in the following format:
nfs://host/path_to_ezupdate_directory
On an NFS server, the ezUpdate directory should be shared for all
users, read-only access.
Manually
configuring
ezUpdate on the
client
If DHCP is not used to provide the path information to the ezUpdate
directory, that information may be entered in the NeoLinux client
setup interface. Even if DHCP is used, the NeoLinux client ezUp-
date configuration may be set to ignore the DHCP setting.
To manually configure ezUpdate on the NeoLinux thin client appli-
ance: