Specifications

System Administration 27
Knowing the General Rules of the ini Files
General rules of the .ini files include the following:
• Commands and parameters can be entered for reference as necessary but are not
mandatory unless changes from defaults are required. Certain parameters to the
Connect= commands are mandatory and are noted in Tables 2 through 4.
• Commands and parameters must always be separated by spaces, regardless of the
command.
• Blank lines can be used to enhance readability.
• Use \ as the last character at the end of a line (that is, \<Enter>) to indicate line
continuation. There must be no white space between the \ and the <Enter>
character. However, white space between parameter entries must be maintained. If the
\<Enter> is not separated by at least one space from the last character of the line,
the next line must start with a space or have the first set of characters concatenated
with the last set from the continued line. For this reason, it is recommended that all
continuation lines start with at least one space character. If all commands start at the
left margin and all continuation lines have at least one leading blank, the indentation
will enhance the readability of the ini file.
•The # character may appear anywhere on a line and all following characters (including
those on continuation lines) are commented out until the end of the command is
reached.
• String parameters containing white spaces must be placed within quotation marks (use
common-practice nesting rules).
• For parameter list selections of type {0, 1}, 0 indicates false or no, and 1 indicates
true or yes, as applicable. The older {0, 1} format is equivalent to and may be used
instead of the {no, yes} format where indicated in Tables 2 through 4.
• For a URL parameter type, the parameter is assumed to point to a file under the thin
client's home directory. The home directory is the wnos subdirectory for the log-in (you
can specify username and password for file server access) of the file server that is
specified by the File Server entry in the Network Setup dialog box. If a File Server
directive is processed, the same user ID and password already configured on the thin
client must be usable for accessing files on the new file server.
• Use semicolons or commas for list separators (such as for the list of ICA browsers).
• All {username}.ini files must be write-enabled to allow the thin client to place the
encrypted user passwords in the files.
• The combined number of connection entries defined in a {username}.ini file and
the wnos.ini file cannot exceed a defined total maximum number of connections.
The maximum number of connections has a default limit of 216, but can be set from
100 to 1000 through wnos.ini.
Note
{username}.ini Only - The command which is valid in {username}.ini only is
the password command. If it is present, it must be the first command in the
file. It is created and updated by the thin client; it is not inserted by the
administrator. When the Change Password check box is checked in the
log-in dialog box, the user is prompted for a new password. The thin client
checks to ensure that the two copies of the password are the same, encrypts
the password, places it at the beginning of the user’s ini file (replacing any
previous password command), and writes the file back to the file server. If
the user forgets the password, the administrator may edit the appropriate ini
file, delete the password command and save the result. Then the next time
the user attempts to log in, no value should be placed in the password field of
the log-in dialog box. Because the password is encrypted using a one-way
algorithm, the original password value can not be recovered from the ini file.
A new password must be created.