Dell Wyse Enhanced SUSE Linux Enterprise Release 11 SP3 INI Guide

Transcription

1 Dell Wyse Enhanced SUSE Linux Enterprise Release 11 SP3 INI Guide

2 Notes, cautions, and warnings A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright 2015 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. Dell and the Dell logo are trademarks of Dell Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies Rev. A00

3 Contents 1 Introduction... 5 Summary of Revisions... 5 The following changes were made to this document since revision...5 About this Guide... 7 Dell Wyse Technical Support...8 Related Documentation and Services... 8 Dell Wyse Online Community Getting Started: Learning INI File Basics... 9 Supported INI Files you can Construct... 9 Working with wlx.ini Files Working with Username.ini Files...10 Working with MAC.ini Files...10 Rules and Recommendations for Constructing the INI Files...11 System Variables Placing the INI Files into the Folder Structure on the Server Parameters for WLX INI and MAC INI files only General Settings for wlx.ini and mac.ini Files Peripheral Settings(wlx.ini and MAC.ini Files Only) Connection Settings for wlx.ini and MAC.ini Files Only Custom GNOME Settings for wlx.ini and MAC.ini Files Only Parameters for WLX INI, MAC INI and Username INI Files General Settings For wlx.ini, MAC.ini and username.ini Files Peripheral Settings For wlx.ini, MAC.ini and username.ini Files Connection Settings For wlx.ini, MAC.ini and username.ini Files Connect Parameter Options...67 Custom Connect Options...67 Ericom PowerTerm TEC Connect Options Ericom PowerTerm WebConnect Connect Options...71 ICA Connect Options...72 Imprivata Connect Options Mozilla Firefox Connect Options...79 RDP Connect Options SSH Connect Options...86 VMware View Client Connect Options

4 VNC Viewer Connect Options...92 vworkspace Connect Options XDMCP Connect Options...98 Configuration Parameters for Wyse Device Agent Printer Parameters Options Jet Direct Printer NetworkPrinter Printer PrinterURI SMBPrinter TimeZone Parameter: Values Keyboard.layouts Parameter: Values

5 Introduction 1 Dell Wyse Enhanced SUSE Linux Enterprise (SLE) from Dell combines the security, flexibility and marketleading usability of SUSE Linux Enterprise with Dell s thin computing optimizations in management and user experience. It is ideal for organizations that want to run server-based, Web-based or local applications including legacy applications without the deployment and security concerns of a nonstandard Linux distribution. Session and networks services available on enterprise networks may be accessed on enterprise networks. A direct intranet connection or from a remote location using a secure gateway from Citrix or VMware. Dell Wyse Enhanced SLE Initialization (INI) files are plain-text files that you can construct to contain the configuration information you want for your thin clients running on. Dell Wyse Enhanced SLE for both global level and individual user level. For example, these INI files can be used by applications to save information about a user s preferences and operating environment. Information and procedures presented in this guide are intended for use by system administrators and should not be used by untrained persons. Summary of Revisions The following changes were made to this document since revision Reference Description AnonymousIdentity AnonymousIdentity parameter is added to Table 4 Connection Settings: wlx.ini files and MAC.ini files only. Used as the unencrypted identity with EAP types that support different tunneled identity like EAP-TTLS. AutoSignoff Default is no DelayedUpdate.Delay Default is 60 New INI parameter is added to Table 4Connection Settings: wlx.ini files and MAC.ini files only. DelayedUpdate.Delay is added to Table 4 Connection Settings: wlx.ini files and MAC.ini files only. 5

6 DelayedUpdate.Enable Default is false DelayedUpdate.Interval Default is 300 New INI parameter is added to Table 4 Connection Settings: wlx.ini files and MAC.ini files only.to enable the delayed/cached updating functionality. DelayedUpdate.Interval is updated to Table 4 Connection Settings: wlx.ini files and MAC.ini files only. DelayedUpdate.MaxRate Default is 100G This parameter is added to Table 4 Connection Settings: wlx.ini files and MAC.ini files only.the optional letter suffix indicates a multiplier: (Bytes, Kilobytes, Megabytes, or Gigabytes). DelayedUpdate.Mode Default is both New INI parameter is added to Table 4 Connection Settings: wlx.ini files and MAC.ini files only. DelayedUpdate.Preserve Default is true This INI parameter is added to Table 4 Connection Settings: wlx.ini files and MAC.ini files only. DelayedUpdate.TimeOut Default is 0 (no timeout) New INI parameter is updated to Table 4 Connection Settings: wlx.ini files and MAC.ini files only. FirmwarePassword FirmwareRootPath FirmwareServer FirmwareUserName ICAAutoLaunchApp ICA.ShowAllApps This parameter is added to Table 4 Connection Settings: wlx.ini files and MAC.ini files only. It specifies the password needed for accessing image files on file repository server This parameter is added to Table 4 Connection Settings: wlx.ini files and MAC.ini files only. This parameter is added to Table 4 Connection Settings: wlx.ini files and MAC.ini files only. This parameter is added to Table 4 Connection Settings: wlx.ini files and MAC.ini files only. New INI parameter is added to Table 4 Connection Settings: wlx.ini files and MAC.ini files only. Default is false. 6

