Configuration

After the Citrix Receiver for Mac software is installed, the following configuration steps allow users to access their hosted applications and desktops.

If you have users who connect from outside the internal network (for example, users who connect from the Internet or from remote locations), configure authentication through NetScaler Gateway.

Configure USB redirection

HDX USB device redirection enables redirection of USB devices to and from a user device. For example, a user can connect a flash drive to a local computer and access it remotely from within a virtual desktop or a desktop hosted application. During a session, users can plug and play devices, including Picture Transfer Protocol (PTP) devices such as digital cameras, Media Transfer Protocol (MTP) devices such as digital audio players or portable media players, point-of-sale (POS) devices and other devices such as 3D Space Mice, Scanners, Signature Pads etc.

Note:

Double-hop USB is not supported for desktop hosted application sessions.

USB redirection is available for the following Citrix Receiver for Mac:

  • Windows
  • Linux
  • Mac

By default, USB redirection is allowed for certain classes of USB devices, and denied for others. You can restrict the types of USB devices made available to a virtual desktop by updating the list of USB devices supported for redirection, as described later in this section.

Tip

In environments where security separation between the user device and server is needed, Citrix recommends that users are informed about the types of USB devices to avoid.

Optimized virtual channels are available to redirect most popular USB devices, and provide superior performance and bandwidth efficiency over a WAN. Optimized virtual channels are usually the best option, especially in high latency environments.

Note:

For USB redirection purposes, Citrix Receiver for Mac handles a SMART board the same as a mouse.

The product supports optimized virtual channels with USB 3.0 devices and USB 3.0 ports, such as a CDM virtual channel used to view files on a camera or to provide audio to a headset). The product also supports Generic USB Redirection of USB 3.0 devices connected to a USB 2.0 port.

Some advanced device-specific features, such as Human Interface Device (HID) buttons on a webcam, may not work as expected with the optimized virtual channel; if this is an issue, use the Generic USB virtual channel.

Certain devices are not redirected by default, and are only available to the local session. For example, it would not be appropriate to redirect a network interface card that is directly attached via internal USB.

To use USB redirection:

  1. Connect the USB device to the device where Receiver is installed.

  2. You will be prompted to select the available USB devices on your local system.

    USB redirect screen

  3. Select the device you wish to connect and click Connect. If the connection fails, an error message appears.

  4. In the Preferences window Devices tab, the connected USB device is listed in the USB panel:

    USB settings

  5. Select the type of virtual channel for the USB device, Generic or Optimized.

  6. A message is displayed. Click to connect the USB device to your session:

    USB redirect notice

Use and remove USB devices

Users can connect a USB device before or after starting a virtual session. When using Citrix Receiver for Mac, the following apply:

  • Devices connected after a session starts immediately appear in the USB menu of the Desktop Viewer.
  • If a USB device is not redirecting properly, sometimes you can resolve the problem by waiting to connect the device until after the virtual session has started.
  • To avoid data loss, use the Windows Safe removal menu before removing the USB device.

Configuring Enlightened Data Transport (EDT)

By default, EDT is enabled in Citrix Receiver for Mac.

Citrix Receiver for Mac reads the EDT settings as set in the default.ica file and applies it accordingly.

To disable EDT, run the following command in a terminal:

defaults write com.citrix.receiver.nomas HDXOverUDPAllowed -bool NO

Configure session reliability and auto client reconnect

Session reliability keeps sessions active and on the user’s screen when network connectivity is interrupted. Users continue to see the application they are using until network connectivity resumes.

With session reliability, the session remains active on the server. To indicate that connectivity is lost, the user’s display freezes until connectivity resumes on the other side of the tunnel. The user continues to access the display during the interruption and can resume interacting with the application when the network connection is restored. Session Reliability reconnects users without reauthentication prompts.

Important

Citrix Receiver for Mac users cannot override the server setting.

You can use session reliability with Transport Layer Security (TLS).

Note

