- Download the Cisco Virtualization Experience Media Engine Add-on
- Download Cisco VXME Utilities
- Create a Cisco VXC Manager Package
- Create a Dell Wyse Device Manager Package
- Install the Cisco AnyConnect Add-on
- Create a CSF Device and a Directory Number for Each User
- Associate New Devices with a User
- Enable the CTI Protocol for Users
- Change a User Password
- Links to Documentation
- Configuration Files
- DHCP Pool Setup
- Domain Name Resolution
- Port Usage
- Upgrade to Release 9.7
- Upgrade Cisco Jabber for Windows
- Upgrade Cisco UC Integration for Microsoft Lync
Installation and Deployment
Download the Cisco Virtualization Experience Media Engine Add-on
 Note | The Cisco Virtualization Experience Media Engine add-on includes a prerequisite add-on, which you must install on the thin client, before you install the Cisco Virtualization Experience Media Engine add-on. The prerequisite add-on includes the auto-login add-on. After installation, the device auto-logs in to the thinuser account at boot. |
| Step 1 | Go to the following URL: http://www.cisco.com/cisco/software/navigator.html |
| Step 2 | Choose . |
| Step 3 | From the list, choose the file for your release.
Example: The file for Release 9.3 is vxme-9.3.0-77.zip. The file for Release 9.7 is vxme-9.7.0-279.zip. |
| Step 4 | Select Download or Add to cart and follow the prompts. |
Download Cisco VXME Utilities
Install Cisco Virtualization Experience Media Engine (VXME) Utilities on the hosted virtual desktops (HVD), before you install Cisco Jabber for Windows. If you plan to install Cisco UC Integration for Microsoft Lync, you need not perform this procedure because Cisco UC Integration for Microsoft Lync includes Cisco VXME Utilities.
| Step 1 | Go to the following URL: http://www.cisco.com/cisco/software/navigator.html |
| Step 2 | Choose . |
| Step 3 | From the list, choose the file for your release. |
| Step 4 | Select Download or Add to cart and follow the prompts. |
Create a Cisco VXC Manager Package
With Cisco VXC Manager, you create and register specific packages to push upgrades and configurations to the thin clients.
To register the package with Cisco VXC Manager, you must create a unique RSP file and, in the same directory, a matching folder of the same name. This matching folder serves as the root directory for the remaining configuration files in the package.
What to Do Next
Use the Default Device Configuration (DDC) method to upgrade the Cisco VXC 6215. For more information about the DDC method, see Administration Guide for Cisco Virtualization Client 6215 for your release.
Cisco VXC Manager Folder Structure
Note | Cisco VXC Manager package names, filenames (including .rsp and .ini files), folders, and so on must be lower-case. |
For example, assuming <packagename>.rsp is the RSP file, the folder structure required to register the package is as follows:
| Directory | Description | ||
|---|---|---|---|
| ~\<packagename>.rsp | The unique RSP file, located in the same directory as the matching root package directory. | ||
| ~\<packagename>\ | The root package directory. It stores the wlx folder and the add-ons folder. It also stores the following files, which are used for imaging and updating devices: |
||
| ~\<packagename>\wlx | The main INI configuration folder. It stores the following: | ||
| ~\<packagename>\wlx\bitmap | The folder where you can place custom images you plan to use. | ||
| ~\<packagename>\wlx\certs | The folder where you can
place the CA certificates that can be imported to a thin client.
|
||
| ~ \<packagename>\wlx\ini | The folder where you can place the {username}.ini files. | ||
| ~\<packagename>\addons | 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 add-ons folder to guarantee that add-ons are properly located. |
You can create this structure in any location on your Cisco VXC Manager server, as long as all required files are in the appropriate folders.
Note | If a folder does not contain a required file for the package, the folder can be omitted from the package directory structure. For example, if the package contains no graphics, the \wlx\bitmap folder is not required. |
After you register the package, Cisco VXC Manager stores the package files in the software repository under c:\inetpub\ftproot\Rapport\<packagename>.
 Caution | Do not attempt to modify a registered package located in the Rapport folder. To modify a package, you must create and register a new package that includes the required changes. |