7 ICA.ShowAllApps parameter is updated to Table 8 Connection Settings For wlx.ini, MAC.ini and username.ini Files. Language ManagementServer This new parameter is added to Table 6 General Settings For wlx.ini, MAC.ini and username.ini Files. It specifies the UI language and the locality where it will be used. New parameter is added to Table 2 General Settings: wlx.ini files and MAC.ini files only For hagent and WDA to run. MultiDesktop RdpDriveMap New INI parameter is added to Table 7 Peripheral Settings For wlx.ini, MAC.ini and username.ini Files. Default is false. This new parameter is added to Table 8 Connection Settings For wlx.ini, MAC.ini and username.ini Files. To enable or disable drive mapping in RDESKTOP session. RemoveCerts shutdownonsignoff TextTrackingEnabled RemoveCerts is a list of certificate names separated by a semicolon.,which needs to be removed. This parameter is added to Table 2 General Settings: wlx.ini files and MAC.ini files only. New parameter is added to Table 2 General Settings: wlx.ini files and MAC.ini files only. Default is false. This parameter is added to Table 12 ICA Connect Options. Upgrade.Image_RootPath VMWareViewIncludeUSBFamily VMWareViewIncludeUSBID New parameter is updated to Table 4 Connection Settings: wlx.ini files and MAC.ini files only. This INI parameter is added to Table 4 Connection Settings: wlx.ini files and MAC.ini files only. New parameter is added to Table 4 Connection Settings: wlx.ini files and MAC.ini files only. About this Guide This guide is intended for administrators of Dell thin clients running Dell Wyse Enhanced SUSE Linux Enterprise (SLE). It provides the detailed information you need to help you understand and use the Dell 7

8 Wyse Enhanced SLE INI files. It contains information on the different INI files you can use and the rules for constructing the files. It also provides the parameter details you need with working examples to get the most out of your INI. Finding the Information You Need in this Guide You can use either the Search window or Find toolbar to locate a word, series of words, or partial word in an active PDF document. For detailed information on using these features, refer to the Help in your PDF reader. Dell Wyse Technical Support To access Dell Wyse technical resources, visit For more information, you can submit your questions by using the Dell Wyse Self-Service Center at selfservice.html or call Customer Support at , Extension: Hours of operation are from 6:00 A.M. to 5:00 P.M. Pacific Time, Monday through Friday. To access international support, visit Related Documentation and Services Fact Sheets containing features of hardware products are available on the Dell Wyse website. Go to and select your hardware product to locate and download the Fact Sheet. To get support for your Wyse product, check your product Service Tag or serial number. For Dell service tagged products, find knowledge base articles and drivers on the Dell Wyse product pages. Refer to Dell TechDirect for online case submission and self service dispatch or contact the support phone queue. For Non-Dell Service Tagged Products, find all the support needed by accessing the Wyse support domain Dell Wyse Online Community Dell Wyse maintains an online community where users of our products can seek and exchange information about user forums. Visit the Dell Wyse Online Community forums at: en.community.dell.com/techcenter/enterprise-client/wyse_general_forum/. 8

9 Getting Started: Learning INI File Basics 2 In this chapter you learn how to construct and use the supported INI files. It includes: Supported INI Files You can Construct Rules and Recommendations for Constructing the INI Files Placing the INI Files into the Folder Structure on the Server After you become familiar with the INI file basics, you can refer to the parameter details you need in the other chapters and appendixes of this guide. Supported INI Files you can Construct The INI files contain the parameters and associated options and values necessary for the various functionalities you want. You can construct the following INI files: wlx. ini file. See Working with wlx.ini Files. {username}.ini file. See Working with username.ini Files. MAC.ini file. See Working with MAC.ini Files. Important: : The INI file processing hierarchy is as follows: Scenario 1 MAC.ini exists. The MAC.ini file is processed and if the Include=WLX.ini statement is included, then the WLX.ini file is processed. Scenario 2 MAC.ini exists and {username}.ini exists. The MAC.ini file is processed and if the Include=WLX.ini statement is included, then the WLX.ini file is processed. Once the credentials are provided, the {username}.ini file is processed. Scenario 3 wlx.ini exists. The WLX.ini file is processed. Scenario 4 wlx.ini exists and {username}.ini exists. The wlx.ini file processed, once the credentials are provided, the {username}.ini file is processed. Scenario 5 No ini files exist. Local configuration is applied. 9

10 Working with wlx.ini Files A wlx.ini file contains the global parameters you want that affects all thin clients accessing the server. Parameters in both Table 4, Connection Settings for wlx.ini and MAC.ini Files, and Table 8, Connection Setting for wlx.ini, MAC.ini, and username.ini Files can be used in a wlx.ini file. Parameters in Table 4, Connection Settings for wlx.ini and MAC.ini Files can only be used in a wlx.ini file; they cannot be used in a {username}.ini file. Working with Username.ini Files A {username}.ini file contains the user-specific or user profile parameters you want that comprises the connection profile for an individual user. These parameters affect only the user you specify. Parameters in Table 8, Connection Setting for wlx.ini, MAC.ini and username.ini Files. User profile parameters found in the {username}.ini file) generally override the identically named global parameters found in the wlx.ini file, however, some global parameters do not allow this for hierarchical precedence of one variable over another, refer to the parameter descriptions in Table 8, Connection Setting for wlx.ini, MAC.ini and username.ini Files If both PNAgent/PNLite and a user profile are being used in the environment, the username must be defined in the Windows domain used, and the password used must be the same for both the Windows domain and the user profile. Working with MAC.ini Files A MAC.ini file can be used instead of a wlx.ini file for device-specific configurations. If the thin client locates a MAC.ini file it is stored in the same directory as a wlx.ini file, then the wlx.ini file is not accessed, unless you use the include =wlx.ini parameter. Note also that the placement of the include =wlx.ini parameter within the MAC.ini file will dictate which value will take priority for a same specific parameter that is contained in both the wlx.ini file and the MAC.ini file but is defined for different values for the same parameter. For example, if the wlx.ini file has parameter A= value B, and the MAC.ini file has the same parameter A= value C, then: - If the include =wlx.ini parameter is included in the MAC.ini file before the parameter A= value C statement, then the wlx.ini parameter A= value B is discarded and paramete A= value C from the MAC.ini file is the final value used. - If the include =wlx.ini parameter is included in the MAC.ini file after the parameter A= value C statement, then the MAC.ini parameter A= value C is discarded and parameter A= value B from the wlx.ini file is the final value used. 10