TLS encrypts only the data sent between the user device and NetScaler Gateway.

Using session reliability policies

The session reliability connections policy setting allows or prevents session reliability.

The session reliability timeout policy setting has a default of 180 seconds, or three minutes. Though you can extend the amount of time session reliability keeps a session open, this feature is designed to be convenient to the user and it does not, therefore, prompt the user for reauthentication.

Tip

As you extend the amount of time a session is kept open, chances increase that a user may get distracted and walk away from the user device, potentially leaving the session accessible to unauthorized users.

Incoming session reliability connections use port 2598, unless you change the port number defined in the session reliability port number policy setting.

If you do not want users to be able to reconnect to interrupted sessions without having to reauthenticate, use the Auto Client Reconnect feature. You can configure the Auto client reconnect authentication policy setting to prompt users to reauthenticate when reconnecting to interrupted sessions.

If you use both session reliability and auto client reconnect, the two features work in sequence. Session reliability closes, or disconnects, the user session after the amount of time you specify in the Session reliability timeout policy setting. After that, the auto client reconnect policy settings take effect, attempting to reconnect the user to the disconnected session.

Session reliability 1

Note

Session reliability is enabled by default at the server. To disable this feature, configure the policy managed by the server.

Configuring session reliability

By default, session reliability is enabled.

To disable session reliability:

  1. Launch Citrix Studio.
  2. Open the Session Reliability connections policy.
  3. Set the policy to Prohibited.

Session reliability 2

Configuring session reliability timeout

By default, session reliability timeout is set to 180 seconds.

Note:

Session reliability timeout policy can be configured only with XenApp/XenDesktop 7.11 and later.

To modify session reliability timeout:

  1. Launch Citrix Studio.
  2. Open the Session reliability timeout policy.
  3. Edit the timeout value.
  4. Click OK.

Configuring auto client reconnection

By default, auto client reconnection is enabled.

To disable auto client reconnection:

  1. Launch Citrix Studio.
  2. Open the Auto client reconnect policy.
  3. Set the policy to Prohibited.

Auto client reconnection

Configuring Auto client reconnection timeout

By default, Auto client reconnection timeout is set to 120 seconds.

Note:

Auto client reconnect timeout policy can be configured only with XenApp/XenDesktop 7.11 and later.

To modify auto client reconnect timeout:

  1. Launch Citrix Studio.
  2. Open the Auto client reconnect policy.
  3. Edit the timeout value.
  4. Click OK.

Limitations:

On a Terminal Server VDA, Citrix Receiver for Mac uses 120 seconds as timeout value irrespective of the user settings.

Configuring the Reconnect user interface transparency level

The Session User Interface is displayed during a session reliability and auto client reconnect attempts. The transparency level of the user interface can be modified using Studio policy.

By default, Reconnect UI transparency is set to 80%.

To modify Reconnect user interface transparency level:

  1. Launch Citrix Studio.
  2. Open the Reconnect UI transparency level policy.
  3. Edit the value.
  4. Click OK.

Auto client reconnect and session reliability interaction

Mobility challenges associated with switching between various access points, network disruptions and display timeouts related to latency create challenging environments when trying to maintain link integrity for active Citrix Receiver sessions. To resolve this issue, Citrix enhanced session reliability and auto reconnection technologies present in this version of Receiver for Mac.

Auto client reconnection, along with session reliability, allows users to automatically reconnect to their Citrix Receiver sessions after recovering from network disruptions. These features, enabled by policies in Citrix Studio, can be used to vastly improve the user experience.

Note:

Auto client reconnection and session reliability timeout values can be modified using the default.ica file in StoreFront.

Auto client reconnection

Auto client reconnection can be enabled or disabled using Citrix Studio policies. By default, this feature is enabled. For information about modifying this policy, see the auto client reconnection section earlier in this article.

Use the default.ica file in StoreFront to modify the connection timeout for AutoClientReconnect; by default, this timeout is set to 120 seconds (or two minutes).

