NICE DCV - User Guide

NICE DCVUser Guide

NICE DCV User Guide

NICE DCV: User Guide

NICE DCV User Guide

Table of ContentsGetting Started .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Step 1: Get the Session Information .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Step 2: Choose a Client ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

NICE DCV clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Requirements .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Supported features .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Windows client ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Installable Windows client ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Portable Windows client ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Web browser client ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Linux client ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6macOS client ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Using NICE DCV .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Connecting to a session .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Connecting using the Windows client ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Connecting using the web browser client ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Connecting using the Linux client ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Connecting using the macOS client ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Changing display resolution .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Managing streaming modes .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Streaming modes on Windows, Linux, and macOS clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Streaming modes on Web browser client ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Transferring files .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Transferring files using Windows, Linux and macOs clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Transferring files using web browser .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Printing .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Copying and pasting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Windows, Linux, and macOS clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Web browser client ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Using a smart card .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Saving a screenshot .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Collaborating sessions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Using multiple screens .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Using USB remotization .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Using a webcam ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Using a webcam on Windows, Linux and macOS clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Using a webcam on the web browser client ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Using accurate audio/video synchronization .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Using high color accuracy .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

High color accuracy on native clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33High color accuracy on Web browser client ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Using a connection file .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Creating the connection file .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Supported parameters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Running the connection file .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Setting certificate validation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Troubleshooting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Using the Log Files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Release notes and document history .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Release Notes .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42NICE DCV 2022.1-13216 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43NICE DCV 2022.1-13067 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43NICE DCV 2022.0-12760 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44NICE DCV 2022.0-12627 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

iii

NICE DCV User Guide

NICE DCV 2022.0-12123 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45NICE DCV 2022.0-11954 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45NICE DCV 2021.3-11591 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46NICE DCV 2021.2-11445 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46NICE DCV 2021.2-11190 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47NICE DCV 2021.2-11135 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47NICE DCV 2021.2-11048 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48DCV 2021.1-10851 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49DCV 2021.1-10598 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49DCV 2021.1-10557 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50DCV 2021.0-10242 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50DCV 2020.2-9662 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51DCV 2020.2-9508 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51DCV 2020.1-9012 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52DCV 2020.1-9012 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52DCV 2020.1-8942 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52DCV 2020.0-8428 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53DCV 2019.1-7644 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54DCV 2019.1-7423 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54DCV 2019.0-7318 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54DCV 2017.4-6898 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55DCV 2017.3-6698 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56DCV 2017.2-6182 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58DCV 2017.1-5870 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59DCV 2017.1-5777 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59DCV 2017.0-5600 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59DCV 2017.0-5121 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60DCV 2017.0-4334 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60DCV 2017.0-4100 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Document history .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

iv

NICE DCV User GuideStep 1: Get the Session Information

Getting Started with NICE DCVNICE DCV is a high-performance remote display protocol. It lets you securely deliver remote desktopsand application streaming from any cloud or data center to any device, over varying network conditions.By using NICE DCV with Amazon EC2, you can run graphics-intensive applications remotely on AmazonEC2 instances. You can then stream the results to more modest client machines, which eliminates theneed for expensive dedicated workstations.

To use NICE DCV, install the NICE DCV server software on a server. The NICE DCV server software isused to create a secure session. You install and run your applications on the server. The server uses itshardware to perform the high-performance processing that the installed applications require. Yourusers access the application by remotely connecting to the session using a NICE DCV client application.When the connection is established, the NICE DCV server software compresses the visual output ofthe application and streams it back to the client application in an encrypted pixel stream. The clientapplication receives the compressed pixel stream, decrypts it, and then outputs it to the local display.

Contents• Step 1: Get the NICE DCV Session Information (p. 1)• Step 2: Choose a NICE DCV Client (p. 1)

Step 1: Get the NICE DCV Session InformationAfter the NICE DCV session is running on the NICE DCV server, you must have specific information toconnect to it. Contact your NICE DCV administrator if you don't have the following information:

• The IP address or host name of the NICE DCV server• The port that the NICE DCV server is configured to communicate over. By default, port 8443 is used by

the NICE DCV server.• The session ID• A user name and password to connect to the NICE DCV host server

Step 2: Choose a NICE DCV ClientNext, choose the NICE DCV client that best meets your needs. NICE DCV offers the following clients:

• A Windows client• A web browser client• A Linux client• A macOS client

For more information about the available clients, see NICE DCV clients (p. 2).

After you choose a NICE DCV client, you can use it to connect to, and interact with the NICE DCVsession. For more information about using the NICE DCV clients to interact with sessions, see Using NICEDCV (p. 9).

1

https://docs.amazonaws.cn/dcv/latest/adminguide/managing-sessions.html

NICE DCV User GuideRequirements

NICE DCV clientsNICE DCV offers a Windows client, Linux client, web browser client, and macOS client. The clients offersimilar feature sets, but there are some differences. Choose the NICE DCV client that meets your specificrequirements.

Topics• Requirements (p. 2)• Supported features (p. 3)• Windows client (p. 4)• Web browser client (p. 5)• Linux client (p. 6)• macOS client (p. 7)

RequirementsTo use NICE DCV, ensure that the client computers meet the following minimum requirements. Bear inmind that your experience is dependent on the number of pixels that are streamed from the NICE DCVserver to the NICE DCV client.

Windows client Web browser client Linux client macOS client

SoftwareThe Windows client issupported on 32-bitand 64-bit versionsof the followingoperating systems:

• Windows 8.1• Windows 10• Windows 11

The client requiresthe followingadditional software:

• .NET Framework4.6.2

• Microsoft Visual C++ Redistributablefor VisualStudio. For moreinformationand downloadinstructions, seethe MicrosoftSupport website.

The web browserclient is supportedon the latest threemajor versions of thefollowing browsers,across all majordesktop operatingsystems (Windows,macOS, and Linux):

• Mozilla Firefox• Google Chrome• Microsoft Edge• Apple Safari

The web browserclient also requiresWebGL and asm.js.

NoteThe webbrowserclient isn'tsupportedon mobileoperatingsystems,such as

The Linux client issupported on thefollowing modernLinux operatingsystems:

• RHEL 7.x andCentOS 7.x

• RHEL 8.x andCentOS 8.x

• SUSE LinuxEnterprise 15.x

• Ubuntu 18.04,20.04, and 22.04

macOS clients withIntel processorsrequire macOSMojave (10.14) orlater.

macOS clients withApple M1 processorsrequire macOS BigSur (11).

2

https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

NICE DCV User GuideSupported features

Windows client Web browser client Linux client macOS client

Android andiOS.

NetworkThe client must connect to the NICE DCV server, and it must communicate over the requiredport. By default, this is port 8443.

For more information about the NICE DCV server requirements, see NICE DCV server requirements in theNICE DCV Administrator Guide.

Supported featuresThe following table compares the features that are supported by the NICE DCV clients.

Feature Windowsclient (p. 4)

Webbrowserclient (p. 5)

Linuxclient (p. 6)

macOSclient (p. 7)

Connect to Windows NICE DCVservers (p. 9)

✓ ✓ ✓ ✓

Connect to Linux NICE DCVservers (p. 9)

✓ ✓ ✓ ✓

QUIC UDP transport protocol (p. 9) ✓ ✗ ✓ ✓

Manage streaming modes (p. 13) ✓ ✓ ✓ ✓

Transfer files (p. 17) ✓ ✓ ✓ ✓

Print from sessions (p. 19) ✓ ✓ 1 ✓ 1 ✓ 1

Copy and paste (p. 20) ✓ ✓ ✓ ✓

Smart card support (p. 21) ✓ ✗ ✓ ✓

USB remotization support (p. 25) ✓(installableclient)

✗ ✗ ✗

Connection file support (p. 34) ✓ ✗ ✓ ✓

Stereo 2.0 audio playback ✓ ✓ ✓ ✓

Surround sound audio playback ✓ (up to 7.1) ✗ ✓ (up to 5.1) ✗

Stereo 2.0 audio recording ✓ ✓ ✓ ✓

Touchscreen support ✓ (Windows8.1 andlater)

✓ 2 ✓ ✗

Stylus support (on Linux and Windows 10and Server 2019 servers)

✓ (Windows10 and later)

✓ 3 ✓ ✓

Gamepad support (on Windows 10 andServer 2016 and later servers)

✓ ✗ ✗ ✗

3

https://docs.amazonaws.cn/dcv/latest/adminguide/servers.html#requirements

NICE DCV User GuideWindows client

Feature Windowsclient (p. 4)

Webbrowserclient (p. 5)

Linuxclient (p. 6)

macOSclient (p. 7)

Multiple monitor support (p. 24) ✓ ✓ ✓ ✓

Webcam support (p. 26) ✓ ✓ 4 ✓ ✓

1 These clients support printing to a file only. They don't support printing to a local printer.2 Supported by Firefox, Edge, and Google Chrome.3 Supported in Chromium-based browsers only. This includes Google Chrome and Microsoft Edge version79 and later. Tilt and pressure events aren't supported in other browsers.4 Supported in Chromium-based browsers only. This includes Google Chrome and Microsoft Edge version79 and later. This doesn't include Firefox and Safari.

For more information about the NICE DCV server features, see NICE DCV server features in the NICE DCVAdministrator Guide.

Windows clientThe NICE DCV Windows client is supported on Windows computers only. The Windows client is astandalone application that runs on the Windows operating system.

For instructions on how to connect to a NICE DCV session using the Windows client, see Connecting to aNICE DCV session using the Windows client (p. 9).

The Windows client is available in two versions: an installable version and a portable version. Bothversions have the same minimum system requirements and have the same features.

Contents• Installable Windows client (p. 4)• Portable Windows client (p. 5)

Installable Windows client

You can use an installation wizard to install the client. The wizard takes you through a series of stepswhere you can customize your client installation. Or, you can use the command line to performan unattended installation. This second method uses default settings to automate the installationprocedure.

Before using the wizard or the command line to install the client, make sure that your computer has therequired software. For a complete list of required software, see Requirements (p. 2).

To install the Windows client using the installation wizard

1. Download the Windows client installer.

TipThe latest packages page of the download website contains links that always point to thenewest available version. You can use these links to automatically retrieve the newest NICEDCV packages.

2. Run the installer.

4

https://docs.amazonaws.cn/dcv/latest/adminguide/servers.html#features

https://d1uj6qtbmh3dt5.cloudfront.net/2022.1/Clients/nice-dcv-client-Release-2022.1-8261.msi

http://download.nice-dcv.com/latest.html

NICE DCV User GuidePortable Windows client

3. On the Welcome screen, choose Next.4. On the End-User License Agreement screen, read the license agreement. If you accept the terms,

select the I accept the terms in the License Agreement check box. Choose Next.5. On the Destination Folder screen, choose Next to keep the default installation folder. To install the

client in a different folder, change the destination path, and then choose Next.6. (Optional) On the Drivers Selection screen, select USB device remotization. Then, choose Will be

installed on local hard drive, Next. This installs the drivers required to support some specializedUSB devices. These devices include 3D pointing devices and graphic tablets.

NoteUsing specialized USB devices requires additional client and server configuration. Forinstructions, see Using USB remotization (p. 25).

7. On the Ready to install screen, choose Install.

To install the Windows client using an unattended installation