11 Rules and Recommendations for Constructing the INI Files In general, Dell Wyse Enhanced SLE INI files follow currently accepted standard INI file formatting conventions. The INI files consist of Dell Wyse parameters. If you are using an INI file, the only parameter you must use is the Connect parameter,see Connect in Table 8 Connection Setting for wlx.ini, MAC.ini and username.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. Every parameter and their options have 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 INI files have the same meaning that is, a parameter named Dell Wyse XYZ in a wlx.ini file and named Dell Wyse XYZ in a {username}.ini file has 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 the INI files: 1. Global Connect Parameters First Global connect parameters should be listed before other connect parameters in a wlx.ini file. 2. Connect is the Only Required Parameter As stated earlier, if you are using an INI file, the only parameter you must use is the Connect parameter. Any of the rest of the parameters can be used if you desire, but are not necessary unless you want changes from client and otherdefaults. 3. Continue Lines by using a Space and Backslash Placing a space and 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; the requirement of white space between parameter entries is maintained by the use of the space before the backslash. In addition, starting all parameters at the left margin and placing at least one leading space or tab at the beginning of all and only continuation lines makes an INI file easier to read. In circumstances where you require string concatenation, you can use a backslash without a space before or after it to concatenate with the first set of characters from the previous line; for example the strings snow and ball may be concatenated to give snowball. 4. Blank Lines Make Files Easy to Read Using blank lines is recommended for making code easier to read. 5. Comment by using a # Sign 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. 6. Values with White Spaces Require Quotation Marks Values of parameters and their options containing white spaces must be placed inside quotation marks use common-practice nesting rules. 7. Separate Lists by using Semicolons or Commas 11

12 Use semicolons or commas for list separators. 8. {username}.ini Files must be Write-Enabled All {username}.ini files must be write-enabled to allow the thin client to place the encrypted user passwords in the files. 9. Use the wlx.ini File to Set the Maximum Number of Connection Entries Allowed The combined number of connection entries defined in a {username}.ini file and a wlx.ini 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 using the wlx.ini file. 10. Use System Variables with Some Options of the Connect Parameter Some options of the Connect parameter can use the system variables shown in Table 1 to map the string. All combinations of the variables are supported. For options that support use of system variables, see Connect Parameter Options. System Variables Table 1. System Variables Option $SN $MAC $IP $DN $UN $PW $TN Value Serial number used. MAC address used. IP Address used. Sign-on domain name used. Sign-on name used. Sign-on password used. Terminal name. If Auto Login in enabled then $PW returns null, so with auto logins enabled do not use $PW as value for any parameter. Placing the INI Files into the Folder Structure on the Server If you have set up your environment to provide your thin clients running Dell Wyse Enhanced SUSE Linux Enterprise with automatic updates and configurations as described in Administrators Guide: Dell Wyse Enhanced SUSE Linux Enterprise Release 11 SP3, you can use the following folder structure on your server. Under the C:/ inetpub/ftproot folder for FTP or C:/inetpub/wwwroot folder for HTTP/HTTPS and place your INI files. Other necessary files inside the structure as noted that this list describes the folder structure, starting with the root directory. 12

13 /wyse/ The root directory. It stores the wlx folder and the addons folder It also stores the following files, which are used for imaging and updating devices: Latest-image.raw Latest-image.raw.info /wyse/wlx The main INI configuration folder. It stores the following: wlx.ini file or MAC.ini file bitmap folder certs folder ini folder /wyse/wlx/bitmap /wyse/wlx/certs The folder where you can place custom images you plan to use. The folder where you can place the CA certificates that can be imported to a thin client. To import the certificates to thin clients, use the Certs and ImportCerts INI parameters in the wlx.ini file. /wyse/wlx/ini /wyse/addons The folder where you can place the {username}.ini files. The folder where you can place the add-ons you want to use. It also stores the directory file and the *.rpm packages available to be installed on the thin client. The directory file should list all available add-ons. The directory file is required in the addons folder to guarantee that add-ons are properly located. If you want to do an update with the Preserve changes option enabled, ensure that your addons folder includes a copy of your current add-ons. The system may require two reboots to fully update the firmware and add-ons while preserving local changes. 13

14 3 Parameters for WLX INI and MAC INI files only This chapter provides the supported parameters that you can use in a wlx.ini file and in a MAC.ini file. For information to help you construct and use the supported INI files, see Getting Started: Learning INI File Basics. Parameters in Tables 2 can only be used in a wlx.ini file or MAC.ini file; they cannot be used in a {username}.ini file. Important: The Bolded value for a parameter is the default value. Some parameters also have options shown within brackets [ ]. If an option has an underlined default value, that option and default value automatically used with the parameter. Options without underlined values can also be used if you want to, but are not automatically used with the parameter. In addition, when using parameters and options, you can leave the default value or change it to another value shown. For example, in the following case where: Parameter X ={yes, no} [Option1 ={0, 1}] [Option2 ={1, 2, 3, 4}] If you use Parameter X, then Option1 and its default value 0 automatically used as Option1 has an underlined default value of 0. You can still use Option2 if you want to, however, Option is not automatically used with the parameter as Option2 does not have a default underlined value. To increase usability such as relation to thin client dialog box equivalents, the supported parameters are separated into the following categories: General Settings For wlx.ini and MAC.ini Files Peripheral Settings for wlx.ini and MAC.ini Files Connection Settings for wlx.ini and MAC.ini Files Custom GNOME Settings for wlx.ini and MAC.ini Files 14

