Install and configure Microsoft Dragon Copilot in virtual environments

In a virtual environment, Dragon Copilot can be hosted on a virtual server or desktop. The client endpoint can be a thick client running a Microsoft Windows operating system, a thin client running a Linux/Microsoft Windows Embedded operating system or a zero client with no operating system. Regardless of your virtualization technology and architecture, you must be able to deliver audio from the client endpoint to the hosted app.

Virtual server and client requirements

Important

For security reasons, make sure that VDI channel encryption is enabled between client endpoints and VDI servers or virtual desktops. Disabling encryption in a virtualized environment can lead to confidential data being exposed. Encryption is enabled by default.

Server requirements

One of the following operating systems:

• Microsoft Windows 11
• Microsoft Windows Server 2016
• Microsoft Windows Server 2019
• Microsoft Windows Server 2022

One of the following virtual server environments:

• Citrix Virtual Apps and Desktops 2311 or higher
• Citrix Virtual Apps and Desktops 1912 LTSR or higher

• VMware Horizon View Agent 7.13 or higher
• Omnissa Horizon Agent 2412 or higher

Client endpoint requirements

• Soundcard or USB audio device

One of the following operating systems:

• Microsoft Windows 11
• Microsoft Windows Server 2016
• Microsoft Windows Server 2019
• Microsoft Windows Server 2022

Virtual client environment:

• Citrix Workspace app for Windows 2402 or higher

One of the following virtual client environments:

• VMware Horizon View Client 5.5 or higher
• Omnissa Horizon Client 2412 or higher

Device drivers/redistributable packages

To use a microphone with buttons or other controls, install the corresponding device drivers/redistributable package on the virtual server and client endpoint. For more information, see the documentation delivered with the redistributable package.

Step 1: Prepare your system

1. Make sure your system fulfills all requirements listed above.
2. In Windows Server 2019 and higher, apps must be given explicit access to hardware devices via Group Policy. To allow Dragon Copilot to access the microphone device that's passed into the VDI session, create a Group Policy Object (GPO) for all users to set the registry key HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\microphone to Allow; this can then be applied to all servers.

3. If you're deploying Dragon Copilot on a virtual server or virtual desktop side-by-side with Dragon Medical One, uninstall the Nuance PowerMic Citrix Client Extension.

3. If you're deploying Dragon Copilot on a virtual server or virtual desktop side-by-side with Dragon Medical One, uninstall the Nuance PowerMic VMware/Omnissa Client Extension.

Step 2: Deploy Dragon Copilot

To deploy the web app, do one of the following:

• On the virtual server, configure the browser as a published application.
• On the virtual desktop, start the browser and navigate to the URL of your Dragon Copilot system. For a list of region-specific URLs, see: Access the web app.

To deploy the desktop app, copy the installation package to a folder on the virtual server and publish the application.

Step 3: Create a policy in Citrix studio to allow USB redirection for a specific device and for specific users

Create a USB redirection policy

Proceed as follows:

1. On the Delivery Controller for your Citrix system, start Citrix Studio.
2. In the tree view, select Policies > Create Policy.
3. On the Settings page, select (All Versions) and USB Devices in the two drop-down lists.
4. Select Client USB device redirection > Select. The corresponding dialog box is displayed.
5. Select Allowed > OK.
6. Select Client USB device redirection rules > Select. The corresponding dialog box is displayed.
7. Enter the device ID as follows (PowerMic III example): ALLOW: VID0554 PID1001. For a list of USB devices and their corresponding IDs, see: Device IDs.
8. Select OK > Next.
9. On the Users and Machines page, assign the delivery group for the new policy and select Next.
10. On the Summary page, enter a name for the new policy, for example: Allow USB redirection- delivery group.
11. Select Finish.

For information on configuring USB redirection for Linux thin clients, see the documentation delivered with the product.

Device IDs

The following device IDs are used when creating a USB redirection policy:

Device	ID
PowerMic III	VID0554 PID1001
PowerMic 4	VID0554 PID0064
Philips SpeechMike Air	VID0911 PID0BB8
Philips SpeechMike Premium	VID0911 PID0C1C
Philips SpeechMike III	VID0911 PID0C1C

Step 4: Create a policy to allow client audio and microphone redirection

Proceed as follows:

1. On the Delivery Controller for your Citrix system, start Citrix Studio.
2. In the tree view, select Policies > Create Policy.
3. On the Settings page, select All Settings in the drop-down box.
4. Select ICA/AudioSelect > Client audio redirection > Allowed > OK.
5. Select Client microphone redirection > Allowed > OK.
6. Select Next, assign the delivery group for the new policy, and select Next.
7. On the Summary page, enter a name for the new policy; for example: Allow client audio and microphone redirection- delivery group.
8. Enable the policy and select Finish.
9. Rank the new policy higher than the Allow USB redirection- delivery group policy.
10. Select Finish.