1. Download the Windows client installer.2. Open a command prompt window and navigate to the folder where you downloaded the installer.3. Run the unattended installer.

C:\> msiexec.exe /i nice-dcv-client-Release-2022.1-8261.msi /quiet /norestart /l*v dcv_client_install_msi.log

To install all of the optional components, including the USB driver, include the ADDLOCAL=ALLoption in the command.

C:\> msiexec.exe /i nice-dcv-client-Release-2022.1-8261.msi ADDLOCAL=ALL /quiet /norestart /l*v dcv_client_install_msi.log

Portable Windows clientThe Windows client is also available in a portable version. You don't need to install the portable versionon your computer. You can copy it to a USB drive and run it directly from the USB drive on any Windowscomputer that meets the minimum requirements.

To use the portable Windows client

1. Download the portable Windows client zip file.


2. Extract the contents of the zip file.3. To launch the client, open the extracted folder, navigate to /bin/, and double-click

dcvviewer.exe.

Web browser clientThe NICE DCV web browser client runs inside a web browser. You don't need to install the web client. Theweb browser client is supported on the following browsers across all major desktop operating systems(including Windows, macOS, and Linux):

5

https://d1uj6qtbmh3dt5.cloudfront.net/2022.1/Clients/nice-dcv-client-Release-2022.1-8261.msi

https://d1uj6qtbmh3dt5.cloudfront.net/2022.1/Clients/nice-dcv-client-Release-portable-2022.1-8261.zip


NICE DCV User GuideLinux client

Browser Version

Google Chrome Latest three major versions

Mozilla Firefox Latest three major versions

Microsoft Edge Latest three major versions

Apple Safari Latest three major versions

For instructions on how to connect to a NICE DCV session using the web browser client, see Connectingto a NICE DCV session using the web browser client (p. 11).

WebCodecs

The web browser client can use WebCodecs to use video decoders that are already present in thebrowser. This can improve frame rate, because packets can be decoded by components of the browser.The NICE DCV web browser client will automatically use it if supported by the browser.

The use of WebCodecs is available on the following browsers:

• Google Chrome version 94 and later

• Microsoft Edge version 94 and later

All major operating systems are supported. This includes Windows, macOS, and Linux.

Limitations

The web browser client has the following limitations:

• It supports up to two screens with a maximum resolution of 1920x1080. The maximum resolution canbe overriden on the server side. For more information, see Managing the NICE DCV Session DisplayLayout in the NICE DCV Administrator Guide.

• It uses the web browser's proxy configuration.

Linux clientThe Linux client runs natively on the operating system. You can use it to connect to NICE DCV sessionsthat are hosted on Windows and Linux NICE DCV servers.

You install the Linux client on a Linux client computer using a software package. The software packageinstalls all required packages and their dependencies, and performs the required client configuration.

For instructions on how to connect to a NICE DCV session using the Linux client, see Connecting to aNICE DCV session using the Linux client (p. 11).

To install the Linux client

1. The software packages are digitally signed with a secure GPG signature. To allow the packagemanager to verify the package signature, import the NICE GPG key. To do this, open a terminalwindow and import the NICE GPG key.

• RHEL 7.x/8.x, CentOS 7.x/8.x, and SUSE Linux Enterprise 15

6

https://docs.amazonaws.cn/dcv/latest/adminguide/managing-session-display.html


NICE DCV User GuidemacOS client

$ sudo rpm --import https://d1uj6qtbmh3dt5.cloudfront.net/NICE-GPG-KEY

• Ubuntu

Download the GPG key.

$ wget https://d1uj6qtbmh3dt5.cloudfront.net/NICE-GPG-KEY

Install the GPG key.

$ sudo apt-key add NICE-GPG-KEY

2. Download the appropriate client software package for your target operating system from the NICEDCV website.


3. Install the Linux client. Enter the filename of the downloaded file to complete the followingcommand.

• RHEL 7.x and CentOS 7.x

$ sudo yum install the downloaded .rpm file

• RHEL 8.x,CentOS 8.x, and Rocky Linux 8.5 or later

$ sudo yum install the downloaded .rpm file

• Ubuntu 18.04, 20.04, and 22.04

$ sudo dpkg --install the downloaded .deb file

• SUSE Linux Enterprise 15

$ sudo zypper install the downloaded .rpm file

macOS clientThe NICE DCV macOS client is supported on Apple Mac computers only. The macOS client is a standaloneapplication that runs on the macOS operating system.

The macOS client is installed using a .dmg software package.

For instructions on how to connect to a NICE DCV session using the macOS client, see Connecting to aNICE DCV session using the macOS client (p. 12).

To install the macOS client

1. Download the correct macOS client installer depending on your client computer.

• macOS client for Intel processors• macOS clients for Apple M1 processors

7

http://download.nice-dcv.com

http://download.nice-dcv.com


https://d1uj6qtbmh3dt5.cloudfront.net/2022.1/Clients/nice-dcv-viewer-2022.1.4251.x86_64.dmg

https://d1uj6qtbmh3dt5.cloudfront.net/2022.1/Clients/nice-dcv-viewer-2022.1.4251.arm64.dmg

NICE DCV User GuidemacOS client


2. Run the downloaded .dmg file.

If you get an error stating that the application can't be installed because it's from an unidentifieddeveloper, see the Safely open apps on your Mac webpage.

3. Click and drag the DCV.app file to the Applications folder.4. (Optional) For easy access, create a desktop shortcut or add the application to the dock.

8


https://support.apple.com/en-ie/HT202491

NICE DCV User GuideConnecting to a session

Using NICE DCVAfter you choose a NICE DCV client, you can use it to connect to and interact with a NICE DCV session.

Topics• Connecting to a NICE DCV session (p. 9)• Changing display resolution (p. 13)• Managing streaming modes (p. 13)• Transferring files (p. 17)• Printing (p. 19)• Copying and pasting (p. 20)• Using a smart card (p. 21)• Saving a screenshot (p. 23)• Collaborating NICE DCV sessions (p. 23)• Using multiple screens (p. 24)• Using USB remotization (p. 25)• Using a webcam (p. 26)• Using accurate audio/video synchronization (p. 31)• Using high color accuracy (p. 33)• Using a connection file (p. 34)• Set certificate validation policy (p. 40)

Connecting to a NICE DCV sessionAfter the NICE DCV session starts running on the NICE DCV server, you can connect to it using yourpreferred client. Ensure that you have the required information when connecting to your NICE DCVsession. For more information, see Step 1: Get the NICE DCV Session Information (p. 1).

If you're connecting to a console session, contact your NICE DCV server administrator. With them, ensurethat the session is started and confirm the server and session details. If you're connecting to a virtualsession on a Linux NICE DCV server, you might need to start your own session. For more information, seeStarting NICE DCV Sessions in the NICE DCV Administrator Guide.

Topics• Connecting to a NICE DCV session using the Windows client (p. 9)• Connecting to a NICE DCV session using the web browser client (p. 11)• Connecting to a NICE DCV session using the Linux client (p. 11)• Connecting to a NICE DCV session using the macOS client (p. 12)

Connecting to a NICE DCV session using the WindowsclientThe steps for connecting to a NICE DCV session are the same for both the installable and portableversions of the Windows client.

9

https://docs.aws.amazon.com/dcv/latest/adminguide/managing-sessions-start.html

NICE DCV User GuideConnecting using the Windows client

To connect to a session using the Windows client

1. Launch the Windows client.

2. Choose Connections Settings, configure your proxy settings as follows, and then choose OK.

• To avoid connecting through a proxy, choose Connect Directly.

• To connect to the NICE DCV server using your preconfigured operating system proxy settings,choose Use system proxy.

• To connect to the NICE DCV server through a specific HTTP proxy server, choose Get through webproxy. Specify the IP address and communication port or the hostname of the proxy server. If theHTTP proxy server requires authentication, select the Proxy server requiring password check boxand enter your user name and password.

• To connect to the NICE DCV server through a specific SOCKS5 proxy server, choose Get throughSOCKSv5 proxy. Specify the IP address and communication port or the hostname of the proxyserver. If the SOCKSv5 proxy server requires authentication, select the Proxy server requiringpassword check box and enter your user name and password.

• To select the transport protocol to use for data transport, choose the Protocol tab. By default, theclient uses the QUIC protocol (based on UDP) for data transport if it's available. If it isn't available,the client uses the WebSocket protocol (based on TCP). This option is always available.

QUIC is available only if the two following conditions are met. First, the NICE DCV server isconfigured to support it. Second, your network configuration supports UDP communicationbetween the NICE DCV client and the NICE DCV server. Additionally, it's only supported for directclient-server communication where there are no intermediate proxies, gateways, or load balancers.

You can force the client to use a data transport protocol by explicitly selecting it. To verify whichprotocol is in use, check the Streaming Modes dialog. Additionally, if the QUIC protocol is in use,"QUIC" appears in the titlebar.

For more information and instructions, see Enable the QUIC UDP transport protocol in the NICEDCV Administrator Guide.

3. Specify the session details in the following format:

server_hostname_or_IP:port#session_id

In the following example, the command connects to a session that's named my-session. Thissession is hosted on a NICE DCV server with the hostname my-dcv-server.com. It's connectedover port 8443.

my-dcv-server.com:8443#my-session

4. Choose Connect.

5. Enter your user name and password and choose Login.

NoteBy default, the connection is terminated after three unsuccessful login attempts. To tryagain, restart the connection.

6. If you're prompted to verify the server's certificate, confirm the certificate's fingerprint with yourNICE DCV administrator. If the fingerprint is valid, choose Trust & Connect.

10

https://docs.amazonaws.cn/dcv/latest/adminguide/enable-quic.html

NICE DCV User GuideConnecting using the web browser client

Connecting to a NICE DCV session using the webbrowser clientThe steps for connecting to a NICE DCV session are the same across all supported web browsers. Theclient connects to the NICE DCV server using your web browser's proxy settings. To connect usingdifferent proxy settings, see the documentation for your specific web browser.

NoteThe web browser client doesn't support the QUIC (UDP) transport protocol.

To connect to your NICE DCV session using the web browser client

1. Open a web browser and enter the NICE DCV server URL in the following format:

https://server_hostname_or_IP:port/#session_id

In the following example, the URL connects to a session that's named my-session. This sessionis hosted on a NICE DCV server with the hostname my-dcv-server.com. It's connected over port8443.

https://my-dcv-server.com:8443/#my-session

2. Enter your user name and password and choose Login.


3. Your web browser might warn you that the server's certificate isn't trusted. If you're unsure aboutthe authenticity of the certificate, confirm it with your NICE DCV administrator. Proceed if it's safe todo so.

NoteThis step varies depending on the web browser that you're using.

Connecting to a NICE DCV session using the LinuxclientThe steps for connecting to a NICE DCV session are the same across all Linux clients.

To connect to a session using the Linux client

1. Launch the Linux client.2. Choose Connections Settings, configure your proxy settings as follows, and then choose Apply.

• To avoid connecting through a proxy, choose Connect directly.• To connect to the NICE DCV server using your preconfigured operating system proxy settings,

choose Use system proxy.• To connect to the NICE DCV server through a specific HTTP proxy server, choose Get through

