Looking for:
Citrix receiver install location |
Install and Uninstall | Citrix Workspace app for Windows
How to Manually Install and Configure Citrix Receiver for Pass-Through Authentication
Citrix receiver install location. How to Manually Install and Configure Citrix Receiver for Pass-Through Authentication
However, this configuration is similar to the previous Workspace for Windows versions. However, release 4. The functionality is useful in environments with a handful of applications that need to be displayed in consistent locations. If RemoveappsOnLogoff and RemoveAppsonExit are enabled, and users are experiencing delays in app enumeration at every logon, use the following workaround to reduce the delays:.
Editing the registry incorrectly can cause serious problems that might require you to reinstall your operating system. 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. Be sure to back up the registry before you edit it.
If you have dozens or even hundreds of apps, allow users to select the applications to add to Favorite and Start menu:. If a user has a family computer, you might not need or want app shortcuts at all. In such scenarios, the simplest approach is browser access; install Citrix Workspace app without any configuration and browse to workspace for web. You can also configure Citrix Workspace app for self-service access without putting shortcuts anywhere.
If the user has only a few apps, put them all in the Start menu or on the desktop, or in a folder on the desktop. If you want to set the location of shortcuts so every user finds them in the same place use XenApp per App Settings:.
If it is, Citrix Workspace app subscribes the application and does not create a shortcut. When the user starts the application from the Citrix Workspace app window, Citrix Workspace app starts the locally installed preferred application. If a user uninstalls a preferred application outside of Citrix Workspace app, the application is unsubscribed during the next Citrix Workspace app refresh. If a user uninstalls a preferred application from the Citrix Workspace app dialog, Citrix Workspace app unsubscribes the application but does not uninstall it.
The keyword prefer is applied when Citrix Workspace app subscribes an application. Adding the keyword after the application is subscribed has no effect. You can specify the prefer keyword multiple times for an application. Only one match is needed to apply the keyword to an application. The following patterns can be used in any combination:. This feature is referred to as Local App Access. When the user starts the application from the Citrix Workspace app dialog, Citrix Workspace app starts the locally installed preferred application.
If a user uninstalls a preferred application from the Citrix Workspace app, Citrix Workspace app unsubscribes the application but does not uninstall it. The application name pattern matches any application with the specified application name in the shortcut file name.
The application name can be a word or a phrase. Quotation marks are required for phrases. Matching is not allowed on partial words or file paths and is case-insensitive. The application name matching pattern is useful for overrides performed manually by an administrator.
The absolute path pattern matches the entire shortcut file path plus the entire application name under the Start menu. The Programs folder is a sub folder of the Start menu directory, so you must include it in the absolute path to target an application in that folder. Quotation marks are required if the path contains spaces. The matching is case-sensitive. The absolute path matching pattern is useful for overrides implemented programmatically in Citrix Virtual Apps and Desktops and Citrix DaaS.
The relative path pattern matches the relative shortcut file path under the Start menu. The relative path provided must contain the application name and can optionally include the folders where the shortcut resides.
Matching is successful if the shortcut file path ends with the relative path provided. The relative path matching pattern is useful for overrides implemented programmatically.
This feature lets you define a virtual monitor layout that applies to the remote desktop. You can also split a single client monitor virtually into up to eight monitors on the remote desktop. You can configure the virtual monitors on the Monitor Layout tab in the Desktop Viewer. There, you can draw horizontal or vertical lines to separate the screen into virtual monitors.
The screen is split according to specified percentages of the client monitor resolution. After applying a virtual monitor layout, resize or reconnect the session. This configuration applies only to full-screen, single-monitor desktop sessions, and does not affect any published applications. This configuration applies to all subsequent connections from this client. Starting from Citrix Workspace app for Windows , virtual display layout is also supported for full-screen and multi-monitor desktop sessions.
Virtual display layout is enabled by default. In case this limit is exceeded, the virtual display layout is ignored and not applied to any session monitor. Use the session prelaunch feature to reduce application launch time during normal or high traffic periods, thus providing users with a better experience.
The prelaunch feature allows to create a prelaunch session. Prelaunch session is created when a user logs on to Citrix Workspace app, or at a scheduled time if the user has signed in. The prelaunch session reduces the launch time of the first application. The default application ctxprelaunch.
For more information, see session prelaunch and session linger guidance in the Citrix Virtual Apps and Desktops article titled Manage delivery groups. Session prelaunch is disabled by default. The default setting, null, means that prelaunch is disabled. If the client machine has been configured to support Domain Passthrough SSON authentication, prelaunch is automatically enabled. You cannot customize the prelaunch feature using the receiver.
However, you can change the prelaunch configuration by modifying registry values. Registry values can be modified during or after Citrix Workspace app for Windows installation. The time hour format and days of a week for the scheduled prelaunch entered in the following format:.
The bidirectional content redirection policy allows you to enable or disable client to host and host to client URL redirection. Server policies are set in Studio, and client policies are set from the Citrix Workspace app Group Policy Object administration template.
However, we recommend that you use bidirectional content redirection for domain-joined Windows clients. To enable bidirectional content redirection using the GPO administrative template:. Use Group Policy Object administrative template configuration only for a first-time installation of Citrix Workspace app for Windows. In the Published Application or Desktop name field, provide the name of the resource used to launch the redirected URL.
The value must match a published application name. To enable bidirectional content redirection, run the redirector. Bidirectional content redirection allows you to configure URLs to redirect from client to server and from server to client using policies on the server and the client.
Server policies are set on the Delivery Controller and client policies on Citrix Workspace app. To register Google Chrome browser to bidirectional URL redirection, run the following command from the Citrix Workspace app installation folder:. When using these commands on Chrome browsers, the bidirectional content redirection extension installs automatically from the Chrome Web Store. To unregister Google Chrome browser from bidirectional URL redirection, run the following command from the Citrix Workspace app installation folder:.
For more information about browser content redirection, see Browser content redirection in the Citrix Virtual Apps and Desktops documentation. If you have multiple Desktop Viewer windows, by default the desktops that are not active are dimmed. If users want to view multiple desktops simultaneously, information on them might be unreadable. You can disable the default behavior and prevent the Desktop Viewer window from dimming by editing the Registry editor.
Editing the registry incorrectly can cause serious problems that might require you to reinstall your Operating system. An entry exists if the Desktop Viewer has been used on the device:. Before using these keys, check whether the Citrix Virtual Apps and Desktops and Citrix DaaS administrator has set a policy for this feature.
If no entries are specified or the entry is set to 0, the Desktop Viewer window is dimmed. If multiple entries are specified, the following precedence is used. The first entry in this list and its value determine whether the window is dimmed:.
The Citrix Ready workspace hub combines digital and physical environments to deliver apps and data within a secure smart space. The complete system connects devices or things , like mobile apps and sensors, to create an intelligent and responsive environment. Citrix Ready workspace hub is built on the Raspberry Pi 3 platform. The device running Citrix Workspace app connects to the Citrix Ready workspace hub and casts the apps or desktops on a larger display.
Citrix Casting feature allows instant and secure access of any app from a mobile device and display on a large screen. You can hide all or part of the Advanced Preferences sheet.
For more information, see Advanced Preferences sheet. Right-click the Citrix Workspace app icon from the notification area and select Advanced Preferences. Selecting the option No does not terminate the current screen casting session. The setting is applied only at the next Citrix Workspace app launch. The list of available hubs is displayed. The list is sorted by the RSSI value of the workspace hub beacon package.
If Citrix Workspace app cannot detect and communicate with any available workspace hubs in range, ensure that you do the following as part of self-check:. For more information about Citrix Ready workspace hub, see the Citrix Ready workspace hub section in the Citrix Virtual Apps and Desktops documentation.
Citrix Workspace app is DPI aware and supports matching display resolution and DPI scale settings on the Windows client to the virtual apps and desktops session. DPI scaling is mostly used with large size and high-resolution monitors to display applications, text, images, and other graphical elements in a size that can be viewed comfortably.
This feature is enabled by default, and it is the recommended setting for all use cases. Those issues are the result of a third-party limitation. For more information, see the Microsoft Support article. To enable generic client IME, run the wfica To disable generic client IME, run the wfica You can use the command-line switch wfica This command does not affect keyboard layout synchronization settings. If you have disabled generic client IME using the command-line interface, you can enable the feature again by running the wfica Citrix Workspace app supports toggle functionality for this feature.
You can run the wfica However, the keyboard layout synchronization settings take precedence over the toggle switch. If keyboard layout synchronization is set to Off , toggling does not enable generic client IME. Generic client IME feature can be enabled by enabling keyboard layout synchronization. For more information, see Keyboard layout synchronization.
Citrix Workspace app allows you to configure different options to use generic client IME. You can select from one these options based on your requirements and usage. The different options for IME modes appear in the top-right corner of the session. The different options for IME modes appear in the top-right corner of the session while switching using these hotkey combinations.
Citrix Workspace app supports the use of the H. In Citrix Workspace app for Windows, this feature is set to Disabled by default. Configuring Citrix Workspace app to use H. Enabling H. You can hide all or part of the Advanced Preferences sheet available from the Citrix Workspace app icon in the notification area. Keyboard layout synchronization enables you to switch among preferred keyboard layouts on the client device.
This feature is disabled by default. The keyboard layout synchronization allows the client keyboard layout to automatically synchronize to the virtual apps and desktops session. To configure keyboard layout synchronization using the GPO administrative template:.
Allow dynamic sync - From the drop-down menu, select Yes or No. This option synchronizes the client keyboard layout to the server when you change the client keyboard layout.
Sync mode on session launch - From the drop-down menu, select one of the following options:. To configure keyboard layout synchronization using the graphical user interface:.
The session reverts to the keyboard layout provided by the remote server when they connect to the next session. Sometimes, switching the client keyboard layout does not take effect in an active session.
To resolve this issue, log off from Citrix Workspace app and login again. The following procedure applies only on Windows server and later. On Windows Server R2 and earlier, the keyboard sync feature is enabled by default.
After you enable the keyboard layout on both the VDA and Citrix Workspace app, the following window appears when you switch keyboard layouts. This window indicates that the session keyboard layout is being switched to the client keyboard layout.
For more information about the keyboard layout synchronization feature on Linux VDA, see Dynamic keyboard layout synchronization. The keyboard layout change notification dialog lets you know that the VDA session is switching the keyboard layout. The keyboard layout switch needs approximately two seconds to switch. When you hide the notification dialog, wait for some time before you start typing to avoid incorrect character input.
The language bar displays the preferred input language in a session. The language bar appears in a session by default. You can hide the language bar tab from the Advanced Preferences sheet by using the registry. You can plug USB devices into their computers and the devices are remote to their virtual desktop. USB devices available for remoting include flash drives, smartphones, PDAs, printers, scanners, MP3 players, security devices, and tablets.
Isochronous features in USB devices, such as webcams, microphones, speakers, and headsets are supported in typical low latency or high-speed LAN environments. Such environment allows these devices to interact with packages, like Microsoft Office Communicator and Skype. The following types of device are supported directly in a virtual apps and desktops session, and so does not use USB support:. For information on configuring Bloomberg keyboards, see Configure Bloomberg keyboards.
Remoting this device would not be appropriate. The following types of USB device are not supported by default in a virtual apps and desktops session:. The following types of USB device are not supported by default for use in a virtual apps session:. When a user plugs in a USB device, it is checked against the USB policy, and, if allowed, remoted to the virtual desktop. If the default policy denies a device, it is available only to the local desktop.
When a user plugs in a USB device, a notification appears to inform the user about a new device. The user can select which USB devices must be remoted to the virtual desktop each time they connect. Although they are on this list, some classes are only available for remoting in virtual apps and desktops sessions after additional configuration.
Such USB device classes are as follows. Some specialty devices for example, VOIP phones require additional configuration. Still Imaging Class 06 - Includes digital cameras and scanners. Cameras might also appear as mass storage devices.
It might be also possible to configure a camera to use either class, through the setup menus provided by the camera itself. If a camera appears as a mass storage device, client drive mapping is used and USB support is not required. Printers Class 07 - In general most printers are included in this class, although some use vendor-specific protocols class ff. Multi-function printers might have an internal hub or be composite devices.
In both cases the printing element generally uses the Printers class and the scanning or fax element uses another class; for example, Still Imaging. This class of device in particular printers with scanning functions requires additional configuration. There are a wide variety of devices with internal storage that also present a mass storage interface; these include media players, digital cameras, and mobile phones.
Mass Storage Class 08 is not applicable to virtual apps because these devices are not available for remoting in virtual apps using USB support.
Known subclasses include:. Mass storage devices can often be accessed through client drive mapping, and so USB support is not required. Content Security Class 0d - Content security devices enforce content protection, typically for licensing or digital rights management. This class includes dongles. Video Class 0e - The video class cover devices that are used to manipulate video or video-related material.
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. Configuring Single sign-on. Domain pass-through access matrix.
Secure communications. Storebrowse for Workspace. Citrix Workspace app Desktop Lock. ICA settings reference. Aviso legal. Este texto foi traduzido automaticamente. Este artigo foi traduzido automaticamente. Both users and administrators can install Citrix Workspace app. Administrator privileges are required only when using pass-through authentication and Citrix Ready workspace hub with Citrix Workspace app for Windows. The following table describes the differences when Citrix Workspace app is installed as an administrator or a user:.
Administrators can override the user-installed instance of Citrix Workspace app and continue with the installation successfully. When the installation is complete, Citrix Workspace app requests that you add an account. For information on how to add an account, see Add accounts or switch servers. You can customize the Citrix Workspace app installer by specifying different command-line options.
The installer package self-extracts to the system temp directory before launching the setup program. The space requirement includes program files, user data, and temp directories after launching several applications. 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. Specifies if you want to display icons for documents or files that have file type association with subscribed applications. Enables the URL redirection feature on the user device. Allows you to save the store credentials locally.
No comments:
Post a Comment