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

Rules and recommendations for constructing the INI files, files

Page 8 highlights

• Scenario 3 - WNOS.ini exists and MAC.ini exists. The WNOS.ini file is processed and if the Include={username}.ini statement is included, then the {username}.ini file is processed. Once the credentials are provided, the MAC.ini file is processed. • Scenario 4 - No ini files exist. Local configuration is applied. Working with wnos.ini files A wnos.ini file contains the global parameters you want that will affect all thin clients accessing the server. Parameters in both Connection Settings: wnos.ini files only, and Connection Settings: wnos.ini files, {username} INI, and $MAC INI Files can be used in a wnos.ini file. NOTE: Parameters in Connection Settings: wnos.ini files only can only be used in a wnos.ini file; they cannot be used in a {username}.ini file. Working with $MAC.ini Files A $MAC.ini file can be used for device-specific configurations. If the thin client locates a wnos.ini file, then the wnos.ini file is processed and if the Include=$MAC.ini statement is included, then the $MAC.ini file is processed. The $MAC.ini file is stored in the same directory as a wnos.ini file if you are not using a WNOS.INI file, otherwise the files should be stored in the INC directory. NOTE: The placement of the include=$MAC.ini parameter within the wnos.ini file will dictate which value will take priority for a same specific parameter that is contained in both the wnos.ini file and the $MAC.ini file but is defined differently, that is different values for the same parameter. For example, if the wnos.ini file has parameterA=valueRED, and the $MAC.ini file has the same parameterA=valueBLUE, then: • If the include=$MAC.ini parameter is included in the wnos.ini file before the parameterA=valueBLUE statement, then the $MAC.ini parameterA=valueRED is discarded and parameterA=valueBLUE from the wnos.ini file is the final value used. • If the include=$MAC.ini parameter is included in the wnos.ini file after the parameterA=valueBLUE statement, then the $MAC.ini parameterA=valueBLUE is discarded and parameterA=valueRED from the wnos.ini file is the final value used. Working with {username}. ini files A {username}.ini file contains the user-specific or user profile parameters you want that will comprise the connection profile for an individual user. These parameters will affect only the user you specify. Parameters in General Settings for wnos.ini Files, {username} INI, and $MAC INI Files. NOTE: User profile parameters found in the {username}.ini file, generally override the identically named global parameters found in the wnos.ini file, 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 files, {username} INI, and $MAC INI Files can be used in a {username}.ini file. If both PNAgent/PNLite and a user profile are being used in the environment, the username must be defined 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 files In general, ThinOS INI files follow currently accepted standard INI file formatting conventions. The INI files consist of Wyse parameters. If you are using an INI file, 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. 8 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

Scenario 3
— WNOS.ini exists and MAC.ini exists. The WNOS.ini
file
is processed and if the Include={username}.ini statement is
included, then the {username}.ini
file
is processed. Once the credentials are provided, the MAC.ini
file
is processed.
Scenario 4
— No ini
files
exist. Local
configuration
is applied.
Working with wnos.ini
files
A wnos.ini
file
contains the global parameters you want that will
affect
all thin clients accessing the server. Parameters in both
Connection
Settings: wnos.ini
files
only
, and
Connection Settings: wnos.ini
files,
{username} INI, and $MAC INI Files
can be used in a wnos.ini
file.
NOTE:
Parameters in
Connection Settings: wnos.ini
files
only
can only be used in a wnos.ini
file;
they cannot be used in a
{username}.ini
file.
Working with $MAC.ini Files
A $MAC.ini
file
can be used for
device-specific
configurations.
If the thin client locates a wnos.ini
file,
then the wnos.ini
file
is processed and
if the Include=$MAC.ini statement is included, then the $MAC.ini
file
is processed. The $MAC.ini
file
is stored in the same directory as a
wnos.ini
file
if you are not using a WNOS.INI
file,
otherwise the
files
should be stored in the INC directory.
NOTE:
The placement of the include=$MAC.ini parameter within the wnos.ini
file
will dictate which value will take priority for a
same
specific
parameter that is contained in both the wnos.ini
file
and the $MAC.ini
file
but is
defined
differently,
that is
different
values for the same parameter.
For example, if the wnos.ini
file
has parameterA=valueRED, and the $MAC.ini
file
has the same parameterA=valueBLUE, then:
If the include=$MAC.ini parameter is included in the wnos.ini
file
before the parameterA=valueBLUE statement, then the $MAC.ini
parameterA=valueRED is discarded and parameterA=valueBLUE from the wnos.ini
file
is the
final
value used.
If the include=$MAC.ini parameter is included in the wnos.ini
file
after the parameterA=valueBLUE statement, then the $MAC.ini
parameterA=valueBLUE is discarded and parameterA=valueRED from the wnos.ini
file
is the
final
value used.
Working with {username}. ini
files
A {username}.ini
file
contains the
user-specific
or
user
profile
parameters you want that will comprise the connection
profile
for an
individual user. These parameters will
affect
only the user you specify. Parameters in
General Settings for wnos.ini Files, {username} INI, and
$MAC INI Files
.
NOTE:
User
profile
parameters found in the {username}.ini
file,
generally override the identically named
global
parameters found in the
wnos.ini
file,
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
files,
{username} INI, and $MAC INI Files
can be used in a {username}.ini
file.
If both PNAgent/PNLite and a user
profile
are being used in the environment, the username must be
defined
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
files
In general, ThinOS INI
files
follow currently accepted
standard
INI
file
formatting conventions. The INI
files
consist of Wyse parameters. If
you are using an INI
file,
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.
8
Getting Started: Learning INI File Basics