web proxy (HTTP). Specify the IP address or the hostname of the proxy server as well as thecommunication port. If the HTTP proxy server requires authentication, select the Proxy serverrequiring password check box and enter your user name and password.

• To connect to the NICE DCV server through a specific HTTPS proxy server, choose Get throughweb proxy (HTTPS). Specify the IP address or the hostname of the proxy server as well as the

11

NICE DCV User GuideConnecting using the macOS client

communication port. If the web proxy server requires authentication, select the Proxy serverrequiring password check box and enter your user name and password.


QUIC is available only if the following two conditions are met. First, the NICE DCV server isconfigured to support it. Second, your network configuration supports UDP communicationbetween the NICE DCV client and the NICE DCV server. Additionally, it's only supported for directclient-server communication where there are no intermediate proxies, gateways, or load balancers.


For more information and instructions, see Enable the QUIC UDP transport protocol in the NICEDCV Administrator Guide.



In the following example, the command connects to a session that's named my-session. Thissession is hosted on a NICE DCV server with the hostname my-dcv-server.com. It's connectedover port 8443.


4. Choose Connect.5. Enter your user name and password and choose Login.


6. If you're prompted to verify the certificate on the server, confirm the fingerprint of the certificatewith your NICE DCV administrator. If the fingerprint is valid, choose Trust & Connect.

Connecting to a NICE DCV session using the macOSclientTo connect to a session using the macOS client

1. Launch the macOS client.

If you get an error stating that the application can't be opened because it's from an unidentifieddeveloper, see the Safely open apps on your Mac webpage.

2. Choose Connections Settings, configure your proxy settings as follows, and then choose Apply.

• To avoid connecting through a proxy, choose Connect directly.• To connect to the NICE DCV server using your preconfigured operating system proxy settings,

choose Use system proxy.• To connect to the NICE DCV server through a specific HTTP proxy server, choose Get through

web proxy (HTTP). Specify the IP address or hostname of the proxy server as well as thecommunication port. If the HTTP proxy server requires authentication, select the Proxy serverrequiring password check box and enter your user name and password.

12


https://support.apple.com/en-ie/HT202491

NICE DCV User GuideChanging display resolution

• To connect to the NICE DCV server through a specific HTTPS proxy server, choose Get throughweb proxy (HTTPS). Specify the IP address or hostname of the proxy server as well as thecommunication port. If the web proxy server requires authentication, select the Proxy serverrequiring password check box and enter your user name and password.


QUIC is available only if the following conditions are met. First, the NICE DCV server is configuredto support it. Second, your network configuration supports UDP communication between theNICE DCV client and the NICE DCV server. Additionally, it's only supported for direct client-servercommunication where there are no intermediate proxies, gateways, or load balancers.


For more information, see Enable the QUIC UDP transport protocol in the NICE DCV AdministratorGuide.



In the following example, the command connects to a session that's named my-session. Thissession is hosted on a NICE DCV server with the host name my-dcv-server.com. It's connectedover port 8443.


4. Choose Connect.5. Enter your user name and password and choose Login.


6. If you're prompted to verify the server's certificate, confirm the certificate's fingerprint with yourNICE DCV administrator. If the fingerprint is valid, choose Trust & Connect.

Changing display resolutionBy default, NICE DCV automatically adapts the display resolution of the remote machine to matchthe current size of the client. When the client window is resized, DCV requests the server to change itsdisplay resolution to a size that fits within the client window.

If you prefer a fixed resolution on the server, which does not change even when the client window isresized, select the Display Resolution menu and specify the desired resolution. If you decide to re-enableautomatic resize, you can select Adapt automatically .

This functionality is available on the Windows client, web browser client, Linux client, and macOS client.

Managing streaming modesNICE DCV uses an adaptive protocol that automatically optimizes the streaming mode depending on thenetwork capabilities. However, you can specify whether you prefer to prioritize responsiveness or image

13


NICE DCV User GuideStreaming modes on Windows, Linux, and macOS clients

quality. Prioritizing responsiveness reduces the image quality to improve the frame rate. Prioritizingimage quality reduces the responsiveness to provide better image quality.

This functionality is available on the Windows client, web browser client, Linux client, and macOS client.The steps for setting the streaming mode depend on the client used.

Topics• Streaming modes on Windows, Linux, and macOS clients (p. 14)• Streaming modes on Web browser client (p. 15)

Streaming modes on Windows, Linux, and macOSclientsTo change the streaming mode on Windows, Linux, and macOS clients:

1. In the client, choose Settings, Streaming Mode.

2. In the Streaming Mode window, choose one of the following options:

• Best responsiveness — This option prioritizes faster response times. It might result in lower imagequality.

• Best quality — This option prioritizes higher image quality. It might result in longer responsetimes.

3. (Optional) For information about network performance, choose Display Streaming Metrics. Formore information, see Streaming metrics (p. 14).

4. Close the Streaming Mode window.

Streaming metricsThe streaming metrics can be used to evaluate your network performance and determine whichstreaming mode is suitable for your network conditions. To view the streaming metrics, choose Settings,Streaming Mode, Display Streaming Metrics.

The streaming metrics provide the following real-time information:

NoteMetrics are displayed for the current NICE DCV session connection.

• Framerate—Indicates the number of frames received from the NICE DCV server every second.• Network latency—Indicates the amount of time (in milliseconds) it takes for a packet of data to be

sent to the NICE DCV server and back to the client.

14

NICE DCV User GuideStreaming modes on Web browser client

• Bandwidth usage—Indicates the amount of data being sent and received over the networkconnection. The red line shows the peak network throughput. The yellow line shows the averagethroughput. The blue line shows the current (real-time) throughput.

The following image shows example streaming metric data.

Streaming modes on Web browser clientThe steps for managing the streaming modes are the same across all supported web browsers.

1. In the client, choose Session, Preferences.

2. Under the Display tab, choose one of the following options from the Streaming options section:

• Best responsiveness — This option prioritizes faster response times. It might result in lower imagequality.

• Best quality — This option prioritizes higher image quality. It might result in longer responsetimes.

15

NICE DCV User GuideStreaming modes on Web browser client

3. (Optional) For information about network performance, choose Display Streaming Metrics. Formore information, see Streaming metrics (p. 16).

4. Save and close the Preferences modal.

Streaming metrics

The streaming metrics can be used to evaluate your network performance and determine whichstreaming mode is suitable for your network conditions.

The streaming metrics provide the following real-time information:

NoteMetrics are displayed for the current NICE DCV session connection.

• Framerate—Indicates the number of frames received from the NICE DCV server every second.

• Network latency—Indicates the amount of time (in milliseconds) it takes for a packet of data to besent to the NICE DCV server and back to the client.

• Bandwidth usage—Indicates the amount of data being sent and received over the networkconnection. The red line shows the peak network throughput. The yellow line shows the averagethroughput. The blue line shows the current (real-time) throughput.

To view the streaming metrics:


2. Under the Display tab, enable the toggle to show Streaming metrics in the toolbar.

3. Close the Preferences modal.

4. The streaming metrics are then displayed in the center of the client toolbar.

5. Click on the streaming metrics to see more detailed streaming data like in the following example.

16

NICE DCV User GuideTransferring files

6. (Optional) Close the Metrics modal.

Transferring filesYou can use NICE DCV to upload files to and download files from NICE DCV session storage. Forinstructions on how to enable and configure session storage, see Enabling Session Storage in the NICEDCV Administrator Guide.

You must be authorized to use this feature. If you are not authorized, the functionality is not available inthe client. For more information, see Configuring NICE DCV Authorization in the NICE DCV AdministratorGuide.

This functionality is available on the Windows, web browser, Linux, and macOS clients.

Topics

• Transferring files using Windows, Linux and macOs clients (p. 17)

• Transferring files using web browser (p. 18)

Transferring files using Windows, Linux and macOsclientsThe steps for uploading, downloading, and renaming files are similar across Windows, Linux and macOSclients.

Downloading a file

If you're using the Windows client, the file is downloaded to your desktop. If you're using the Linux, ormacOS client, the file is downloaded to your default Downloads folder.

17

https://docs.amazonaws.cn/dcv/latest/adminguide/manage-storage.html

https://docs.amazonaws.cn/dcv/latest/adminguide/security-authorization.html

NICE DCV User GuideTransferring files using web browser

To download a file from the session storage to your computer

1. In the client, choose Storage.

2. In the File Storage window, either select the file to download, or choose the down arrow next to thefile and then choose Download.

Uploading a fileFiles that you upload to a session are saved to a path that's specified by the NICE DCV serveradministrator.

To upload a file from your computer to the session storage

1. In the client, choose Storage.2. (Optional) To upload the file to a new folder, choose Create Folder, enter a folder name, and then

open the folder.3. In the File Storage window, choose Upload File, browse to and select the file to upload, and then

choose Open.

Renaming a fileYou can change the name of the file in session storage.

To change the name of a file in session storage

1. In the client, choose Storage.2. Choose the down arrow that's next to the file to rename, and choose Rename.3. Enter the new file name and press Enter.

Transferring files using web browserThe steps for uploading, downloading, and renaming files are the same across all supported webbrowsers.

Downloading a fileIn the web browser client the file is downloaded to your default Downloads folder.

To download a file from the session storage to your computer

1. In the client, choose Storage.

18

NICE DCV User GuidePrinting

2. In the File Storage window, either select the file to download, or select a table row corresponding tothe file to download and click on the Actions button and the Download option from there. You canalso just click on the name of the file to download it.

Uploading a fileFiles that you upload to a session are saved to a path that's specified by the NICE DCV serveradministrator.

To upload a file from your computer to the session storage

1. In the client, choose Storage.2. (Optional) To upload the file to a new folder, choose Create Folder, enter a folder name, and then

open the folder.3. In the File Storage window, choose Upload File, browse to and select the file to upload, and then

choose Open.

Renaming a fileYou can change the name of the file in session storage.

To change the name of a file in session storage

1. In the client, choose Storage.2. Select a table row corresponding to the item to rename and click on the Actions button and the

Rename option from there.3. Enter the new file name and press Enter.

PrintingYou can use NICE DCV to print content from a NICE DCV session. The available printing devices dependon the client that you're using.

• Windows client — You can print to the physical printer that's connected to your client computer. Or,you can print to a .PDF document that uses the NICE DCV virtual printer.

• Linux client and macOS client — You can print to a .PDF document using the NICE DCV virtualprinter.

• Web browser client — You can print to a .PDF document using the NICE DCV virtual printer.

When you print to the NICE DCV virtual printer, the content is exported to a printable file. You candownload it to your local computer using the client and then print it using your local printer.


To print content from the session

1. In the client, open the Print window.2. In the Print window, choose one of the following printing devices and then choose Print.

• (All clients connected to all Windows and Linux server) DCV Printer — Prints to the NICE DCVvirtual printer

19


NICE DCV User GuideCopying and pasting

• (Windows client connected to Windows server only) <local-printer-name>-Redirected —Prints to the local printer

• (Windows client connected to Linux server only) <local-printer-name>-Redirected-<connection-id> — Prints to the local printer

3. If you print to the NICE DCV virtual printer, a notification appears when the file is ready fordownload. In the top-right corner, choose Notifications, locate the Print notification in the list, andthen choose Download.

• If you're using the web browser client, after the download has completed, choose Show in folder.

• If you're using the Windows client, the printer dialog is automatically opened when the file isdownloaded.

