Home

Different connection clients to Windows Virtual Desktop

%3CLINGO-SUB%20id%3D%22lingo-sub-822221%22%20slang%3D%22en-US%22%3EDifferent%20connection%20clients%20to%20Windows%20Virtual%20Desktop%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-822221%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20the%20official%20documention%2C%20it%20says%20that%20%3A%3C%2FP%3E%3CDIV%20class%3D%22lia-spoiler-container%22%3E%3CA%20class%3D%22lia-spoiler-link%22%20href%3D%22%23%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3ESpoiler%3C%2FA%3E%3CNOSCRIPT%3E(Highlight%20to%20read)%3C%2FNOSCRIPT%3E%3CDIV%20class%3D%22lia-spoiler-border%22%3E%3CDIV%20class%3D%22lia-spoiler-content%22%3E%22Don't%20use%20%3CSTRONG%3ERemoteApp%20and%20Desktop%20Connections%20(RADC)%3C%2FSTRONG%3Eor%20%3CSTRONG%3ERemote%20Desktop%20Connection%20(MSTSC)%3C%2FSTRONG%3Eto%20access%20Windows%20Virtual%20Desktop%20resources%20because%20Windows%20Virtual%20Desktop%20doesn't%20support%20either%20client.%22%20Source%20%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fconnect-windows-7-and-10%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fconnect-windows-7-and-10%3C%2FA%3E%3C%2FDIV%3E%3CNOSCRIPT%3E%3CDIV%20class%3D%22lia-spoiler-noscript-container%22%3E%3CDIV%20class%3D%22lia-spoiler-noscript-content%22%3E%22Don't%20use%20RemoteApp%20and%20Desktop%20Connections%20(RADC)%20or%20Remote%20Desktop%20Connection%20(MSTSC)%20to%20access%20Windows%20Virtual%20Desktop%20resources%20because%20Windows%20Virtual%20Desktop%20doesn't%20support%20either%20client.%22%20Source%20%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fconnect-windows-7-and-10%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fconnect-windows-7-and-10%3C%2FA%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FNOSCRIPT%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%20end%20user%20point%20of%20view%2C%20we%20find%20that%20MSTSC%20is%20so%20much%20faster%20than%20both%20Remote%20Desktop%20and%20the%20web%20client%2C%20so%20if%20possible%20we%20would%20like%20to%20stick%20to%20the%20RDP%20protocol.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20is%20the%20difference%20between%20the%20MSTSC%20and%20the%20newly%20provided%20Remote%20Desktop%20client%3F%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-824392%22%20slang%3D%22en-US%22%3ERe%3A%20Different%20connection%20clients%20to%20Windows%20Virtual%20Desktop%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-824392%22%20slang%3D%22en-US%22%3EI%20find%20the%20lack%20of%20UDP%20support%20reduces%20the%20end%20user%20experience%20massively.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-824766%22%20slang%3D%22en-US%22%3ERe%3A%20Different%20connection%20clients%20to%20Windows%20Virtual%20Desktop%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-824766%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F394998%22%20target%3D%22_blank%22%3E%40Lionel_B4%3C%2FA%3E%3A%20Hi%20Lionel!%20Can%20you%20elaborate%20what%20you%20mean%20with%20much%20faster%3F%20For%20features%20you%20are%20missing%20you%20can%20suggest%20them%20here.%20Please%20add%20a%20little%20bit%20of%20context%20which%20problem%20that%20one%20solves%20on%20your%20side%3A%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fwvdfbk%26nbsp%3B%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fwvdfbk%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-826001%22%20slang%3D%22en-US%22%3ERe%3A%20Different%20connection%20clients%20to%20Windows%20Virtual%20Desktop%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-826001%22%20slang%3D%22en-US%22%3EFaster%20meaning%20the%20feedback%20of%20every%20action%20we%20do%20on%20Windows%2010.%3CBR%20%2F%3E%3CBR%20%2F%3ETypical%20example%20is%20typing%20in%20a%20Notepad.%20Using%20MSTSC%20the%20feedback%20is%20instantaneous%2C%20while%20using%20the%20web%20client%20or%20Remote%20Desktop%2C%20the%20delay%20between%20pressing%20a%20key%20and%20the%20character%20appearing%20on%20the%20screen%20is%20a%20few%20hundred%20milliseconds.%20Presumably%20because%20it%20uses%20HTML5%20to%20emulate%20RDP.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-826923%22%20slang%3D%22en-US%22%3ERe%3A%20Different%20connection%20clients%20to%20Windows%20Virtual%20Desktop%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-826923%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F394998%22%20target%3D%22_blank%22%3E%40Lionel_B4%3C%2FA%3E%26nbsp%3BOut%20of%20interest%20which%20datacenter%20is%20your%20VM%20located%20in%3F%20During%20testing%20I%20found%20that%20the%20connection%20is%20very%20laggy%20as%20you%20describe%20to%20my%20VMs%20in%20the%20EU%20as%20the%20gateway%20connection%20is%20going%20from%20the%20EU%20to%20the%20US%20and%20back%20to%20the%20EU%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-828440%22%20slang%3D%22en-US%22%3ERe%3A%20Different%20connection%20clients%20to%20Windows%20Virtual%20Desktop%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-828440%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20connecting%20from%20Malaysia%20to%20VMs%20in%20Singapore.%20Pretty%20small%20distance%20compared%20to%20EU-US%20but%20the%20web%20client%20and%20Remote%20Desktop%20client%20is%20still%20so%20laggy%20it%20makes%20it%20pretty%20impossible%20to%20use%20in%20a%20call%20center.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20just%20want%20to%20know%20for%20Azure%20WVD%2C%20if%20we%20can%20use%20MSTSC%20(RDP)%20a.k.a.%20Remote%20Desktop%20Connection%2C%20until%20the%20performance%20issue%20is%20improved%20in%20the%20other%202%20clients%3F%3F%20or%20hopefully%20the%20upcoming%20Linux%20client%20is%20better.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-828714%22%20slang%3D%22en-US%22%3ERe%3A%20Different%20connection%20clients%20to%20Windows%20Virtual%20Desktop%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-828714%22%20slang%3D%22en-US%22%3EYou%20likely%20have%20the%20same%20problem%20I%20have%20then.%20As%20the%20gateway%20for%20the%20preview%20is%20in%20the%20US%20your%20connection%20when%20using%20the%20proper%20client%20is%20going%20out%20to%20the%20US%20and%20back%20again.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-829273%22%20slang%3D%22en-US%22%3ERe%3A%20Different%20connection%20clients%20to%20Windows%20Virtual%20Desktop%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-829273%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F394998%22%20target%3D%22_blank%22%3E%40Lionel_B4%3C%2FA%3E%3A%20The%20latency%20might%20be%20expected%20from%20your%20region.%20You%20could%20deploy%20your%20VMs%20in%20the%20US%20to%20reduce%20the%20round%20trip.%20Note%3A%20Doesn't%20matter%20which%20client%20you%20use%20the%20protocol%20is%20as%20performant%20as%20in%20on-premises%20scenarios.%20Watch%20out%20for%20further%20news%20or%20announcements%20in%20this%20forum.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Lionel_B4
New Contributor