15 General Settings for wlx.ini and mac.ini Files The Following Table contains parameters used for configuring general settings where default values are underlined. Table 2. General Settings: wlx.ini files and MAC.ini files only Parameter ActiveDirectoryServer=<Active Directory Server IP> Description ActiveDirectoryServer Active Directory Server IP for Domain Login to the client. For example: ActiveDirectoryServer= AudioMute={no, yes} Yes/no option to mute the audio. AudioVolume=<value of 0 to 100> Determines the audio volume level. Values of provide more exact volume level. AutoPower={no, yes} Yes/no option on how the system starts when the power is first applied to the thin client. If set to yes, then the system starts itself without waiting for users to press the power button, In cases where power was lost unexpectedly; even if the thin client was shut down properly before power was lost unexpectedly, when the power is restored, the thin client is powered on. This setting is useful in a kiosk environment. Once an AutoPower statement is processed, it alters the behavior of the thin client until a countermanding statement is processed. The effect of an AutoPower=yes statement continues even if the statement is removed from the INI file in which it was found. Use of the AutoPower option does not interfere with performing a user directed shutdown. BiosCmosImages=<PlatformType>-<BIOS/ CMOS>-<BiosVersion>.img ChangeAdminPassword=<password> ChangeGuestPassword=<password> Do Not Use. No Longer Supported. Specifies the new password for the admin user. Default is base-64 encoded. Specifies the new password for the guest user. Default is base-64 encoded. 15

16 ChangeRootPassword=<password> ChangeThinUserPassword=<password> DefaultUser=<username> DisableReadyMode={no, yes} Enable802={no, yes} Authentication={TLS, PEAP} [PromptPassword={no, yes}] [InnerAuthentication={MSCHAPv2}] [UserCertificate=<certificate name>] [CACertificate=<certificate name>] [PrivateKey=<certificate name>] [PrivateKeyPassword=<password>] [PeapVersion={Auto, 0, 1}] [AuthMode={Machine, User}] Is802DirectEnabled= [yes,no] MachinePassword =[any string] Specifies the new password for the root user. Default is base-64 encoded. Specifies the new password for the thin user. Default is base-64 encoded. Specifies the default sign-on user. See also AutoLogin. Do Not Use. No Longer Supported. Important: :Put the parameters on the same line. This is the generic syntax of INI parameter for 802-1x settings for Wiredconnection. Parameter usage is based on the use case and EAP method chosen. Enable802 Yes/no option to enable or disable 802.1x settings for Auto Eth0 Wired connection. Yes Enables 802-1x settings for Wired network. No Disables 802-1x settings for Wired network. Authentication The authentication method (EAP method) to be used for 802.1X. PromptPassword Yes/no option to prompt for password every time for 802-1x authentication when the network comes up. InnerAuthentication The second EAP type inside the PEAP tunnel. Used only in cases of PEAP authentication. UserCertificate The client/user certificate name. Used for TLS authentication. CACertificate Root CA certificate name for authentication. PrivateKey Client/user private key certificate. Used for TLS authentication. PrivateKeyPassword The password given during the creation of a user/client certificate. This should be a base64 encoded password. PeapVersion Default is Auto. PEAP protocol version. AuthMode Authentication Mode for TLS. Set AuthMode as Machine for TLS machine authentication or set to User for TLS user authentication. 16

17 Is802DirectEnabled Default is no If you enable this will directly trigger the 802-1x authentication from the GDM login screen itself. It is highly recommended that we have the value set for this parameter. In case the value is not set in the registry it is considered as false/no. MachinePassword =[any string] This is mandatory if Authmode=machine and Authentication=PEAP. This password is used for authenticating machine with the RADIUS server. This value remains same for all the machine in a domain which needs to be 802-1x authenticated. Example: Below is an example INI for 802-1x TLS Machine authentication. Enable802=yes Authentication=TLS PromptPassword=no CACertificate=scep UserCertificate=scep PrivateKey=scep PrivateKeyPassword=ZG90MXg= AuthMode=Machine Example: Below is an example INI for 802-1x TLS User authentication. Enable802=yes Authentication=TLS PromptPassword=no CACertificate=scep UserCertificate=scep PrivateKey=scepPrivateKeyPassword=ZG90 MXg= AuthMode=User Example: Below is an example INI for EAP-PEAP connection User authentication. If you set Is802DirectEnabled=yes, the direct authentication is enabled which trigger the 802-1x authentication from the GDM login screen, In this case the ActiveDirectoryServer parameter is not required If you set Is802DirectEnabled=no, the 802-1x authentication is triggered after the user login to the thin client. In this case you to include the ActiveDirectoryServer parameter in the INI. For AD and Domain settings. DomainList=npac.local DisableDomain=no For Imports Certificates. ImportCerts=no 802-1x Configuration. Enable802=yes Authentication=PEAP InnerAuthentication=MSCHAPv2 PromptPassword=no AuthMode=User Is802DirectEnabled=yes CACertificate=SCEP PeapVersion=Auto 17

