Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell Wyse ThinOS 9.1.4234, 9.1.5067 and 9.1.6108 Migration Guide

PDF

ThinOS system variables

ThinOS uses system variables or part of a system variable when defining command values. System variables are often used to define unique values for fields such as terminal name or default user. For example, if the client has an IP address 123.123.123.022, ACC&Right($FIP,3) results in a value of ACC022. Using system variables makes it easier to manage groups of devices that require a unique terminal name or default user.

The following are the ThinOS system variables:

Table 1. ThinOS system variablesThinOS system variables
Variable Description
$IP IP address
$IPOCT4 The fourth octet of the IP Address, for example: if the IP address is 10.151.120.15, then the value is 15.
$MAC Mac address
$CMAC Mac address with colon.
$UMAC Mac address with uppercase letters is used.
$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. You must remap the options from GUI or INI if you want to use $DHCP(166) or $DHCP(167).

$DN Sign on domain name
$TN Terminal name
$UN Sign on username
$SUBNET For subnet notation, the format is {network_address}_{network_mask_bits}. For example, if the IP address is 10.151.120.15, the network mask is 255.255.255.0, and 10.151.120.0_24 is used.
$FIP

IP address is used in fixed format with 3 digits between separators. For example, 010.020.030.040.ini. Using it in conjunction with the left or 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.

$SN Serial number or Service tag
$VN Version number
Right($xx, i) or and Left($xx, i) Specifies that the variable is to be read from left or right. The $xx is any of above parameters and the parameter i specifies the digits for the offset of right or left.
$PF

Use the thin client’s platform name—This is the first part of image name xxxxx_wnos, for example, if the image name is A10Q_wnos, the platform name is A10Q, which refers to 3040. Other values include:

  • A10Q—3040 ThinOS
  • PA10Q—3040 ThinOS + PCoIP
  • X10—5070, 5470AIO, 5470MTC ThinOS
  • PX10—5070, 5470AIO, 5470MTC ThinOS + PCoIP
$PW Use the Sign-on password.
$WPDN PEAP/MSCHAPv2 domain used (802.1x dependent).
$WPPW PEAP/MSCHAPv2 password used (802.1x dependent).
$WPUN PEAP/MSCHAPv2 username used (802.1x dependent).
&Right($xx, i) or &Left($xx, i)

Specifies whether the variable is read from left or right. The $xx refers to any of the above System Variables. The option “i” specifies left or right offset digits. For example, the parameter TerminalName=CLT-$SN$RIGHT$07. If the Serial Number (or Service Tag number) of the thin client is MA00256, the terminal name of the thin client is assigned as below:

  • First four characters—CLT-
  • The rest—The last right-most seven digits of the thin client serial number. The resulting terminal name is displayed as CLT-MA00256.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\