Step 5 Enable Citrix HDX audio

By default, Citrix HDX audio is enabled; if it's not, you must enable it in Citrix Studio.

Step 6: Configure automatic device splitting

Proceed as follows:

1. On the client endpoint, make sure the audio device is connected and switched on.
2. Copy the CitrixBase.admx and receiver.admx files from C:\Program Files (x86)\Citrix\ICA Client\Configuration to C:\Windows\PolicyDefinitions.
3. Copy the CitrixBase.adml and receiver.adml files from C:\Program Files (x86)\Citrix\ICA Client\Configuration\en-US to C:\Windows\PolicyDefinitions\en-US.
4. In the Group Policy Editor, browse for Computer Configuration\Administrative Templates\Citrix Components\Citrix Workspace\Remoting client devices\Generic USB Remoting and select SplitDevices. Enable this setting.
5. To enable automatic device splitting for the audio device each time the Citrix session is started, select USB Device Rules and enter the corresponding rule:

Device	Rule
PowerMic III	CONNECT: vid=0554 pid=1001 split=1 intf=03
PowerMic 4	CONNECT: vid=0554 pid=0064 split=1 intf=04
Philips SpeechMike III/Premium	CONNECT: vid=0911 pid=0c1c split=1 intf=04

6. Select Existing USB Devices > Enabled > Connect all available USB devices > OK.
7. Select New USB Devices > Enabled > Connect the USB device > OK.
8. On the client endpoint, connect to the Citrix server and start a published app.

Step 3: Configure the native audio channel and automatic device splitting

Proceed as follows:

1. Start VMware/Omnissa Horizon Client and connect to the virtual desktop you want to use.
2. Install vdm_agent.adm in the Group Policy Editor of the virtual desktop; the file is located on the Connection Server at C:\Program Files\VMWare\VMware View\Server\extras\GroupPolicyFiles. For more information on how to install ADM files, see: Add or remove an Administrative Template (.amd file).
3. In the Group Policy Editor, browse for Computer Configuration/Administrative Templates/Classic Administrative Templates (ADM)/VMware View Agent Configuration/View USB Configuration and select Include Vid/Pid Device.
4. Enable this setting and enter the device-specific string.
5. Browse for Computer Configuration/Administrative Templates/Classic Administrative Templates (ADM)/VMware View Agent Configuration/View USB Configuration/Client Downloadable only Settings and select Split Vid/Pid Device.
6. Enable this setting and enter the device-specific string.
7. In the Device Manager of the virtual desktop, select Sound, video and game controllers and make sure that VMware Virtual Audio (DevTap) and VMware Virtual Microphone are enabled.
8. Disconnect from the virtual desktop and close VMware/Omnissa Horizon Client.
9. Connect the microphone/control device to the client endpoint.
10. Start VMware/Omnissa Horizon Client and connect to the virtual desktop.
11. In the VMware/Omnissa Horizon Client app, select Settings > USB Devices and select the audio device (for example, PowerMic 4). Select the settings icon next to the audio device, enable Auto-connect at Startup and Auto-connect when Inserted, then select OK.

Device-specific strings

Enter strings for specific devices in the IncludeVid/PidDevice and SplitVid/PidDevice settings.

Device	IncludeVid/PidDevice	SplitVid/PidDevice
PowerMic III	o:vid-0554_pid-1001	o:vid-0554_pid-1001 (exintf:00; exintf:01; exintf:02)
PowerMic 4	o:vid-0554_pid-0064	o:vid-0554_pid-0064 (exintf:00; exintf:01; exintf:02)
Philips SpeechMike Premium	o:vid-0911_pid-0c1c	o:vid-0911_pid-0c1c (exintf:00; exintf:01; exintf:02; exintf:03)
Philips SpeechMike III	o:vid-0911_pid-0c1c	o:vid-0911_pid-0c1c (exintf:00; exintf:01; exintf:02; exintf:03)

To configure more than one device in one string, use a semicolon as a separator. For example, to configure a PowerMic III and a PowerMic 4, enter the following:

Include Vid/Pid Device: o:vid-0554_pid-1001;o:vid-0554_pid-0064
Split Vid/Pid Device: o:vid-0554_pid-1001(exintf:00;exintf:01;exintf:02);o:vid-0554_pid-0064(exintf:00;exintf:01;exintf:02)