Release Notes for Cisco Virtualization Experience Client 2112/2212 ICA Firmware Release 7.1_118
Release Notes for Cisco Virtualization Experience Client 2112/2212 ICA Firmware Release 7.1_118
Downloads: This chapterpdf (PDF - 1.05MB) The complete bookPDF (PDF - 1.31MB) | Feedback

Release Notes for Cisco Virtualization Experience Client 2112/2212 ICA Firmware Release 7.1_118

Release Notes for Cisco Virtualization Experience Client 2112/2212 ICA Firmware Release 7.1_118

Introduction

The Cisco Virtualization Experience Client (VXC) 2112 and 2212 are workstation-class virtualization clients for use with the Independent Computing Architecture (ICA) and the Remote Desktop Protocol (RDP). The ICA and RDP protocols are designed to deliver a user desktop from a centralized host server across standard IP networks, enabling you to use applications and desktop peripherals as if you were using them locally.

This release supports the following Cisco Virtualization Experience Clients (VXC) clients using WTOS firmware:

  • Cisco VXC 2112, integrated
  • Cisco VXC 2212, standalone

The Cisco VXC 2112 attaches to the Cisco Unified IP Phone 8961, 9951, or 9971 through a spine connector cable. The Cisco Unified IP Phone 8961, 9951, or 9971 must run Firmware Release 9.1(2) or later.

The Cisco VXC 2212 operates independently and is powered by either an AC adapter (CP-PWR-CUBE-4) or by Power over Ethernet (PoE) capable Cisco Switches.

Related documentation

For more information, see the documents available at the following URLs:

New and changed information

RemoteApp (Microsoft broker)

Microsoft RemoteApp and Desktop Connection provides the ability to group RemoteApp programs in a Windows 2008 server R2 with Remote Desktop Session Host role installed, and make them available to end users. By specifying the broker server address in the WTOS broker setup, WTOS users are able to launch remote applications through Connect Manager or desktop shortcuts. The broker server address can begin with http, https or no protocol prefix. For example, the following inputs are all acceptable:

  • http://ip
  • https://ip
  • IP
  • http://FQDN
  • https://FWDN
  • FQDN

Setting

Open System Setup > Remote Connections > Broker Setup and check Microsoft.

Notes

  1. Due to default server settings, the connections are all converted to HTTPS security connections, and you need import the server certification to WTOS for security considerations.
  2. You must install Remote Desktop Session Host server, Remote Desktop Connection Broker server and Remote Desktop Web Access server. All are required on the Windows Server 2008 R2. For details, please see Microsoft documents at http://msdn.microsoft.com/en-us/library/dd883258(v=WS.10).aspx.
  3. Seamless is only supported in Classic mode.
Figure 1. Remote Connections dialog box



Localization

WTOS now supports administrator-defined user interface languages within the WTOS operating system. WTOS supports loading localization files from an FTP server, controlled by INI configurations.


Note


Administrators can change preset translations or create their own translations to meet the needs of their users. To modify an existing translation file, the administrator can open a .msg file in a text editor, edit the translated strings, and then resave as a .msg file.


Implementation Example: Japanese Locale Font

  1. Within the downloaded 7.1_118 firmware package, locate the zipped localization folder.
  2. On the file server, unzip the localization folder.
  3. Within the WNOS folder, create folders named Font and Locale.
  4. Copy the Japanese.msg file from the localization folder into the Locale folder (WNOS\Locale).
  5. Copy the Japanese.fnt file from the localization folder into the Font folder (WNOS\Font).
  6. In the wnos.ini file, add the following parameters Locale=Japanese load=Yes and save the wnos.ini file.
  7. (Optional) Add a User language selection menu within the system preference. This will enable the user to switch between different languages. You can specify a list of locales in the wnos.ini file, so that a user can switch the system language as needed (for example, LocaleList=German, Japanese). All the values display in the administrative interface ( System Preference > General > Locale ). Be sure to place the necessary files, for example German.msg, Japanese.msg, and Japanese.fnt in the correct locations under the WNOS folder.
  8. Restart the thin client.
Figure 2. Japanese localization



Table 1 Localization INI parameter definition
Parameter Definition

