Dell Wyse 3020 Wyse ThinOS Version 8.5 INI Reference Guide - Page 10

System variables

Get Dell Wyse 3020 PDF manuals and user guides View all Dell Wyse 3020 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 10 highlights

NOTE: No parameter should ever be executed twice. Some ThinOS hardware configuration parameters require a reboot to become active, and if the same parameters are defined more than once, the thin client may then go into an infinite reboot cycle. IMPORTANT: We recommend you place the include= statement on the last line of the wnos.ini file to verify that all parameters are processed properly for terminal-specific settings. 11 Use of System Variables with Some Options of the Connect Parameter Some options of the Connect parameter can use the system variables shown in System Variables to map the string. All combinations of the variables are supported. For options that support use of system variables, see Connect Parameters Options. System variables The following table contains the system variables you can use with some options of the connect parameter: Table 2. System variables Option $SN $MAC $IP $IPOCT4 $TN $PF $UN $PW $DN $FIP Value Serial number used. MAC address used. IP Address used. The fourth octet of IP Address, for example, if IP is 10.151.120.15, then the fourth octet is 15. Terminal name. Platform name-The first part of image name xxx_wnos, for example, R10L. Sign-on name used. Sign-on password used. Sign-on domain name used. IP address used in fixed format with 3 digits between separators, for example, 010.020.030.040.ini. Using it in conjunction with the left/right modifier helps to define policy for subnet. For example, include=&Left($FIP,11).ini is specified to include file 010.020.030.ini for subnet 010.020.030.xxx. $WPUN $WPPW $WPDN $DHCP (extra_dhcp_option) $SUBNET PEAP/MSCHAPv2 username used (802.1x dependent). PEAP/MSCHAPv2 password used (802.1x dependent). PEAP/MSCHAPv2 domain used (802.1x dependent). Extra DHCP options for Windows CE unit, including 169, 140, 141, 166, 167. For example, set a string test169 for option tag 169 in DHCP server, and set TerminalName=$DHCP(169) in wnos.ini. Check terminal name in GUI, and the terminal name will be test169. 166 and 167 is default for CCM MQTT Server and CCM CA Validation in ThinOS. So you need to remap the options from GUI or INI if you want to use $DHCP(166) and/or $DHCP(167). Specifies Subnet notation. The format is {network_address}_{network_mask_bits}. For example, if the IP 10 Getting Started: Learning INI File Basics

  • 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
NOTE:
No parameter should ever be executed twice. Some ThinOS hardware
configuration
parameters require a reboot to become
active, and if the same parameters are
defined
more than once, the thin client may then go into an
infinite
reboot cycle.
IMPORTANT:
We recommend you place the include=<$mac.ini or {username}> statement on the last line of the wnos.ini
file
to verify that all
parameters are processed properly for
terminal-specific
settings.
11
Use of System Variables with Some Options of the Connect Parameter
Some options of the Connect parameter can use the system variables shown in
System Variables
to map the string. All combinations
of the variables are supported. For options that support use of system variables, see
Connect Parameters Options
.
System variables
The following table contains the system variables you can use with some options of the connect parameter:
Table 2. System variables
Option
Value
$SN
Serial number used.
$MAC
MAC address used.
$IP
IP Address used.
$IPOCT4
The fourth octet of IP Address, for example, if IP is 10.151.120.15,
then the fourth octet is 15.
$TN
Terminal name.
$PF
Platform name—The
first
part of image name xxx_wnos, for
example, R10L.
$UN
Sign-on name used.
$PW
Sign-on password used.
$DN
Sign-on domain name used.
$FIP
IP address used in
fixed
format with 3 digits between separators,
for example, 010.020.030.040.ini. Using it in conjunction with the
left/right
modifier
helps to
define
policy for subnet.
For example, include=&Left($FIP,11).ini is
specified
to include
file
010.020.030.ini for subnet 010.020.030.xxx.
$WPUN
PEAP/MSCHAPv2 username used (802.1x dependent).
$WPPW
PEAP/MSCHAPv2 password used (802.1x dependent).
$WPDN
PEAP/MSCHAPv2 domain used (802.1x dependent).
$DHCP (extra_dhcp_option)
Extra DHCP options for Windows CE unit, including 169, 140, 141,
166, 167. For example, set a string test169 for option tag 169 in
DHCP server, and set TerminalName=$DHCP(169) in wnos.ini.
Check terminal name in GUI, and the terminal name will be test169.
166 and 167 is default for CCM MQTT Server and CCM CA
Validation in ThinOS. So you need to remap the options from GUI or
INI if you want to use $DHCP(166) and/or $DHCP(167).
$SUBNET
Specifies
Subnet notation. The format is
{network_address}_{network_mask_bits}. For example, if the IP
10
Getting Started: Learning INI File Basics