[http://www.ncomputing.com NComputing] makes sure [http://www.stratodesk.com/products/notouch-desktop NoTouch] has latest versions of Citrix Receiver Workspace App (formerly known as ICA clientCitrix Receiver) for Linux integrated. Our Citrix Receiver Workspace App implementation supports both ICA and HDX, as well as Flash, multimedia and USB redirection, [http://www.stratodeskncomputing.com/solutions/ica-hdx-endpoint hub making a perfect Citrix endpoint solution], without any need for installing software, cryptic configuration files or command line options! NoTouch provides a complete configuration environment for Citrix ReceiverWorkspace App, so it is not necessary to directly work with Citrix' own configuration windows - everything can be configured and managed via the local NoTouch configuration menu as well as centrally with NoTouch Center. The [[Citrix_Workspace_Hub | Citrix Workspace Hub]] also uses Citrix Workspace App.
The This article gives an overview of the different configuration scenarios and later describes Citrix Receiver can be used for connecting to Citrix XenApp, XenDesktop, product-specific configuration steps. We assume that you basically understand [[VDI-in-a-BoxConfigure NoTouch OS|how NoTouch OS is configured]] (successor to the Kaviza product), and all earlier especially how [[Connection|server connections are created and configured]]. The Citrix software such as Presentation Server or MetaFrame. It can be run as a standalone application, run Workspace App for Linux differs in many aspects from the web browserWindows-based Receiver, or "hidden" so that the end user just sees a login dialog not only in terms of look&feel, but also in terms of available features and then the actual server connection. NoTouch also supports StoreFronteven bugs.
This article gives an overview of the different = Citrix configuration scenarios and later describes Citrix product specific configuration steps. We assume that you basically understand [[Configure in NoTouch OS|=The following options are available how NoTouch OS is configured]] and especially how [[Connection|server connections are created and configured]]. The Citrix Receiver for Linux differs in many aspects from to configure the Windows-based Receiver, not only in terms of look&feel, but also in terms of available features and even bugs.system:
== Citrix-based connection modes in NoTouch * Go directly into one published resource, e.g. a fullscreen desktop* Present a choice to users for XenApp multiple available resources, e.g. published applications* Use [[Mozilla_Firefox | Firefox]] or Chromium web browsers and XenDesktop ==log in via browser* Use the "selfservice" GUI to provide a browser-like experience
Yes, == Browser-based login == If you can use the web want to log in via browser. However, we find that many people rather prefer create a more "direct" approach[[Connection | connection]], use either [[Mozilla_Firefox | Firefox]] or Chromium, letting users connect and enter their credentials without going through a web browser. Several different session modes exist point it to facilitate different ways of using your Citrix (note URL. You will notice that you have the "published applicationCitrix Workspace App" can also refer to a full desktop). The most important two are:
* '''Citrix/StoreFront'''. The mode of On most modern PCs a browser is a good choice for using , and NoTouch with StoreFront (NoTouch 2cleans out the environment after the browser is closed.40.188 On older systems or later). It can be used to either run one resources (absolutely seamless to the end user) or show Raspberry Pi you may find a menu where users can choose from - at your option!* '''Citrix/One application or desktop'''. Login to Web frontend (in browser solely for the background!), then run a single published application or desktop. This creates the most seamless experience for end users, they will be taken directly into one specific published resource. This mode is what most people want.* '''Citrix/Program Neighborhood'''. Login to Web frontend (purpose of logging in the background!), and put all available published applications into the local Start Menu, allowing the user to choose from uses too many available resources, though.
Please note that NoTouch OS configures the full == Citrix client for each session. Workspace App ==In most cases a [[Connection | connection]] of type '''Citrix makes Workspace App''' and a different between client and session parameters, whereas NoTouch OS allows to set everything Citrix URL as session-dependent parameter. This gives you more flexibility, but could lead to problems in the rare case when several Citrix sessions with conflicting sessions connection target are supposed to be started at the same time. At the end of the day, it is always the client originating an ICA connection enough to successfully run a terminal server, no matter what session mode you use, what Citrix products you useclient.
One thing not mentioned in "Citrix Workspace App", the list above is the possibility mode of starting a browser choice for using NoTouch with both on the desktop device -premise and have cloud-based Citrix deployments, including Citrix Workspace. It can be used to either run one resource (absolutely seamless to the end user connect via browser; NoTouch OS considers this ) or show a browser session menu where users can choose from - see [[Firefox]].at your option!
== StoreFront connections If you want to XenApp and XenDesktop ==connect to sites using the older PNA protocol or any earlier Citrix products, please visit [[Legacy_Citrix_configuration | Legacy Citrix configuration]].
Note: Before version 2.40.4680 (i.e. end of 2018), the '''Citrix Workspace App''' connection mode was called '''Citrix/StoreFront''' === Creating a StoreFront connection === Setting up a connection to a Citrix StoreFront portal is really easy. Follow these simple steps:
# Create a connection
# Set its <code>Connection Mode</code> parameter to "Citrix Workspace App" (older versions call this "Citrix/StoreFront")
# Set the Citrix StoreFront URL into the <code>Connection Target</code> parameter
#* Use the real StoreFront API URL, typically like /Citrix/Store (as opposed to the user/web browser URL that ends in /StoreWeb)
#* You can also use the <code>Citrix URL</code> parameter of the Citrix options instead of <code>Connection Target</code> - both parameters work equally well
# Make sure the client has access to all necessary [[Certificates]]. StoreFront is SSL-only, it is mandatory to install proper root certificates!
NoTouch will display a chooser if more than one published resources are available (otherwise, if it is only one, it will launch that without further questioning). If you want to go directly into one resource, please read below.
Note: The Citrix Workspace App will display a choice between different stores. That is especially common if going through a NetScaler that bundles multiple stores. To avoid that, you must set up your URLs that it goes to one store. It is really all depending on the URL and the server configuration.
=== Starting directly into a specific application or desktop ===
However, if your use case is different, you can modify the <code>StoreFront stay logged in</code> parameter in the Citrix options. It is 0 by default (=immediate termination), any number of seconds is ok. Thus, if you type in 120, you would give your users two minutes (120 seconds) time to choose another connection out of the chooser window.
== Legacy Citrix product specific information Selfservice==Selfservice is part of Citrix Workspace App. Any connection of type "Citrix/StoreFront" can be simply switched to use selfservice, simply look for the "Use selfservice GUI parameter" and switch it on.
=Common Configuration scenarios=
=== Non-StoreFront XenApp =Desktop Viewer Toolbar== [[Image:OS-en-The Desktop Viewer Toolbar is an overlay menu that allows to quickly end or modify a Citrix-Step1-1session. You can switch it off. Usually system administrators like it, but end users not so much.jpg|right|550px]]
Registering at The Raspberry Pi can display the Citrix Web frontend allows for better load balancing, reconnect and session distributionDesktop Viewer Toolbar only when NOT in H.264 mode. That means, since if you want it on the user authenticates first to the connection brokerRaspberry Pi, and after that starts a connection you have to a specified serverboth disable H. The session modes "Citrix/One application or desktop" 264 and "Citrix/Program Neighborhood" take advantage of this:enable the Desktop Viewer Toolbar.
# Create a connection==Help! It's not fullscreen!==# Set session type to "Connection modes Citrix/One application or desktop" or "and Citrix/Program Neighborhood"# Save changes and then navigate as well as connecting to the "Citrix" parameter subcategory# Set via browser means that the "Citrix URL" parameter to an URL containing actual session specification will be created on the host name/IP address where server. This includes for example the Web frontend window size. It is installed, not possible to modify such as <nowiki>http://mycitrix.mycompany.com/Citrix/PNAgent/config.xml</nowiki>#* Have your Citrix URL always refer to a config.xml if possible. Yes, settings from the client side - you can abbreviate but only if must do it in the paths are standard like <code>/Citrix/PNAgent</code> on the server# If using "Citrix/One application or desktop"management console, write the name of the desired published application into e.g. setting the "Launch Resourcewindow size" parameter # Save changesto Fullscreen.
=== Non-StoreFront XenDesktop =Multimonitor/Dualscreen operation==The Citrix Receiver will take advantage of multiple monitors automatically and it will report screen geometry to the server. Please make sure Multimonitor support works, more information can be found here: Multimonitor operation with NoTouch
[[Image:OS-enTwo parameters influence the dualmonitor/multimonitor behavior -the effects of these parameters are entirely up to Citrix and may change with different versions of the Citrix-Step2-1-1.jpg|right|550px]]client:
XenDesktop also uses *Use screens (span)**Default. This is the ICA/HDX protocol and default. All monitors are available will be used if present.**All. Force using all monitors.**No setting. NoTouch will not set this parameter at all when launching the Citrix Web service, so client.**Custom. The values from the configuration "Custom span parameter" will be taken.*Custom span parameter (only if "Use screens" is similar set to how you would configure XenAppcustom. (Note that there The following excerpt is a special hint for XenDesktop 7 below...)from the Citrix manual:
# Create -span [h[[o][a connection# Set the connection mode to either (according to what you want to use)#* "Citrix/One application or desktop" (start one named desktop)#** In this case|mon1[, please write the name of the desktop to be started into the "Launch Resource" parameter. Observe casem2[, spacesm3, punctuation!#* "Citrix/Program Neighborhood" (get desktops added to local start menu)# m4]]] Set the parameter "Citrix URL" in the Citrix parameter subtree to the URL where the Citrix Webservice residesmonitor spanning of full-screen sessions.
There are a few other hints you should consider (mostly these are fulfilled by Most people will be fine with defaultsettings, but double check):* Workplace-Management has to be set to either none, disconnected or all. This will either reconnect no sessions (none), only disconnected sessions (disconnected) or all kinds of sessions (all).* The authentication method for the webxml service must be set to 'prompt'. 'passthrough' is NOT supported by the Linux Citrix Receiver.* Make sure the device is set to 24 bit colorboth in single-depth and the ICA session is also using 24 bit colorin dual-depthmonitor setups.
==== XenDesktop 7 and higher ====
XenDesktop 7 =HTTPS/SSL and higher certificates=To operate Citrix Receiver properly with HTTPS connections, it must trust your StoreFront site's CA root certificate. In case you have publicly available Citrix URL you will most likely have used a well- by default - only known certification authority (CA) whose certificates are already in the StoreFront interface activesystem's trusted certificate store. This is perfectly fine as On private, internal sites however you can might use a self-signed certificate or one signed by your (private) Microsoft Active Directory Certification Service. In these latter cases, you must make the certification authority'''Citrix/StoreFront''' connection mode s (see aboveCA). Only if you want root certificate available to use NoTouch via the other modes that use configmechanisms defined in documentation on certificates.xml, you need to enable "Legacy Support" according to this screenshot:
[[Image:Other* Citrix does not accept SHA-CitrixXenDesktop7LegacySupport1 certificates.jpg|none|500px]]SHA2 (e.g. SHA256) is required.* If your server certificate was signed by a sub-CA, the server must send the certificate chain or you must supply the intermediate CA certificates. This is a very common problem.* '''Certificates you upload must be named .crt and be in human-readable form (starting with ---- BEGIN CERTIFICATE ---, what is called 'Base64-encoded DER'). If the file you plan to upload is not human-readable, you are using the wrong format'''.* Please avoid having whitespaces and non-ASCII characters in the file name (no accented characters, no umlauts)
=== Non-StoreFront Access Gateway ===The Citrix Receiver for Linux does not have any switch to simply ignore the certificate check. That means you can not just turn the checks off. This is a Citrix policy (or "limitation", depending on your point of view).
Connecting via Citrix Access Gateway is, generally spoken, not different from connecting to a XenApp or XenDesktop. However, there are three things you need to be aware of:* Configuration of Access gateway and Citrix URLs. Please For more information please see http://support.citrix.com/the article/CTX124937 for information on how to make Access Gateway work directly with Citrix Receiver (i.e. NoTouch). * Citrix URLs: When just providing a short URL or even just a host name, NoTouch will add the standard config.xml path for you. People using Access Gateway are much more likely to change paths so the automatic completion won't work, '''you must provide the exact and correct URL to config.xml'''* [[Certificates]]: If you use HTTPS (SSL) with a self-signed/private certificate (and not one from a well-known certificate authority), then you must upload your root CA certificate to NoTouch. The Citrix Receiver does not offer an option to ignore unverifiable certificates nor does it offer to accept and store a private certificate for you (as a web browser does). It must be present before the connection is launched, no matter if you connect via browser or directly with the Citrix Receiver. See here for more information on how to deal with certificates in NoTouch: [[Certificates]]
Furthermore=USB forwarding=By default, you need USB forwarding is switched to on and USB devices will be forwarded to have Access Gateway configured correctly as well: * it must allow the connection from wherever you are connecting server automatically. So called HIDs (IP/network rangehuman interface devices, such as keyboards, mice, but also mouse-emulating devices like digital dictation foot pedals)* it must allow the connection from the user account will not be forwarded, but rather handled locally and the user account must be allowed brought to connect from this network* it must allow the connection from a non-Windows machine VDI desktop as keystrokes and non-domain member* make sure that there are no redirects that only work "inside", no private IP addresses are usedmouse movements.
The following article may There are two parameters, both need to be helpful as well: http://www.jasonsamuel.com/2012/04/10/how-enabled for USB forwarding to-setup-your-citrix-netscaler-access-gateway-and-web-interface-for-ipads-and-mobile-devices-work (yes, the default is that-use-citrix-receiver/both are on):
Note that if it works from another client, notably a Windows PC, this doesn* "'t mean your Access Gateway is configured correctly. Especially when testing from inside your network with external URLs, you may experience a perfectly working scenario, and from outside it doesn't work. You might find out that your system would redirect to internal IP addresses or find similar error causes'Citrix USB forwarder'''" in the "Services" section* "'''Generic USB forwarding'''" in the ICA parameters section of the actual connection.
=== Non-StoreFront NetScaler ===The Citrix USB forwarder is a system service, thus it can be configured from the "Services" parameters, not the Citrix ICA connection parameters. The startup behavior is controlled by the parameter named "'''Citrix USB forwarder'''" parameter. It has these options:
Similar to what * "with Citrix connection". This is said above about NetScaler, in general, the default. Start the Citrix USB forwarder only if there is no difference between connecting with or without NetScalera Citrix connection configured. However, there are three things you need to be aware of:* Configuration of NetScaler and PNAgent service"off". Please see http://support.citrix.com/article/CTX133771 for information on how to configure PNAgent service (config.xml) on NetScaler. * Do not start the Citrix URLs: When just providing a short URL or even just a host name, NoTouch will add the standard configUSB forwarder.xml path for you. People using NetScaler are much more likely to change paths so the automatic completion won't work, '''you must provide the exact and correct URL to config.xml'''* [[Certificates]]: If you use HTTPS (SSL) with a self-signed/private certificate (and not one from a well-known certificate authority), then you must upload your root CA certificate to NoTouch"on". The Citrix Receiver does not offer an option to ignore unverifiable certificates nor does it offer to accept and store a private certificate for you (as a web browser does). It must be present before the connection is launched, no matter if you connect via browser or directly with Start the Citrix ReceiverUSB forwarder after system boot. See here for more information on how to deal with certificates in NoTouch: [[Certificates]]
The following article may be helpful as well: http:Futhermore, you can allow or deny specific devices by using the "'''Allow devices'''" and "'''Deny devices'''" parameters in the "Services"//www"Citrix USB" parameters.jasonsamuelThese parameters directly modify Citrix' usb.com/2012/04/10/how-conf file and thus accept the original Citrix syntax only [1]. Multiple stanzas, each one describing one device, stanzas separated by commas, can be added to-setup-your-citrix-netscaler-access-gateway-and-web-interface-for-ipads-and-mobile-devices-either of these parameters. A stanza consists of tags that-use-citrix-receiver/in turn have the form TAG=VALUE. Acceptable tags are:
Note that if it works * '''VID''' Vendor ID from another client, notably a Windows PC, this doesnthe device descriptor* '''REL'''t mean your NetScaler is configured correctly. Especially when testing Release ID from inside your network with external URLs, you may experience a perfectly working scenario, and the device descriptor* '''PID''' Product ID from outside it doesnthe device descriptor* 't work. You might find out that your system would redirect to internal IP addresses ''Class''' Class from either the device descriptor or an interface descriptor* '''SubClass''' SubClass from either the device descriptor or an interface descriptor* '''Prot''' Protocol from either the device descriptor or find similar error causes.an interface descriptor
=== Legacy VDI-in-a-Box ===Valid examples for either of the two parameters are:
VDI-in-a-Box has been discontinued by Citrix long ago and as such NoTouch support for has been end-of-life'd as well. This information is provided as a courtesy only.For VDI-in-a-Box connections you would also use the Citrix Receiver as described here in the article - use the "Citrix/One application or desktop" connection mode. The only notable difference is that the URL to config.xml looks a little bit different - please check the dedicated article about VDI-in-a-Box connections: [[VDI-in-a-Box]] * VID=1460 PID=0008* Class= Legacy systems - Presentation Server, MetaFrame ==07 SubClass=06
There are three more "direct" Citrix modes that were used with earlier Citrix products such as MetaFrame and Presentation Server. Most people use either The Information page of the local configuration application will present information about USB devices to you - this is the place how you can find out the web browser VID or PID, for instance. Command line afficionados will prefer the XenApp/XenDesktop modes (see above)lsusb command, preferably in lsusb -v form.
* '''Legacy Citrix/ICA connect'''. Run a single ICA session to a host or published application. This was Please see the main mode for original Citrix terminal servers before XenApp/XenDesktop, mainly in Presentation Server deployments. Nowadays most people go documentation for the other modes below:* '''Legacy Citrix/Built-in PNAgent view'''more information [2]. Login Changes to Web frontend (in the background!), then run what Citrix calls "PNAgent view on Linux" - these parameters need a window showing icons for different published applications. The pnagent mode uses Citrix receiver's own GUI which is not as beautiful as it could be. We suggest reboot to use Citrix/One application or desktop or Citrix/Program Neighborhood. * '''Legacy Citrix/ICA configurator'''. Run the Citrix configuration dialog (basically the wfcmgr binary, if you are familiar with the Citrix Receiver for Linux). This is somehow what one would see when running ICA client on any normal Linux. We discourage from using this, as ordinary end users will find this too complicated and are usually much better off with Citrix/One application or desktop or Citrix/Program Neighborhoodbecome active.
The availability of these modes =Browser Content Redirection (BCR)=Browser Content Redirection (BCR) is also depending on a Citrix feature to use the used Citrix local, client versionCPU to render certain webpages instead of the VDA side. RXIn other words, instead of the VDA side rendering the whole page, a Workspace-HDX thin client comes with Citrix client 13.x App-side rendering engine will be started and instructed to fetch the web content from the URL, render it locally and above which only allows draw it into the browser window "Legacy over" the rest of the Citrix/ICA connect"session.
To make On the simplest ICA connection possibleNoTouch side, just follow these steps (in NoTouch OS or NoTouch Center):# Create a connection# Set session type BCR needs to be switched on with the "Legacy Browser Content Redirection" parameter under the Citrix/ICA connectoptions - set it to "# Set on"Connection target" to . On the host name of a Citrix-enabled terminal server (=XenApp server)# Save changesside, you'll have to deal with
== Web *certain Citrix policies,*browser ==plugin installation,*URL whitelisting (only whitelisted URLs will be redirected).
You More information can use the local builtbe found here: [https://docs.citrix.com/en-in Web us/citrix-virtual-apps-desktops/multimedia/browser -content-redirection.html Browser Content Redirection] and [[Firefox]] to connect to Citrix servershttps://support. In this case simply add a "browser" connectioncitrix. Your users can surf to the Citrix Web fronted, log in, and start the applicationscom/article/CTX230052 Troubleshoot Browser Content Redirection].
In this scenarioNeedless to say, make sure the server does not try to use the Java client - all required components for BCR are part of NComputing NoTouch OS has the native client built in and is advertising it . You do not need to the serverworry about installing GStreamer, WebKitGtk+, so don't bother with downloading the Java clientCEF etc.
Note: In order to take advantage of all features such as drive mappingTo use BCR with multimedia content on the EX400 (x64) thin client, you may have to execute Firefox with "root" permissionswill need the Fluendo codec pack. As of WSA 19. To do so06, please go to the Connection options, Extended, and enable Citrix can not simply work with "Force execution as rootonly free codecs". Please read through the [[Firefox]] article to understand See below for a more detailed explanation on the implicationscodec question.
== Help! It's not fullscreen! Codes==A codec in this context is a program to playback a certain kind of video or audio stream. NComputing NoTouch OS only includes codecs that are free from any patent license fees. We understand many people don't care but we do. If you download any kind of desktop Linux and then additionally install these patented codecs such as AAC or H.264, you are at risk of being sued, at least in a commercial environment. That said, please don't report bugs to NComputing that sound like "It works on Ubuntu, I just installed all these codecs...". The proper way is to purchase the Fluendo codecs, which are high-performing and properly licensed codecs on Linux. This codec is relatively inexpensive and gives you legal safety as well as the highest performance. Note: This only applies to software. If your system has hardware decoders and the drivers can make use of them, the royalties are already being paid for by the HW manufacturer.
Connection modes Citrix/One application or desktop Typical free codecs are VP8, VP9, AV1, Theora (video), and Citrix/Program Neighborhood as well as connecting to Citrix via browser means that the actual session specification will be created on the serverOpus, FLAC, MP3 (audio). This includes for example Yes, MP3 is now patent-free since the window sizelast patent expired in mid-2017. It is not possible to modify such settings from the client side Typical codecs that require licensing are AAC (audio), MPEG- you must do it in the Citrix management console2, eH.g264, and HEVC/H. setting the "window size" to Fullscreen265, again, unless your hardware has such codecs built-in.
== Multimonitor/Dualscreen operation RX-HDX (based on Raspberry Pi platform)==Browser Content Redirection on the Raspberry Pi 3 does work in principle but is unsupported by NComputing as there are a few caveats. The Pi implementation, as of mid-2019, uses CEF (Chrome Extension Framework) as opposed to WebkitGtk+ which is actually the more modern approach. However,
The software is still very early and may not work in all circumstances (please direct support questions to Citrix Receiver will take advantage of [[Multimonitor|multiple monitors]] automatically and it will report )It does not work conceptually with a full-screen geometry to the serverH. Please make sure Multimonitor support works264 encoded session, more information can be found here: [[Multimonitor|Multimonitor operation obviouslyIt will degrade performance because the Pi 3's CPU is not made for rendering complete web pagesThe Raspberry Pi 4 with NoTouch]]its improved CPU power changes the game - As the Raspberry Pi 4 emerges, both Citrix and NComputing are working together on next-generation BCR capabilities.
Two parameters influence the dualmonitor/multimonitor behavior - the effects of these parameters are entirely up to Citrix = HDX and may change with different versions of the Citrix client:* Use screens (span)** Default. This is the default. All monitors are available will be used if present.** All. Force using all monitors.** No setting. NoTouch will not set this parameter at all when launching the Citrix client.Multimedia support = ** Custom. The values from From within the "Custom span parameterHDX/Multimedia" will be taken. * Custom span parameter section (only if a subsection of Citrix "Use screensICA" is set to custom. The following excerpt is from the Citrix manual: -span [h[[o][a|mon1[parameters),m2[,m3,m4]]] Set monitor spanning several aspects of multimedia support of full-screen sessionsthe ICA/HDX protocol can be configured.
Most people will be fine with default settings, both in single- and in dual-monitor setups.===HDX MediaStream Flash Redirection===
== HTTPS/SSL Flash redirection is enabled by default. Please note that the list of software requirements on the server side is long and certificates ==the list of supported software modules such as browsers is very short. You may have to adapt your VDI environment to meet Citrix requirements.
If you use private certificates, you must add your own certificate - please refer to the [[Certificates|documentation on certificates]]. Notes:
The * You can use your own version of Flash. Sometimes this is necessary because NoTouch is shipped with newer Flash, but Citrix Receiver for Linux does not have any switch support the new Flash and instead requires an older Flash. Please look at this article for instructions on how to simply ignore install your own version of Flash: Mozilla Firefox#Updating the certificate checkFlash Player plugin* Taking that one step further, it is even possible to have a separate, different version of Flash installed just for Citrix purposes. That means This solves the problem that arises when you can not just turn want the checks offlatest Flash in Firefox, but an older, Citrix-approved plugin for Citrix redirection. This is a To install your own version of Flash specifically for use with Citrix Flash redirection, look for the "Extension"->"Citrix limitationFlash player URL" parameter, otherwise follow the instructions given above.
== USB forwarding ==While for some time Citrix has required Flash version numbers to match on client and server, this is not required any more. In fact, the opposite is now true - Citrix suggests to disable the Flash version number check, as stated below and here: http://support.citrix.com/article/CTX134786
By defaultYou should disable the Flash version check by adding/modifying Windows Registry Key on VDA, USB forwarding named “FlashPlayerVersionComparisonMask” which is switched to on and USB devices will be forwarded to the server automatically. So called HIDs (human interface devices, such as keyboards, mice, but also mouse-emulating devices like digital dictation foot pedals) will not a dword that should be forwarded, but rather handled locally and brought set to the VDI desktop as keystrokes and mouse movementszero.
There are two parameters, both This will need to be enabled for USB forwarding to work (yes, the default is that both are set on)each VDA:* "'''Citrix USB forwarder'''" in the "Services" section* "'''Generic USB forwarding'''" in the ICA parameters section of the actual connection.
The Citrix USB forwarder is a system service, thus it can be configured from the "Services" parameters, not the Citrix ICA connection parameters. The startup behavior is controlled by the parameter named "'''Citrix USB forwarder'''" parameter. It has these options* 32 bit OS:* "with Citrix connection". This is the default. Start the HKLM\\Software\\Citrix USB forwarder only if there is a Citrix connection configured.\\HdxMediaStreamForFlash\\Server\\PseudoServer* "off". Do not start the Citrix USB forwarder.* "on". Start the 64 bit OS: HKLM\\Software\\Wow6432Node\\Citrix USB forwarder after system boot.\\HdxMediaStreamForFlash\\Server\\PseudoServer
Futhermore, you can allow or deny specific devices by using the "'''Allow devices'''" and "'''Deny devices'''" parameters in the "Services"/"Citrix USB" parameters. These parameters directly modify Citrix' usb.conf file and thus accept the original Citrix syntax only [http://support.citrix.com/proddocs/topic/receiver-linux-13-0/linux-usb-remoting.html]. Multiple stanzas, each one describing one device, stanzas separated by commas, can be added to either of After making these parameters. A stanza consists of tags that in turn have the form TAG=VALUE. Acceptable tags are:* VID Vendor ID from the device descriptor* REL Release ID from the device descriptor* PID Product ID from the device descriptor*Class Class from either the device descriptor or an interface descriptor* SubClass SubClass from either the device descriptor or an interface descriptor* Prot Protocol from either the device descriptor or an interface descriptor Valid examples for either of the two parameters are:* VID=1460 PID=0008* Class=07 SubClass=06 The Information page of the local configuration application will present information about USB devices to modifications you - this is the place how you can find out the VID or PID, for instance. Command line afficionados will prefer the lsusb command, preferably in lsusb -v form. Please see the original Citrix documentation for more information [http://support.citrix.com/proddocs/topic/receiver-linux-13-0/linux-usb-remoting.html]. Changes to these parameters need a reboot to become active. == HDX and Multimedia support == From within the "HDX/Multimedia" parameter section (a subsection of Citrix "ICA" parameters), several aspects of multimedia support of the ICA/HDX protocol can be configuredrestart IE on VDA. === HDX RealTime Webcam Video Compression ===
===HDX RealTime Webcam Video Compression===
HDX RealTime Webcam Video Compression needs audio input to be enabled both on client and server to work. NoTouch typically has audio input ("microphone in") disabled by default, so you have to turn this on. Besides that, no extra switch is necessary to enable HDX RealTime Webcam Video Compression, but there's still an extra switch to force the redirection, "HDX RealTime webcam video compression".
=== HDX RealTime Media Engine (RTME) ===
The Citrix HDX RealTime Media Engine (RTME) is the client-side component of the Citrix HDX RealTime Optimization Pack for Skype for Business. To enable Skype for Business experience, both client side and server side need to be properly configured.
On the client side, the both [https://www.ncomputing.com/products/RX-series/RX-HDX RX-HDX ] and [https://www.ncomputing.com/products/EX-series/EX400 EX400] thin client comes clients come with RTME integration (firmware version 2.40.2675 and above). By default, the HDX RealTime Media Engine is disabled and must be enabled for the Citrix connection to optimize the Skype for Business experience. This can be done in Connection -> Citrix -> HDX/Multimedia settings by setting the “HDX Realtime Media Engine (Skype for Business)” parameter to “on” (see screenshot below).
<br>
[[image:RTME local.png|border|800px700px]]
<br>
<br>
[[image:HDX connector.png|border|800px700px]]
<br>
Once the HDX RealTime Optimization Pack is setup, the audio and video devices connected to the RX-HDX thin client are enumerated locally by RTME (i.e. not redirected from the client to the VDA). The Audio and video settings can be modified directly from Skype for Business setting menu.
<br>
<br>
=== HDX 3D Pro GPU/H.264 acceleration ===
HDX 3D Pro GPU/H.264 acceleration is enabled by default. Switch it off by setting the "HDX 3D Pro GPU/H.264 acceleration" parameter to off.
http://support.citrix.com/article/CTX131501
== Printing == Printing works fine with Citrix in NoTouch. Please consult our [[Printer configuration]] page. HDX Mediastream Windows Media Redirection== Expired passwords == The Citrix Receiver for Linux has a feature to allow users to enter a new password should theirs have expired. This has to be done before actually logging inNoTouch includes GStreamer, so it requires a special mechanism. Again, this functionality provided as required by the Citrix Receiver, it just needs to be configured properly - set these two parameter in the Citrix parameters correctly:* '''Kerberos KDC Server (Domain Controller Name)'''. This needs to be a DNS host name or IP address of the Domain Controller. Please make sure the name is resolvable by DNS (i.e. not just a support Mediastream Windows/WINS name) - a simply test is to ping the name from the Console of a NoTouch system or any other non-Windows system such as a Mac.* '''Kerberos KDC Realm (Domain Name)'''. Set this to the domain name of your AD domain. Keep in mind that NoTouch systems are not members of the AD domain - this is the reason why you have to supply to these parameters to NoTouch, which in turn passes them on directly to the Citrix ReceiverMedia Redirection [4].
== Smartcard support Printing==Printing works fine with Citrix in NoTouch. Please consult our [[Printer_configuration|Printer configuration]] page.
=Smartcard support=
Citrix can forward smartcard readers and use these for login purposes. U.S. Federal customers will enjoy the CAC card support. In that case, do not forward the smartcard reader with generic USB forwarding. Configure smartcard support according to these instructions:
# Switch on the "Smartcard service (PCSCD)" in the "Services" options
#* In most cases the default settings for the Smartcard driver parameter will be fine. Some readers need the Omnikey setting, not only Omnikey readers. You may have to experiment with that or contact support.
# Set the "Smartcard login" parameter in the Citrix parameters to "on"
Note: For XenDesktop, do not attempt to use the generic USB forwarding mechanism to forward the smartcard reader (it won't be default, you would have to play with the settings). The downside is that then you can't use the reader for login purpose. It would work to forward a reader into the session only (ie without login) if that is what you want.
== Advanced configuration == NoTouch comes with reasonable default values and should accomodate all Citrix options that are used by 99% of the people. However sometimes even deeper configuration accesses are necessary. NoTouch comes with an easy-to-use method of modifying Citrix INI files: [[Citrix Receiver configuration files]]
Furthermore, you can totally rewrite the files that are used to generate the Citrix configuration, which would work by the [[Templates|template mechanism]].
== Selecting the Citrix Receiver version == Most NoTouch images have at least two Citrix Receiver versions included. Yes, you read that correctly, two different versions of the Citrix product, so you can select the one that fits your use case better. By default, the newer client will be used. At the time of writing, this is the 13.7 4 Receiver is the latest Citrix for Linux receiver incorporated in and the RX-HDX thin clientalternative, older Receiver is 12.1.
To switch to an alternative version of the Citrix Receiver, use the "Client version (if present)" parameter in the Citrix options. You may have to scroll down a bit to find it, it is pretty far down below.
== Proxy settings ==The Citrix Receiver can connect via a proxy server. While these parameter may seem obvious, it is important to note that from OS 2.40.1310 on the Citrix Receiver will inherit the Firefox proxy settings of the same connection, if you switch the "Use Firefox proxy settings" parameter to on. This will inherit exactly your NoTouch settings that you made in the "Firefox" parameters.
The Citrix Receiver Certainly you can connect via a configure the proxy server. While these parameter may seem obvious, it is important settings directly and even specify to note that inherit from OS 2.40.1310 on the Citrix Receiver will inherit the [[Mozilla Firefox#Proxy settings|Firefox proxy settings]] of the same connection, if you switch the "Use Firefox system-level proxy settings" parameter to on. This will inherit exactly your NoTouch settings that you made in Here are the "Firefox" parameters. in more detail:
Certainly you can configure the proxy settings directly and even specify to inherit from the [[Network#Proxy settings|system-level proxy settings]]. Here are the parameters in more detail:
* '''Use Firefox proxy settings'''. If set to on, all parameters below will be ignored and the Firefox configuration parameters of the same connection will be evaluated.
* '''Proxy type'''. Master switch denoting the kind of proxy configuration used:
** No setting. Do not mention anything about proxy in the Citrix configuration files.
** None. No proxy is to be used.
** System settings. The [[Network#Proxy settings|system-level proxy settings]] will be used.
** Auto config (Script). The system will download a .pac file from the "Proxy autoconfig URL" and evaluate it.
** Secure Host. Think of this as the "manual configuration". The system will use the "Proxy hostname" parameter and the "proxy bypass list". ** SOCKS. Uses the "proxy hostname" as a SOCKS proxy.
* '''Proxy hostname'''. Hostname:port combination of the proxy server to be used. It must be configured to accept HTTPS traffic.
* '''Proxy bypass list'''. A comma-separated list of hostnames and IP addresses that Receiver will always contact directly.
* '''Fallback to direct if no autoconfig received'''. In case the autoconfig URL (see above) can not be reached, Receiver will connect directly. This can be useful if people are traveling.
== Citrix considerations == Citrix has a lot of options, some combinations may have strange effects. Most people are fine with the defaults, in fact , NComputing recommends to change something only when a) necessary and b) advised to do so. NComputing Stratodesk can not provide support for Citrix installation, be sure to have a Citrix professional at hand when troubleshooting.
More detailed information can be found in [http://docs.citrix.com/en-us/receiver/linux/13-4.html Citrix Receiver for Linux 13.4 eDocs] - you can skip the part about installation and integration, since this is already done in NoTouch.
Also please check out the [https://www.citrix.com/content/dam/citrix/en_us/documents/products-solutions/citrix-receiver-feature-matrix.pdf Citrix Receiver Feature Matrix].
In case something does not work as expected, always open a Citrix support case before contacting NComputing.
In case something does not work as expected, always open a Citrix support case before contacting NComputing.
[[Category:Server connections]] [[Category:NoTouch OS]]