Cisco Cisco Virtualization Experience Client 2111 Guida Di Riferimento
1-2
Cisco Virtual Experience Client 2112/2212 INI Files Reference Guide for WTOS 7.0_214
OL-25153-01
Chapter 1 Understanding WTOS INI Files
Rules and Recommendations for Constructing WTOS INI Files
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
the connection profile for an individual user. These parameters will affect only the user you specify.
Parameters in
can be used in a {username}.ini file.
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 notations in
“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 notations in
.
Warning
If both PNAgent/PNLite and a user profile are being used in the environment, the username must be
defined in the Windows domain to be used, and the password used must be the same for both the
Windows domain and the user profile.
defined in the Windows domain to be used, and the password used must be the same for both the
Windows domain and the user profile.
Rules and Recommendations for Constructing WTOS INI Files
In general, WTOS INI files follow currently accepted “standard” INI file formatting conventions. WTOS
INI files consist of WTOS parameters. These parameters can be entered as necessary for reference, but
are not mandatory unless changes from defaults are required or the parameter is noted as required in the
tables. Every parameter 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 WTOS INI files have the same meaning
(that is, a parameter named XYZ in a wnos.ini file and named XYZ in a {username}.ini file will have
the same meaning). Number signs (#) indicate the start of a comment. Comments can begin anywhere
on a line. Everything between the # and the End of Line is ignored.
INI files consist of WTOS parameters. These parameters can be entered as necessary for reference, but
are not mandatory unless changes from defaults are required or the parameter is noted as required in the
tables. Every parameter 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 WTOS INI files have the same meaning
(that is, a parameter named XYZ in a wnos.ini file and named XYZ in a {username}.ini file will have
the same meaning). Number signs (#) indicate the start of a comment. Comments can begin anywhere
on a line. Everything between the # and the End of Line is ignored.
Along with these general formatting conventions, use the following guidelines when constructing WTOS
INI files:
INI files:
•
Order of Parameters—Global connect parameters should be listed before other connect parameters
in a wnos.ini file.
in a wnos.ini file.
•
Mandatory Parameters—As stated earlier, parameters can be entered as necessary for reference,
but are not mandatory unless changes from defaults are required or the parameter is noted as
required in the tables. For example, the Connect= parameter is mandatory.
but are not mandatory unless changes from defaults are required or the parameter is noted as
required in the tables. For example, the Connect= parameter is mandatory.
•
Use of Backslashes and White Spaces—Placing a backslash (\) at the end of a line indicates line
continuation; that is, the backslash means that the line and the following line are, for the purposes
of reading code, the same line. No white space can appear after the backslash; however, white space
between parameter entries must be maintained. Therefore, the line after a backslash must either start
with a space (not a tab) or concatenate with the first set of characters from the previous line. To avoid
confusion, starting each line with at least one white space character is recommended. Starting all
parameters at the left margin and placing at least one leading space at the beginning of all
continuation lines makes an INI file easier to read.
continuation; that is, the backslash means that the line and the following line are, for the purposes
of reading code, the same line. No white space can appear after the backslash; however, white space
between parameter entries must be maintained. Therefore, the line after a backslash must either start
with a space (not a tab) or concatenate with the first set of characters from the previous line. To avoid
confusion, starting each line with at least one white space character is recommended. Starting all
parameters at the left margin and placing at least one leading space at the beginning of all
continuation lines makes an INI file easier to read.
•
Use of Blank Lines—Using blank lines is recommended for making code easier to read.
•
Use of Number Signs—As stated earlier, number signs (#) indicate the start of a comment.
Comments can begin anywhere on a line. Everything between the # and the End of Line is ignored.
Comments can begin anywhere on a line. Everything between the # and the End of Line is ignored.
•
Use of Quotation Marks—String parameters containing white spaces must be placed inside
quotation marks (use common-practice nesting rules).
quotation marks (use common-practice nesting rules).