18 Example: Below is an example INI for EAP-PEAP connection Machine authentication. For AD and Domain settings. DomainList=npac.local DisableDomain=no For Imports Certificates. ImportCerts=yes Certs=npac-ca-cert.pem For 802-1x Configuration. Enable802=yes Authentication=PEAP InnerAuthentication=MSCHAPv2 PeapVersion=Auto PromptPassword=no CACertificate=npac-ca-cert.pem Authmode=Machine MachinePassword=tango charlie We recommend you to set values for all the 802-1x parameters because these parameters are part of the persistent registry which remains across the reboot and if any parameter is not set, it takes the previously set value, which may show inconsistent behaviors. EnableGKey={yes, no} Default is yes. Yes/no option to enable G key reset. EnableBanner={no, yes} [BannerMsg=<text description>] EnableBanner Provides a banner description. BannerMsg The text must be enclosed in double quotation marks if it contains spaces or punctuation characters. Example: EnableBanner=yes BannerMsg=DELL Wyse IdleAction.Enable={no, yes} [IdleAction.TimeOut=<value of 0 to 1440>] [IdleAction.Action=<Any valid Command>] IdleAction.Enable Yes/no option to enable IdleAction allows an action of the device for an idle state. IdleAction.Timeout Specifies in minutes from 0 to 1440 the amount of inactive time before the device executes the command specified in the IdleAction.Action parameter if IdleAction.Enable=yes. 18

19 Example: IdleAction.Enable=yes IdleAction.TimeOut=30 IdleAction.Action=/sbin/reboot ImportCerts={no, yes} [Certs=<list of certificate names>] ImportCerts Yes/no option to import certificates from the server Certs is a list of certificate names must be separated by a semicolon. Example: Certificates must be placed in the wyse/wlx/ certs directory. The certificates must be.crt,.pem or any valid certificate type. ImportCerts=yes Certs=Cert1.cer; Cert2.crt; Cert3.pem; Cert4.der InstallAddons=<name of addon> Specifies addons to install. Use comma-separated add-on names You can use InstallAddons= or NewAddons= for the parameter name ManagementServer={CCM/WDM} For example, For hagent to run, you have to enter ManagementServer=WDM. For CCM to run, you have to enter ManagementServer=CCM. MgmtDiscoveryMethod={SRV, CNAME, HOSTNAME, UI, DHCP, STATIC, DEFAULT} Default is the following order INI (Static), HOSTNAME, CNAME, SRV, DHCP, UI if any of the method specified in the INI file fails Specifies the automatic discovery methods you want to use for the automatic discovery of a thin client after failure of thin client discovery. Use any or all of the following: SRV DNS SRV Record for Dynamic Discovery Allows devices to use the DNS SRV record lookup method to discover a WDM Server. CName DNS Alias Allows devices to use the DNS Alias method to discover a WDM Server. Hostname DNS Name Record for Dynamic Discovery Allows devices to use the DNS Host name lookup method to discover a WDM Server. 19

20 UI Allows devices to use the UI entries to discover a WDM Server. DHCP Option Tags Dynamic Discovery Allows devices to use DHCP option tags to discover a WDM Static Allows devices to use a static location to discover a WDM Server. When the Static option is used, the MgmtDiscoveryMethod parameter should be used with a valid Fully Qualified Domain Name or IP Address. Default The Default method to discover a WDM Server is used when none is specified or if any of the method mentioned in this section fails; then the default method is used which is the following dicovery order {INI (Static), host name, CNAME,SRV,DHCP,UI}. PowerButtonAction={interactive, reboot, restart, halt, shutdown, none, nothing} Default is interactive. Specifies the action taken when the power button is pressed. interactive option window presented to user reboot or restart reboots the device halt or shutdown shuts down the device none or nothing no action, do nothing RemoveAddons=<name of addon> RemoveCerts Specifies addons to uninstall. Use commaseparated add-on names. RemoveCerts is a list of certificate names separated by semicolon which needs to be removed. For example, RemoveCerts=Cert1.cer; Cert2.crt; Cert3.pem; Cert4.der RootPath=<root path> This root path is used to access files on the server. The directory name /wlx is appended to the root path entry before use. Important: If no root path is provided, /wyse is the default. ScepClientCertSettings=CertName=<Name of Certificate file> URL=<Scep sever URL> [ChallengePassword=<Password>] CertName Name of certificate to be enrolled using SCEP. URL:- SCEP server URL. ChallengePassword Certificate Enrollment Challenge Password. 20

21 CADN=<CA Distinguished Name> [AutoEnroll={yes, no}] CADN CA Distinguished Name. AutoEnroll Yes/no parameter to enable or disable certificate automatic enrollment. Example: ScepClientCertSettings=CertName=ScepCertOne URL= ChallengePassword=C35F78367BA20216 CADN=scepca-root-ca ScreenSaver=<value of 0 to 180> [LockTerminal={no, yes}] [SoftSaver={no, yes}] [LogoutButton={no, yes}] [Type={1, 2, name[,name...]}] [CycleDelay=<value of 0 to 180>] [Image=<filename>] [Layout={none, centered, wallpaper, scaled, stretched}] ScreenSaver Specifies to put the thin client in a screensaver state when the time limit for inactivity in minutes delay before starting is reached. 0 turns off the screensaver. Put the parameters on the same line. For example: ScreenSaver= 5 LockTerminal=yes SoftSaver=yes Type=coral, drift, hypertorus, interaggregate, pipes, skytentacles CycleDelay=5 LockTerminal Yes/no option to specify the thin client LOCK state function when the screen saver is activated. no Disabled. yes Puts the thin client in a LOCK state when the screensaver is activated. The user is prompted with an unlock dialog box to enter the sign-on password to unlock the thin client. SoftSaver Yes/no option to specify that the thin client run a soft saver. Soft savers are only available when the optional SCREENSAVER- THEMES addon is installed. no blank the screen. yes run a graphical display. LogoutButton Yes/no option to display a logout button in the unlock dialog box if LockTerminal=yes. Type Specifies which display programs should run if SoftSaver=yes. Note: Names are preferred over the legacy numbers. 1=fadeplot; 2=rocks 21