• If you're using the Linux or macOS clients, the downloaded file is automatically opened with thedefault associated application.

NoteThe file is deleted from the NICE DCV server after you have downloaded it, and it's nolonger available for download.

Copying and pastingYou can use NICE DCV to copy and paste text between your local computer and the NICE DCV session.You must be authorized to use this feature. If you are not authorized, the functionality is not available inthe client. For more information, see Configuring NICE DCV Authorization in the NICE DCV AdministratorGuide.

The type of content that can be copied and pasted, and the methods for copying and pasting differbetween the Windows client, web browser client, Linux client, and macOS client.

Topics

• Windows, Linux, and macOS clients (p. 20)

• Web browser client (p. 20)

Windows, Linux, and macOS clientsYou can use the Windows, Linux, and macOS clients to copy and paste text and images between yourlocal computer and the NICE DCV session. You can do this using the keyboard shortcuts and context(right-click) menu shortcuts. If you can't copy and paste, contact your NICE DCV server administrator toensure that the permissions are properly configured.

Web browser clientYou can use the web browser client to copy and paste text and images between your local computer andthe NICE DCV session. Use keyboard shortcuts and context (right-click) menu to copy and paste text andimages on Google Chrome and Microsoft Edge. Mozilla Firefox and Apple Safari do not support copyingand pasting images, and require a different procedure to copy and paste text.

To copy text from the session in Mozilla Firefox or Apple Safari and paste on your localcomputer

1. In the web browser client, highlight the text to copy and choose Clipboard, Copy to Local Device.

20


NICE DCV User GuideUsing a smart card

The text is now placed in your computer's clipboard.

2. Paste the text using the paste keyboard shortcut or context menu shortcut.

To copy text from your local computer and paste in the session in Mozilla Firefox or AppleSafari

1. On your local computer, copy the text using the copy keyboard shortcut or context menu.

2. In the web browser client, choose Clipboard, Paste to Remote Session.

3. Paste the text using the host operating system's paste shortcuts.

Using a smart cardYou can use NICE DCV to use one or more smart cards that's connected to your client computer. You cando this using the standard Personal Computer/Smart Card (PC/SC) interface, in a NICE DCV session. Foreach session, only one connected client can connect a smart card at a time. This is especially important inenvironments where multiple clients connect to the same session.

Smart card access is supported only with the Windows, Linux, and macOS clients. It's not supported withthe web browser client.


To use a smart card

1. Launch the client and connect to the NICE DCV session.

2. Connect the smart card to the session or release it.

While your smart card is connected, no other clients who are connected to the session can connect asmart card. This is because only one client can connect a smart card at a time.

After you're done using the smart card in the DCV session, release it. After it's released, other clientswho are connected to the session can connect a smart card. The smart card is automatically releasedwhen you disconnect from the session.

a. In the client, choose Settings, Removable Devices.

b. To connect a smart card, enable the Smart Card toggle. To release control of the smart card,disable the Smart Card toggle.

21


NICE DCV User GuideUsing a smart card

3. (Optional) To have the NICE DCV server cache smart card data, enable the smart card cachingfeature. By default, smart card caching is disabled. With smart card caching enabled, the servercaches the results of recent calls to the client's smart card. This helps to reduce the amount of trafficthat is transferred between the client and the server and improves performance.

You can't enable smart card caching if it's permanently disabled on the server. For more information,see Configuring Smart Card Caching in the NICE DCV Administrator Guide.

To enable smart card caching, set and export the DCV_PCSC_ENABLE_CACHE environment variable.In the session, open a terminal window and run the following command:

• Windows server

To enable smart card caching for the current terminal window, run the following command.

C:\> set DCV_PCSC_ENABLE_CACHE=1

To enable smart card caching permanently for all applications on the server, run the followingcommand.

C:\> setx DCV_PCSC_ENABLE_CACHE 1

• Linux server

$ export DCV_PCSC_ENABLE_CACHE=1

NoteMake sure to run the following command in the same terminal that you intend to launchthe application from (in step 4).

4. (Linux NICE DCV server only) Launch the required application with smart card support. In thesession, open a terminal window, and launch the application using the dcvscrun command. Forexample, to launch firefox with smart card support, use the following command:

$ dcvscrun firefox

22

https://docs.amazonaws.cn/dcv/latest/adminguide/manage-smart-card.html

NICE DCV User GuideSaving a screenshot

ImportantIf you enabled smart card caching, run the following command in the same terminal thatyou set and exported the DCV_PCSC_ENABLE_CACHE environment variable in.

Saving a screenshotYou can use NICE DCV to save a screenshot of the NICE DCV session. This functionality is available onthe Windows, web browser, Linux, and macOS clients. The steps for saving a screenshot are similar on allclients.

You must be authorized to use this feature. If you aren't authorized, the functionality isn't available inthe client. For more information, see Configuring NICE DCV Authorization in the NICE DCV AdministratorGuide. If you aren't authorized to save screenshots, the client also avoids the external tools that arerunning on your client computer to capture a screenshot of the NICE DCV client. Images that areobtained by these tools either show a black rectangle instead of the NICE DCV client window or onlyshow the background desktop. This functionality is available only on Windows and macOS clients.

To save a screenshot

1. Launch the client, and connect to the NICE DCV session.2. In the client, choose Session, Save a Screenshot.

3. Choose a location and the name for the screenshot file.

Collaborating NICE DCV sessionsYou can collaborate with other users in a session using the NICE DCV clients. Users can join any sessionsthey are authorized to access and session owners can disconnect users from any session collaboration.

23

https://docs.amazonaws.cn/../adminguide/security-authentication.html

NICE DCV User GuideUsing multiple screens

To collaborate on the NICE DCV session:

1. On the NICE DCV client, choose Collaborators.

2. On the Collaborators Window, all users connected to the NICE DCV session are listed.

3. Choose Disconnect to remove an user from an active session.

Using multiple screensYou can use the NICE DCV clients to extend the display for a session across multiple screens.

With the Windows, Linux, and macOS clients, the extended display matches your physical displaylayout and screen resolutions. For example, assume that you have three screens connected to your localcomputer. The server extends the display for a session across all three screens and matches the specificscreen resolutions of your displays.

With the web browser client, the session display can be extended to up to two screens with 1920x1080screen resolution. When the display is extended, the additional screen is opened in a new browserwindow. The second extends the display to the right of the original screen. Ensure that you position thescreens accordingly.

You can also manually specify custom display layouts. For more information, see Managing the NICEDCV Session Display Layout in the NICE DCV Administrator Guide.

NoteIf the requested layout isn't supported by the server, the layout might be adjusted to match thedisplay limits of your server. If the layout can't be adjusted, the request fails and the changesaren't applied.

To extend the display

Do one of the following depending on your client.

• Windows and Linux clients

In the client, choose Enter fullscreen, Across all monitors.

24



NICE DCV User GuideUsing USB remotization

• macOS client

In the client, choose View, Full Screen All Monitors.

• Web browser client

In the client, choose Multiscreen.

After you extend the displays or enter fullscreen mode, a tab appears at the top-center edge of thescreen. To exit fullscreen mode, choose the tab and then Exit fullscreen.

Using USB remotizationNICE DCV allows you to use specialized USB devices, such as 3D pointing devices and two-factorauthentication USB dongles. These devices must be physically connected to your computer to interactwith an application that's running on a NICE DCV server.

Graphic tablets, gamepads, and smart card readers are automatically supported by NICE DCV and do notrequire USB remotization to be used.


25


NICE DCV User GuideUsing a webcam

NoteUSB remotization is only supported in the installable Windows client. It isn't supported bythe portable Windows client, web browser client, Linux client, or macOS client. Additionalconfiguration might be required on the NICE DCV server. For more information and instructions,see Enabling USB Remotization in the NICE DCV Administrator Guide.

By default, the most commonly used USB devices are supported. For these devices, you can connectthem to your computer and use them on the server without any additional configuration required. To usea USB device, connect it to your computer. In the client, choose Settings, and then move the slider nextto the USB device in the list.

However, some specialized USB devices aren't supported in the default configuration. Unsupporteddevices don't appear in the Settings menu after they're connected. These devices must be added to theUSB device allow list on the NICE DCV server before they can be used. After they're added to the allowlist, they appear in the Settings menu in the client.

To use a device that must be added to the allow list on the NICE DCV server

1. Ensure that you installed the latest version of the Windows client and that you opted to install theUSB remotization drivers. For more information, see Installable Windows client (p. 4).

2. Ensure that the USB device is connected to your computer and that you installed the requiredhardware drivers.

3. Navigate to C:\Program Files (x86)\NICE\DCV\Client\bin\ and run dcvusblist.exe.

4. Open the context (right-click) menu for the USB device in the list and choose Copy filter string.Then, send the filter string to your NICE DCV server administrator.

NoteThe NICE DCV server administrator adds the filter string for each USB device to the allowlist. For more information, see Enabling USB Remotization in the NICE DCV AdministratorGuide.

5. After the device is added to the allow list on the NICE DCV server, choose Settings. Then, move theslider next to the USB device to use it.

Using a webcamWith NICE DCV, you can use a webcam connected to your local client computer in a remote applicationthat runs in a NICE DCV session. For each session, only one connected client can use a webcam at a time.This is especially important in environments where multiple clients connect to the same session.

Webcam functionality is supported with all NICE DCV clients. However, with the web browser client,webcam functionality is only supported with Chromium-based browsers, such as Google Chrome orMicrosoft Edge. It isn't supported on Mozilla Firefox or Apple Safari.

Webcam functionality is supported on Windows NICE DCV servers only. It's not supported on Linux NICEDCV servers.


If you have multiple webcams connected to your local client computer, you can select the webcam thatyou want to use. The selected camera is used automatically when the webcam is enabled using thewebcam toolbar icon.

Topics

26

https://docs.amazonaws.cn/dcv/latest/adminguide/manage-usb-remote.html



NICE DCV User GuideUsing a webcam on Windows, Linux and macOS clients

• Using a webcam on Windows, Linux and macOS clients (p. 27)

• Using a webcam on the web browser client (p. 29)

Using a webcam on Windows, Linux and macOSclientsThe steps for selecting the camera to use are similar across the Windows, Linux and macOS clients.

To select the webcam to use


2. Do one of the following depending on your client.

• Windows and Linux clients

Choose Settings, Camera and then select the webcam to use.

• macOS client

Choose Connection, Camera Settings and then select the webcam to use.

27

NICE DCV User GuideUsing a webcam on Windows, Linux and macOS clients

Note

• The camera menu items appears only if you're authorized to use a webcam in the session. Ifyou don't see the camera menu items, you might not be authorized to use a webcam.

• You can't change the webcam selection while the webcam is in use, or while another clientenabled a webcam in the session.

To start using your webcam in a session

You must first enable it. Use the webcam icon on the toolbar to enable or disable your webcam for usein the session. You can also use the icon to determine its current state. The webcam icon appears on thetoolbar only if the following is the case:

• You're authorized to use a webcam.

• You have at least one webcam connected to your local computer.

• No other users enabled a webcam for use in the session.

Toolbar icon Description

Your webcam is disabled in the session. Other clients can enable a webcamfor use in the session.

Click the icon to enable your webcam in the session. If you didn't previouslyselect the webcam to use, the default webcam is used.

