Looking for:
Citrix workspace app icon
Citrix workspace app icon.Install and Uninstall
Devices, such as webcams, digital camcorders, analog video converters, some television tuners, and some digital cameras that support video streaming. Most video streaming devices use isochronous transfers that XenDesktop 4 or later supports. Some video devices for example webcams with motion detection require additional configuration. Personal Healthcare Class 0f - These devices include personal healthcare devices such as blood pressure sensors, heart rate monitors, pedometers, pill monitors, and spirometry.
Application and Vendor Specific Classes fe and ff - Many devices use vendor-specific protocols or protocols not standardized by the USB consortium, and such devices usually appear as vendor-specific class ff. Human Interface Devices Class Includes a wide variety of both input and output devices. Typical Human Interface Devices HIDs are keyboards, mice, pointing devices, graphic tablets, sensors, game controllers, buttons, and control functions. The reason is most keyboards and mice are handled appropriately without USB support.
Also, it is normally necessary to use these devices locally as well remotely when you connect to a virtual desktop. USB Hubs Class USB hubs allow extra devices to be connected to the local computer.
It is not necessary to access these devices remotely. Smart Card Class 0b. Smart card readers include contactless and contact smart card readers, and also USB tokens with an embedded smart card-equivalent chip. Wireless Controller Class e0. Some of these devices might be providing critical network access, or connecting critical peripherals, such as Bluetooth keyboards or mice.
The default USB policy does not allow these devices. However, there might be particular devices to which it is appropriate to provide access using USB support. Miscellaneous network devices Class ef, subclass 04 - Some of these devices might be providing critical network access. Edit the Citrix Workspace for Windows template file to update the range of USB devices available for remoting to desktops. The file is in the following installed folder:.
Editing the Registry incorrectly can cause serious problems that might require you to reinstall your operating system. USB 2. Such devices employ a single configuration space and shared bus connection where a unique interface number ff is used to identify each child device. When a composite USB device is forwarded, the entire device becomes unavailable to the endpoint. Forwarding also blocks the local usage of the device for all applications on the endpoint, including the Citrix Workspace client needed for an optimized HDX remote experience.
If the entire device is forwarded using a generic USB channel, the device becomes unavailable for redirection over the optimized HDX audio channel. However, you can achieve best experience when the audio is sent through the optimized HDX audio channel unlike the audio sent using host-side audio drivers through generic USB remoting. The behavior is because of the noisy nature of the USB audio protocols. You also notice issues when the system keyboard or pointing device are part of a composite device with other integrated features required for the remote session support.
When a complete composite device is forwarded, the system keyboard or mouse becomes inoperable at the endpoint, except within the remote desktop session or application. To resolve these issues, Citrix recommends that you split the composite device and forward only the child interfaces that use a generic USB channel. Such mechanism ensures that the other child devices are available for use by applications on the client endpoint, including, the Citrix Workspace app that provides optimized HDX experiences, while allowing only the required devices to be forwarded and available to the remote session.
As with regular USB devices, device rules set in the policy or client Citrix Workspace app configuration on the end point select the composite devices for forwarding. Citrix Workspace app uses these rules to decide which USB devices to allow or prevent from forwarding to the remote session. Each rule consists of an action keyword Allow, Connect, or Deny , a colon : , and zero or more filter parameters that match actual devices at the endpoints USB subsystem.
Device rules are clear text with each rule on a single line and an optional comment after a character. Rules are matched top down descending priority order. The first rule that matches the device or child interface is applied. Subsequent rules that select the same device or interface are ignored. The first six parameters select the USB devices for which the rule must be applied. If any parameter is not specified, the rule matches a device with ANY value for that parameter.
You can check the vendor, product, release, and interface IDs of a specific device directly in the Windows device manager or using a free tool like UsbTreeView. When present, the last two parameters apply only to USB composite devices. The split parameter determines if a composite device must be forwarded as split devices or as a single composite device.
The intf parameter selects the specific child interfaces of the composite device to which the action must be applied. If omitted, the action applies to all interfaces of the composite device. Citrix Workspace app for Windows includes a set of default device rules that filters certain undesirable classes of devices and allow one that customers often encounter. Citrix recommends preserving the default rules shipped with the client when creating this policy by copying the original rules and inserting new rules to alter the behavior as desired.
You can change the preferences in the Desktop viewer toolbar as shown in the following image. The two check boxes at the bottom of the pane controls if the devices must connect automatically or wait for manual connection in the session. These settings are not enabled by default.
You can change the preferences if generic USB devices must be connected automatically. Alternatively, an administrator can override the user preferences by deploying the corresponding policies from Citrix Workspace app Group Policy Object administrative template. Citrix recommends using explicit device rules to identify specific devices or interfaces that need to be split instead of changing the default. This setting will be deprecated in a future release. Citrix recommends that you do not split interfaces for a webcam.
As a workaround, redirect the device to a single device using Generic USB redirection. For a better performance, use the optimized virtual channel. Citrix Workspace app supports the use of Bloomberg keyboard in a virtual apps and desktops session. The required components are installed with the plug-in. You can enable the Bloomberg keyboard feature when installing Citrix Workspace app for Windows or by using the Registry editor.
Bloomberg keyboards provide other functionality when compared to standard keyboards, that allows the user to access financial market data and perform trades. In addition to the normal functionality of these devices, the audio device includes support for some keys, control of the keyboard, and keyboard LEDs.
To use the specialized functionality inside a session, you must redirect the audio device as a USB device. This redirect makes the audio device available to the session, but prevents the audio device from being used locally.
In addition, the specialized functionality can only be used with one session and cannot be shared between multiple sessions. Multiple sessions with Bloomberg keyboards are not recommended. The keyboard operates in a single-session environment only. You must configure various interfaces of the Bloomberg keyboard. New lines or semicolon can be used to separate rules which allows to read either single line or multi-line registry values. This procedure makes the Bloomberg keyboard 5 ready for use.
The DENY rules that are mentioned in the steps enforce the redirection of the primary keyboard and audio channel over an optimized channel but not over Generic USB. The CONNECT rules enable automatic redirection of the fingerprint module, special keys on the keyboard, and keys related to audio control. Citrix cannot guarantee that problems resulting from the incorrect use of the Registry editor can be solved. Use the Registry editor at your own risk.
Bloomberg keyboard 3 support is available in the online plug-in If the value is 1, support is enabled. Citrix Receiver for Windows 4. However, you must use the Bloomberg keyboard feature instead of this policy for the Bloomberg keyboard 4. The support for the Bloomberg keyboard changes the way certain USB devices are redirected to a session.
This support is not enabled by default. To enable support after installing the online plug-in, edit the Windows Registry on the system where the online plug-in is running:. For Bloomberg 3, a single session or the local system can use the fingerprint reader, and cannot be shared. Bloomberg 4 is prohibited for redirection.
If you enable support for Bloomberg keyboards in the online plug-in, you have the benefit of sharing the specialized keyboard functionality with multiple sessions.
You also experience less network bandwidth from the audio. Enabling support for the Bloomberg keyboard prevents the redirection of the Bloomberg Keyboard audio device. Instead, a new device is made available. Redirecting this device provides the specialized Bloomberg keys to the session. Enabling the Bloomberg keyboard support only affects the specialized Bloomberg keys and the audio device.
Because the ordinary keys and fingerprint reader are used in the same way as when the support is not enabled. The media device includes cameras, scanners, media players, and point of sale POS devices.
You or the user can restrict the redirection of all or some of the devices. Edit policies on the server or apply group policies on the user device to configure the redirection settings.
A user can set permissions in Citrix Workspace app to allow or reject device redirection always or notify each time a device is connected. The setting affects only devices plugged in after the user changes the setting. These mappings can be used like any other network mappings. You can map client COM ports at the command prompt. For information about policies, see the Citrix Virtual Apps and Desktops documentation. To use this COM port in a virtual desktop or application, install your user device to the mapped name.
For mass storage devices only, in addition to USB support, remote access is available through client drive mapping. When you apply this policy, the drives on the user device automatically map to drive letters on the virtual desktop when users log on.
The drives are displayed as shared folders with mapped drive letters. If you enable both Generic USB and the client drive-mapping policies and insert a mass storage device before a session starts, it is redirected using client drive mapping first, before being considered for redirection through USB support.
If it is inserted after a session has started, it will be considered for redirection using USB support before client drive mapping. Client drive mapping supports the transfer of data between the host and the client as a stream. The file transfer adapts to the changing network throughput conditions.
It also uses any available extra bandwidth to scale up the data transfer rate. Users can:. By default, client drives are mapped to server drive letters and server print queues are created for client printers, which make them appear to be directly connected to the session. These mappings are available only for the current user during the current session.
You can use the redirection policy settings to map user devices not automatically mapped at logon. For more information, see the Citrix Virtual Apps and Desktops documentation. You can configure user device-mapping including options for drives, printers, and ports, using the Windows Server Manager tool. For more information about the available options, see your Remote Desktop Services documentation.
Client folder redirection changes the way client-side files are accessible on the host-side session. Enabling only client drive mapping on the server, client-side full volumes automatically maps to the sessions as Universal Naming Convention UNC links. When you enable client folder redirection on the server and the user configures it on the user device, part of the user specified local volume gets redirected.
Only the user-specified folders appear as UNC links inside the sessions, instead of the complete file system on the user device. If you disable UNC links through the registry, client folders appear as mapped drives inside the session. For more information, including how to configure client folder redirection for user devices, see the Citrix Virtual Apps and Desktops documentation.
Client drive mapping redirects drive letters on the host-side to drives that exist on the user device. For example, drive H in a Citrix user session can be mapped to drive C of the user device running Citrix Workspace app for Windows.
Client drive mapping is built into the standard Citrix device redirection facilities transparently. To File Manager, Windows Explorer, and your applications, these mappings appear like any other network mappings.
The server hosting virtual desktops and applications can be configured during installation to map client drives automatically to a given set of drive letters. The default installation maps drive letters assigned to client drives starting with V and works backward, assigning a drive letter to each fixed drive and CD-ROM drive. Floppy drives are assigned their existing drive letters. This method yields the following drive mappings in a session:.
So, the server drive letters are changed to higher drive letters. In the following example, changing server drives C to M and D to N allows client devices to access their C and D drives directly. The drive letter used to replace the server drive C is defined during Setup. These drive letters must not conflict with any existing network drive mappings. Connecting a user device to a server, reestablishes client mappings unless automatic client device mapping is disabled.
Client drive mapping is enabled by default. You can also use policies to give you more control over how client device mapping is applied. For more information about policies, see the Citrix Virtual Apps and Desktops documentation.
Starting with Version 4. When you launch the application, Citrix Workspace app reads the resource data present on the StoreFront server and applies the settings based on the vprefer flag at the time of enumeration. If present, launches the local instance of the application.
Otherwise, a hosted instance of the application is launched. If you launch an application that is not on the VDA, Citrix Workspace app launches the hosted application.
For more information on how StoreFront handled the local launch, see Control of local application launch on published desktops in the Citrix Virtual Apps and Desktops documentation. This feature helps to launch applications faster, thereby providing a better user experience. By default, vPrefer is enabled only in a double-hop scenario.
When you upgrade or install Citrix Workspace app for the first time, add the latest template files to the local GPO. For an upgrade, the existing settings are retained while importing the latest files. Citrix Workspace app for Windows supports configuring Workspace for subscribers, who might be using one or more services available from Citrix Cloud.
Citrix Workspace app intelligently displays only the specific workspace resources to which users are entitled. All your digital workspace resources available in Citrix Workspace app are powered by the Citrix Cloud Workspace experience service. A workspace is part of a digital workspace solution that enables IT to securely deliver access to apps from any device.
This screenshot is an example of what the workspace experience looks like to your subscribers. This interface is evolving and might look different to what your subscribers are working with today. Citrix Content Collaboration enables you to easily and securely exchange documents, send large documents by email, securely handle document transfers to third parties, and access a collaboration space.
Citrix Content Collaboration provides many ways to work, including a web-based interface, mobile clients, desktop apps, and integration with Microsoft Outlook and Gmail. You can view the Files tab only if Content Collaboration Service is enabled in the Workspace configuration from the Citrix Cloud console. The following image displays example contents of the Files tab of the new Citrix Workspace app:. Secure access to SaaS applications provides a unified user experience that delivers published SaaS applications to the users.
SaaS apps are available with single sign-on. Administrators can achieve this by filtering access to specific websites and website categories.
Users get seamless and secure access to all the apps that they need to stay productive, including features such as embedded browsing and single sign-on. With this integration, all your data is accessible within Citrix Workspace app. The ability to upload and download files and even open files within Citrix Workspace app are now integrated into one application. Citrix Workspace app is enhanced to deliver more capabilities regarding data loss prevention, secure access to SaaS apps, secure internet browsing capabilities, advanced search, and more.
For information about the features available in Citrix Workspace app, see Citrix Workspace app feature matrix. The Citrix Workspace apps are adapted for use in languages other than English. This section lists the supported languages in the latest release of Citrix Workspace apps. The following table lists the languages supported for the Citrix Workspace app on various operating systems or platforms.
An X indicates that the app is available in that particular language. This article discusses feature flag management and the various Citrix Workspace apps that support feature flags.
If an issue occurs with Citrix Workspace app in production, we can disable an affected feature dynamically in Citrix Workspace app even after the feature is shipped. To do so, we use feature flags and a third-party service called LaunchDarkly. You do not need to make any configurations to enable traffic to LaunchDarkly, except when you have a firewall or proxy blocking outbound traffic. The following table calls out the various apps that support feature flags and the release versions in which feature flags were introduced in these apps.
While you can still download older versions of Citrix Receiver, new features and enhancements are released for Citrix Workspace app. Configure the Client Choices page. Configure access scenario fallback. Configure connections for the Citrix Secure Access agent.
Configure the number of user sessions. Configure time-out settings. Connect to internal network resources. Configure split tunneling. Configure client interception. Configure name service resolution. Enable proxy support for user connections. Configure address pools. Support for VoIP phones. Configuring application access for the Citrix Secure Access agent for Java. Configure Access Interface. Configure SmartAccess. Traffic policies. Session policies. Configure Citrix Gateway session policies for StoreFront.
To install the Citrix Workspace app using the Windows command line, launch the command prompt and type the following on a single line:. Use this switch in the following scenarios:. For more information, see Deprecation. If you have enabled auto-update, you can choose the version you want to update. See Lifecycle Milestones for more information.
Indicates the number of times that you can defer notifications when an update is available. For more information, see Citrix Workspace Updates. When a new version of the app is available, Citrix rolls out the update for a specific delivery period. With this parameter, you can control at what time during the delivery period you can receive the update.
Start App Protection component and provides enhanced security by restricting the ability of clients to be compromised by keylogging and screen-capturing malware. See App Protection for more information. Excludes the Citrix Embedded Browser binaries. If your version of Citrix Workspace app includes the Citrix Embedded Browser binaries and you are upgrading to Version , the embedded browser binaries are automatically updated during the upgrade.
Specifies the custom installation directory for Citrix Workspace app installation. Example, CitrixWorkspaceApp. When you update Citrix Workspace app, the Citrix Casting gets updated automatically. For more information on Citrix Casting, see Citrix Casting. Indicates if bidirectional content redirection between the client and the host is enabled. For more information, see the Bidirectional content redirection policy settings section in the Citrix Virtual Apps and Desktops documentation.
Install the workspace app with administrator privileges for this component to work.