22 CycleDelay When more than one Type name is specified, CycleDelay specifies how many minutes each Type name should run. Image Filename to use for the screen saver, this option is ignored in cases of backwards compatibility. Lay out Lay out to use for the screen saver, this option is ignored in cases of backwards compatibility. For a complete list of screensaver names, install the SCREENSAVER-THEMES addon and then search in /usr/ share/applications/ screensavers. The filenames, without the desktop suffix, are the available saver names. The 'Name entry in each.desktop file provides the value that is displayed in the Screensaver configuration GUI application; and the 'Comment' entry provides a brief description. shutdownonsignoff={<boolean><true/false, yes/ no>} TerminalName=<name of thin client> TimeFormat={ 12-hour format, 24-hour format } TimeServer=<host address>[;<host address>] TimeZone=<zone value> [ManualOverride={no, yes}] Default is false. When this value is set to 'yes', the system shutsdown after all the VDI sessions gets over. Name of the thin client comprising a 15-character string. Specifies the time format to use how the clock on the desktop panel is displayed used. By default, the local format is used. Specifies the SNTP time servers to use for time retrieval. You can designate one or two as shown in the parameter example, Network Time Protocol servers separated by a semicolon. The client synchronizes the time of day to the servers at boot time, and keeps the time in sync with the servers during operation. TimeZone Specifies the time zone if the zone is unspecified on the thin client or is used with Manual Override. ManualOverride Yes/no option to override the thin client System Preference Menu setting with this TimeZone setting. TimeZone settings in the wlx.ini file will be saved into NVRAM if EnableLocal=yes is set in the wlx.ini file. Default is no. 22

23 For the complete list of TimeZone values, see TimeZone Parameter: Values UpdateBiosCmos={no, yes} Update.Mode= {Both, Image, Addons, None} Do Not Use. No Longer Supported. Default is Both. Specifies the update mode for image upgrades. Value and Description: Both Updates image and add-ons Image Updates image only Addons Updates add-ons only None Does not upgrade Update.Preserve_changes={no, yes} Default is yes. Yes/no option to preserve changes while upgrading. No means that it enables the check box Restore factory defaults when updating in the novell-addon-manager > Server settings applet, so that after image upgrade/downgrade it will not preserve the previous image device settings, that is the device will be in factory reset condition after imaging. Yes means that it disables the check box Restore factory defaults when updating in the novell-addon-manager > Server settings applet, so that after image upgrade/downgrade it will preserve/apply previous image device settings to to the image after imaging. Peripheral Settings(wlx.ini and MAC.ini Files Only) The Following Table contains parameters used for configuring peripheral settings such as keyboard, monitor, mouse, printer default values are underlined. Table 3. Peripheral Settings: wlx.ini files and MAC.ini files only Parameter CursorHideDelay=<value of 1 to 60> MicMute={no, yes} Description Specifies the amount of time to wait before the cursor is hidden after the specified number of seconds. After pressing any keyboard key or mouse movement/mouse event, the cursor will reappear. Yes/no option to mute the microphone volume. MicVolume=<value of 0 to100> Default is

24 Specifies the microphone volume level. Connection Settings for wlx.ini and MAC.ini Files Only The Following Table contains parameters used for configuring connection settings where default values underlined.. Table 4. Connection Settings: wlx.ini files and MAC.ini files only Parameter AddtoEtcHosts= ip1 FQDN1aliases1; ip2 FQDN2 aliases2;... AnonymousIdentity=<string> AutoLogin= {no, yes} [CountDown=<value in seconds>] Description Adds entries to the hosts file where aliases are an optional space-separated list of host names. Anonymous identity string for EAP authentication methods are used as unencrypted identity with EAP types, that support different tunneled identity such as EAP-TTLS. Default CountDown value in seconds is 8 Yes/no option to automatically log the user in as DefaultUser if no login occurs before the CountDown interval. this is for use at kiosks and other environments where the user logs in without human intervention. Autologin can be canceled by pressing the ESC button. The first time a device reads Autologin, it may stay at the login screen for a few seconds before taking effect. Once doing so, it will automatically log in and all future reboots will autologin with the defined delay. Changing from AutoLogin=yes to AutoLogin=no may require 2 reboots to take effect in some cases. No password is required for automatic login even if the user normally needs a password. SignOn=no and AutoLogin=yes are alternative parameters/ways to provide similar functionality. SignOn=no and AutoLogin=yes should not be used together. In general, use AutoLogin; SignOn=no is being deprecated. AutoLogin=yes logs in as the default user; Which may be set via the DefaultUser ini-file parameter; the privilege level is that user's normal 24