28

NICE DCV User GuideUsing a webcam on the web browser client


Your webcam is enabled in the session, but it isn't in use. While your webcamis enabled, no other clients that are connected to the session can use awebcam.

Click the icon to disable your webcam in the session.

Your webcam is in use by a remote application in the NICE DCV session. Noother clients can enable a webcam while your webcam is in use.


TroubleshootingTopics

• Webcam doesn't work on Windows 10 (p. 29)

• Client application says that the webcam is in use (p. 29)

Webcam doesn't work on Windows 10

Windows 10 provides built-in privacy settings that manage access to the device camera. If you're runningWindows 10 on your client computer, these privacy settings might prevent use of the webcam.

NoteIf you're connecting to a Windows 2019 NICE DCV server, you might need to perform thesesteps on the NICE DCV server as well.

To modify the privacy settings on your computer, do the following:

1. Choose the search icon on the toolbar.

2. Enter Settings and press Enter.

3. In the left-hand panel, choose Camera.

4. For Allow apps to access your camera, switch the toggle to the On position.

5. You might need to restart your computer for the changes to take effect.

Client application says that the webcam is in use

Only one application can use the webcam at a time. If you're using the webcam in multiple applications,first close the applications where it's no longer needed.

Using a webcam on the web browser clientWebcam functionality is only supported with Chromium-based browsers, such as Google Chrome orMicrosoft Edge. It isn't supported on Mozilla Firefox or Apple Safari.

The steps for selecting the camera to use are the same across all supported web browsers..

To select the webcam to use



29

NICE DCV User GuideUsing a webcam on the web browser client

3. Under the Camera tab, select the camera to use.

4. Close the Preferences modal.

Note

• The camera menu items appears only if you're authorized to use a webcam in the session. Ifyou don't see the camera menu items, you might not be authorized to use a webcam.

• You can't change the webcam selection while the webcam is in use, or while another clientenabled a webcam in the session.

• If the camera permission settings have not been expressly granted or denied by the user,you're prompted to allow camera detection before being able to select the camera to use.

• In case the camera permission settings have been expressly granted or denied by the user, youwould be able to change such setting following this procedure:

1. At the top left of your browser window, click the area on the address bar left of the URL.2. In the popup window that opened, select the desired camera permission setting to be

applied.

To start using your webcam in a session

You must first enable it. Use the webcam icon on the toolbar to enable or disable your webcam for usein the session. You can also use the icon to determine its current state. The webcam icon appears on thetoolbar only if the following is the case:

• You're authorized to use a webcam.• You have at least one webcam connected to your local computer.• No other users enabled a webcam for use in the session.


Your webcam is disabled in the session. Other clients can enable a webcamfor use in the session.

Click the icon to enable your webcam in the session. If you didn't previouslyselect the webcam to use, the default webcam is used.

30

NICE DCV User GuideUsing accurate audio/video synchronization


Your webcam is enabled in the session, but it isn't in use. While your webcamis enabled, no other clients that are connected to the session can use awebcam.


Your webcam is in use by a remote application in the NICE DCV session. Noother clients can enable a webcam while your webcam is in use.


Troubleshooting

Client application says that the webcam is in use

Only one application can use the webcam at a time. If you're using the webcam in multiple applications,first close the applications where it's no longer needed.

Using accurate audio/video synchronizationThe Accurate Audio/Video synchronization setting enables a mode that minimizes the time differencein audio and video playback. This mode improves lip sync. This mode is useful in workloads that requirethe video and audio to be accurately synchronized. This feature might introduce a lag in the perceivedresponsiveness of the remote system.

Accurate Audio/Video Synchronization functionality is supported on all native clients.

Accurate Audio/Video Synchronization functionality is supported on Windows and Linux servers withhardware GPU acceleration, and for console sessions only.

To enable or disable Audio/Video Synchronization


2. Do one of the following depending on your client.

• Windows, and Linux clients

Choose Settings, Accurate Audio/Video Synchronization

31

NICE DCV User GuideUsing accurate audio/video synchronization

• macOS client

Choose Connection, Accurate Audio/Video Synchronization

32

NICE DCV User GuideUsing high color accuracy

Using high color accuracyBy default, NICE DCV uses YUV 4:2:0 chroma subsampling when compressing the display outputand then updates the parts of the screen that are not changing over time to a full lossless RGBimplementation. This default behavior aims to strike a balance between performance and image fidelity,though it may introduce chroma artifacts. By enabling the High color accuracy setting, the YUV chromasubsampling will be set to 4:4:4, thus increasing color fidelity. However this will increase networkbandwidth and could affect performance of clients, especially at high resolution, because most clientmachines do not support HW accelerated decoding when using YUV 4:4:4.

The steps for setting the high color accuracy depend on the client used.

Topics• High color accuracy on native clients (p. 33)• High color accuracy on Web browser client (p. 33)

High color accuracy on native clientsAs long as you are using a NICE DCV Server and a NICE DCV Client both having version 2022.0 or later,please follow these steps to enable high color accuracy:

1. In the client, choose Settings, Streaming Mode.

2. In the Streaming Mode window, the High color accuracy (YUV 4:4:4) checkbox allows to enable ordisable the corresponding feature.

3. Close the Streaming Mode window.

High color accuracy on Web browser clientIn order to use high color accuracy on Web browser client you need a NICE DCV Server with version2022.0 or later, as well as a browser supporting the VideoDecoder interface of the Web Codecs API.

The steps for enabling the high color accuracy are the same across all supported web browsers.


33

https://developer.mozilla.org/en-US/docs/Web/API/VideoDecoder

NICE DCV User GuideUsing a connection file

2. Under the Display tab, if the high color accuracy feature is available, the corresponding toggle willbe visible and allows to specify whether to enable or disable the YUV chroma subsampling set to4:4:4:

3. Save and close the Preferences modal.

Using a connection fileUsing the Windows, Linux, or macOS native client, you can create a connection file that you can use toinstantly connect to a NICE DCV session.

Contents

• Creating the connection file (p. 34)

• Supported parameters (p. 35)

• Running the connection file (p. 39)

Creating the connection fileThe connection file is a text-based file with a .dcv file extension. The format of the .dcv file is similar tothat of an .ini file. The file includes [groups] followed by the parameters and their values. The groupsand parameters take the following format:

[group_name]parameter_name=parameter_value

For example:

[options]fullscreen=true

For the Windows client, you can create a connection file for a specific NICE DCV session directly from theclient. Or, alternatively, you can create a connection file from scratch using a text editor. For the Linuxand macOS clients, you can only create a connection file from scratch using a text editor.

34

NICE DCV User GuideSupported parameters

NoteThe procedure for creating a connection file from scratch using a text editor is the same for theWindows, Linux, and macOS clients.

To create a connection file from the Windows client

1. Open the Windows client and connect to the server and session to create the file from.2. Select the hostname for the NICE DCV server in the top-right corner and choose Save Connection

As.3. In the Save As window, enter a file name and destination folder, and choose Save.

By default, when you create a connection file using the Windows client, the file includes the format,host, port, user, and proxytype parameters. These parameters are required to connect to the sessionthat the file was created from. You can manually customize or add parameters at any time by editing thefile using a text editor.

To create a connection file from scratch using a text editor

1. Create a .dcv file with the following file name format: file_name.dcv2. Open the .dcv file using your preferred text editor.3. Add the [version] group and format parameter to the top of the file in the following format:

[version]format=1.0

ImportantIf the .dcv file doesn't include the [version] group and format parameter, parsing fails.

4. Add the required parameter groups using the following format:

[group_name]

For more information about the parameter groups, see Supported parameters (p. 35).5. Add the parameters and parameter values after the groups using the following format:

parameter_name=parameter_value

Note

• Parameter names are case sensitive.• Don't enclose string parameter values in quotation marks.

For more information about the parameters and parameter values, see Supportedparameters (p. 35).

6. Save the changes and close the .dcv file.

You can also use this procedure to add additional parameters to an existing connection file at any time.

Supported parametersCurrently, the .dcv file supports parameters in three parameter groups—[version], [connect], and[options]. The following tables list the groups and their available parameters.

35


Groups• [version] parameters (p. 36)• [connect] parameters (p. 36)• [options] parameters (p. 38)

[version] parametersImportantThis is a required group. If your .dcv file doesn't include this group, parsing fails.

The following table lists the parameters that can be specified in the [version] group.

Parameter Type Defaultvalue

Description

format string ImportantThis is arequiredparameter.Theparametervalue mustbe 1.0.If your .dcvfile doesn'tinclude thisparameter,parsing fails.

[connect] parametersThe following table lists the parameters that can be specified in the [connect] group.


Description

host String The hostname ofthe NICE DCV serverhosting the session.

port Integer 8443 The port to usewhen connecting tothe NICE DCV server.

weburlpath String A custom path onthe NICE DCV serverfor connection.For example,if you specifycustomPath, theclient attemptsto connect tohost:port/customPath.

36



Description

sessionid String The ID of the NICEDCV session toconnect to.

authtoken String The authenticationtoken to be usedfor the connection.If you specify anauthtoken, youmust also specify asessionid. Whenusing authtoken,you can omit theuser and passwordparameters.

user String The user name touse when connectingto the NICE DCVserver.

password String The password to usewhen connecting tothe NICE DCV server.The password isn'tencrypted.

proxytype String SYSTEM The proxy type to beused. Valid valuesinclude HTTPS,HTTP, SOCKS5|SOCKS, SYSTEM, orNONE|DIRECT. Ifyou specify SYSTEM,your computer'sproxy settings areused.

proxyhost String The address of theproxy server to beused if connectingthrough a proxyserver.

proxyport Integer The port to beused if connectingthrough a proxyserver.

proxyuser String The user name tobe used for proxyauthentication.

37



Description

proxypassword String The password tobe used for proxyauthentication.The password isn'tencrypted.

transport String websocketThe protocolto use for datatransport. Specifywebsocket to usethe WebSocket (TCP)protocol for datatransport, or specifyquic to use theQUIC (UDP) protocolfor data transport.If you enable QUIC,the QUIC protocolis used for datatransport andWebSocket is usedfor authenticationtraffic. If you enableWebSocket, theWebSocket protocolis used for bothdata transport andauthenticationtraffic.

webport Integer 8443 The port to use forWebSocket (TCP)traffic.

quicport Integer 8443 The port to use forQUIC (UDP) traffic.

certificatevalidationpolicyString ask-user The policy forvalidating anuntrusted certificate.Values includestrict, accept-untrusted, andask-user.

[options] parameters

The following table lists the parameters that can be specified in the [options] group.

38

NICE DCV User GuideRunning the connection file


Description

fullscreen Boolean false Indicates whetherthe client starts infull screen mode.

useallmonitors Boolean false Indicates whetherthe client uses allmonitors whenstarting full screenmode.

promptreconnect Boolean true Indicates whetherthe client promptsyou to reconnectafter you disconnectfrom a session. Ifthe parameter isset to true, you'reredirected to thesign-in screen whenyou disconnect. Ifthe parameter is setto false, the clientcloses when youdisconnect.

enableyuv444decodingBoolean false Indicates whetherto enable the Highcolor accuracy (YUV4:4:4) (p. 33)when encodingdynamic videocontent.

Running the connection fileTo run .dcv connection file, navigate to the file and double-click it.

