HP Neoware e90 NeoLinux Thin Clients User Manual - Page 30

Network Settings dialog, netconfig.nl, DHCPSERVER, neoware, By default, this setting is

Page 30 highlights

Configuring Your Network Settings if it did not receive information in DHCP tag 137 (or tag number as redefined), by-passing the ezUpdate startup sequence. ezUpdate script file: [Default: netconfig.nl] By default, the script file name that is initially obtained from the ezUpdate server is netconfig.nl. Appliance profile: [Default: ] By default, the profile name field is empty. To maintain multiple device configurations using ezUpdate, the appliance profile name can be used. Creating separate profiles on the ezUpdate server allows you to point one or more appliances to a specific profile using this field. Specify manual settings: [Default: unchecked] This allows administrators who are configuring an ezUpdate server with a new profile, to override the existing ezUpdate settings for one or more appliances. This provides the ability to test a new configuration without exposing all installed appliances to the untested profile. By checking this checkbox, and using the manual settings fields below (which are not grayed out when the checkbox is checked), an individual appliance can test a configuration on any server. Protocol: By default, this setting is not available. If the Specify manual settings checkbox is checked, you can choose between ftp and nfs protocols for communication with the ezUpdate server. Set DHCP server as ezUpdate server: By default, this setting is not available. If Specify manual settings is checked, and this is unchecked, then you can define a server other than the DHCP server to provide the ezUpdate software or configurations by replacing the @DHCPSERVER entry to the IP address or DNS name of the ezUpdate server. Directory: By default, this setting is not available. If Specify manual settings is checked, you can define a directory or path within the ezUpdate directory structure other than the default /neoware. Username: By default, this setting is not available. If Specify manual settings is checked, you can define a username for accessing the ezUpdate server. 30 Network Settings dialog

  • 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
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138

Configuring Your Network Settings
30
Network Settings dialog
if it did not receive information in DHCP tag 137 (or tag number as
redefined), by-passing the ezUpdate startup sequence.
ezUpdate script file:
[Default:
netconfig.nl
] By default, the script
file name that is initially obtained from the ezUpdate server is
net-
config.nl
.
Appliance profile:
[Default: <Empty>] By default, the profile name
field is empty. To maintain multiple device configurations using
ezUpdate, the appliance profile name can be used. Creating separate
profiles on the ezUpdate server allows you to point one or more
appliances to a specific profile using this field.
Specify manual settings:
[Default: unchecked] This allows admin-
istrators who are configuring an ezUpdate server with a new profile,
to override the existing ezUpdate settings for one or more appli-
ances. This provides the ability to test a new configuration without
exposing all installed appliances to the untested profile. By checking
this checkbox, and using the manual settings fields below (which are
not grayed out when the checkbox is checked), an individual appli-
ance can test a configuration on any server.
Protocol:
By default, this setting is not available. If the Specify
manual settings checkbox is checked, you can choose between
ftp
and
nfs
protocols for communication with the ezUpdate server.
Set DHCP server as ezUpdate server:
By default, this setting is not
available. If Specify manual settings is checked, and this is
unchecked, then you can define a server other than the DHCP server
to provide the ezUpdate software or configurations by replacing the
@DHCPSERVER
entry to the IP address or DNS name of the ezUp-
date server.
Directory:
By default, this setting is not available. If Specify man-
ual settings is checked, you can define a directory or path within the
ezUpdate directory structure other than the default
/neoware
.
Username:
By default, this setting is not available. If Specify man-
ual settings is checked, you can define a username for accessing the
ezUpdate server.