25 privilege level; determined in the same manner as if they had logged in manually. Any valid user may be specified; but note that PNA and Active Domain users will not obtain a password first; which may prevent them from accessing the Published Apps or Domain services. If there is no Default User specified in the registry, it uses Guest. Note that for both SignOn=no and AutoLogin with a short delay, it is likely that the login process will proceed before the network is up and the wlx.ini file has been read. This means that changes to the wlx.ini login parameters will not take effect until a logout or reboot. Note also that changes to the System/ DefaultUser or System/ PrivLevel registry keys do not automatically adjust the login parameters; that is normally done only after fetching and parsing a wlx.ini file when a network interface comes up. If you need to change the parameters outside that sequence; use the /sbin/configuregdm script to modify the system's login configuration. The wlx.ini is fetched and processed every time the network comes up; so if the network goes down and is restored during a session, it may affect existing settings although the login-related settings will not be apparent until the current user logs out. Also note that neither mechanism actually authenticates the user they just verify that the user exists. But both methods, and normal manual login, fetch and process a $USER.ini file, if one exists, independent of what, if any, authentication mechanism was used. AutoSignoff={no, yes} Default is no DelayedUpdate.Delay=<integer> Default is 60 Automatically signsoff/logsout when all the connections are closed. Number of seconds to wait between detecting the specified interface and starting the cache update DelayedUpdate.Enable={False,True} Default is false This option must be set to TRUE to enable the delayed/cached updating functionality. DelayedUpdate.Interval=<integer> Default is

26 The number of seconds to wait between checks for whether the interface is available. DelayedUpdate.MaxRate= <integer>[b, K, M, G] Default is 100G The maximum bandwidth to be used in bytes/ second. The optional letter suffix indicates a multiplier: (Bytes, Kilobytes, Megabytes, or Gigabytes). There is no way to indicate that all available bandwidth is to be used except to specify a value that is expected to exceed the actual capacity. DelayedUpdate.Mode={ both, image, addons } The values for DelayedUpdate.Mode is as following: both Updates image and add-ons. image Updates image only. addons Updates add-ons only. DelayedUpdate.Preserve={<boolean><true/false, yes/no>} DelayedUpdate.TimeOut=<Integer> Default is true Whether or not the user settings will be saved after image upgrading. Default is 0 (no timeout) Maximum time, in seconds, to wait while attempting to contact the server. Zero indicates no timeout. Note that obtaining the directory and downloading each add-on are separate operations and will be subject to the timeout individually. DisableDomain={no, yes} DisableVNC={no, yes} Yes/no option to disable the display of a Domain field. The default value depends on the value of the Domain List option. When the Domain List is empty, DisableDomain defaults to yes; otherwise, it defaults to no, the display of a Domain field does not display either of a case. Default is yes. Yes/no option to disable an installed VNC-Server Add-on. DomainList=<list of Windows domain> A list of domain names that appear in the login dialog box as options to help users in selecting the domain to log in to PNAgent/PNLite servers. Once specified, it is saved in nonvolatile memory. 26

27 Be sure to enclose in quotation marks if spaces are included. For example: DomainList=North_America.com,SQA.com,te st-domain.com EnableApplianceMode={no, yes} [XenDesktopURL=<URL of Xendesktop>] Dell Wyse Enhanced SLE devices can be converted to Desktop Appliance mode by enabling the EnableApplianceMode parameter. When enabled, upon system boot the thin client connects to the XenDesktop server and prompt for XenDesktop login credentials to access the desktop. By default EnableApplianceMode=No. XenDesktopURL specifies the virtual desktop to use when EnableApplianceMode is enabled. For example:- EnableApplianceMode=Yes XenDesktopURL= EnableLocal={yes, no} Default is yes. Yes/no option to enable locally configured connection entries to show in the connection list that is, activate local entries. EnableSSH={no, yes} Yes/no option to enable SSH. EthernetSpeed={Auto, 100M-F, 100M-H, 10M-F, 10M-H} Default is Auto. Specifies the NIC speed: Auto - autonegotiates speed with peer (default). 100M-F is 100 Mbps Full Duplex. 100 M-H is 100 Mbps Half Duplex. 10 M-Fis 10 Mbps Full Duplex. 10M-H is 10 Mbps Half Duplex. Gigabit Ethernet (1000 Mbps) is available on hardware that supports it via the Auto value. FileServer=<protocol://><hostaddress> Host is used to access files using the specified protocol. If no protocol is specified, FTP is assumed for example, is understood as ftp://

28 FileServerUsername=<username> FileServerPassword=<password> FirmwarePassword=<string> FirmwareRootPath=<string> Specifies the username for File server. Specifies the Base-64 encrypted password for File server. This parameter specifies the password needed for accessing image files on file repository server. This parameter specifies the relative path of the file server, where image is found. Once this is set to TC, upon reboot the TC gets imaged. For example, FirmwareRootPath=/wyse. If file server is ftp:// /z50/imagerepo, then full path of the image will be ftp:// /z50/ imagerepo/wyse FirmwareServer=<string> This specifies the base path of image in the file repository server. If no protocol is specified, FTP is considered. FirmwareUserName=<string> ICAAutoLaunchApp=<app_list> This parameter specifies the username needed for accessing image files on the file repository server. This parameter can have a set of app names separated by comma. The first valid app (as published at the server) will be autolaunched upon PAM Login. 1. INI parameter ICAAutoLaunchApp can have multiple apps separated by comma. 2. Among the set of apps given in INI first valid app is the one considered for auto launch upon login. 3. If no app is valid app in INI, then auto connect is not applicable for any of the apps. 4. If there is no INI parameter and only one app is published from server, then it is auto launched (It is the default behavior which we must retain when there is no INI). In the case of multiple apps and if there is no INI then the auto connect is not be applicable to any of the apps. 5. After you login only one app is launched automatically, this is due to implementation limitation. ICADenyUSB=vid=<hexnumber><space>pid=<hex number>,... Specifies the USB devices that are excluded from ICA session. 28