Or, specify the file path as an argument for the dcvviewer command.

• Windows client

C:\> dcvviewer.exe path\connection_file_name.dcv

• Linux and macOS client

$ dcvviewer path/connection_file_name.dcv

39

NICE DCV User GuideSetting certificate validation

Set certificate validation policyNICE DCV uses a secure TLS connection for communication between the server and client. The certificatevalidation policy determines how the NICE DCV client responds when a certificate can't be verified astrustworthy. Set one of the following options in the connection file:

• Strict: Prohibits the connection if there is any problem validating the TLS certificate.• Ask user: Prompts the user to determine whether to trust the certificate when a certificate can't be

verified.• Accept untrusted: Connects to the server even if the TLS certificate is self signed and can't be

validated by the client.

For information about editing the connection file, see ??? (p. 34).

40

NICE DCV User GuideUsing the Log Files

Troubleshooting NICE DCVThis chapter describes how to identify and troubleshoot problems that you might have with NICE DCVclient.

Topics• Using the Log Files (p. 41)

If you are a NICE DCV on-premises customer and you need additional help, contact your NICE DCVreseller to get the first level of support. If you are using NICE DCV on Amazon EC2, you can log a supportticket with Amazon support. If you do not have an Amazon support plan, you can seek help from theNICE DCV community by posting your question on the Amazon forum.

Using the Log FilesUse the NICE DCV client log files to identify and troubleshoot problems with your NICE DCV client. Logsaren't enabled by default on Windows clients. After logs are enabled, the log files are stored in thefollowing location on your NICE DCV client:

• Windows client

C:\ProgramData\client.log

NoteBy default, the ProgramData folder might be hidden. If you don't see the ProgramDatafolder, set your file browser to show hidden items. Alternatively, enter %programdata% in theaddress bar and press Enter.

• Linux or macOS client

~/.local/share/NICE/dcvviewer/log/viewer.log

To enable NICE DCV to store log files on a Windows client

1. Navigate to the folder where the dcvviewer.exe file is located. (By default, this is C:\ProgramFiles (x86)\NICE\DCV\Client\bin\.) Then, open a command prompt window.

2. Launch NICE DCV client using the command line interface.

dcvviewer --log-level info --log-file-name C:/ProgramData/client.log

Or add the following configuration to the connection file (p. 34):

[debug]logfilename=C:/ProgramData/client.logloglevel=info

41

https://forums.aws.amazon.com/forum.jspa?forumID=366

NICE DCV User GuideRelease Notes

Release notes and document historyfor NICE DCV

This page provides the release notes and document history for NICE DCV.

Topics

• NICE DCV release notes (p. 42)

• Document history (p. 61)

NICE DCV release notesThis section provides an overview of the major updates, feature releases, and bug fixes for NICE DCV.All the updates are organized by release data. We update the documentation frequently to address thefeedback that you send us.

Topics

• DCV 2022.1-13216— July 21, 2022 (p. 43)

• DCV 2022.1-13067— June 29, 2022 (p. 43)

• DCV 2022.0-12760— May 23, 2022 (p. 44)

• DCV 2022.0-12627— May 19, 2022 (p. 44)

• DCV 2022.0-12123— March 23, 2022 (p. 45)

• DCV 2022.0-11954— February 23, 2022 (p. 45)

• DCV 2021.3-11591— December 20, 2021 (p. 46)

• DCV 2021.2-11445— November 18, 2021 (p. 46)

• DCV 2021.2-11190— October 11, 2021 (p. 47)

• DCV 2021.2-11135— September 24, 2021 (p. 47)

• DCV 2021.2-11048— September 01, 2021 (p. 48)

• DCV 2021.1-10851— July 30, 2021 (p. 49)

• DCV 2021.1-10598— June 10, 2021 (p. 49)

• DCV 2021.1-10557— May 31, 2021 (p. 50)

• DCV 2021.0-10242— April 12, 2021 (p. 50)

• DCV 2020.2-9662— December 04, 2020 (p. 51)

• DCV 2020.2-9508— November 11, 2020 (p. 51)

• DCV 2020.1-9012— September 30, 2020 (p. 52)

• DCV 2020.1-9012— August 24, 2020 (p. 52)

• DCV 2020.1-8942— August 03, 2020 (p. 52)

• DCV 2020.0-8428 — April 16, 2020 (p. 53)

• DCV 2019.1-7644 — October 24, 2019 (p. 54)

• DCV 2019.1-7423 — September 10, 2019 (p. 54)

• DCV 2019.0-7318 — August 5, 2019 (p. 54)

42

NICE DCV User GuideNICE DCV 2022.1-13216

• DCV 2017.4-6898 — April 16, 2019 (p. 55)• DCV 2017.3-6698 — February 24, 2019 (p. 56)• DCV 2017.2-6182 — October 8, 2018 (p. 58)• DCV 2017.1-5870 — August 6, 2018 (p. 59)• DCV 2017.1-5777 — June 29, 2018 (p. 59)• DCV 2017.0-5600 — June 4, 2018 (p. 59)• DCV 2017.0-5121 — March 18, 2018 (p. 60)• DCV 2017.0-4334 — January 24, 2018 (p. 60)• DCV 2017.0-4100 — December 18, 2017 (p. 60)

DCV 2022.1-13216— July 21, 2022

Build numbers Changes and bug fixes

• nice-dcv-server: 13216• nice-dcv-client (Windows): 8261• nice-dcv-viewer (macOS): 4251• nice-dcv-viewer (Linux): 4251• nice-xdcv: 433• nice-dcv-gl: 966• nice-dcv-gltest: 295• nice-dcv-simple-external-authenticator: 193

• Fixed a problem in all clients that resulted in afailure to connect to NICE DCV server 2019.1and older.

• Fixed a problem with SmartCard redirection onWindows server.

• Fixed a problem that could cause the streamingto fail when connecting to a NICE DCV server ona host with a GPU.

DCV 2022.1-13067— June 29, 2022

Buildnumbers

New features Changes and bug fixes

• nice-dcv-server: 13067

• nice-dcv-client (Windows):8248

• nice-dcv-viewer(macOS):4241

• nice-dcv-viewer(Linux):4241

• nice-xdcv:433

NICE DCV added the following features:

• Added support for Ubuntu 22.04 and RockyLinux 8.5 and higher for the server.

• Added support for Ubuntu 22.04 for the nativeclient.

• Improved collaboration experience for theWindows, macOS and Linux native clients.

• Improved performance, up to a30% reduction of overall CPUconsumption on non-GPU servers.

• Log rotation can now beconfigured in the settingsspecifying a time interval or a sizelimit.

• Fixed problems in the QUICtransport which could cause theinitial handshake to fail.

• Fixed a problem that could causerelative mouse motion on Linuxserver to not work as expected forsome applications.

43


Buildnumbers

New features Changes and bug fixes

• nice-dcv-gl:966

• nice-dcv-gltest:295

• nice-dcv-simple-external-authenticator:193

DCV 2022.0-12760— May 23, 2022



Changes:

Fixed a problem preventing successful connectionof the Web Client when specifying the web-url-path option.

DCV 2022.0-12627— May 19, 2022



Changes:

• Fixed some problems in the QUIC transportwhich could cause incorrect bandwidthestimation and visual artifacts.

• Fixed a problem with the Audio service in theinstaller of the Windows server which couldcause the update process to fail.

• Fixed a problem with the USB handling in theinstaller of the Windows client which couldcause the uninstall process to fail.

• Fixed a problem when saving a screenshot inthe macOS and Linux clients.

• Updated the OpenSSL, zlib and gdk-pixbuf thirdparty libraries.

44


DCV 2022.0-12123— March 23, 2022

Build numbers New features Changes and bug fixes

• nice-dcv-server: 12123• nice-dcv-client (Windows):

7920• nice-dcv-viewer (macOS):

3973• nice-dcv-viewer (Linux): 3973• nice-xdcv: 424• nice-dcv-gl: 961• nice-dcv-gltest: 291• nice-dcv-simple-external-

authenticator: 188

NICE DCV added the followingfeatures:

• Added option to enable highcolor accuracy to the macOSand Linux clients.

Changes:

• Improved bandwidthestimation and imagequality when using the QUICtransport.

Fixes:

• Fixed visual artifacts inconsole sessions on Linuxwhen using NVIDIA drivers510.xx.

• Fixed problem with DualShock4 controllers connected viaBluetooth in the Windowsnative client.

• Fixed possible crash in themacOS client when enablingthe webcam.

DCV 2022.0-11954— February 23, 2022





authenticator: 188


• Game controller support forWindows Server and Windowsnative client.

• The NICE DCV Web Clientnow leverages WebCodecs onbrowsers that support it.

• Added option to enable highcolor accuracy to the Windowsand Web clients.

• Improved collaborationexperience: users get notifiedwhen someone joins thesession

• Added CentOS 8 Stream tothe list of supported Linuxdistributions.

Changes:

• TLS certificates can now beupdated without restartingthe NICE DCV Server.

• It is now possible to configurethe NICE DCV Server to listenon a specific network interfaceor on specific IPv4 or IPv6addresses.

• The 'DCV Printer' is nowautomatically configured alsoon Linux systems.

• The NICE DCV processes onWindows are now executed athigher priority.

Fixes:

• Fixed a crash on agent restarton Windows 2016 when usinginstances with a GPU.

45



• Fixed a crash on Windowswhen logging out of a sessionwhile some USB devices areredirected from the NICE DCVClient.

• Normalize user namesthat contain a Windowsdomain when performingauthorization checks.

• Improved relative mousemode in the Windows Client.

• Fixed a problem with thesynchronization of theCapsLock key.

DCV 2021.3-11591— December 20, 2021





authenticator: 176


• The user interface of the WebClient has been updated.

• EC2 G5 and G5g instances arenow supported.

• Windows Server 2022and Windows 11 are nowsupported operating systems.

• The init script for Linux virtualsessions does not load theuser's bash profile anymore,thus avoiding recurringproblems with environmentvariables overriding thesystem's default values.

• The nice-dcv-ext-authenticator now requiresPython 3.

DCV 2021.2-11445— November 18, 2021



Fixes:

• Fixed a problem preventing the client fromworking correctly on macOS Monterey.

• Improved security in the server on Windows.• Fixed a bug which could cause multi-monitor

layouts to not be applied correctly, in particularwhen using the Web Client.

• Fixed a problem which could cause the Deletekey to not work correctly with some Windowsapplications.

46



• Marked the Web client package on Linux asmutually exclusive with old versions of theserver package, which included the Web clientitself.

DCV 2021.2-11190— October 11, 2021



Fixes:

• Fixed a problem in the Windows client whichprevented the user from dismissing thecertificate validation dialog when connecting toa server with an expired certificate.

• Fixed a problem with the middle click button onStylus pens not working as expected on nativeclients.

• Fixed a regression in Xdcv which preventedlegacy X11 fonts to be loaded.

• Fixed a problem in the macOS and Linux clientswith keyboard combinations not workingcorrectly when using a keyboard layout whichuses dead keys.

DCV 2021.2-11135— September 24, 2021



Fixes:

• Fixed a problem with QUIC packet sizenegotiation that can cause connectivity andperformance problems when using a 2021.2client to connect with an older server.

• Fixed a bug with NVIDIA device selection thatcould cause NVENC encoder to fail.