Setting Example Default
TransportReconnectRetryMaxTimeSeconds TransportReconnectRetryMaxTimeSeconds=60 120

Session reliability

Session reliability can be enabled or disabled using Citrix Studio policies. By default, this feature is enabled.

Use the default.ica file in StoreFront to modify the connection timeout for session reliability; by default, this timeout is set to 180 seconds (or three minutes).

Setting Example Default
SessionReliabilityTTL SessionReliabilityTTL=120 180

How auto client reconnection and session reliability works

When auto client reconnection and session reliability are enabled for a Citrix Receiver for Mac, consider the following:

  • A session window is greyed out when a reconnection is in progress; a countdown timer displays the amount of time remaining before the session is reconnected. Once a session is timed out, it is disconnected.

By default, the reconnect countdown timer notification starts at 5 minutes; this time value represents the combined default values for each of the timers (auto client reconnection and session reliability), 2 and 3 minutes respectively. The image below illustrates the countdown timer notification which appears in the upper right portion of the session interface:

Reconnect timer

Tip

You can alter the greyscale brightness used for an inactive session using a command prompt. For example, defaults write com.citrix.receiver.nomas NetDisruptBrightness 80. By default, this value is set to 80. The maximum value cannot exceed 100 (indicates a transparent window) and the minimum value can be set to 0 (a fully blacked out screen).

  • Users are notified when a session successfully reconnects (or when a session is disconnected). This notification appears in the upper right portion of the session interface:

Reconnect success

  • A session window which is under auto client reconnect and session reliability control provides an informational message indicating the state of the session connection. Click Cancel Reconnection to move back to an active session.

Reconnect cancel

Configuring CEIP

CEIP is scheduled to collect and securely upload data to Citrix at an interval of 7 days by default. You can change your participation in CEIP anytime using the Citrix Receiver for Mac > Security > Preferences screen.

Tip

When CEIP is disabled, minimal information containing only the installed Citrix Receiver for Mac version is uploaded; this happens only once. This minimal information is valuable to Citrix because it provides the distribution of different versions used by customers. This happens only once as soon as CEIP is disabled.

To disable CEIP, or to forego participation:

  1. In the Preferences window, select Security and Privacy.
  2. Select the Privacy tab.
  3. Change the appropriate radio button. For example, to disable CEIP, click “No, Thanks.”
  4. Click OK.

CEIP

Configure your application delivery

When delivering applications with XenDesktop or XenApp, consider the following options to enhance the experience for your users when they access their applications:

Web access mode

Without any configuration, Citrix Receiver for Mac provides web access mode: browser-based access to applications and desktops. Users simply open a browser to a Receiver for Web or Web Interface site and select and use the applications that they want. In web access mode, no app shortcuts are placed in the App Folder on your user’s device.

Self-service mode

By adding a StoreFront account to Citrix Receiver for Mac or configuring Citrix Receiver for Mac to point to a StoreFront site, you can configure self-service mode, which enables your users to subscribe to applications through Citrix Receiver for Mac. This enhanced user experience is similar to that of a mobile app store. In self-service mode you can configure mandatory, auto-provisioned, and featured app keyword settings as needed. When one of your users selects an application, a shortcut to that application is placed in the App Folder on the user device.

When accessing a StoreFront 3.0 site, your users see the Citrix Receiver for MacTech Preview user experience.

When publishing applications on your XenApp farms, to enhance the experience for users accessing those applications through StoreFront stores, ensure that you include meaningful descriptions for published applications. The descriptions are visible to your users through Citrix Receiver for Mac.

Configure self-service mode

As mentioned previously, by adding a StoreFront account to Citrix Receiver for Mac or configuring Citrix Receiver for Mac to point to a StoreFront site, you can configure self-service mode, which allows users to subscribe to applications from the Citrix Receiver for Mac user interface. This enhanced user experience is similar to that of a mobile app store.

