Install and configure Dragon Copilot in virtual environments

In a virtual environment, you can host Dragon Copilot 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 or Microsoft Windows Embedded operating system, or a zero client with no operating system. This architecture has the following implications:

  • The client workstation, where the user speaks, doesn't run a locally installed instance of Dragon Copilot or the EHR. The user's apps run on a virtualization server or virtual desktop. The workstation displays a bitmap representation of the apps or virtual desktop through a receiver app.

  • You must route button controls and high-quality audio from the workstation where the microphone is connected to the virtualization layer where Dragon Copilot runs.

Regardless of your virtualization technology and architecture, you must be able to capture clear audio from the user's device and deliver it to the Dragon Copilot system. This article guides you through the configuration steps in Citrix and Omnissa systems to configure audio and button control routing.

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 expose confidential data. Encryption is enabled by default.

Server requirements

Operating systems:

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

Virtual server environments: See the Citrix product matrix for supported versions of Citrix Virtual Apps and Desktops for the Current Release (CR) and Long Term Service Release (LTSR) lifecycles.

Virtual server environments: See the Omnissa lifecycle matrix for supported versions of Omnissa Horizon Agent.

Client endpoint requirements

  • Sound card or USB audio device

Operating systems:

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

Virtual client environment: See the Citrix product matrix for supported versions of Citrix Workspace app for the Current Release (CR) and Long Term Service Release (LTSR) lifecycles.

Virtual client environments: See the Omnissa lifecycle matrix for supported versions of Omnissa Horizon Client.

Step 1: Prepare your system

  1. Make sure your system fulfills all requirements listed above.

  2. In Windows Server 2019 and later versions, you must give apps explicit access to hardware devices through 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. Apply this GPO to all servers.

  1. 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 from all client endpoints.

  2. On the client endpoint, make sure there aren't any Citrix device splitting settings left over from previous installations.

    Group policies:

    To check this condition, open the Group Policy Editor, browse to Computer Configuration > Administrative Templates, and make sure there's no Citrix Components folder listed. If this folder is present, remove the following files:

    • Go to C:\Windows\PolicyDefinitions and remove the CitrixBase.admx and receiver.admx files.
    • Go to C:\Windows\PolicyDefinitions\en-US and remove the CitrixBase.adml and receiver.adml files.

    Removing these files removes all Citrix policies from the 'old' device splitting configuration.

    Registry:

    Remove any device specific registry keys that were required for the 'old' device splitting configuration. For example, for Nuance PowerMic III, remove these keys:

    • Key (64-bit Windows): HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client\GenericUSB\Devices\VID0554 PID1001

    • Key (32-bit Windows): HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA Client\GenericUSB\Devices\VID0554 PID1001

    • DWORD value: AutoRedirect = 1

  3. To ensure the microphone will be active after roaming to another endpoint, add the following registry keys to the Citrix Virtual Delivery Agent:

    • Location: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge
      Name: AudioSandboxEnabled
      Type: Reg_DWORD
      Value: 0

    • Location: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome
      Name: AudioSandboxEnabled
      Type: Reg_DWORD
      Value: 0

    For more information, see No audio comes up through MS Edge or Google Chrome as published app.

  1. 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, use one of the following methods:

  • On the virtual server, configure the browser as a published application.
  • On the virtual desktop, start the browser and go 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: Configure Citrix device splitting

The procedure to configure Citrix device splitting depends on your Citrix Virtual Apps and Desktops version.

For newer Citrix versions (2511 or higher, 2507 LTSR):

  1. Create a policy in Citrix studio to allow USB redirection for a specific device and for specific users.
  2. Create a policy in Citrix studio to enable microphone and audio redirection for those users.

For older Citrix versions (below 2511 or 2507 LTSR):

  1. Create a policy in Citrix studio to allow USB redirection for a specific device and for specific users.
  2. Create a policy in Citrix studio to enable microphone and audio redirection for those users.
  3. Configure automatic device splitting.

Expand the following sections to see the full procedure:

Citrix Virtual Apps and Desktops 7 2511 or higher or Citrix Virtual Apps and Desktops 7 2507 LTSR

This procedure applies to:

  • Citrix Virtual Apps and Desktops 7 2511 or higher
  • Citrix Virtual Apps and Desktops 7 2507 LTSR

Create a USB redirection policy (newer Citrix versions)

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 (Version 2) > Select. The corresponding dialog box is displayed.
  7. Enter the device ID as follows (PowerMic 4 example): CONNECT: VID=0554 PID=0064 split=1 intf=04. 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, such as 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.

