Configuring ICA Multi-Stream – Virtual Channel Stream Assignment

The ICA stream that virtual channels are assigned to when Multi-Stream is enabled can be changed if needed.

If using VDA 2003+, or VDA 1912 LTSR CU1+, this is done using the policy setting “Multi-Stream virtual channel stream assignment”, which is available in Studio with Citrix Cloud as well as the VDAs’ corresponding on-prem Delivery Controllers.

If using older versions of XAXD/CVAD, this must be done in the VDAs’ registry by modifying the “VirtualChannels” value under the “HKLMSYSTEMCurrentControlSetControlTerminal ServerWdsicawdMultiStreamIca” key. The format for this value is “vcName,stream#;”, where “vcName” is the name of the virtual channel, and “stream#” is the number of the stream the virtual channel is assigned to.

Please note that the “VirtualChannels” value will not work with VDA 2003+ nor VDA 1912 LTSR CU1+.

To change the stream assignment, change the stream number in the Virtual Channel Stream Pair for the appropriate virtual channel(s). Please note that the virtual channel names must contain seven characters. In the case that a virtual channel name is less than seven characters, spaces are added. Do not remove these spaces.

The default data in the “VirtualChannels” value is:


Also under the HKLMSYSTEMCurrentControlSetControlTerminal ServerWdsicawdMultiStreamIca” key is a value named “Streams”, which applies to all versions of XAXD/CVAD. This value defines which of the four streams is the primary one and which are secondary. The format for this value is “stream#,streamType;”, where “stream#” starts with 0 and increments by 1, and streamType is either ‘P’ for primary or ‘S’ for secondary. Please note that there can only be one primary stream. The default data for this value is “0,S;1,P;2,S;3,S;”.

Note: Changes to the registry values mentioned in this article do not require a reboot to take effect. However, changes to the “Multi-Port Policy” setting do require a reboot.

Information on how to change the virtual channel priorities within the ICA stream can be found in CTX128190.


  • No Related Posts

Connectrix B-Series: Device logging in as a loopback

Article Number: 504622 Article Version: 3 Article Type: Break Fix

Connectrix,Connectrix B-Series Hardware

Why does a HBA or storage device automatically configure to a loopback port?

This could be caused by controller configuration on the HBA or storage.

Check if the end device is configured for Fiber Channel Arbitrated loop (FC-AL). Also check the integrity of the SFP and cable and reset the port as follows

– portcfgpersistentdisable

– portcfgdefault

– portcfgpersistentenable.

If the status of the port is still loopback after doing the above, move the cable to a free port. If the issue follows then it could well be an issue with the connected device and more troubleshooting would need to be done at that end.


  • No Related Posts

1-16-2019 Citrix Cloud Connector Incident Management: Failed Connectivity Check

Impact & Workaround

  • New Cloud Connectors will fail the connectivity check performed during install which will prevent installation from proceeding. A workaround is available by installing the connector from the command line using the /SkipConnectivityTest:true parameter. Using this workaround customers can install new connectors, and the connector will be fully functional.

To install a new connector while this issue is active, run this from the command line: .cwcconnector.exe /skipconnectivitytest:true

User-added image
Example of connectivity check failure alert appearing during connector install

  • Existing Cloud Connectors will fail their regular connectivity checks and generate in-product notifications and warning status. Connectivity checks are executed automatically every hour, or on-demand via the administrative UI.
    • At this time, Citrix has stopped the regular hourly health checks from running to avoid unnecessary alerting.
    • In-product connector status may still reflect the results of the last executed health check. There is no workaround available to suppress the failed connectivity check status in the connector UI.

User-added image

Example of connectivity check failure alert appearing in the Connector UI

User-added image

Example of connectivity check failure notifications appearing in the Citrix Cloud administrator navigation UI

User-added imageExample of connectivity check failure notifications appearing in the Citrix Cloud notifications UI

How it works:

The connectivity check is performed to confirm the connector machine can access the storage URL hosting the connector download. The connectivity check reaches out to a storage URL to confirm the connector machine is able to contact and receive a response from that URL. The primary function of this check is to ensure network connectivity to the internet, and access to that specific URL. During this check, the connector is not targeting a specific file or download, but is confirming a specific response from that storage. The response the connectivity check receives from accessing that URL has changed recently, triggering the error shown and issue cited above.


  • No Related Posts

FPGAs vs. GPUs: A Tale of Two Accelerators

EMC logo

In deep learning applications, FPGA accelerators offer unique advantages for certain use cases. In artificial intelligence applications, including machine learning and deep learning, speed is everything. Whether you’re talking about autonomous driving, real-time stock trading or online searches, faster results equate to better results. This need for speed has led to a growing debate on the best accelerators for use in AI applications. In many cases, this debate comes down to a question of server FPGAs vs. GPUs — or field programmable gate arrays vs. graphics processing units. To see signs of this lively debate, you … READ MORE


Update your feed preferences





submit to reddit


  • No Related Posts