In self-service mode, you can configure mandatory, auto-provisioned and featured app keyword settings as needed.

  • To automatically subscribe all users of a store to an application, append the string KEYWORDS:Auto to the description you provide when you publish the application in XenApp. When users log on to the store, the application is automatically provisioned without the need for users to manually subscribe to the application.
  • To advertise applications to users or make commonly used applications easier to find by listing them in the Citrix Receiver for Mac Featured list, append the string KEYWORDS:Featured to the application description.

For more information, see the StoreFront documentation.

If the Web Interface of your XenApp deployment does not have a XenApp Services site, create a site. The name of the site and how you create the site depends on the version of the Web Interface you have installed. For more information, see the Web Interface documentation.

Configure StoreFront

With StoreFront, the stores you create consist of services that provide authentication and resource delivery infrastructure for Citrix Receiver for Mac. Create stores that enumerate and aggregate desktops and applications from XenDesktop sites and XenApp farms, making these resources available to users.

  1. Install and configure StoreFront. For more information, see the StoreFront documentation.

    Note: For administrators who need more control, Citrix provides a template you can use to create a download site for Citrix Receiver for Mac.

  2. Configure stores for CloudGateway just as you would for other XenApp and XenDesktop applications. No special configuration is needed for Citrix Receiver for Mac. For more information, see Configuring Stores in the StoreFront documentation.

Provide users with account information

After installation, you must provide users with the account information they need to access their hosted applications and desktops. You can provide this information by:

  • Configuring email-based account discovery
  • Providing users with a provisioning file
  • Providing users with an auto-generated setup URL
  • Providing users with account information to enter manually

Configuring email-based account discovery

You can configure Citrix Receiver for Mac to use email-based account discovery. When configured, users enter their email address rather than a server URL during initial Citrix Receiver for Mac installation and configuration. Citrix Receiver for Mac determines the NetScaler Gateway, or StoreFront server associated with the email address based on Domain Name System (DNS) Service (SRV) records and then prompts the user to log on to access their hosted applications and desktops.

To configure your DNS server to support email-based discovery, see the topic Configuring Email-based Account Discovery in the StoreFront documentation.

To configure NetScaler Gateway to accept user connections by using an email address to discover the StoreFront, NetScaler Gateway, see Connecting to StoreFront by Using Email-Based Discovery in the NetScaler Gateway documentation.

Provide users with a provisioning file

You can use StoreFront to create provisioning files containing connection details for accounts. You make these files available to your users to enable them to configure Receiver automatically. After installing Citrix Receiver for Mac, users simply open the file to configure Citrix Receiver for Mac. If you configure Receiver for Web sites, users can also obtain Citrix Receiver for Mac provisioning files from those sites.

For more information, see the StoreFront documentation.

Provide users with an auto-generated setup URL

You can use the Citrix Receiver for Mac Setup URL Generator to create a URL containing account information. After installing Citrix Receiver for Mac, users simply click on the URL to configure their account and access their resources. Use the utility to configure settings for accounts and email or post that information to all your users at once.

Provide users with account information to enter manually

If providing users with account details to enter manually, ensure you distribute the following information to enable them to connect to their hosted and desktops successfully:

  • The URL for the StoreFront store or XenApp Services site hosting resources; for example: https://servername.example.com

  • For access using NetScaler Gateway: the NetScaler Gateway address, product edition, and required authentication method

    For more information about configuring NetScaler Gateway, see the NetScaler Gateway documentation.

When a user enters the details for a new account, Receiver attempts to verify the connection. If successful, Citrix Receiver for Mac prompts the user to log on to the account.

Configuring auto-update

Configuring using the graphical user interface

An individual user can override the Citrix Receiver Updates setting using the Preferences dialog. This is a per-user configuration and the settings apply only to the current user.

  1. Go to the Preferences dialog in Citrix Receiver for Mac.

  2. In the Advanced pane, click Auto Update. The Citrix Receiver Updates dialog appears.

  3. Select one of the following options:

    • Yes, notify me
    • No, don’t notify me
    • Use administrator specified settings
  4. Close the dialog box to save the changes.

