Virtualisation - Information
Overview
Dragon Medical One, Professional Anywhere and Legal Anywhere support the following virtualised environments.
- Citrix XenApp/XenDesktop
- Microsoft Remote Desktop Services (RDS)
- VMware Horizon View/RDSH
To provide the best end user experience, the Dragon application must be installed in the same environment as the application the end user wishes to dictate into. Where APP's are published, the Dragon application must come from the same server as the application the end user wishes to dictate into has come from.
Requirements
Hardware
Any currently supported operating system from Microsoft is supported for use with Dragon. As operating systems are retired so is the support for Dragon as unsupported operating systems are no longer tested and validated.
With modern multi-core CPU architecture and provided that a given virtual session has been assigned at least one core, Dragon Medical One consumes between 1% and 3% of the available CPU per user session while the user is dictating. Recommendation is a CPU of 2.8Ghz.
Memory usage, when in use, will fluctuate (increase and decrease based on user behavior and Microsoft Windows memory management behavior). For sizing and planning purposes we estimate memory utilization of 220 MB (full working set), of which approximately 70 MB (shared working set) are shared between all instances of the SoD.exe process on the same machine – the real physical memory impact therefore is approximately 150 MB per instance.
Disk space is shared amongst users and is typically around 200MB. Additional space may be require when additional logging is configured.
Microphone
Any microphone that can record audio data in 16 kHz, 16-bit mono format is supported. Professional microphones from Nuance (PowerMic) and Philips (SpeechMike) are also supported if the required and supplied device extensions are present.
When using Dragon Medical One, the use of the PowerMic Mobile APP (Android and iOS) is also supported.
Nuance Virtual Extensions
Nuance provides a custom audio channel to reduce the audio bandwidth requirements between the client end point and the virtual server. This custom audio channel requires 28 kbit/s for each user while they are dictating (native audio channels often require up to 1.4 Mbit/s).
To use the custom audio channel, deploy it on the client end point. It is supplied in the Dragon download package.
Network Requirements
For more information on network requirements for each of the products, including information on latency (including a latency checker) please visit one of the following pages.
Additional Information
In addition to the Nuance Virtual Extensions, when using Microsoft Remote Desktop, it is recommended UDP transport is disabled. This can be done at a client or server level, and there are various ways this can be achieved. Due to environments being different, The below recommendations should be tested to find the most suitable.
Client End Point
Tested on Windows 11
Open the Registry Editor by running the "regedit" command in a Command Prompt or PowerShell as an administrator. Navigate to the following path:
HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client\
Create a new DWORD entry (32-bit value) and name it "fClientDisableUDP". Set "fClientDisableUDP" to 1 to disable UDP support for RDP connections.
Any existing RDP connections must be disconnected and re-established for the changes to take effect.
Server
Tested on Server 2022
Open the "Local Group Policy Editor" by running the "gpedit.msc" command in the command line, in PowerShell (or Win+X → Run) as an administrator.
Go to Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Connection Client.
Find the Turn Off UDP On Client option and set it to Enabled.
Go to Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Connections.
Find the Select RDP Transport Protocols option and set it to Enabled, and in the options select Use only TCP.
The server must be restarted for the changes to take effect.
To ascertain if UDP is in use or not, click the Connection Information icon at the top of the RDP window and choosing See Details.