Locale[7.1_025]={English | us | French | fr | German | de | …} load={ yes | no }

LocaleList[7.0_109]={English | us, French | fr, German | de, …}

Locale is used to specify system language. Load=yes/no is used to tell WTOS to load the language file or not. The language file must be placed under the folder wnos/locale on the fileserver. Its suffix is "msg". For example, if user wants to specify his system language to be French and load the localized messages, he or she should place a file named French.msg under the folder wnos/locale in fileserver, and then he should add 'Locale=French load=yes' in INI.

LocaleList is to specify a list of locale, so that user can switch the system language between them as they wish. All the values will be display in the GUI (System Preference -> General-> Locale). A max 16 items can be specified. Also, the corresponding file, e.g. German.msg, should be placed under the folder wnos/locale.

For CCJK (Chinese simplified, Chinese traditional, Japanese and Korean) localization, the font file must be placed under the folder wnos/font in fileserver. Its suffix is "fnt". For example, if user wants to specify his system language to be Japanese, he or she should place a file named "Japanese.msg" in wnos/locale and "Japanese.fnt" in wnos/font in file server. The following is the mapping of language alias to language name.

  • us: English
  • fr: French
  • de: German
  • gb: Chinese Simplified
  • b5: Chinese Traditional
  • jp: Japanese
  • ko: Korean
  • la: Latin

ICA RTP audio

ICA RTP audio uses UDP as the underlying transport making it suitable for real time audio data. Audio data that is not transported through RAVE (the ICA multimedia redirection channel) uses RTP as a separate channel for transport. As a result, audio performance can be improved when there is very large audio data between the client and the server, for example, when you are using a VoIP application such as Skype.

Note

  1. This feature is only supported in XenDesktop 5 FP1 or above.
  2. You must enable the Audio over UDP Real-time Transport option in the XenDDC policy settings.
  3. RTP is enabled only when the resultant audio quality is medium. Resultant audio quality will be the lower of the server and the client.
  4. You must set the encryption level for the desktop session to Basic or 128 Bits Login Only.
  5. This feature is not supported if a gateway connection (Citrix Access Gateway) exists between the client and the server.

Plug and play in XenApp 6.0 and later

The ICA Plug and Play function supports two ways to map USB disks:

  1. Launch the ICA session with Disks enabled first, and then plug in the USB disk; the USB disk can then be mapped to the server.
  2. Plug in the USB disk first, and then launch ICA session with Disks enabled; the USB disk can then be mapped to the server.

Note


For users of earlier versions than XenApp 6.0, you must use method 2 (plug in the USB disk first, and then launch the ICA session with Disks enabled; the USB disk can then be mapped to the server).


You can enable the Disks option for all sessions using the SessionConfig=All MapDisks=yes INI parameter or under Global Connection Settings > Session in the Administrative interface. To enable the Disks option for a single session, click Settings at session login.

Certificate manager

Certificate Management

To deploy an SSL-based application, the server must be configured so that it will authenticate the identity of the client. If a user certificate is applied from the Root certificate authority (CA), then that user can access file servers and applications in the subdomain. Due to the fact that the Sub-CA is configured to be trusted automatically by the Root CA, when the client sends the entire certificate chain to the server in the root domain for authentication, the user is then able to access file servers and applications in the subdomain.

Figure 3. Network Setup: Security tab

  • Click Certificate Center to open the Certificates Browser and choose the Import From option from which you want to import a certificate (either USB Storage or File Server).
  • USB Storage - If you choose the USB Storage option, click Import to open and use the Import dialog box to find and select the certificate you want to use. The maximum importing path is limited to 128 characters and the maximum certificate name is limited to 64 characters.
  • File Server - If you choose the File Server option, click Import to open and use the Import dialog box to enter the detailed path to the certificate you want to use in the File Servers box (if necessary, be sure to use the correct Username and Password). Note that you must enter the absolute path of the certificate. For example: 10.151.121.100/wnos/cacerts/mycertificate.cer. The maximum importing path is limited to 128 characters and the maximum certificate name is limited to 64 characters.

EAP authentication update