• Fixed problems on machines with Windows anda NVIDIA GPU that could cause compressionartifacts and color accuracy artifacts.

• Fixed a bug with modifier keys on Linux serverwhich could cause some keyboard combinationsto not work as expected.

• Fixed a performance regression for macOSclients on machines with the M1 CPU.

• Fixed a bug in the macOS client which wouldcause some keyboard combinations to not workas expected.

47



• Fixed a problem with how touch events arehandled in Linux virtual sessions that couldcause termination of the session.

DCV 2021.2-11048— September 01, 2021





authenticator: 160


• Web client clipboardimprovements. With theseimprovements, you can nowcopy and paste PNG formatimages using the NICE DCVweb client on Google Chromeand Microsoft Edge.

• A screenshot blocking featurefor the Windows and macOSclients. This feature adds anadditional layer of securityby preventing users fromtaking screenshots of NICEDCV session content. Whenenabled, any screenshots thata user capture result in a blankscreen.

• Streaming qualityimprovements. Streamingquality improved specificallythrough better “build-to-lossless” performance whenusing the QUIC protocol.

• A certificate-validation-policy optionto specify the behavior ofyour client was addded. Youcan use it when the serverpresents an untrusted X.509certificate, such as a self-signed certificate.

• The number of channelsconfigured in the Audio Driverat run time can be changed.

• The Pressure2K option wasadded to the dcvinputXorg module. You can usethis to change the pressuresensitivity range of thestylus from 0-65335 to0-2048, for compatibility with

Changes:

• The NICE DCV web clientis now a separate packageon Linux and an optionalcomponent in the Windowsinstaller. With this change,customers can decide whetherto deploy the web client.

• The H.264 High Profile is nowsupported when the NVENCencoder is used. Using NVENCencoder with NVIDIA GPUs,you can reduce bandwidthusage while maintaining thesame image quality.

• NICE DCV server now usesall available GPUs forcompression on machines withmore than one GPU.

• All Windows drivers shippedwith NICE DCV are now WHQLcertified.

• OpenSSL was updated toversion 1.1.1.

• Xdcv was updated to version1.20.13 of XServer.

Fixes:

• Fixed a problem with numpadkeys on macOS clients.

• Fixed an issue that preventedsome USB devices (forexample, gamepads) tobe properly redirected toWindows servers.

• Fixed a bug where modifierkeys couldn't be properlyreleased on disconnection.

48

NICE DCV User GuideDCV 2021.1-10851


applications, such as Mari andNuke

• Support for the experimentalWebCodecs API on GoogleChrome and Microsoft Edgewas added. When you enablethis API in the browser, theNICE DCV web client can use itto accelerate video decodingand deliver higher frame rates.

• Fixed a crash in the Linuxnative client when usingUbuntu 20.04 and Intel GPUs.

DCV 2021.1-10851— July 30, 2021



Changes:

• We improved stability on the Windows, Linux,and macOS clients.

Fixes:

• Fixed a bug that caused screen flickering withAMD and NVIDIA graphic adapters on Windowsservers.

• Fixed a sporadic issue when connecting to aLinux server running multiple sessions.

• Fixed bugs that were related to handling ofnon-western keyboard layouts on Linux server.

• Fixed visual artifact on the connection windowin the Windows client.

• Fixed several bugs and improved devicecompatibility in the USB redirection driver onWindows.

DCV 2021.1-10598— June 10, 2021



• Fixed a problem in the Windows installer of theserver to prefill the session owner field withthe current user.

• Improved the overall stability of the macOS andLinux clients.

49


DCV 2021.1-10557— May 31, 2021





authenticator: 154

• NICE DCV added client optionto enable accurate Audio/Video synchronization whenconnecting to a server with aGPU.

• NICE DCV added support formicrophone on Linux consolesessions.

• Reduced CPU usage onWindows server hosts withouta GPU.

• Fixed a problem with reading.dcv connection files in themacOS and Linux clients.

• Added fallback to softwaredecoding for macOS machinesthat don't support hardwareaccelerated decoding.

• Added support for macOSclient to read CA certificatesthat are stored in the systemkeychain.

DCV 2021.0-10242— April 12, 2021





authenticator: 134

• Added webcam redirectionsupport for Windows NICEDCV servers.

• Added printer redirectionsupport for Linux NICE DCVservers.

• Added support for M1processors on macOS clients.

• Added multi-monitor displaysupport for macOS clients.

• Optimized GPU and CPUresource usage on Linuxservers and on Amazon EC2instances with an NVIDIA GPU.

• Added support for GPUaccelerated video encodingusing AMD GPUs on AmazonEC2 G4ad instances for LinuxNICE DCV servers.

• Optimized audio processing toreduce audio latency

• Changed the default forclients to the QUIC protocol ifthe protocol is enabled on theserver.

• Added a new get-screenshotcommand to the DCVcommand line tool.

• Added a force logout optionthat uses the --logout-user option of the close-session command. You canuse this option when closing aconsole session.

50


DCV 2020.2-9662— December 04, 2020



• Enhanced the security protocols used in the webbrowser client.

• Increased performance and robustness ofAmazon EC2 G4ad instances used with theWindows client.

• Fixed a problem with port selection in theconnection settings dialog of the Windowsclient.

DCV 2020.2-9508— November 11, 2020





authenticator: 125

• Added support for the QUIC(UDP-based) transportprotocol.

• Added support for SLES 15and Ubuntu 20.4.

• Added smart card support forWindows NICE DCV servers.

• Changed the default the NICEDCV frame rate limiter to 60FPS for console sessions thatare hosted on servers and EC2instances with an NVIDIA GPU.

• Optimized the GPU and CPUresources used on WindowsNICE DCV servers that arehosted on EC2 instances withan NVIDIA GPU.

• Added the list-endpointsNICE DCV CLI command.This lists the current activeendpoints.

• The version NICE DCV CLIcommand supports the --json option.

• On Linux servers, the create-session NICE DCVCLI command now supportsthe --disable-login-monitor option.

• Improved compatibility withdifferent display managers onLinux NICE DCV servers.

• Fixed several issues in thehandling of keyboard input.

• The USB devices allow list fileis now dynamically reloaded.

51


DCV 2020.1-9012— September 30, 2020



• Added missing macOS client icons.

DCV 2020.1-9012— August 24, 2020



• Fixed Amazon S3 access in Amazon GovCloudRegion

• Web-based client improvements

DCV 2020.1-8942— August 03, 2020





authenticator: 111

• The Linux NICE DCV servernow supports AmazonGraviton2-based Arminstances, such as M6g,C6g, and R6g. For moreinformation, see AmazonGraviton Processor.

• Added support for RHEL 8.xand CentOS 8.x on Linux NICEDCV server.

• Added support for printerredirection when using aWindows NICE DCV server andthe Windows NICE DCV client.

• Added stylus support withpressure sensitivity on macOS

• Added support for the newNICE DCV Virtual Displaydriver on Amazon EC2instances that don't have aGPU.

• Resolved the issue that causedvisual artifacts as a result ofcolorspace conversion whenusing the NVENC encoder.

• The dcv list-sessionscommand now alwaysincludes the console session, ifone is present

• On newer Linux distributions,the agent for console sessionsis now started as part ofthe desktop session to

52

http://www.amazonaws.cn/ec2/graviton/

http://www.amazonaws.cn/ec2/graviton/



and Linux native NICE DCVclient.

• Added surround sound 5.1support for Linux NICE DCVserver and Linux NICE DCVclient.

• Added touch screen supportfor Linux NICE DCV nativeclient.

• You can now associate acustom name to a NICE DCVsession.

• Support for hardwareaccelerated decoding andrendering on the macOSnative NICE DCV client.

better support newer displaymanagers, such as GDM3.

• Native clients nowautomatically open whenactivating a URL with thedcv:// scheme.

• Improved how the macOSnative client and web clienthandle keyboard modifiers.

• Improved visual and fbconfigselection in DCV-GL toimprove support for someapplications.

• Reduced CPU usage during filetransfer

• Improved WebGL renderingin the web browser client toreduce resource usage.

DCV 2020.0-8428 — April 16, 2020





authenticator: 87

• Added on-screen stylus andtouch support on Linux server.

• Added 7.1 surround soundplayback support on Windowsserver to Windows nativeclient.

• Added hardware accelerationand stylus support on Linuxnative client.

• Added a new API commandto set display layout on theserver side.

• Added multi-monitor webclient display support onthe Microsoft Edge browser(version 79.0.309 or later).

• The toolbar grip on theWindows client can now behidden while in full screenmode.

• Added NTLM proxy support onWindows native client.

• Improved support forWindows headless physicalhosts using NVIDIA adapters.

• Removed support for thelegacy NVIDIA NvIFR library.

• Added support for WindowsGraphic Capture API on latestWindows 10.

• Added support for AmazonEC2

Instance Metadata Service(IMDS) v2 on EC2 instances.

• DCV CLI providesnew on-client-connected/disconnectedcommands to detect when aclient connects or disconnectsfrom a session.

• Added support for specifyingthe host name to bind

53



certificates for the externalauthenticator.

• DCV-GL now uses the GLVendor-Neutral Dispatchlibrary (GLvnd) on systemsthat support it.

DCV 2019.1-7644 — October 24, 2019



• Fixed an issue in the integration API used byNICE EnginFrame and other session managers.

• Fixed an issue with the 32-bit version of theWindows native client.

DCV 2019.1-7423 — September 10, 2019



• Improved security for DCV server on Windows.• Fixed a rendering problem with Autodesk Maya

on Linux.• Added improvements and bug fixes related to

keyboard handling.

DCV 2019.0-7318 — August 5, 2019




1530• nice-dcv-viewer (Linux): 968

• Multiple monitor support onWeb client.

• Stylus input support onWindows Server 2019.

• Audio in/out on macOS andLinux native clients.

• Added improved compatibilityfor pressure sensitivity forWindows touch input.

• Improved behavior on systemsthat have heterogeneousgraphic adapters on Windows.

54



• nice-xdcv: 224• nice-dcv-gl: 529• nice-dcv-gltest: 218• nice-dcv-simple-external-

authenticator: 72

• Enhanced clipboard capabilityon Linux server (middle-clickpaste).

• Reduced time required todetect inactive connections(for example, in response tochanges from wired to Wi-Finetworks on the client).

• Reduced logging when thecursor icon can't be capturedon Linux.

• Support for disabling theComposite extension inthe virtual sessions Xdcvcomponent.

• Added the option to a limiton the number of concurrentvirtual sessions.

• Improved script compatibilityfor systems with Bash 5installed.

• Changed default for OpenGLand GLES to be detectedand used automatically forrendering on the Linux client.

• Updated the DCV-GL on-screen buffer when thevisibility of a GL windowchanges.

• Fixed the mouse wheeldetection in the Windowsclient on Windows 7.

• Fixed a problem that causedthe Windows client to failwhen loading libraries onsome Windows 7 systems.

• Improved printing on theWindows client when printingdocuments with landscapeorientation.

DCV 2017.4-6898 — April 16, 2019




1376• nice-dcv-viewer (Linux): 804• nice-xdcv: 210

• New native client for macOS. • The Windows nativeclient now uses hardwareacceleration for decoding andrendering, if available in thesystem.