Deployment Tasks
If you are upgrading from a previous release, see the upgrade sections in this chapter.
| Step | Details | |||
|---|---|---|---|---|
1 |
Build the Microsoft Windows desktop image. For best practices for cloning Microsoft desktop images, consult Microsoft. |
Multiple registrations to the Cisco Unified Communications Manager are not supported. To help prevent multiple registrations, we recommend that you create only one HVD for each user. |
||
2 |
Add users and devices on the Cisco Unified Communications Manager. |
|||
3 |
Set up users on the Cisco Unified Communications Manager for Cisco Jabber Unified Communications features, such as Cisco Unified CM IM and Presence and WebEx integration. |
See the Server Setup Guide for your release of Cisco Jabber for Windows: http://www.cisco.com/en/US/products/ps12511/prod_installation_guides_list.html See the Administration Guide for Cisco UC Integration for Microsoft Lync for your release: http://www.cisco.com/en/US/products/ps11390/prod_installation_guides_list.html |
||
4 |
Ensure that users know how to access the user guides. |
|||
5 |
Set up the Cisco Virtualization Experience Client 6215 or Dell Wyse Z50D hardware and configure the device. |
For links to software downloads, documentation roadmap, licensing information, and release notes, see: http://www.cisco.com/en/US/products/ps11976/tsd_products_support_general_information.html For links to the Quick Start Guide, VESA mount instructions, and regulatory information, see: http://www.cisco.com/en/US/products/ps11976/prod_installation_guides_list.html For the Dell Wyse Z50D, see Administrators Guide Wyse Enhanced SUSE Linux Enterprise Release 11 SP2, available from http://wyse.com/. |
||
6 |
Install the Cisco Virtualization Experience Media Engine add-on, on the Cisco Virtualization Experience Client 6215 or on the Dell Wyse Z50D. |
The Cisco Virtualization Experience Media Engine add-on comes with a prerequisite add-on, which you must install on the thin client, before you install the Cisco Virtualization Experience Media Engine add-on. See Administrator Guide for Cisco Virtualization Experience Client 6215 for your release: http://www.cisco.com/en/US/products/ps11976/prod_maintenance_guides_list.html
For the Dell Wyse Z50D, see Administrators Guide Wyse Enhanced SUSE Linux Enterprise Release 11 SP2, available from http://wyse.com/. If you are upgrading from a previous release, see the upgrade sections in this chapter. If you are upgrading from Voice and Video Firmware 8.6 or 8.7, you must first upgrade to Cisco Virtualization Experience Media Engine Release 9.0 or later. |
||
7 |
Open the required ports in all firewalls. |
See Ports Reference Guide for Cisco Virtualization Experience Media Engine Release 9.0. http://www.cisco.com/en/US/products/ps12862/prod_installation_guides_list.html |
Create a Dell Wyse Device Manager Package
Wyse Device Manager is the recommended deployment tool to deploy the Cisco Virtualization Experience Media Engine add-on to Dell Wyse Z50D thin clients. See the Dell Wyse documentation for supported versions. You can also use this procedure if the Cisco Virtualization Experience Client 6215 or the Dell Wyse Z50D device is already running the required base image and you want to deploy an add-on.
Follow the optional steps in this procedure to deploy Cisco AnyConnect with Cisco Virtualization Experience Media Engine add-on.
Ensure that the Z50D devices are running the required firmware build; see Release Notes for Cisco Virtualization Experience Media Engine for your release. If necessary, contact Dell Wyse to get a compatible image.
Ensure that the Z50D devices are checked-in to Dell Wyse Device Manager (WDM). The devices should appear green in WDM.
| Step 1 | On the server, on which you have WDM installed, extract the add-on files to a local folder.
The extracted add-on folder structure appears as follows for Release 9.3: ~/vxme-9.3.0-77/addons/vxme-pre-reqs-9.3.0-27.sletc11sp2.rpm ~/vxme-9.3.0-77/addons/vxme-9.3.0-77.sletc11sp2.rpm ~/vxme-9.3.0-77/addons/directory The extracted add-on folder structure appears as follows for Release 9.7: ~/vxme-9.7.0-279/addons/vxme-pre-reqs-9.7.0-19.sletc11sp2.rpm ~/vxme-9.7.0-279/addons/9.7.0-279.sletc11sp2.rpm ~/vxme-9.7.0-279/addons/directory | ||
| Step 2 | (Optional) To deploy Cisco AnyConnect with Virtualization Experience Media Engine, extract anyconnect_bundle.<version>.zip. For Release 9.3, the file name is anyconnect_bundle-3.1.04063-50.zip. For Release 9.7, the file name is anyconnect_bundle-3.1.05152-58.zip. | ||
| Step 3 |
Copy vxme-pre-reqs-<version>.rpm and vxme-<version>.rpm to ~/CiscoVXME/CiscoVXME_9.x, where 9.x is your release number. The folder structure for Release 9.3 is as follows: ~/CiscoVXME/CiscoVXME_9.7/install-sletc-addons.sh ~/CiscoVXME/CiscoVXME_9.7/update-addons-list ~/CiscoVXME/CiscoVXME_9.7/vxme-pre-reqs-9.3.0-27.sletc11sp2.rpm ~/CiscoVXME/CiscoVXME_9.7/vxme-vxme-9.3.0-77.sletc11sp2.rpm ~/CiscoVXME/CiscoVXME_9.7.rsp The folder structure for Release 9.7 is as follows: ~/CiscoVXME/CiscoVXME_9.7/install-sletc-addons.sh ~/CiscoVXME/CiscoVXME_9.7/update-addons-list ~/CiscoVXME/CiscoVXME_9.7/vxme-pre-reqs-9.7.0-19.sletc11sp2.rpm ~/CiscoVXME/CiscoVXME_9.7/vxme-9.7.0-279.sletc11sp2.rpm ~/CiscoVXME/CiscoVXME_9.7.rsp | ||
| Step 4 | (Optional) To deploy Cisco AnyConnect with Virtualization Experience Media Engine, copy the anyconnect_bundle<version>.rpm file to ~/CiscoVXME/CiscoVXME_9.x where 9.x is your release number. For Release 9.3, the file name is anyconnect_bundle-3.1.04063-50.zip. For Release 9.7, the file name is anyconnect_bundle-3.1.05152-58.zip. | ||
| Step 5 | (Optional) To deploy Cisco AnyConnect with Virtualization Experience Media Engine, add the following line to update-addons-list: UPDATE_ADDONS_LIST+=" anyconnect_bundle-<version>.rpm" For Release 9.3 add the following: UPDATE_ADDONS_LIST+=" anyconnect_bundle-3.1.04063-50.sletc11sp2.rpm" For Release 9.7 add the following: UPDATE_ADDONS_LIST+=" anyconnect_bundle-3.1.05152-58.sletc11sp2.rpm" | ||
| Step 6 | In the navigation pane of the Administrator Console, right-click Package Manager and then choose . | ||
| Step 7 | In the Package Wizard window, select Register a Package from a Script File (.RSP), and then select Next. | ||
| Step 8 |
Enter the path to the CiscoVXME_9.x.rsp file (where 9.x is your release), and then select Next.
| ||
| Step 9 |
In the Software Package Information dialog, check Active, and then select Next. This step makes the WDM package active for distribution. | ||
| Step 10 | To create and register the WDM package, select Next. | ||
| Step 11 | Select Finish. WDM copies the package to the Master Repository, where it appears under the appropriate category. The package is ready for distribution. |
Scripts
You use the following scripts when you create a Dell Wyse Device Manager package.
Note | The examples for each script depict a Release 9.3 installation; the file names for later releases are different. |
install-sletc-addons.sh
#!/bin/bash
source /tmp/update-addons-list
WYSE_INIT_ADDON_UPDATE=/etc/wyseinit_factory_reset
NEED_REBOOT=no
for A in ${UPDATE_ADDONS_LIST} ; do
if [ -e /tmp/${A} ] ; then
/usr/sbin/addon-install /tmp/${A}
# Find WYSE_INIT addon among the list of
specified addons
WYSE_INIT=${A:0:9}
if [ "$WYSE_INIT" = "wyse_init" ] ; then
/bin/touch $WYSE_INIT_ADDON_UPDATE
/bin/sync
NEED_REBOOT=yes
fi
fi
done
sync
# WYSE_INIT addon needs reboot
if [ "$NEED_REBOOT" == "yes" ] ; then
/sbin/init 6
Fi
update-addons-list
# Quick guide # Copy all the add-ons needs to be installed in to this directory ~install-sletc-addons/install-sletc-addons/ # Specify list of add-ons to be installed/updated preferably order in which you wish to install as explained below # # Do not modify below line UPDATE_ADDONS_LIST= # Specify each add-on full name in separate line, with leading one space enclosed inside quotes, as shown in below example # Example:- # Lets say you want to install following two add-ons # abcd-xyz-1.1.1.sletc11sp2.rpm and aaaa-xxxx-2.2.2.sletc11sp2.rpm # Specifiy these two add-ons as below # UPDATE_ADDONS_LIST+=" abcd-xyz-1.1.1.sletc11sp2.rpm" # UPDATE_ADDONS_LIST+=" aaaa-xxxx-2.2.2.sletc11sp2.rpm" # UPDATE_ADDONS_LIST+=" vxme-pre-reqs-9.3.0-27.sletc11sp2.rpm" UPDATE_ADDONS_LIST+=" vxme-9.3.0-77.sletc11sp2.rpm"
CiscoVXME_9.3.rsp
Note | This RSP script is provided as an example; you may need to specify different parameters depending on your environment. See Administration Guide for Cisco Virtualization Experience Client Manager for details about how to create RSP files. |
[Version] Number=CiscoVXME_9.3 Description=Cisco Virtualization Experience Media Engine OS=SLX Category=Cisco USE_Pxe=NO [Script] CO "SLX" LU SF "<regroot>/*" "/tmp/" EX "dos2unix /tmp/update-addons-list" EX "dos2unix /tmp/install-sletc-addons.sh" EX "/bin/bash /tmp/install-sletc-addons.sh &" EL
Install the Cisco AnyConnect Add-on
| Step 1 |
Extract the anyconnect_bundle-<version>.zip. For Release 9.3, the file name is anyconnect_bundle-3.1.04063-50.zip. For Release 9.7, the file name is anyconnect_bundle-3.1.05152-58.zip. |
| Step 2 | Copy the .rpm file to the appropriate folder for VXC-M or for WDM. Folder for VXC-M: ~\<packagename>\addons Folder for WDM: ~/CiscoVXME/CiscoVXME_9.x 9.x is your release number. |
| Step 3 | Add one of the following lines to the appropriate file for VXC-M or for WDM. Directory file for VXC-M: For Release 9.3 add the following line: anyconnect_bundle-3.1.04063-50.sletc11sp2.rpm For Release 9.7 add the following line: anyconnect_bundle-3.1.05152-58.sletc11sp2.rpm Update-addons-list for WDM: For Release 9.3 add the following: UPDATE_ADDONS_LIST+=" anyconnect_bundle-3.1.04063-50.sletc11sp2.rpm" For Release 9.7 add the following: UPDATE_ADDONS_LIST+=" anyconnect_bundle-3.1.05152-58.sletc11sp2.rpm" |
Create a CSF Device and a Directory Number for Each User
Note | Use the same Cisco Unified Client Services Framework (CSF) devices type for the virtual environment as you do for a nonvirtual environment. We recommend that you create only one CSF device for each virtual user. If multiple devices exist for a virtual user, Cisco Virtualization Experience Media Engine automatically selects the first device in the list. |
| Step 1 | From Cisco Unified Communications Manager Administration, choose . | ||||||||||||||||||||||
| Step 2 | Select Add New. | ||||||||||||||||||||||
| Step 3 | From the Phone Type drop-down list, choose Cisco Unified Client Services Framework, and then select Next. | ||||||||||||||||||||||
| Step 4 | In the Phone Configuration window, enter the applicable information for the phone as follows:
| ||||||||||||||||||||||
| Step 5 | Scroll down to the Product Specific Configuration Layout section, and set Video Calling to Enabled. | ||||||||||||||||||||||
| Step 6 | Select Save. | ||||||||||||||||||||||
| Step 7 | Select Apply Config if this button is available, and then confirm when prompted. | ||||||||||||||||||||||
| Step 8 | Select Add a new DN in the Association Information section that appears on the left side of the window. | ||||||||||||||||||||||
| Step 9 | Enter information for the directory number on the Directory Number Configuration window.
| ||||||||||||||||||||||
| Step 10 | Select Save. | ||||||||||||||||||||||
| Step 11 | Select Apply Config if this button is available, and then confirm when prompted. | ||||||||||||||||||||||
| Step 12 | Scroll to the bottom of the Directory Number Configuration window, and then select Associate End Users. | ||||||||||||||||||||||
| Step 13 | In the Find and List Users window, use the search criteria to find the user who you want to associate with the directory number. | ||||||||||||||||||||||
| Step 14 | Check the box next to that username, and then select Add Selected.
The user is now associated with the DN. | ||||||||||||||||||||||
| Step 15 | In the User Associated with Line section of the window, select the username. | ||||||||||||||||||||||
| Step 16 | In the End User Configuration window, scroll down to the Direct Number Associations section. | ||||||||||||||||||||||
| Step 17 | From the Primary Extension drop-down list, choose the DN for the user. | ||||||||||||||||||||||
| Step 18 | In the End User Configuration window, under Permissions Information, select Add to User Group or Add to Access Control Group, depending on your version of Cisco Unified Communications Manager. | ||||||||||||||||||||||
| Step 19 | In the Find and List User Groups window, use the search criteria to find Standard CCM End Users. | ||||||||||||||||||||||
| Step 20 | Check the box next to Standard CCM End Users, and then select Add Selected. | ||||||||||||||||||||||
| Step 21 | In the Find and List User Groups window, use the search criteria to find Standard CTI Enabled. | ||||||||||||||||||||||
| Step 22 | Check the box next to Standard CTI Enabled, and then select Add Selected. | ||||||||||||||||||||||
| Step 23 | Select Save. Cisco Unified Communications Manager reminds you that changes to line or directory number settings require a restart. However, you need only restart after you edit lines on Cisco Unified IP Phones that are running at the time of the modifications. |
Associate New Devices with a User
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 CTI Protocol for Users
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. |
What to Do Next
Enable the Unified Communications Manager IM and Presence Service. See the documentation for your version of Cisco Unified Communications Manager.
Change a User Password
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. |
Links to Documentation
Users may require assistance to familiarize themselves with their Cisco Unified Communications client and the accessories in the virtual environment. You can add links to the virtualization platform desktop, or to the Citrix or VMware login screens, so that users can easily locate the documentation.
- Create Desktop Shortcut
- Add a Link to the Citrix Landing Page
- Add a Link to the VMware Prelogin Banner
Create Desktop Shortcut
Add a desktop shortcut to the user documentation, for users who do not connect to their hosted virtual desktops in kiosk mode. Users can click the shortcut to access the documentation and to get help.
| Step 1 |
Open the wlx.ini
file for editing, by using Cisco VXC Manager or Dell Wyse Device Manager. Depending on your deployment, you may need to edit this file locally, in which case the file name is wnos.ini. |
| Step 2 |
Add the following lines:
CONNECT=BROWSER \ Description="Help Getting Started" \ URL=http://www.cisco.com/en/US/products/ps12862/products_user_guide_list.html \ Resolution=FullScreen \ Mode=Normal |
| Step 3 | Optional. Add the icon parameter to change the shortcut icon. Icon=image file The image file must be located in the wlx/bitmap directory on the server. If you do not specify an image file, the default icon appears. Supported file types are PNG, JPEG, and GIF, as well as XPM for backward compatibility. |
| Step 4 | Save the changes to the wlx.ini file. |
Add a Link to the Citrix Landing Page
You can add a link to the Citrix landing page. This link is important for Citrix connections that operate in kiosk mode. In kiosk mode, the users have no access to the thin client desktop.
Note | You must be a Desktop Delivery Controller (DDC) administrator. |
| Step 1 | Establish a Remote Desktop connection to the server running the Desktop Delivery Controller (DDC). |
| Step 2 | In the navigation tree, under Access, select . |
| Step 3 | Under Internal Site - Edit Settings, select Web Site Appearance. |
| Step 4 | In the Customize Web Site Appearance - Internal Site window, under Options, select Content. |
| Step 5 | Select the language code (for example, English [en]), and then select Edit. |
| Step 6 | In the Edit Custom Text window, check Footer text (all screens). |
| Step 7 |
In the Edit Custom Text window, under Customize Footer Text, enter text to point the user to the online documentation. Example:Sample text User Guides: http://www.cisco.com/en/US/products/ps12862/products_user_guide_list.html |
| Step 8 | Select Finish, and then select OK. |
Add a Link to the VMware Prelogin Banner
You can add a link to the VMware prelogin banner. This link is important for VMware connections that operate in kiosk mode. In kiosk mode, the users have no access to the thin client desktop.
Note | You must be a VMware Connection Server administrator. |
| Step 1 | Log in to the VMware Connection Server. |
| Step 2 | Select View Configuration - Global Settings. |
| Step 3 | Under the General section, select Edit. |
| Step 4 | Check Display a prelogin message. |
| Step 5 |
Enter text to point the user to the online documentation URL. Example:Sample text User Guides: http://www.cisco.com/en/US/products/ps12862/products_user_guide_list.html |
| Step 6 | Select OK. |
Configuration Files
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 their supported Cisco Unified Communications application, 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.
DHCP Pool Setup
If your network uses DHCP, you must specify the domain name in the DHCP pool. Without this setting, DHCP does not assign a domain to the Cisco Virtualization Experience Client 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 !
Domain Name Resolution
If the Cisco Virtualization Experience Client devices 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, you must edit the /etc/hosts file on the thin client. To make the change permanent, use the Cisco Virtualization Experience Client Manager to 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 Files Reference Guide.
Syntax
AddtoEtcHosts= "ip1 FQDN1 aliases1;ip2 FQDN2 aliases2"
Sample wlx.ini file
;************************************************************* ;* 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
Port Usage
If the network includes firewalls, you may have to open ports. See Ports Reference Guide for Cisco Virtualization Experience Media Engine Release 9.0, available from:
Upgrade to Release 9.7
You must upgrade both the image on the Cisco Virtualization Experience Client and the Unified Communications software on the hosted virtual desktop (HVD), for the Unified Communications features to work.
| Step 1 | Upgrade the image on the Cisco Virtualization Experience Client. |
| Step 2 | Install the Cisco Virtualization Experience Media Engine (VXME) prerequisite add-on. |
| Step 3 | Install the Cisco Virtualization Experience Media Engine (VXME) add-on. |
| Step 4 | On the HVD, uninstall any previously installed Cisco VXME Utilities and Cisco Unified Communications clients, such as Cisco Jabber, Cisco UC Integration™ for Microsoft Lync, or Cisco Unified Personal Communicator. |
| Step 5 | On the HVD, install Cisco VXME Utilities. |
| Step 6 | On the HVD, install Cisco Jabber. |
Upgrade Cisco Jabber for Windows
Use this procedure to upgrade to a newer release, or to repair either the Cisco Jabber or the Cisco VXME Utilities installation.
To upgrade to a new release, you must upgrade both the image on the Cisco Virtualization Experience Client and the Unified Communications software on the hosted virtual desktop (HVD), for the Unified Communications features to work.
Upgrade Cisco UC Integration for Microsoft Lync
Use this procedure to upgrade to a newer release, or to repair the Cisco UC Integration for Microsoft Lync and VXME Utilities installation. The Cisco UC Integration for Microsoft Lync Microsoft Installer (MSI) includes Cisco VXME Utilities.
To upgrade to a new release, you must upgrade both the image on the thin client and the Cisco Unified Communications software on the hosted virtual desktop (HVD), for the Unified Communications features to work.
| Step 1 | Close Cisco UC Integration for Microsoft Lync and ensure that it is not running on the HVD. If Cisco UC Integration for Microsoft Lync is running during the installation, you must completely exit and restart Cisco UC Integration for Microsoft Lync to enable virtualization. |
| Step 2 | Install Cisco UC Integration for Microsoft Lync. |
Feedback