Microsoft Azure Virtual Desktop

Information on how to configure Microsoft AVD with Stratodesk NoTouch OS

Update: On June 2021 Microsoft renamed Windows Virtual Desktop (WVD) to Azure Virtual Desktop or AVD for short.

Stratodesk NoTouch OS has the Microsoft Windows Virtual Desktop client integrated, for x86 or ARM/Raspberry Pi based devices. Our AVD implementation supports the Microsoft WVD client for Linux features, everything can be configured and managed via the Local NoTouch OS Interface menu as well as centrally with NoTouch Center.

This article gives an overview of the configuration steps. We assume that you basically understand how NoTouch OS is configured and especially how server connections are created and configured.

Creating the Microsoft AVD  connection is simple, create the connection type and the client will connect to the Microsoft resources where your credentials will direct you to the services that have been provisioned for you by your Azure Administrator.

Create the connection from within NoTouch Center by choosing New Connection, Connection Mode, Select Windows Virtual Desktop (AVD )


After choosing the connection mode, if additional parameters are needed for your connection, you can select Windows Virtual Desktop tab to make the appropriate settings


If no additional parameters are required, you can announce the settings change via NoTouch Center and your Endpoint should be provisioned



Additional configuration options - Below are additional configuration parameters available on the Windows Virtual Desktop tab, as well as the default setting

RDP filename

Directory ID

Audio forwarding  \ On

Microphone (Audio in) forwarding \ Off

Printer Forwarding \ Off

Camera Forwarding \ Auto

Use Server Time Zone \ Off

Include System-defined Drives \ On

Drive Mappings

HTTP Proxy Address:port

WVD Version \ Auto /  Latest

Command Line Parameters \ default value is empty.  Example  --debug if asked by Technical Support


*Tech Notes

Time Zone - Redirection - You may have to use gpedit.msc in the Host Pool to modify Group Policy for the Time Zone Redirection to work correctly.  The GPO that may need to be modified

[Administrative Template/ Windows Components / Remote Desktop Services / Remote Desktop Session Host / Device and Resource Redirection / Allow time zone redirection]