In the Authentication Properties dialog box, if you choose EAP-MSCHAPv2 as the EAP Type (, you can specify EAP Identity as the first level of authentication (after which, MSCHAPv2 will occur).

To open the Authentication Properties dialog box, choose Network Setup > Security, choose PEAP as the EAP Type, and then click Properties .

In addition, if you check the Enable Single Sign On check box, the zero client will use the credentials of MSCHAPv2 to sign on to the WTOS local desktop and establish the system variables $UN, $PW and $DN to sign on to your RDP or ICA sessions.

Figure 4. Authentication Properties dialog box



Hardware codecs

  • Removed Divx3, MSMPEG4V2, MSMPEG4V3 video decoder support. H264, WMV3 and WMVA are supported.
  • Added ACC audio decoder for a total of 3 audio decoders (MP3, WMA and AAC) supported.

Support for built-in camera microphone

If you connect a USB camera with built-in microphone to the zero client, WTOS now recognizes the built-in microphone as a local audio recording device. The user can also use the built-in microphone in remote sessions.

However the built-in microphone sometimes may not function properly by itself, and therefore, Cisco recommends that you enable video capturing on the camera when you use the built-in microphone. This problem is also observed on Windows operating systems.

MirrorFileServer INI parameter

The MirrorFileServer parameter provides the same functionality as the previously supported enablecacheini parameter that is removed from the 7.1_118 and later versions of firmware. You are now able to save the file server settings onto the local flash of the unit. This allows the client to boot to the configured state without having to have a connection to the file server. For example, INI files, wallpaper, bitmap, font, locale messages and so on are all saved to the local flash.

Set MirrorFileServer=yes to enable the feature.


Note


  1. From release 7.1_118 onward, the functionality supported by the enableinicache parameter is discarded and the MirrorFileServer parameter replaces it.
  2. After you upgrade from release 7.0_627 to release 7.1_118, the cached INI is still saved but ineffective. Set MirrorFileServer=yes to save it again.
  3. After the INI is specified in the file server, WTOS will read it at the first restart, and the parameter will be effective after the second restart.

Administrative interface updates

Granular Control over USB redirection

The following sections describe the updates to the administrative interface.

By default, audio, video, and printer devices do not use HDX USB for redirection. You can make selections for USB device redirection on the Session tab of the Global Connection Settings dialog box.


Note


For Web camera mapping, if the server does not support HDX USB redirection and you set this mode in the client, the client uses HDX Realtime Webcam Compression.


Figure 5. Global Connection Settings



Audio options

A drop-down list is added on the Audio tab of the Peripherals dialog box. When you connect a USB headset, its name will be shown in the drop-down list. The HD Audio option is for analog earphone use. The Boost option is for audio enhancement.

Figure 6. Audio tab



Map All Disks additions

A drop-down list has been added on the ICA tab of the Global Connection Settings dialog box allowing you to select additional drives for the Map all disks under setting (no longer only Z drive).

Figure 7. ICA tab



Device Viewer window

A Device Viewer window displays when you click the Device Viewer button (System Information > Devices) allowing you to easily view recognized devices.


Note


This screen provides USB information (such as PIV and VID) needed for forcelocal= or forceredirect= INI parameters.


Figure 8. Device Viewer



Hide domain security option

When EAP Type EAP-MSCCHAPV2 is selected on the Authentication Properties dialog box (for PEAP IEEE802.1x authentication), a new option to hide the domain is available for selection (the Username and Password text boxes are available for use, but the Domain text box displays gray).

Figure 9. Authentication Properties



Wild card certificates

Wild card certificates are now supported on IEEE802.1x Authentication for EAP-TLS and EAP-PEAP.

For EAP-TLS to support this feature, you must check the Validate Server Certificate check box, which means that the end user must have a root certificate.

With EAP-PEAP, the Validate Server Certificate setting is optional.

Figure 10. Authentication Properties: Validate Server Certificate



The following kinds of server names are supported (all examples are based on the certificate common name of company.cisco.com):

  • company.cisco.com
  • *.cisco.com
  • *cisco.com
  • *.com
  • *

The server certificate text field supports 127 characters at most, and also supports multiple server names.

VMware View client security updates

The VMware View Client provides three security modes that govern verifying the identity of the servers to which it connects.

  • Full Verification
  • Warn on View (default)
  • No Security

Setting

Open Remote Connections > Broker Setup and click VMware View.

Figure 11. Broker Setup tab



See the following table for an understanding of how the VMware View Security Error handling results are based on the different configuration options.

Certificate Security mode Configuration Action Details
Self-signed cert (default) Full security FQDN Cannot continue

The certificate authority is invalid or incorrect.

Warn on View (default)

IP

Can continue

The certificate authority is invalid or incorrect. The host name in the certificate is invalid or does not match.

FQDN

Can continue

The certificate authority is invalid or incorrect.

FQDN + expired server cert

Cannot continue

The certificate authority is invalid or incorrect. The supplied certificate is invalid.

Issued by CA Full Security

FQDN + root cert

Can access

 

IP + root cert

Cannot continue

The host name in the certificate is invalid or does not match.

FQDN without root cert

Cannot continue

The certificate authority is invalid or incorrect.

FQDN + expired root cert and server cert

Cannot continue

The certificate authority is invalid or incorrect. The supplied certificate is invalid.

FQDN + expired root cert and server cert

Cannot continue

The supplied certificate is invalid.

Revoked cert Not supported
Key usage Select a certificate and click the View Certificate button to check.
Warn on View (default) IP + root cert Cannot continue The host name in the certificate is invalid or does not match.
FQDN + expired root cert and server cert Cannot continue The certificate authority is invalid or incorrect. The supplied certificate is invalid.
FQDN + expired server cert Can continue The supplied certificate is invalid.

Note



Note the following recommendations and guidelines:

  • Use Full Security if the server certificate is issued by a CA.
  • Use Warn on View (default) if the server certificate is self-signed.
  • Smartcard logon is not supported if the server certificate is issued by a CA, regardless of which security mode you select.
  • Smartcard logon is supported on Warn on View (default) and No Security modes if the server certificate is self-signed.
  • See the following link for information on changing a self-signed cert to CA issued certificate: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1008705

CMOS Central Management

CMOS Central Management allows administrators to easily manage BIOS setting for large deployments of zero clients using central configuration.

For detailed information on how to use CMOS Central Management (CCM), see the Administration Guide for Cisco Virtualization Expereience Client 2112/2212.

New and modified INI parameters

The following table describes the new and modified INI parameters added to the INI Files Reference Guide for Cisco Virtualization Experience Client 2112/2212 for release 7.1_118. These changes include the new parameters introduced in release 7.0_627.

Table 2 New and modified INI parameters
Parameter Description
$WPDN and $PF $WPDN and $PF parameters added to Table 1 "System Variables."
BootpDisable

New parameter to disable BOOTP requests added in Table 5 "General Settings: wnos.ini files and {username}.ini Files."

ConnectionBroker= has the following new options:

  • [IgnoreProfile={no, yes}]
  • [SecurityMode={None,Warning, Full}]

ConnectionBroker options in Table 4 "Connection Settings: wnos.ini files only" updated to include:

  • IgnoreProfile to disable parsing the global setting from the VDI broker. It is only valid in the case of ConnectionBroker=default.
  • SecurityMode to specify the security mode for the VMware broker. It is only valid in the case of ConnectionBroker=VMware.

ConnectionBroker={default, Microsoft, VMware}

Additional ConnectionBroker values for VMware and Microsoft added to Table 7 "Connection Settings: wnos.ini files and {username}.ini files" providing additional connection broker options.

CustomInfo

New parameter to configure/store custom information into NVRAM added in Table 5 "General Settings: wnos.ini files and {username}.ini Files."

Desktop=Bitmap file

IconTextColor option added to Desktop=Bitmap file parameter in Table 5 "General Settings: wnos.ini files and {username}.ini Files" to specify the icon text color in RGB string format.

Device=audio has the following new option:

  • [min_cache={1-50}]

Device=audio options in Table 6 "Peripheral Settings: wnos.ini files and {username}.ini Files" updated to include:

  • min_cache to configure the WTOS audio playback minimum buffering amount (in ten millisecond units). "min_cache" can be used when network bandwidth is not large enough to play audio smoothly. In such cases, set "min_cache" higher, so that WTOS will buffer more audio data before playing the audio.
Device=cmos

New parameter to extract and restore CMOS content added in Table 5 "General Settings: wnos.ini files and {username}.ini Files."

Device=camera

Device=camera added to Table 6 "Peripheral Settings: wnos.ini files and {username}.ini Files" providing an option to set local camera settings.

Device=Ethernet

Device=Ethernet parameter option KeepAlive has values updated to 1 to 600 seconds in Table 7 "Connection Settings: wnos.ini files and {username}.ini files."

DNSIPVersion

New parameter to Specifies the DNS server and domain added in Table 4 "Connection Settings: wnos.ini files only."

EnableCacheIni
Important:

DO NOT USE: This parameter is no longer supported and cannot be used. It is replaced by the MirrorFileServer parameter (see MirrorFileServer parameter in Table 2 "General Settings: wnos.ini files only").

IEEE8021X

IEEE8021X options in Table 7 "Connection Settings: wnos.ini files and {username}.ini files" updated to include:

  • Peapidentity to specify the identity/username for PEAP.
  • Peapsinglesignon to enable single sign-on.
  • tlsauthtype={user, machine}
  • peapmschaphidedm option to have the domain use saved peap MSCHAP domain name and the pop up dialog will not include the domain field when doing IEEE8021x authentication.
  • [peapgtcpwdEnc={password for encrypted for EAP-PEAP/ EAP-GTC}].
IPProto=ICMP

New parameter to configure the ICMP protocol added in Table 7 "Connection Settings: wnos.ini files and {username}.ini files."

Language=code

Language=code option ImageSuffix values in Table 5 "General Settings: wnos.ini files and {username}.ini Files" updated to include localization builds with different suffixes according to the keyboard language.

Locale

Additional Locale language values added to Table 5 "General Settings: wnos.ini files and {username}.ini Files" providing additional language options.

LocaleList

Additional LocaleList language values added to Table 5 "General Settings: wnos.ini files and {username}.ini Files" providing additional language options.

MirrorFileServer

MirrorFileServer parameter added to Table 2 "General Settings: wnos.ini files only" providing an option to enable the cache all server files functionality (cache all server files such as INI files, wallpaper, bitmap, font, local messages and so on to the local flash when files are changed in the file server). WTOS would use the cached files when files on the file server are unavailable.

MultiLogon
Important:

DO NOT USE as this parameter is being deprecated. Use SelectServerList={PNA, VDI} in Table 4 "Connection Settings: wnos.ini files only."

NoReducer

NoReducer option Encryption added in Table 7 "Connection Settings: wnos.ini files and {username}.ini files" to specify the default setting of encryption level for all ICA connections (ICA Only).

PlatformConfig=all

[EncryptFS=yes]

New parameter to encrypt local flash, specifically cached INI files and credentials that are stored (if using signon=yes) added in Table 4 "Connection Settings: wnos.ini files only."

PnliteServer

PnliteServer parameter in Table 7 "Connection Settings: wnos.ini files and {username}.ini files" updated to include

  • Option CAGRSAAuthMethod values LDAP and RSA for authentication.
  • CAGAuthMethod option for CAG authentication.
RDPAudioQualityMode
Important:

DO NOT USE as this option is being deprecated.

Reconnect

Reconnect options in Table 7 "Connection Settings: wnos.ini files and {username}.ini files" updated to include seconds value (the interval to wait before automatically restarting the connection after disconnect).

Resolution=DDC has additional information

Resolution option [rgamma={1-100} ggamma={1-100} bgamma={1-100}] removed from Table 6 "Peripheral Settings: wnos.ini files and {username}.ini Files" as this option is no longer supported.

The following note was added to Table 6 "Peripheral Settings: wnos.ini files and {username}.ini Files" providing additional information for Resolution=DDC:

Important:

When using a Y Cable, DDC will properly work on both monitors by default.

SessionConfig=ALL

SessionConfig=ALL options in Table 7 "Connection Settings: wnos.ini files and {username}.ini files" updated to include:

  • DefaultColor to specify the default color depth to use for the session.
  • VUSB_DISKS, VUSB_AUDIO, VUSB_VIDEO, and VUSB_PRINTER — Specifies if these USB devices will be redirected to the server using TCX Virtual USB or ICA/RDP USB redirection when USB redirection is enabled. By default, these devices are set as local devices.
  • DisableResetVM to disable "Reset VM" function. As default, this function is controlled by the server side including VMware View or Citrix PNA
  • FullScreen to specify the default screen mode.
  • Resolution to specify the session resolution. For example, 640 x 480 and so on (refer to supported resolutions).

SessionConfig=ICA

SessionConfig=ICA options in Table 7 "Connection Settings: wnos.ini files and {username}.ini files" updated to include:

  • CGPParseMessageLen to have the CGP parse the incoming stream before receiving the full package. By default CGP will parse the stream.
  • mapdisksunderz updated to include a driver letter to replace the default drive letter Z. For example, if MapdisksUnderZ=X, all the disks will be under the drive X instead of drive Z.
  • USBRedirection to select the channel of USB devices redirection. Default is ICA|HDX. This option is recommended to replace older setting "device=vusb type={TCX, HDX}".
SessionConfig=RDP

SessionConfig=RDP in Table 7 "Connection Settings: wnos.ini files and {username}.ini files" updated to include the following new options:

  • RDPScreenAlign4 to force RDP session width to 4 pixels aligned
  • "WallPaper", "Dragging", "Animation" and "Theme" options to set the RDP experience
  • ForceSpan — Yes/no option to disable RDP Multi Monitor feature. Default is no.
  • EnableTSMM — Yes/no option to enable RDP7 Multi-media redirect. Default is yes.
  • EnableRecord — Yes/no option to enable RDP feature of recording from local. Default is no.
  • EnableRFX — Yes/no option to enable Bitmap Codec RemoteFX. Default is yes.
  • USBRedirection — Option to select the channel of usb devices redirection. Default is TCX.

For example:

SessionConfig=RDP MaxBmpCache=1024 DefaultColor=1 EnableNLA=yes ForceSpan=yes EnableTSMM=no EnableRecord=yes EnableRFX=no

Shutdown

New parameter to specify the system state when shutting down the unit added in Table 5 "General Settings: wnos.ini files and {username}.ini Files."

SignOn

SignOn options in Table 4 "Connection Settings: wnos.ini files only" updated to include:

  • SaveLastDomainUser additional values of user and domain.
  • DefaultINI=filename to specify the file name which is in the default folder of the username ini files. If the {username}.ini is not found, this file will be loaded as default.
  • PasswordVariables to enable variable mapping ($TN, $UN etc) for a password.

SignOn= has the following new option:

[ExpireTime={1 - 480}]

SignOn options in Table 4 "Connection Settings: wnos.ini files only" updated to include:

  • ExpireTime to specify the signon expiration time. The range is 0 to 480 minutes. The default is 0 which means no expiration.
SwitchApplication
Important:

DO NOT USE as this parameter is being deprecated.

SysMode= has the following new options:

  • [ToolbarAutoQuit={yes, no}]
  • [ToolbarStay={1~20}]
  • [ToolbarEnableOneSession={no, yes}]

SysMode options in Table 4 "Connection Settings: wnos.ini files only" updated to include:

  • ToolbarAutoQuit to prevent the sub-window from being closed. The toolbar will auto-hide after a certain amount of time after user moves the mouse pointer away from the toolbar.
  • ToolbarStay to control the auto-hide duration, 0.5s per value. Thus if ToolbarStay=1, the Toolbar will auto-hide after 0.5 second; If ToolbarStay=10, the Toolbar will auto-hide after 5 seconds.
  • ToolbarEnableOneSession option to enable the toolbar when only one session is available.
TcpMaxRetransmission={2~12}

New parameter to configure the retransmission of a TCP connection. added in Table 7 "Connection Settings: wnos.ini files and {username}.ini files."

TcpTimeOut

New TcpTimeOut values 1 and 2 to specify the timeout value of a TCP connection (the number of 30 seconds for the timeout value of a TCP connection) added in Table 4 "Connection Settings: wnos.ini files only."

WakeOnLAN={yes, no}

New parameter to specify the WakeOnLAN settings added in Table 5 "General Settings: wnos.ini files and {username}.ini Files."

WINSServer=server_list

New parameter to specify the WINS server address added in Table 4 "Connection Settings: wnos.ini files only."

Additional notes

The following provides additional notes and relevant information for release 7.1_118:

  • EnableCacheINI has been deprecated in 7.1.
  • Unsupported Headsets:
    • When a device is not supported by WTOS it can be force redirected into the session using the following parameter. Vusbaudio=Yes.

      Note


      If you are using ICA redirection, this configuration will not work. This is due to the fact that RAVE looks for the local device to bring to the audio too from the remote session. When you force the headset into the remote session, it is no longer recognized as a local device, thus you will get no sound from the headset.


  • Video or sound pauses with H.264 Redirected Playback within XD5 and XD5 SP1:
    • If you change the registry below, it will work as expected. [HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\SpeedScreen] change the value to 1: SkipFlowControl"=dword:00000001
  • In some situations in order to use the Citrix Access Gateway (CAG), you must enact the following policy:
    • REQ.HTTP.HADER USER-Agent CONTAINS WYSE THINOS; not citrix receiver.
  • In some situations the Timezone Parameter will not display properly. A workaround to this issue is using the following for timezone settings. Single Brackets TimeZone=’GMT+05:30’ must have Manualoverride=yes

Installation notes

For installation instructions, see Quick Start Guide: Cisco Virtualization Experience Client (VXC) 2112/2212.

Installing Firmware Release 7.1_118 for Cisco VXC 2112/2212 Clients

  1. Go to the following URL: http://www.cisco.com/cisco/software/navigator.html
  2. Log in to the Download Software page.
  3. Choose Products > Voice and Unified Communications > IP Telephony > Virtualized Endpoints.
  4. Choose Cisco Virtualization Experience Client 2000 Series.
  5. Choose your client type.
  6. In the Latest Releases folder, choose 7.1.118.
  7. Select one the following firmware files, click the Download Now or Add to cart button, and follow the prompts:
    • ICA7.1_118.zip (Release 7.1_118 Firmware for Cisco VXC 2112/2212)
    • VXC2x12-7.1_118-VXCM-Package.zip (Package containing Release 7.1_118 Firmware for Cisco VXC 2112/2212 and supporting files for upgrades using Cisco VXC Manager)
  8. To update the firmware using Cisco VXC Manager, see the Administration Guide for Cisco VXC Manager. For more information about using central configuration for client upgrades, see the "Central Configuration: Automating Updates and Configuration" section of the Administration Guide for Cisco Virtualization Experience Client 2112/2212.

Important notes

This section provides general information about using and supporting the Cisco VXC 2112/2212 in your environment.

ICA Compatibility

For best experience and performance, use Citrix XenDesktop 5.6 or Citrix XenApp 6.5 with Firmware Release 7.1_118.

RDP Compatibility

Firmware Release 7.1_118 supports RDP 7.1 including the use of VMware View for RDP deployments.

Cisco VXC VPN with Cisco IP Phones 8961, 9951, or 9971

Cisco IP Phones 8961, 9951, or 9971 running Firmware Release 9.3(1) or later provide support for the Cisco VXC VPN feature, which provides integrated VPN functionality for the Cisco VXC 2112. You can use this feature to enable VPN tunneling for the Cisco VXC 2112 clients when they are attached to Cisco Unified IP Phones 8961, 9951, or 9971. This feature is not supported on the Cisco VXC 2212.

The Cisco VXC clients require no configuration to support the VPN. All VPN configuration is performed for the phone only.

To support the Cisco VXC VPN feature, the Cisco VXC 2112 clients must be running the minimum ICA Firmware Release 7.1_118 or later.

For more information, see Cisco Unified IP Phone 8961, 9951, and 9971 Release Notes for Firmware Release 9.3(1).

LLDP Required for Cisco VXC 2212 Power Negotiation

To allow PoE-powered Cisco VXC 2212 clients to negotiate power requirements with the connected switch, you must enable LLDP on the connected switch. Otherwise, the client may not be able to draw sufficient power to operate properly.

RDP USB Redirection

The USB redirection feature does not function with RDP as it does with ICA. In ICA when USB devices are plugged in, the client displays the auto-play dialog window and the device appears as removable storage (which can be ejected). In RDP, the client maps the device as network storage, which can cause issues if the application that has the file open for writing crashes, causing a locked file. For USB redirection to work the same way with RDP as it does with ICA, the VM must be Windows 7 running on a Hyper-V hypervisor.

To enable USB redirection, you must enable disk mapping using the mapdisks parameter in the INI file or using the Disks option on the Global Connection Settings > Session tab.

Maximum Resolution and Bit Rate for Windows Media Viewer (WMV) files with RDP

The following table describes the maximum and recommended resolution and bit rate for Windows Media Viewer (WMV) files in RDP sessions.

Table 3 Maximum Resolution and bit rate for WMV files with RDP
Protocol

RDP

Decoder

WMV

Maximum Resolution/Bit Rate

720p/6.5 Mbit/s

Recommended Resolution/Bit Rate

480p/3 Mbit/s

Comments

At a higher resolution or bit rate, audio and video may not be fully synchronized.

Smart card support

Cisco VXC 2112/2212 clients do not currently support smart cards. Cisco VXC 2112/2212 clients will support smart cards in a future firmware release.

Caveats

Using bug toolkit

Known problems (bugs) are graded according to severity level. These release notes contain descriptions of:

  • All severity level 1 or 2 bugs
  • Significant severity level 3 bugs

You can search for problems by using the Cisco Software Bug Toolkit.

To access Bug Toolkit, you need the following items:

  • Internet connection
  • Web browser
  • Cisco.com user ID and password

To use the Software Bug Toolkit, follow these steps:

  1. To access the Bug Toolkit, go to: http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs
  2. Log in with your Cisco.com user ID and password.

To look for information about a specific problem, enter the bug ID number in the "Search for bug ID" field, then click Go.

Open caveats

The following table lists severity 1, 2, and 3 defects that are open for the Cisco Virtualization Experience Client 2112/2212 using Firmware Release 7.1_118.

For more information about an individual defect, you can access the online record for the defect by clicking the Identifier or going to the URL shown. You must be a registered Cisco.com user to access this online information.

Because defect status continually changes, be aware that the following table reflects a snapshot of the defects that were open at the time this report was compiled. For an updated view of open defects, access Bug Toolkit as described in the Using bug toolkit.

Table 4  Open Caveats for the Cisco Virtualization Experience Client 2112/2212

Identifier

Severity

Headline

CSCtu48455 2 VXC2112 keeps link up when user already power-off device
CSCtz55392 3 ICA_7.1_118:Power source field is always displayed as "AF PSE".
CSCua18656 3 Domain name is being sent for Authentication although Hide Domain set
CSCua23049 2 All EAP and dot1x authentication methods fail when using re-authentication
CSCua27680 3 ICA_7.1_118: ERR_CERT_BAD_SUBJECT_NAME displayed for certificate server
CSCua33949 3 Deleting "Self service" server address causes no applications to be list

Resolved caveats

The following table lists severity 1, 2, and 3 defects that are resolved for the Cisco Virtualization Experience Client 2112/2212 using Firmware Release 7.1_118.

For more information about an individual defect, you can access the online record for the defect by clicking the Identifier or going to the URL shown. You must be a registered Cisco.com user to access this online information.

Because defect status continually changes, be aware that this table reflects a snapshot of the defects that were open at the time this report was compiled. For an updated view of open defects, access Bug Toolkit as described in Using bug toolkit

Table 5  Resolved Caveats for the Cisco Virtualization Experience Client 2112/2212

Identifier

Severity

Headline

CSCtu51676 3 VXC2112 does not use the new DNS/Domain Name in later ACK

Documentation changes

This section provides documentation changes that will be implemented in the next major update of WTOS firmware.

Internal Button Cell Battery: Nonreplaceable

The Quick Start Guide: Cisco Virtualization Experience Client (VXC) 2112/2212 states that the internal button cell battery in the Cisco VXC 2112/2212 client is replaceable by Cisco. This information is incorrect.

The internal button cell battery in the Cisco VXC 2112/2212 client is not replaceable by Cisco. If issues arise with the battery, you must return the Cisco VXC client.

Obtaining documentation and submitting a service request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.