Configuring Citrix Receiver Updates using StoreFront

Administrators can configure Citrix Receiver Updates using StoreFront. Citrix Receiver only uses this configuration for users who have selected “Use administrator specified settings.” To manually configure it, follow the steps below.

  1. Use a text editor to open the web.config file. The default location is C:\inetpub\wwwroot\Citrix\Roaming\web.config

  2. Locate the user account element in the file (Store is the account name of your deployment)

    For example: <account id=… name=”Store”>

    Before the </account> tag, navigate to the properties of that user account:

    <properties>

    <clear /> </properties>

  3. Add the auto-update tag after <clear /> tag.

auto-update-Check

This determines that Citrix Receiver can detect if updates are available.

Valid values:

  • Auto – Use this option to get notifications when updates are available.
  • Manual – Use this option to not get any notification when updates are available. Users need to check manually for updates by selecting Check for Updates.
  • Disabled – Use this option to disable Citrix Receiver Updates.

auto-update-DeferUpdate-Count

This determines the number of times the end user will be notified to upgrade before they are forced to update to the latest version of Citrix Receiver. By default, this value is 7.

Valid values:

  • -1 – The end user will always have the option of getting reminded later when an update is available.
  • 0 – The end user will be forced to update to the latest version of Citrix Receiver as soon as the update is available.
  • Positive integer – The end user will be reminded this many number of times before being forced to update. Citrix recommends not to set this value higher than 7.

auto-update-Rollout-Priority

This determines how quickly a device will see that an update is available.

Valid values:

  • Auto – The Citrix Receiver Updates system will decide when available updates are rolled out to users.
  • Fast – Available updates will be rolled out to users on high priority as determined by Citrix Receiver.
  • Medium – Available updates will be rolled out to users on medium priority as determined by Citrix Receiver.
  • Slow – Available updates will be rolled out to users on low priority as determined by Citrix Receiver.

Configuring the enhanced client IME using the configuration file

The enhanced client IME is dependent on the keyboard layout synchronization feature. By default, the enhanced IME feature is enabled when the keyboard layout synchronization feature is turned on. To control this feature alone, open the Config file in the ~/Library/Application Support/Citrix Receiver/ folder, locate the “EnableIMEEnhancement” setting and turn the feature on or off by setting the value to “true” or “false,” respectively.

Note:

The setting change takes effect after restarting the session.

Keyboard layout synchronization

Keyboard layout synchronization enables users to switch among preferred keyboard layouts on the client device. This feature is disabled by default.

To enable keyboard layout synchronization, go to Preferences > Keyboard and select “Use local keyboard layout, rather than the remote server keyboard layout.”

Note:

  1. Using the local keyboard layout option activates the client IME (Input Method Editor). If users working in Japanese, Chinese or Korean prefer to use the server IME, they must disable the local keyboard layout option by clearing the option in Preferences > Keyboard. The session will revert to the keyboard layout provided by the remote server when they connect to the next session.
  2. The feature works in the session only when the toggle in the client is turned on and the corresponding feature enabled on the VDA; a menu item,“Use Client Keyboard Layout,” in Devices > Keyboard > International is added to show the enabled state.

Limitations:

  • Using the keyboard layouts listed in “Supported Keyboard Layouts in Mac” works while using this feature. When you change the client keyboard layout to a non-compatible layout, the layout might be synced on the VDA side, but functionality cannot be confirmed.

  • Remote applications that run with elevated privileges (for example, running applications as an administrator) can’t be synchronized with the client keyboard layout. To work around this issue, manually change the keyboard layout on the VDA or disable UAC.

  • When RDP is deployed as an application and the user is working within an RDP session, it is not possible to change the keyboard layout using the Alt + Shift shortcuts. To work around this issue, users can use the language bar in the RDP session to switch the keyboard layout.

Keyboard layout