Reference Guide

Scenario 4 — No ini les exist. Local conguration is applied.
Working with wnos.ini les
A wnos.ini le contains the global parameters you want that will aect all thin clients accessing the server. Parameters in both Connection
Settings: wnos.ini les only, and Connection Settings: wnos.ini les, {username} INI, and $MAC INI Files can be used in a wnos.ini le.
NOTE: Parameters in Connection Settings: wnos.ini les only can only be used in a wnos.ini le; they cannot be used in a
{username}.ini le.
Working with $MAC.ini Files
A $MAC.ini le can be used for device-specic congurations. If the thin client locates a wnos.ini le, then the wnos.ini le is processed and
if the Include=$MAC.ini statement is included, then the $MAC.ini le is processed. The $MAC.ini le is stored in the same directory as a
wnos.ini le if you are not using a WNOS.INI le, otherwise the les should be stored in the INC directory.
NOTE: The placement of the include=$MAC.ini parameter within the wnos.ini le will dictate which value will take priority for a
same specic parameter that is contained in both the wnos.ini le and the $MAC.ini le but is dened dierently, that is dierent
values for the same parameter.
For example, if the wnos.ini le has parameterA=valueRED, and the $MAC.ini le has parameterA=valueBLUE, then:
If the parameter include=$MAC.ini is added in the wnos.ini le before the parameterA=valueBLUE statement, then
parameterA=valueRED is discarded and parameterA=valueBLUE is used.
If the parameter include=$MAC.ini is included in the wnos.ini le after the parameterA=valueBLUE statement, then the
parameterA=valueBLUE is discarded and parameterA=valueRED is used.
Working with {username}. ini les
A {username}.ini le contains the user-specic or user prole parameters you want that will comprise the connection prole for an
individual user. These parameters will aect only the user you specify. Parameters in General Settings for wnos.ini Files, {username} INI, and
$MAC INI Files.
NOTE
:
User prole parameters found in the {username}.ini le, generally override the identically named global parameters found in the
wnos.ini le, however, some global parameters do not allow this. For hierarchical precedence of one variable over another, refer to the
parameter descriptions in Connection Settings: wnos.ini les, {username} INI, and $MAC INI Files can be used in a {username}.ini le.
If both PNAgent/PNLite and a user prole are being used in the environment, the username must be dened in the Windows domain,
and the password used must be the same for both the Windows domain and the user.
Rules and recommendations for constructing the INI
les
In general, ThinOS INI les follow currently accepted standard INI le formatting conventions. The INI les consist of Wyse parameters. If
you are using an INI le, the only parameter you must use is the Connect parameter, see Connect in General Settings for wnos.ini Files,
{username} INI, and $MAC INI Files. Any of the rest of the parameters can be used if you desire, but are not necessary unless you want
changes from client and other defaults, for example, other can be the default resolution of your monitor.
Every parameter (and their options) has a name and a value, with the name appearing to the left of the equals sign (name=value). All
parameters with the same name in the various INI les have the same meaning that is, a parameter named WyseXYZ in a wnos.ini le and
named WyseXYZ in a {username}.ini le will have the same meaning.
Getting Started: Learning INI File Basics
7