Optional Subkeys & Values - Neoware e140 - Thin Client User Manual

DHCP Reference
Optional Subkeys &
Values
322 Native DHCP Options
perform before continuing the process. The actual value
is useless, BDRUPD uses the type of the RegType
value as the type of the value(s) it will write to the keys.
Target : REG_MULTI_SZ. Contains couples of path + value to
modify. The data given by the DHCP option value will
be set at each path / value set in this list. The Target
value must contain an even number of strings. The first
string is a path to a key in the registry. The second string
is the name of the value to modify in the key whose path
is stored in the first string. The third string is a path to a
key in the registry. The fourth string is the name of the
value to modify in the key whose path is stored in the
third string, etc. For example, if the first string contains
\Registry\Machine\SOFTWARE\Neoware
ond string contains
value named
HKEY_LOCAL_MACHINE\SOFTWARE\Neoware
The process is as follows. BDRUPD gets a DHCP option value (or
an NVDDTag option value). It searches the corresponding subkey in
its registry parameters. If it exists, it reads the Type and RegType to
perform a conversion (if required). Then it reads the targets and
inserts the converted data to each location.
If an option needs multiple to be set at multiple places in the regis-
try, it is possible to add a new subkey to the option key. Subkeys are
numeric (starting at 1 and incrementing). BDRUPD will try to locate
these keys in order until it fails to find one. Each subkey has the
same structure as the main option key, except that it cannot have a
subkey. BDRUPD will process its content as described above.
When an option must be set only if a condition is validated, the user
can use the "If" and "IfNot" values, at the same level as the Reg-
Type, Type and Target values.
, BDRUPD will update the
Test
in the key:
Test
and the sec-
.