# System Requirements and Feature Support (WorkSpaces Applications Client)
<a name="client-system-requirements-feature-support"></a>

This topic provides information to help you understand the requirements for the WorkSpaces Applications client and supported features.

**Topics**
+ [

# System Requirements and Considerations
](client-system-requirements.md)
+ [

# Feature and Device Support
](client-feature-support.md)

# System Requirements and Considerations
<a name="client-system-requirements"></a>

The WorkSpaces Applications client requires the following:
+ Follow the principle of least privilege when launching the WorkSpaces Applications client. The client should only run with the level of privilege required to complete a task. 
+ Client requirements
  + Windows client
    + Operating system — Windows 10 (32-bit or 64-bit), Windows 11 (64-bit)
    + Microsoft Visual C\$1\$1 2019 version 14.20.xx Redistributable or later. For more information, see the [Latest Microsoft Visual C\$1\$1 Redistributable Version](https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170) in the Microsoft Support documentation.
    + RAM — 2 GB minimum
    + Hard drive space — 200 MB minimum
  + macOS client
    + Operating system — macOS 13 (Ventura), macOS 14 (Sonoma), macOS 15 (Sequoia)
    + Hard drive space — 200 MB minimum
+ Local administrator rights — Used if you want to install the WorkSpaces Applications USB driver for USB driver support.
**Note**  
Local administrator rights are not supported for the macOS client.
+ An WorkSpaces Applications image that uses the latest WorkSpaces Applications agent or agent versions published on or after November 14, 2018. For information about WorkSpaces Applications agent versions, see [WorkSpaces Applications Agent Release Notes](agent-software-versions.md).
+ The client supports UDP as well as the default TCP-based streaming over NICE DCV. For more information about NICE DCV and UDP, see [Enabling the QUIC UDP transport protocol](https://docs.aws.amazon.com/dcv/latest/adminguide/enable-quic.html). If you want to enable UDP streaming for the client, make sure you meet the following requirements. If you don't meet the following requirements, the client will default back to TCP-based streaming.
  + Your Stack has been configured to prefer UDP in the **Streaming Setting Experience** section. For more information, see [Create an Amazon WorkSpaces Applications Fleet and Stack](set-up-stacks-fleets.md).
  + Your network allows UDP traffic on port 8433 for the AWS IP Ranges. For more information, see [AWS IP address ranges](https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html).
  + You are using the latest base image when creating your fleet. For more information, see [WorkSpaces Applications Base Image and Managed Image Update Release Notes](base-image-version-history.md).
  + Your end users are using the latest client. For more information, see [Supported clients](https://clients.amazonappstream.com/).

**Note**  
We recommend an internet connection for WorkSpaces Applications client installation. In some cases, the client can't be installed on a computer that is not connected to the internet, or USB devices might not work with applications streamed from WorkSpaces Applications. For more information, see [Troubleshooting WorkSpaces Applications User Issues](troubleshooting-user-issues.md).

# Feature and Device Support
<a name="client-feature-support"></a>

The WorkSpaces Applications client supports the following features and devices.

**Topics**
+ [

# Native Application Mode
](feature-support-native-application-mode.md)
+ [

# Automatic and On-Demand Diagnostic Log Uploads
](feature-support-diagnostic-log-upload.md)
+ [

# Peripheral Devices
](feature-support-peripheral-devices.md)

# Native Application Mode
<a name="feature-support-native-application-mode"></a>

**Note**  
Native application mode is not available when streaming from Linux instances, streaming in Desktop mode, or when using the WorkSpaces Applications macOS client application.

Native application mode provides a familiar experience for your users during their WorkSpaces Applications streaming sessions. When your users connect to WorkSpaces Applications in this mode, they can work with their remote streaming applications in much the same way that they work with applications that are installed on their local computer. Each streaming application in native application mode opens in its own window, and application icons appear on the taskbar on your users' local PC.

If you want your users to connect to WorkSpaces Applications in classic mode only, you can configure the `NativeAppModeDisabled` registry value to disable native application mode. For more information, see [Choose Whether to Disable Native Application Mode](install-client-configure-settings.md#disable-native-application-mode-client).

For more information about native application mode and classic mode, and for guidance that you can provide to your users, see [WorkSpaces Applications Client Connection Modes](client-application-windows-connection-modes-user.md).

**Feature requirements**

To enable this feature for your users, you must use an image that uses a [version of the WorkSpaces Applications agent](agent-software-versions.md) released on or after February 19, 2020. In addition, version 1.1.129 or later of the WorkSpaces Applications client must be installed on your users' PCs. For more information about client versions, see [WorkSpaces Applications Windows Client Release Notes](client-release-versions.md).

If WorkSpaces Applications client version 1.1.129 or later is installed on your users' computer, but you are not using an image that uses an agent version released on or after February 19, 2020, the client falls back to classic mode even if native application mode is selected.

**Testing requirements**

Applications must be tested thoroughly in native application mode before production deployment. Testing in classic mode is not sufficient, because applications might have compatibility issues with native application mode. Key testing areas include the following:
+ Core application functionality
+ Network performance
+ Local device interactions
+ File handling operations
+ Print capabilities
+ Multi-monitor support
+ Audio/video features

We recommend starting with a pilot user group and documenting any application-specific limitations before full deployment. Application behavior and performance might vary between streaming modes. Comprehensive testing helps ensure optimal user experience and identifies any potential limitations before production rollout.

**Known Issues**

When users try to dock or undock tabs in one browser window into separate windows during a streaming session in native application mode, their remote streaming browser doesn't work the same way as a local browser. To perform this task during a streaming session in native application mode, users must press the Alt key until their browser tabs are docked into separate browser windows. 

# Automatic and On-Demand Diagnostic Log Uploads
<a name="feature-support-diagnostic-log-upload"></a>

To help with troubleshooting issues that might occur when your users are using the WorkSpaces Applications client, you can enable automatic or on-demand diagnostic log uploads, or let your users do so themselves. 

**Note**  
Diagnostic logs do not contain sensitive information. You can disable automatic and on-demand diagnostic log uploads on user PCs that you manage, or allow your users to disable these features themselves.

**Automatic diagnostic log uploads **

When you install the client on PCs that you manage, you can configure the WorkSpaces Applications client to upload diagnostic logs automatically. That way, when a client issue occurs, the logs are sent to WorkSpaces Applications (AWS) without user interaction. For more information, see [Configure Additional WorkSpaces Applications Client Settings for Your Users](install-client-configure-settings.md#configure-client).

Or, you can let your users choose whether to enable automatic diagnostic log uploads when they install the WorkSpaces Applications client, or after client installation. For guidance that you can provide your users to help them perform this task, see [Setup for Windows](client-application-windows-installation-user.md).

**On-demand diagnostic log uploads **

If you require more control over logging, you can disable automatic logging and enable on-demand diagnostic log uploads. If you let your users upload diagnostic logs on demand, they can also choose whether to send minidumps (error reports) to WorkSpaces Applications (AWS) if an exception occurs or the client stops responding.

 For guidance that you can provide your users to help them perform these tasks, see [Logging](client-application-windows-how-to-enable-diagnostic-logging-user.md).

# Peripheral Devices
<a name="feature-support-peripheral-devices"></a>

The WorkSpaces Applications client provides the following support for peripheral devices such as monitors, webcams, mice, keyboards, and drawing tablets.

**Note**  
With certain exceptions, USB redirection is required for the WorkSpaces Applications client to support USB devices. And in most cases, when USB redirection is required for a device, you must qualify the device before it can be used with WorkSpaces Applications streaming sessions. For more information, see [USB Redirection](feature-support-USB-devices-qualified.md#feature-support-USB-devices-USB-redirection).

**Topics**
+ [

# Multiple Monitors
](feature-support-multiple-monitors.md)
+ [

# Real-Time Audio-Video
](feature-support-real-time-av.md)
+ [

# USB Devices
](feature-support-USB-devices-qualified.md)
+ [

# Drawing Tablets
](feature-support-drawing-tablets.md)
+ [

# Keyboard Shortcuts
](feature-support-keyboard-shortcuts.md)
+ [

# Relative Mouse Offset
](feature-support-relative-mouse-offset.md)

# Multiple Monitors
<a name="feature-support-multiple-monitors"></a>

WorkSpaces Applications supports the use of multiple monitors during streaming sessions, including monitors that have different resolutions. To help ensure an optimal streaming experience, we recommend that users who have monitors with different resolutions set the display scale for their monitors to 100 percent.

**Note**  
For WorkSpaces Applications streaming sessions that use [native application mode](feature-support-native-application-mode.md), monitors with up to 4K resolution are supported. If higher-resolution monitors are used for streaming sessions, the WorkSpaces Applications client falls back to classic mode. In this scenario, the WorkSpaces Applications classic mode streaming view occupies 4K of the screen, and the remaining portion of the screen is black.

## Multiple Monitors (up to 4K Resolution)
<a name="feature-support-multiple-monitors-4K"></a>

**Default behavior:** By default, all instance types support up to 4 monitors with a maximum display resolution of 4096x2160 pixels per monitor, except for instances with small or medium sizes.

**For all instance types with small and medium sizes:** While we do not recommend using 4K resolution on small and medium instances due to performance limitations, you can enable it by making the following changes in your images:
+ For Windows: Configure the following registry setting on image builder.
  + Using PowerShell:

    ```
    Set-ItemProperty "HKLM:\SOFTWARE\Amazon\AppStream" -Name EnableNonGraphics4K -Value 1
    ```
  + Using registry edit (regedit):
    + Registry path: `HKLM:Software\Amazon\AppStream`
    + Registry value name: `EnableNonGraphics4K`
    + Registry value data: `1`
    + Registry value type: `DWord`
+ For Linux: Edit `/etc/euc/workspaces-applications.conf` and update the following `[display]` configuration:

  ```
  EnableNonGraphics4K=1
  ```
+ Create a new image using this setting.
+ Use this new image with your fleets.
+ Your end users will see a max of 4K resolution on their display devices, depending upon the display resolution of their devices.

**Important**  
High-resolution monitors (such as 4K displays) require significantly more GPU and encoding resources, with actual performance depending on display configuration (resolution and number of monitors) and the compute instance being used. If your users experience suboptimal performance on 4K monitors, either switch your fleets to more powerful instances or recommend your users to reduce their display resolution to improve responsiveness.  
Ultrawide monitors with resolutions exceeding 4096 pixels in either dimension (e.g., 5120x2160) will display black bars on the sides, as the maximum supported resolution is limited to 4096 pixels per dimension.

**Disable 4K resolution for non-graphics instances**

If your users are facing performance issues with 4K monitor resolutions on instances without graphics hardware, you can follow the steps below to limit the resolution to 2K (2560x1440).
+ For Windows: Configure the following registry setting on image builder.
  + Using PowerShell:

    ```
    Set-ItemProperty "HKLM:\SOFTWARE\Amazon\AppStream" -Name EnableNonGraphics4K -Value 0
    ```
  + Using registry edit (regedit):
    + Registry path: `HKLM:Software\Amazon\AppStream`
    + Registry value name: `EnableNonGraphics4K`
    + Registry value data: `0`
    + Registry value type: `DWord`
+ For Linux: Edit `/etc/euc/workspaces-applications.conf` and update the following `[display]` configuration:

  ```
  EnableNonGraphics4K=0
  ```
+ Create a new image using this setting.
+ Use this new image with your fleets.
+ Your end users will see a max of 2K resolution on their display devices.

# Real-Time Audio-Video
<a name="feature-support-real-time-av"></a>

WorkSpaces Applications supports real-time audio-video (AV) by redirecting local webcam video input to WorkSpaces Applications streaming sessions. This capability enables your users to use their local webcam for video and audio conferencing within an WorkSpaces Applications streaming session. With real-time AV and support for real-time audio, your users can collaborate by using familiar video and audio conferencing applications without having to leave their WorkSpaces Applications streaming session.

When a user starts a video conference from within an WorkSpaces Applications streaming session, WorkSpaces Applications compresses the webcam video and microphone audio input locally before transmitting this data over a secure channel to a streaming instance. During their streaming sessions, users can enable audio and video input by using the WorkSpaces Applications toolbar. If users have more than one webcam (for example, if they have a USB webcam that is connected to their local computer and a built-in webcam), they can also choose which webcam to use during their streaming session.

**Note**  
For multi-session fleets, only in/out functionalities are accessible. Video in (webcam support) is not yet available for multi-session fleets.

To configure and test support for real-time AV, complete the following steps.

**Configure and test support for real-time AV**

1. Create a new image builder or connect to an existing image builder that meets the following requirements:
   + The image builder must run Windows Server 2016 or Windows Server 2019.
   + The image builder must use a version of the WorkSpaces Applications agent released on or after June 1, 2021.
   + For WorkSpaces Applications agents released on or after May 17, 2021, real-time AV is enabled by default. To create a streaming URL for testing, you can skip steps 3 through 6 and disconnect from the image builder. If you need to disable real-time AV, complete all of the steps, and disable webcam permissions in step 4.
   + The image builder must use a version of the WorkSpaces Applications agent released on or after June 24, 2021 to support video when connecting using web browser access. For more information about supported web browsers, see [Web Browser Access](web-browser-user.md).

   For information about how to create an image builder, see [Launch an Image Builder to Install and Configure Streaming Applications](tutorial-image-builder-create.md).

1. Connect to the image builder that you want to use and sign in as Administrator. To connect to the image builder, do either of the following:
   + [Use the WorkSpaces Applications console](managing-image-builders-connect-console.md) (for web connections only)
   + [Create a streaming URL](managing-image-builders-connect-streaming-URL.md) (for web or WorkSpaces Applications client connections)
**Note**  
If the image builder that you want to connect to is joined to an Active Directory domain and your organization requires smart card sign in, you must create a streaming URL and use the WorkSpaces Applications client for the connection. For information about smart card sign in, see [Smart Cards](feature-support-USB-devices-qualified.md#feature-support-USB-devices-qualified-smart-cards).

1. On the image builder, open Registry Editor. To do so, on the image builder desktop, in the search box on the taskbar, type **regedit**. Then, select the top result for **Registry Editor**.

1. Under **HKEY\$1LOCAL\$1MACHINE\$1SOFTWARE\$1Amazon\$1AppStream\$1**, create a new registry value that has the following type, name, and value data:
   + Registry value type: DWORD
   + Registry value name: WebcamPermission
   + Registry value data (Hexademical): 1 to enable or 0 to disable webcam permissions

1. After you create the registry value, switch to **Template User** or to a domain account that does not have administrator permissions on the image builder. To switch to **Template User**, in the toolbar on the top right of the session window, choose **Admin Commands**, **Switch User**, **Template User**.

1. Switch back to **Administrator**.

1. Disconnect from the image builder and create a streaming URL for the image builder. To do so:

   1. Open the WorkSpaces Applications console at [https://console.aws.amazon.com/appstream2](https://console.aws.amazon.com/appstream2).

   1. In the navigation pane, choose **Images**, then choose **Image Builder**.

   1. Select the image builder from which you just disconnected, and choose **Actions**, **Create streaming URL**.

   1. Choose **Copy Link** and save the link to a secure and accessible location. You will use the link in the next step to connect to the image builder.

1. Using the streaming URL that you just created, connect to the image builder by using the WorkSpaces Applications client or web browser access.

1. Test the real-time AV experience on the image builder by following the steps in [Video and Audio Conferencing](client-application-windows-how-to-use-local-webcam-user.md).

1. After you verify that real-time AV is working as expected, disconnect from your streaming session, reconnect to the image builder and follow the necessary steps in Image Assistant to finish creating your image. For information about how to create an image, see [Tutorial: Create a Custom WorkSpaces Applications Image by Using the WorkSpaces Applications Console](tutorial-image-builder.md).

After you finish configuring your image builder and creating an image that supports real-time AV, you can make this feature available to your users on WorkSpaces Applications fleets. Ensure that version 1.1.257 or later of the WorkSpaces Applications client is installed on your users' computers.

**Note**  
To use real-time AV with the WorkSpaces Applications client, your WorkSpaces Applications base image and agent version should be June 1, 2021 or later. We recommend using the latest WorkSpaces Applications client. For guidance that you can provide to your users to help them use real-time AV, see [Video and Audio Conferencing](client-application-windows-how-to-use-local-webcam-user.md).  
To use real-time AV with web browser access, your WorkSpaces Applications image must use a version of the WorkSpaces Applications agent released on or after June 24, 2021. For more information on supported web browsers, see [Web Browser Access](web-browser-user.md).





# USB Devices
<a name="feature-support-USB-devices-qualified"></a>

The following sections provide information about WorkSpaces Applications support for USB devices.

**Topics**
+ [

## USB Redirection
](#feature-support-USB-devices-USB-redirection)
+ [

## Smart Cards
](#feature-support-USB-devices-qualified-smart-cards)

## USB Redirection
<a name="feature-support-USB-devices-USB-redirection"></a>

USB redirection is required for most local USB devices to be used during WorkSpaces Applications streaming sessions. When USB redirection is required, you must [qualify the device](qualify-usb-devices.md) before your users can use it during their WorkSpaces Applications streaming sessions. After you qualify the device, users must [share the device with WorkSpaces Applications](client-application-windows-how-to-share-usb-devices-user.md). With USB redirection, during WorkSpaces Applications streaming sessions, users' devices are not accessible for use with local applications.

In other cases, USB devices are already enabled for use with WorkSpaces Applications and no further configuration is required. For example, smart card redirection is already enabled by default when the WorkSpaces Applications client is installed. Because USB redirection isn't used when this feature is enabled, you don't need to qualify smart card readers, and users don't need to share these devices with WorkSpaces Applications to use them during streaming sessions.

**Note**  
USB redirection is currently not supported for Linux-based fleet instances, or when using the WorkSpaces Applications macOS client application.

## Smart Cards
<a name="feature-support-USB-devices-qualified-smart-cards"></a>

WorkSpaces Applications supports using a smart card for Windows sign in to Active Directory-joined streaming instances and in-session authentication for streaming applications. Because smart card redirection is enabled by default, users can use smart card readers that are connected to their local computer and their smart cards without USB redirection.

**Topics**
+ [

### Windows Sign In and In-Session Authentication
](#feature-support-USB-devices-qualified-smart-cards-windows-signin-in-session-auth)
+ [

### Smart Card Redirection
](#feature-support-USB-devices-qualified-smart-cards-support)

### Windows Sign In and In-Session Authentication
<a name="feature-support-USB-devices-qualified-smart-cards-windows-signin-in-session-auth"></a>

WorkSpaces Applications supports the use of Active Directory domain passwords or smart cards such as [Common Access Card (CAC)](https://www.cac.mil/Common-Access-Card) and [Personal Identity Verification (PIV)](https://piv.idmanagement.gov/) smart cards for Windows sign in to WorkSpaces Applications streaming instances (fleets and image builders). Your users can use smart card readers connected to their local computer and their smart cards to sign in to an WorkSpaces Applications streaming instance that is joined to a Microsoft Active Directory domain. They can also use their local smart card readers and smart cards to sign in to applications within their streaming session.

To ensure that your users can use their smart cards for Windows sign in to Active Directory-joined streaming instances and for in-session authentication for streaming applications, you must:
+ Use an image that meets the following requirements:
  + The image must be created from a base image published by AWS on or after December 28, 2020. For more information, see [WorkSpaces Applications Base Image and Managed Image Update Release Notes](base-image-version-history.md).
  + The image must use a version of the WorkSpaces Applications agent released on or after January 4, 2021. For more information, see [WorkSpaces Applications Agent Release Notes](agent-software-versions.md).
+ Enable **Smart card sign in for Active Directory** on the WorkSpaces Applications stack that your users access for streaming sessions, as described in this section.
**Note**  
This setting controls only the authentication method that can be used for Windows sign in to an WorkSpaces Applications streaming instance (fleet or image builder). It doesn't control the authentication method that can be used for in-session authentication, after a user signs in to a streaming instance.
+ Ensure that your users have WorkSpaces Applications client version 1.1.257 or later installed. For more information, see [WorkSpaces Applications Windows Client Release Notes](client-release-versions.md).

By default, password sign in for Active Directory is enabled on WorkSpaces Applications stacks. You can enable smart card sign in for Active Directory by performing the following steps in the WorkSpaces Applications console.

**To enable smart card sign in for Active Directory by using the WorkSpaces Applications console**

1. Open the WorkSpaces Applications console at [https://console.aws.amazon.com/appstream2/home](https://console.aws.amazon.com/appstream2/home).

1. In the left navigation pane, choose **Stacks**.

1. Choose the stack for which you want to enable smart card authentication for Active Directory.

1. Choose the **User Settings** tab, and then expand the **Clipboard, file transfer, print to local device, and authentication permissions** section.

1. For **Smart card sign in for Active Directory**, choose **Enabled**.

   You can also enable **Password sign in for Active Directory**, if it's not already enabled. At least one authentication method must be enabled.

1. Choose **Update**.

Alternatively, you can enable smart card sign in for Active Directory by using the WorkSpaces Applications API, an AWS SDK, or the AWS Command Line Interface (AWS CLI).

### Smart Card Redirection
<a name="feature-support-USB-devices-qualified-smart-cards-support"></a>

When the WorkSpaces Applications client is installed, smart card redirection is enabled by default. When this feature is enabled, users can use smart card readers that are connected to their local computer and their smart cards during WorkSpaces Applications streaming sessions without USB redirection. During WorkSpaces Applications streaming sessions, users' smart card readers and smart cards remain accessible for use with local applications. The WorkSpaces Applications client redirects the smart card API calls from users’ streaming applications to their local smart card. 

**Note**  
Smart card redirection is currently not supported for Linux-based fleet instances or multi-session fleet instances, or when using the WorkSpaces Applications macOS client application. 

**Note**  
If your smart card requires middleware software to operate, the middleware software must be installed on both the user’s device, and the WorkSpaces Applications streaming instance.

You can disable smart card redirection during client installation on managed devices. For more information, see [Choose Whether to Disable Smart Card Redirection](install-client-configure-settings.md#disable-local-smart-card-support-client). If you disable smart card redirection, your users can't use their smart card reader and smart card during an WorkSpaces Applications streaming session without USB redirection. In this case, you must [qualify the device](qualify-usb-devices.md). After you qualify the device, users must [share the device with WorkSpaces Applications](client-application-windows-how-to-share-usb-devices-user.md). When smart card redirection is disabled, during users' WorkSpaces Applications streaming sessions, their smart card reader and smart card are not accessible for use with local applications.

# Drawing Tablets
<a name="feature-support-drawing-tablets"></a>

Drawing tablets, also known as pen tablets, are computer input devices that let users draw with a stylus (pen). With WorkSpaces Applications, your users can connect a drawing tablet, such as a Wacom drawing tablet, to their local computer and use the tablet with their streaming applications.

**Note**  
Drawing tablets are not supported when using the WorkSpaces Applications macOS client application. 

Following are requirements and considerations for enabling your users to use drawing tablets with their streaming applications.
+ To enable your users to use this feature, you must configure your WorkSpaces Applications fleet to use an image that runs Windows Server 2019.
+ To use this feature, users must access WorkSpaces Applications by using the WorkSpaces Applications client, or through the Google Chrome or Mozilla Firefox browsers only.
+ Streaming applications must support Windows Ink technology. For more information, see [Pen interactions and Windows Ink in Windows apps](https://docs.microsoft.com/en-us/windows/uwp/design/input/pen-and-stylus-interactions).
+ Some applications, such GIMP, must detect drawing tablets on the streaming instance to support pressure sensitivity. If this is the case, your users must use the WorkSpaces Applications client to access WorkSpaces Applications and stream these applications. In addition, you must qualify your users' drawing tablets, and users must share their drawing tablets with WorkSpaces Applications every time they start a new streaming session. For more information, see [Qualify USB Devices for Use with Streaming Applications](qualify-usb-devices.md).
+ This feature is not supported on Chromebooks.

To get started with using drawing tablets during application streaming sessions, users connect their drawing tablet to their local computer with USB, share the device with WorkSpaces Applications if required for pressure sensitivity detection, and then use the WorkSpaces Applications client or a [supported web browser](drawing-tablet-support-web-access-admin.md) to start an WorkSpaces Applications streaming session.

# Keyboard Shortcuts
<a name="feature-support-keyboard-shortcuts"></a>

For the Windows client, most operating system keyboard shortcuts are supported. Supported keyboard shortcuts include Alt \$1 Tab, Clipboard shortcuts (Ctrl \$1 X, Ctrl \$1 C, Ctrl\$1 V), Esc, and Alt \$1 F4.

For the macOS client, supported keyboard shortcuts include Clipboard shortcuts (Command \$1 X, Command \$1 C, Command \$1 V, Command \$1 A, Command-Z).

# Relative Mouse Offset
<a name="feature-support-relative-mouse-offset"></a>

By default, during users' streaming sessions, WorkSpaces Applications transmits information about mouse movements to the streaming instance by using absolute coordinates and rendering the mouse movements locally. For graphics-intensive applications, such as computer-aided design (CAD)/computer-aided manufacturing (CAM) software or video games, mouse performance improves when relative mouse mode is enabled. Relative mouse mode uses relative coordinates, which represent how far the mouse moved since the last frame, rather than the absolute x-y coordinate values within a window or screen. When relative mouse mode is enabled, WorkSpaces Applications renders the mouse movements remotely.

Users can enable this feature during their WorkSpaces Applications streaming sessions by doing either of the following:
+ Pressing Ctrl\$1Shift\$1F8 on the Windows client application or Ctrl\$1Shift\$1Fn\$1F8 on the macOS client application
+ Choosing **Relative Mouse Position [Ctrl\$1Shift\$1F8]** from the **Settings **menu on the WorkSpaces Applications toolbar in the top left area of their streaming session window. This method works when they use classic mode or **Desktop View**.