Create a policy to allow client audio and microphone redirection (newer Citrix versions)

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, such as 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.
Citrix Virtual Apps and Desktops versions older than 2511 or 2507 LTSR

This procedure applies to Citrix Virtual Apps and Desktop versions older than 2511 and 2507 LTSR.

Create a USB redirection policy (older Citrix versions)

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 4 example): CONNECT: VID=0554 PID=0064. 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, such as 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.

Create a policy to allow client audio and microphone redirection (older Citrix versions)

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, such as 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.

Configure automatic device splitting (older Citrix versions)

Only automatic device splitting is supported. As manual device splitting leads to audio problems when working with standby mode, it's not supported.

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 to 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 starts, select USB Device Rules and enter the corresponding rule:

    Device Rule
    Nuance PowerMic III CONNECT: vid=0554 pid=1001 split=1 intf=03
    Nuance PowerMic 4 CONNECT: vid=0554 pid=0064 split=1 intf=04
    Philips SpeechMike Air CONNECT: VID=0911 PID=0BB8 split=1 intf=04
    Philips SpeechMike III and 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.

Device IDs

Use the following device IDs when you create a USB redirection policy:

Device ID
Nuance PowerMic III CONNECT: VID=0554 PID=1001 split=1 intf=03
Nuance PowerMic 4 CONNECT: VID=0554 PID=0064 split=1 intf=04
Philips SpeechMike Air CONNECT: VID=0911 PID=0BB8 split=1 intf=04
Philips SpeechMike III and Premium CONNECT: VID=0911 PID=0C1C split=1 intf=04

Step 4: Enable Citrix HDX audio

By default, Citrix HDX audio is enabled. If it's not, enable it in Citrix Studio.

Important

Use the optimized mode in Citrix Studio, not generic. Optimized audio delivers superior real-time performance and lower latency. Generic audio streams raw or compressed audio through the Citrix ICA protocol and consumes more bandwidth.

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. Download the Omnissa-Horizon-Extras-Bundle-YYMM-x.x.x-yyyyyyyy.zip file from the Omnissa Horizon download page and extract the file. From the extracted folder, copy hzn_agent.admx to C:\Windows\PolicyDefinitions, and copy hzn_agent.adml to C:\Windows\PolicyDefinitions\en-US.
  3. In the Group Policy Editor, browse for Computer Configuration/Administrative Templates/Horizon 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/Horizon USB Configuration/Client Downloadable only Settings and select Split Vid/Pid Device.
  6. Enable this setting and enter the device-specific string.
  7. Disconnect from the virtual desktop and close VMware/Omnissa Horizon Client.
  8. Connect the microphone/control device to the client endpoint.
  9. Start VMware/Omnissa Horizon Client and connect to the virtual desktop.
  10. 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, and then select OK.

Device-specific strings

Enter strings for specific devices in the Include Vid/Pid Device and Split Vid/Pid Device settings.

Device Include Vid/Pid Device Split Vid/Pid Device
Nuance PowerMic III o:vid-0554_pid-1001 o:vid-0554_pid-1001<br>(exintf:00;exintf:01;exintf:02)
Nuance PowerMic 4 o:vid-0554_pid-0064 o:vid-0554_pid-0064<br>(exintf:00;exintf:01;exintf:02)
Philips SpeechMike III and Premium o:vid-0911_pid-0c1c o:vid-0911_pid-0c1c<br>(exintf:00;exintf:01;exintf:02;exintf:03)

To configure more than one device in one string, use a semicolon as a separator and leave out o: for all devices except the first in the list. For example, to configure a PowerMic III and a PowerMic 4, enter the following:

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

Microsoft Edge WebView2 deployment in Citrix environments

Some Citrix environments exhibit problems that can cause the Microsoft Edge WebView2 runtime process to fail to work as expected. This failure leads to Dragon Copilot not displaying properly, and it can sometimes terminate with a message visible to end users. As a workaround, apply a configuration change to Citrix to disable the Citrix Special Folder Redirection feature (SfrHook) for the Microsoft Edge WebView2 runtime process. To do this, add the following registry keys to your Citrix environment configuration:

  • [HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\CtxHook\AppInit_DLLs\SfrHook\msedgewebview2.exe]
  • [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Citrix\CtxHook\AppInit_DLLs\SfrHook\msedgewebview2.exe]
  • Last updated on