The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
AutoLogin is disabled by default (AutoLogin=no). If enabled, the AutoLogin feature automatically logs the user in as the Default User, unless you cancel the AutoLogin before the CountDown interval expires. You can cancel AutoLogin by pressing the ESC key. This feature is useful for kiosk environments.
To enable the AutoLogin feature, change the AutoLogin parameter in the wlx.ini file to AutoLogin=yes. For more information about how to edit the wlx.ini file, or about the AutoLogin or Countdown parameters, see the INI reference guide for the thin client.
If you enable AutoLogin, the thin client automatically boots and signs in as the default user (thinuser mode), which restricts user access.
In thinuser mode, the FireFox shortcut does not appear in the Start menu and xterm does not appear in the Application Browser. Users can access System Information by clicking an icon in the notification area of the task bar. To set up access to FireFox, edit the wlx INI file to specify the required parameters.
Example:
CONNECT=BROWSER \ Description="Cisco Home Page" \ URL=http://www.cisco.com \ Resolution=FullScreen \ Mode=Normal
After application of the new wlx INI file, an icon for FireFox appears on the thin client desktop. For more information about how to edit the wlx INI file, see the INI reference documentation for your device.
Note | Dell Wyse thin client users do not have access to the WDM icon in thinuser mode. This behavior is expected because users do not need this access. If you require access WDM to troubleshoot device check-in issues, you can open the application from xterm. For more information about how to manage Dell Wyse thin clients, see the administrator guides for your base image version. |
If your network uses DHCP, specify the domain name in the DHCP pool. Without this setting, DHCP does not assign a domain to the thin clients. Therefore, the devices cannot register with the Cisco Unified Communications Manager, the client keypads are dimmed, and users cannot make calls.
Example:
ip dhcp pool Non-VXCM server network 10.2.209.0 255.255.255.0 dns-server 10.2.25.11 default-router 10.2.209.1 domain-name rtpvxi.com !
If thin clients reside in a different domain than the Cisco Unified Communications Manager, the DNS server may be unable to resolve the domain name for the Cisco Unified Communications Manager.
To resolve this issue, edit the /etc/hosts file on the thin client. To save the change permanently, edit the wlx.ini file. Add the AddtoEtcHosts= parameter, and specify the IP, FQDN, and aliases for each Cisco Unified Communications Manager in the cluster. This parameter adds entries to the /etc/hosts file, where aliases are an optional space-separated list of hostnames.
For more information about how to edit the wlx.ini file, see the INI reference guide for the thin client.
AddtoEtcHosts= "ip1 FQDN1 aliases1;ip2 FQDN2 aliases2"
;************************************************************* ;* General 1 * ;************************************************************* AddtoEtcHosts="10.200.252.2 CUCM123.cisco.com CUCM123;10.100.7.117 CUCM456.cisco.com CUCM456" IniFileSource=cache ;************************************************************* ;* Connections * ;************************************************************* Browser.Homepage=http://gwydlvm120 CONNECT=BROWSER \ Description="Citrix-HVD" \ URL=www.cisco.com \ AutoConnect=yes \ Sound=yes \ mode=normal
For each Cisco Unified Client Services Framework (CSF) device that you add to the system, Cisco Unified Communications Manager creates a configuration (CNF.xml) file. The CNF file contains the device specifications for the associated user.
When users sign in to Cisco Jabber, Cisco Virtualization Experience Media Engine starts the download of the associated CNF file to the thin client. To ensure the successful transfer of the file, open the relevant ports in all firewall applications to allow the thin client to access the ports. For more information about how to open ports, see the documentation for the firewall software.
Download of the CNF.xml file follows the system setting for HTTP proxy. Ensure that the proxy does not route the HTTP request from the thin client outside of the corporate network.
Command or Action | Purpose | |
---|---|---|
Step 1 | Create a CSF Device and a Directory Number for Each User. | |
Step 2 | Associate New Devices with a User. | |
Step 3 | Enable the CTI Protocol for Users. | |
Step 4 | Configure Cisco Unified Communications Features for Users. | Enable the Unified Communications Manager IM and Presence Service. See the documentation for your version of Cisco Unified Communications Manager. |
Note | You can use the same Cisco Unified Client Services Framework (CSF) devices for the virtual environment, as you do for the nonvirtual environment. We recommend that you create only one CSF device for each virtual user. If multiple devices exist for a virtual user, virtual Jabber automatically selects the first device in the list. |
Note | Perform this task in Cisco Unified Communications Manager. |
Step 1 | From Cisco Unified Communications Manager Administration, choose . |
Step 2 | Search for the user in the Find and List Users window. |
Step 3 | Select the user. |
Step 4 | Select Device Association in the Device Information section. |
Step 5 | Search for the devices that you require in the User Device Association window. |
Step 6 |
Select the devices that you require. For example, you can select a device whose type is Cisco Unified Client Services Framework, and a desk-phone device. |
Step 7 | Select Save Selected/Changes. |
Step 8 | Select Back to User from the menu in the Related Links navigation box at the top right of the window. |
Step 9 | Select Go. |
Step 10 | Verify that the devices are listed in the Device Information section in the End User Configuration window. |
Enable the computer-telephony integration (CTI) protocol for each Cisco Virtualization Experience Client user.
Step 1 | From Cisco Unified Communications Manager Administration, choose . |
Step 2 | Search for the user in the Find and List Users window. |
Step 3 | Select the user. |
Step 4 | In the End User Configuration window, scroll down to Permissions Information. |
Step 5 | Select Add to User Group. |
Step 6 | Select the following groups: |
Step 7 | Select Save. |
Enable the Unified Communications Manager IM and Presence Service. See the documentation for your version of Cisco Unified Communications Manager.
For information about how to configure Cisco Unified Communications features for Cisco Jabber, see the deployment and installation guide for your release, available from http://www.cisco.com/c/en/us/support/unified-communications/jabber-windows/products-installation-guides-list.html.
Use this procedure to change the password for a user only if LDAP Authentication is not enabled. If LDAP Authentication is enabled, the passwords are stored on the LDAP Server. For Cisco Unified Communications Manager 9.0 or later, this procedure applies only to passwords for users created locally.
Step 1 | From Cisco Unified Communications Manager Administration, choose . |
Step 2 | Search for the user in the Find and List Users window. |
Step 3 | Select the user. |
Step 4 | In the End User Configuration window, in the Password field, enter a new password for the user. |
Step 5 | In the Confirm Password field, enter the new password for the user again. |
Step 6 | Select Save. |