29 When using the ICADenyUSB parameter, a user can deny redirection of devices using class/subclass also along with vid/pid ICADenyUSB=class=01 subclass=01 to deny USB Audio family. Important: :You can use vendor IDs and product IDs together as shown; or also use only the vendor IDs that are not use the product IDs if you want to exclude the same vendor ID group of devices regardless of their product ID. The format must be the following: ICADEnyUSB=vid=<hexnumber><space>pid=< hexnumber> or ICADenyUSB=vid=<hexnumber> For example: ICADenyUSB=vid=1234 pid=5678,vid=1234 pid=9876 This example excludes two USB devices. There is a space between vid and pid and each device is separated with a comma. or ICADenyUSB=vid=1234, vid=5678 This example excludes all USB devices that have the same vendor ID regardless of their product ID. While the ICAAllowUSB parameter exists, it is highly recommended that it not be used as by default all USBs are allowed. Java.Exception.Sites={URLs separated by space} Specifies the JRE exception sites. Example: Java.Exception.Sites= bbb.222.bbb Java.Security.Level={medium, high, very_high} Default is high. Specifies the JRE security level. PermitSSHRootLogin={no, yes} 29

30 Yes/no option to enable logging in through SSH as the Linux superuser (root). PNLiteServer=<host address>[:<port>] DO NOT USE.This parameter is being deprecated and the use of PNAgentServer is recommended. RapportSecurePort=<port> Default port number is 443. Designates the HTTP(S) secure port used for the WDM agent. For example: RapportServer= :80 RapportSecurePort=443 RapportServer==<hostaddress>[:<port>] Default port number is 80. The WDM Server and optional port to which to connect. This can be either a DNS name or an IP Address, optionally followed by a : and a port number. Seamless={no, yes} Yes/no option to set the default resolution for ICApublished applications to seamless. SignOn={yes, no} DO NOT USE TCXUSBDevice=<any description of your device> [active={allow, deny}] [class=<hexadecimal-number class value of your device>] [subclass=<hexadecimal-number subclass value of your device>] [protocol=<hexadecimal-number protocol value of your device>] [vendorid=<hexadecimal-number vendorid value of your device>] [productid=<hexadecimal-number productid value of your device>] DO NOT USE. This parameter is deprecated and the use of AutoLogin is recommended This parameter will work when you install the optional tcx_aur & tcx_usb addons. String in the following format: TCXUSBDevice=<any description of your device> \ active={allow/deny}\ class=<value> \ subclass=<value> \ protocol=<value> \ vendorid=<value> \ productid=<value> \ Active=allow means allow USB access to be redirected to the remote location. Active=deny means keep the USB access local. Either class or vendorid/productid is required. 30

31 For example, BisonCam \ active=deny \ vendorid=5986 \ productid=0241 \ tcxusbdevice=bluetooth \ active=deny \ class=0e \ subclass=01 \ protocol=01 \ vendorid=13d3 \ productid=3249 \ tcxusbdevice=smart Card Devices \ active=deny \ class=0b TCXUSBVirtualize={no, yes} Yes/no option to enable TCX USB virtualization. TCXUSBVirtualize.ActiveSync.disable= {no, yes} Yes/no option to disable TCX USB Active Sync device virtualization. TCXUSBVirtualize.Audio.disable={no, yes} Yes/no option to disable TCX USB Audio device virtualization. TCXUSBVirtualize.Communication.disable={no, yes} TCXUSBVirtualize.Composite.disable={no, yes} Yes/no option to disable TCX USB Communication device virtualization. Yes/no option to disable TCX USB Composite devices virtualization. TCXUSBVirtualize.DataInterface.disable={no, yes} Yes/no option to disable TCX USB Data Interface device virtualization. TCXUSBVirtualize.HID.disable={no,yes} Yes/no option to disable TCX USB HID device virtualization. TCXUSBVirtualize.PalmSync.disable={no, yes} Yes/no option to disable TCX USB Palm Sync device virtualization. TCXUSBVirtualize.Video.disable={no,yes} 31

32 Yes/no option to disable TCX USB Video device virtualization. Upgrade.Image_RootPath=<string> This parameter specifies the file server path where user stores the image. For example, Upgrade.Image_RootPath=ftp:// /Z50/imagerepo This value indicates that we have to place latestimage.raw and latest-image.raw.info files inside Z50/imagerepo in ftp.this parameter in mostly used during mixed environment image upgrade. VMWareViewExcludeUSBFamily=<USB device family>,... Specifies the USB family of devices that are excluded from the VMware View session commaseparated USB device families that are excluded from the VMware View session. The format must be the following: VMWareViewExcludeUSBFamily=<USB device family> For example, VMWareViewExcludeUSBFamily=audio, storage. This example excludes all USB devices per their device class/family. VMWareViewExcludeUSBID=vid<hexnumber>pid< hexnumber>,... Specifies the USB devices that are excluded from VMware View session, comma-separated vendor Ids and product Ids of USB devices that are excluded from the VMware View session. The format must be the following: VMWareViewExcludeUSBID=vid<hexnumber>p id<hexnumber> For example: VMWareViewExcludeUSBID=vid148fpid2770, vid0x13d3pid3273 This example excludes two USB devices. There is no space between vid and pid and each device is separated with a comma. VMWareViewIncludeUSBID= vid<hexnumber>pid<hexnumber>,... Comma separated vendor Ids and product Ids of USB devices that are included from VMWare View session. The format: VMWareViewIncludeUSBID=vid<hexnumber>pid<h exnumber>,... Example: 32