In the official documention, it says that :

Spoiler
"Don't use RemoteApp and Desktop Connections (RADC) or Remote Desktop Connection (MSTSC) to access Windows Virtual Desktop resources because Windows Virtual Desktop doesn't support either client." Source : https://docs.microsoft.com/en-us/azure/virtual-desktop/connect-windows-7-and-10

 

From end user point of view, we find that MSTSC is so much faster than both Remote Desktop and the web client, so if possible we would like to stick to the RDP protocol.

 

What is the difference between the MSTSC and the newly provided Remote Desktop client??

 

7 Replies
I find the lack of UDP support reduces the end user experience massively.

@Lionel_B4 : Hi Lionel! Can you elaborate what you mean with much faster? For features you are missing you can suggest them here. Please add a little bit of context which problem that one solves on your side: https://aka.ms/wvdfbk 

Faster meaning the feedback of every action we do on Windows 10.

Typical example is typing in a Notepad. Using MSTSC the feedback is instantaneous, while using the web client or Remote Desktop, the delay between pressing a key and the character appearing on the screen is a few hundred milliseconds. Presumably because it uses HTML5 to emulate RDP.

@Lionel_B4 Out of interest which datacenter is your VM located in? During testing I found that the connection is very laggy as you describe to my VMs in the EU as the gateway connection is going from the EU to the US and back to the EU

I'm connecting from Malaysia to VMs in Singapore. Pretty small distance compared to EU-US but the web client and Remote Desktop client is still so laggy it makes it pretty impossible to use in a call center.

I just want to know for Azure WVD, if we can use MSTSC (RDP) a.k.a. Remote Desktop Connection, until the performance issue is improved in the other 2 clients?? or hopefully the upcoming Linux client is better.

You likely have the same problem I have then. As the gateway for the preview is in the US your connection when using the proper client is going out to the US and back again.

@Lionel_B4 : The latency might be expected from your region. You could deploy your VMs in the US to reduce the round trip. Note: Doesn't matter which client you use the protocol is as performant as in on-premises scenarios. Watch out for further news or announcements in this forum.

Related Conversations
Add App pinning to Windows 10
HotCakeX in Windows Insider Program on
0 Replies
PacketMon Components are not loading in WAC 1909
HotCakeX in Windows Admin Center on
2 Replies
Python for testing item
紫頤 秦 in Education on
1 Replies