• The dcv command line toolnow uses the same options

55



• nice-dcv-gl: 490• nice-dcv-gltest: 216• nice-dcv-simple-external-

authenticator: 70

and output format on bothWindows and Linux.

• The dcv command line toolnow reports informationabout licenses.

• Clients now show a warning tothe user before disconnectiondue to inactivity.

• Improved support forkeyboard combinations thatuse multiple modifiers.

• Improved robustness ofthe interaction with theReprise License Manager forcommunication failures.

• The dcvusers command linetool now defaults to savingdata to the dcv user homedirectory on Linux.

• Followed the same orderingused by the nvidia-smitool when using the NVENChardware encoder withmultiple GPUs on Linux.

• The Linux client now receivesand handles printed files fromthe Windows DCV printer.

DCV 2017.3-6698 — February 24, 2019


• nice-dcv-server: 6698• nice-dcv-client: 5946• nice-dcv-viewer (Linux): 683• nice-xdcv: 207• nice-dcv-gl: 471• nice-dcv-gltest: 210• nice-dcv-simple-external-

authenticator: 66

• Added support for Kerberos(GSSAPI) authentication.

• Added support for touchevents on Windows versionsthat support it.

• Automatically unlockWindows sessions whenusing system authentication(Windows CredentialProvider).

• Added an option to opt in toY'UV444 encoding.

• The EL6 RPM now includes theNVENC encoder module.

• Windows systemauthentication now acceptsthe name@domain format.

• Yubikey USB devices are nowadded to the allow list.

• Improved Japanese keyboardsupport.

• Input authorizationpermissions are more fine-grained. Added pointerpermission to handle virtualcursors. Relative mousemode depends on mouse(for motion injection) and

56



pointer (for motion feedback).Added keyboard-saspermission to handle SAS onWindows ( Control+Alt+ Del).keyboardsas depends onkeyboard permission.

• Fixed a problem with emptyclipboard events in the Webclient on browsers thatsupport the async clipboardAPI.

• Fixed a race on the capturemodule that prevented clientsfrom receiving the first frame.

• Improvements to handlingof concurrent file storagetransfers.

• Fixed NvIFR on Windows withnewer NVIDIA drivers. Newdrivers changed behavior.The driver version is nowdetected automaticallyand memory handling isperformed accordingly.

• Never stop retrying re-acquiring an RLM licensetoken. This allows you torecover from a licensingerror state even afterextended time periods.

• Added an option to set fullscreen keyboard shortcut inthe Windows client.

• Improved auto-fit logic whendragging window acrossmultiple monitors in theWindows client.

• Fixed the prompt-reconnectoption when disconnectionis not triggered by UIin theWindows client.

• Fixed DCV-GL incompatibilitywith NVIDIA driver 410.xx.

• Fixed regressions in DCV-GLwith the Matlab and Blenderapplications.

57


DCV 2017.2-6182 — October 8, 2018



authenticator: 58

• Added audio playback supporton Linux virtual sessions.

• Improved smart cardperformance.

• Added file transfer support onthe Linux client.

• Improvements and bug fixesrelated to keyboard handling.

• Changing the log level inthe configuration no longerrequires a server restart.

• The Windows server installernow skips installationof Microsoft C runtimeredistributable if it's alreadyinstalled.

• When running on EC2, ifaccessing S3 for the licensefails, a notification is displayedin the user interface.

• The Linux dcv commandline tool now supportslist-connections anddescribe-session sub-commands and includes anoption to emit JSON output.

• Added a cuda-devicessetting in the displaysection. This configures theserver to distribute NVENCencoding over different CUDAdevices.

• Improved robustness ofsession creation code whenhandling multiple concurrentcommands.

• Increased the defaultclipboard limit to 20 MB.

• The Windows client nowdetects legacy .dcv filesand launches the DCV 2016Endstation (if installed).

• The DCV simple externalauthenticator now always usesthe system Python interpreterinstead of the one set in theenvironment.

• Improved the read-backstrategy of DCV-GL forimproved performance androbustness.

• DCV-GL now checks if awindow changed size aftera front buffer readback. This

58



fixes a rendering problem withthe Coot application.

DCV 2017.1-5870 — August 6, 2018



authenticator: 53

Released package for Ubuntu18.04. When working in consolemode, the system must beconfigured to use LightDM oranother display manager of yourchoice because GDM does notexpose the required X11 displayinformation. Virtual sessions arenot affected by this limitation.

• The license setting is now readwhen a session is created. Thisallows the administrator tochange this setting withoutrestarting the server.

• Resolved stability problemin the Windows client thatcaused the program toexit unexpectedly on somesystems.

• Reduced logging in a possibleerror condition.

DCV 2017.1-5777 — June 29, 2018



authenticator: 51

• Added a Linux native client.• Added support for

3DConnexion mouses and USBstorage devices.

• Windows session lockedautomatically when the lastclient disconnects.

• Performance improvements inthe Linux version.

• Changed the default HWencoder on NVIDIA devices toNVENC to avoid problems withNvIFR in new NVIDIA drivers.

• Improved smart card supporton Linux.

• Fixed file permissions foruploaded files when usingLinux console sessions.

DCV 2017.0-5600 — June 4, 2018


• nice-dcv-server: 5600• nice-dcv-client: 5600• nice-xdcv: 160• nice-dcv-gl: 279• nice-dcv-gltest: 184

• Added support for multiplemonitors on Linux.

• Windows client performanceimprovements.

• Used new Clipboard API onChrome 66+.

• Usage on EC2 now requiresability to reach S3 from theinstance running DCV server.

• Performance improvements toserver frame processing andWindows client decoding.

59



• nice-dcv-simple-external-authenticator: 48

• Added NVENC encoder forWindows.

• Fixed keyboard issues relatedto NumPad and blockedmodifiers.

• Prevent file descriptor leakwhen using an externalauthenticator on Linux.

• Fixed possible errors in smartcard connection.

DCV 2017.0-5121 — March 18, 2018


• nice-dcv-server: 5121• nice-dcv-client: 5121• nice-xdcv: 146• nice-dcv-gl: 270• nice-dcv-gltest: 184• nice-dcv-simple-external-

authenticator: 46

• Windows native client is nowDPI aware.

• Added support for relativemouse movement mode.

• Prevented hang on Ansyscfx5solve on Linux.

• Fixed possible agent hang onWindows 10.

• Improved the Web Client userinterface.

• Normalized Windows username when a domain isspecified.

• Fixed the externalauthenticator on RHEL6.

DCV 2017.0-4334 — January 24, 2018


• nice-dcv-server: 4334• nice-dcv-client: 4334• nice-xdcv: 137• nice-dcv-gl: 254• nice-dcv-gltest: 184• nice-dcv-simple-external-authenticator: 45

• Improved keyboard handling.• Fixed DBus problem on RHEL6 where closing of

a session doesn't allow a new one to be created.• Improved support for SOCKS5 proxy on the

native client.• Addressed the bug that cause crashes on

Headwave when running on virtual sessions andon Chimera when running on virtual sessions.

• Improved font support on virtual sessions.

DCV 2017.0-4100 — December 18, 2017

Build numbers

• nice-dcv-server: 4100• nice-dcv-client: 4100

60

NICE DCV User GuideDocument history

Build numbers

• nice-xdcv: 118• nice-dcv-gl: 229• nice-dcv-gltest: 158• nice-dcv-simple-external-authenticator: 35

Document historyThe following table describes the documentation for this release of NICE DCV.

Change Description Date

NICE DCV Version 2022.1 NICE DCV 2022.1 is nowavailable. For more information,see DCV 2022.1-13067— June29, 2022 (p. 43).

June 29, 2022

NICE DCV Version 2022.0 NICE DCV 2022.0 is nowavailable. For more information,see DCV 2022.0-11954—February 23, 2022 (p. 45).

February 23, 2022

NICE DCV Version 2021.3 NICE DCV 2021.3 is nowavailable. For more information,see DCV 2021.3-11591—December 20, 2021 (p. 46).

December 20, 2021

NICE DCV Version 2021.2 NICE DCV 2021.2 is nowavailable. For more information,see DCV 2021.2-11048—September 01, 2021 (p. 48).

September 01, 2021

NICE DCV Version 2021.1 NICE DCV 2021.1 is nowavailable. For more information,see DCV 2021.1-10557— May31, 2021 (p. 50).

May 31, 2021

NICE DCV Version 2021.0 NICE DCV 2021.0 is nowavailable. For more information,see DCV 2021.0-10242— April12, 2021 (p. 50).

April 12, 2021

NICE DCV Web Client SDK The NICE DCV Web Client SDKis now available. The NICE DCVWeb Client SDK is a JavaScriptlibrary that you can use todevelop your own NICE DCVweb browser client applicationsthat your end users can use toconnect to and interact with arunning NICE DCV session. Formore information, see the NICEDCV Web Client SDK DeveloperGuide.

March 24, 2021

61

https://docs.amazonaws.cn/dcv/latest/websdkguide/what-is.html





NICE DCV Version 2020.2 NICE DCV 2020.2 is nowavailable. For more information,see DCV 2020.2-9508—November 11, 2020 (p. 51).

November 11, 2020

NICE DCV Version 2020.1 NICE DCV 2020.1 is nowavailable. For more information,see DCV 2020.1-8942— August03, 2020 (p. 52).

August 03, 2020

NICE DCV Version 2020.0 NICE DCV 2020.0 includessupport for surround sound7.1, touch and stylus, andmulti-monitor using the newMicrosoft Edge browser. Formore information, see Installingthe NICE DCV Server in the NICEDCV Administrator Guide.

April 16, 2020

HTTP response headers The NICE DCV server can beconfigured to send additionalHTTP response headers.

August 26, 2019

macOS client NICE DCV now offers a macOSclient. For more information, seemacOS Client in the NICE DCVUser Guide.

April 18, 2019

Smart card caching The NICE DCV server cannow cache smart card datareceived from the client to helpimprove performance. For moreinformation, see ConfiguringSmart Card Caching in the NICEDCV Administrator Guide.

October 08, 2018

Linux client NICE DCV offers Linux clients forRHEL 7, CentOS 7, SLES 12, andUbuntu 16.04/18.04. For moreinformation, see Linux Client inthe NICE DCV User Guide.

August 29, 2018

Updated Parameter Reference The Parameter Reference wasupdated. For more information,see NICE DCV Server ParameterReference in the NICE DCVAdministrator Guide.

August 07, 2018

USB remotization NICE DCV enables clients to usespecialized USB devices, such as3D pointing devices or graphictablets. For more information,see Enabling USB Remotizationin the NICE DCV AdministratorGuide.

August 07, 2018

62

https://docs.amazonaws.cn/dcv/latest/adminguide/setting-up-installing.html

https://docs.amazonaws.cn/dcv/latest/adminguide/setting-up-installing.html

https://docs.amazonaws.cn/dcv/latest/userguide/client-mac.html



https://docs.amazonaws.cn/dcv/latest/userguide/client-linux.html

https://docs.amazonaws.cn/dcv/latest/adminguide/config-param-ref.html

https://docs.amazonaws.cn/dcv/latest/adminguide/config-param-ref.html




Initial release of NICE DCV First publication of this content. June 05, 2018

63

NICE DCV - User Guide

Documents

Transcript of NICE DCV - User Guide