54 Appendix AHow INI Files are EmployedINI files (created and maintained by the administrator) determine how the thin client isconfigured. The thin client accesses INI files from the server during the initializationprocess. Typically, INI files are accessed through FTP, HTTP, and HTTPS; if no protocolis specified, the default is anonymous FTP.INI files are employed as follows:• wlx.ini - This is the global INI file. One wlx.ini file is available to all users. It containsglobal parameters for all thin clients accessing the server. If the operating systemcannot find wlx.ini, it defaults to wnos.ini.• {username}.ini - This file is unique to each user. The {username}.ini file contains theconnection profile for each user. Parameters in the user profile generally supersedethe identically named global parameters.• $MAC.ini - This file can be used for device-specific configuration. If the thin clientlocates this INI file (it is stored in the same directory as wlx.ini), wlx.ini is notaccessed, unless you use the include=wlx.ini parameter.When a thin client is initialized, it accesses the global wlx.ini file. When a user logs in,the thin client accesses the user’s unique {username}.ini file. For detailed informationon constructing and using Wyse Enhanced Ubuntu Linux INI files, refer to ReferenceGuide: Dell® Wyse Enhanced Ubuntu™ Linux INI Files.TIP: If both PNLite and a user profile are being used, the username must be defined inthe Windows domain to be used, and the password must be the same for the domainand the profile.