Reference Guide

• Scenario 1 — WNOS.ini exists. The WNOS.ini le is processed and if the Include=$MAC.ini (or Include={username}.ini) statement is

included, then the relative MAC.ini (or {username}.ini) le is processed.

• Scenario 2 — WNOS.ini exists and {username}.ini exists. The WNOS.ini le is processed and if the Include=$MAC.ini statement is

included, then the MAC.ini le is processed. Once the credentials are provided, the {username}.ini le is processed.

• Scenario 3 — WNOS.ini exists and MAC.ini exists. The WNOS.ini le is processed and if the Include={username}.ini statement is

included, then the {username}.ini le is processed. Once the credentials are provided, the MAC.ini le is processed.

• 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 Table 4:

Connection Settings: wnos.ini les only, and Table 7: Connection Settings: wnos.ini les, {username} INI, and $MAC INI Files can be used in

a wnos.ini le.

NOTE: Parameters in Table 4 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 the same parameterA=valueBLUE, then:

• If the include=$MAC.ini parameter is included in the wnos.ini le before the parameterA=valueBLUE statement, then the $MAC.ini

parameterA=valueRED is discarded and parameterA=valueBLUE from the wnos.ini le is the nal value used.

• If the include=$MAC.ini parameter is included in the wnos.ini le after the parameterA=valueBLUE statement, then the $MAC.ini

parameterA=valueBLUE is discarded and parameterA=valueRED from the wnos.ini le is the nal value 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 Table 5: 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 Table 7: 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 Table 5: General Settings for wnos.ini

Getting Started: Learning INI File Basics