SOLVED

MSTSC client with Windows Virtual Desktop

%3CLINGO-SUB%20id%3D%22lingo-sub-1593265%22%20slang%3D%22en-US%22%3EMSTSC%20client%20with%20Windows%20Virtual%20Desktop%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1593265%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EI%20am%20currently%20managing%20a%20Windows%20Server%202019%20RDS%20farm%20with%20several%20RDSH%20to%20publish%20in%20RemoteApp%20the%20application%20that%20my%20company%20is%20developing.%3CBR%20%2F%3EThe%20advantage%20of%20this%20solution%20is%20that%20the%20end%20users%20access%20our%20application%20via%20the%20RDWeb%2C%20then%20launch%20the%20RemoteApp%20with%20the%20native%20MSTSC%20client.%3CBR%20%2F%3EOur%20software%20should%20then%20be%20able%20to%20display%20the%20remote%20file%20explorer%20and%20mount%20the%20user's%20local%20drives%20with%20drives%20redirection.%3C%2FP%3E%3CP%3EWe%20are%20currently%20studying%20a%20migration%20to%20Azure%20WVD.%3CBR%20%2F%3EUnfortunately%2C%20the%20MSTSC%20client%20is%20not%20compatible%20with%20this%20solution%2C%20and%20we%20should%20have%20to%20force%20our%20clients%20to%20install%20the%20%22Windows%20Desktop%22%20thick%20client%20so%20that%20clients%20can%20access%20their%20RemoteApp.%3CBR%20%2F%3EUsing%20the%20HTML5%20client%20is%20not%20possible%20as%20this%20client%20does%20not%20have%20local%20drive%20redirection.%3CBR%20%2F%3EThe%20only%20solution%20available%20to%20us%20currently%20would%20be%20to%20ask%20the%20customer%20to%20install%20the%20Windows%20Desktop%20client%2C%20which%20is%20counterintuitive%20since%20we%20are%20selling%20an%20application%20in%20RemoteApp%20which%20does%20not%20require%20installation%20on%20the%20client%20workstation.%3C%2FP%3E%3CP%3EAre%20there%20any%20solutions%20for%20this%3F%3CBR%20%2F%3ECould%20MSTSC%20client%20be%20WVD%20compatible%20so%20we%20can%20migrate%20our%20clients%20without%20worries%3F%3C%2FP%3E%3CP%3EFor%20the%20moment%2C%20it%20is%20the%20dead%20end%20for%20us.%20Thank%20you%20!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1593265%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMSTSC%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Virtual%20Desktop%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWVD%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1599394%22%20slang%3D%22en-US%22%3ERe%3A%20MSTSC%20client%20with%20Windows%20Virtual%20Desktop%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1599394%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F762011%22%20target%3D%22_blank%22%3E%40tpironneau%3C%2FA%3E%26nbsp%3BUnfortunately%20the%20MSTSC%20client%20is%20not%20supported%20as%20you%20mentioned.%20The%20only%20option%20would%20be%20to%20use%20the%20Windows%20Desktop%20client%20which%20requires%20installation.%20Admins%20can%20also%20install%20the%20client%20for%20their%20users%20through%20standard%20MSI%20install%20processes%20but%20I'm%20not%20sure%20that's%20an%20option%20for%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1600642%22%20slang%3D%22en-US%22%3ERe%3A%20MSTSC%20client%20with%20Windows%20Virtual%20Desktop%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1600642%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F217952%22%20target%3D%22_blank%22%3E%40David%20Belanger%3C%2FA%3E%3CSPAN%20class%3D%22tlid-translation%20translation%22%3E%3CSPAN%20class%3D%22%22%3EHello%2C%20this%20is%20a%20shame.%20Our%20RemoteApp%20application%20is%20used%20by%20many%20users%20of%20whom%20we%20do%20not%20have%20the%20control%20of%20the%20computer%20station.%20While%20Microsoft's%20policy%20is%20to%20push%20to%20migrate%20RDS%20On-premise%20to%20WVD%2C%20we%20lose%20a%20lot%20of%20flexibility%20on%20the%20client%20side.%20It%20is%20unthinkable%20to%20ask%20our%20customers%20to%20install%20an%20application%20to%20launch%20a%20cloud%20application%20...%20Thank%20you%20anyway.%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hello,

I am currently managing a Windows Server 2019 RDS farm with several RDSH to publish in RemoteApp the application that my company is developing.
The advantage of this solution is that the end users access our application via the RDWeb, then launch the RemoteApp with the native MSTSC client.
Our software should then be able to display the remote file explorer and mount the user's local drives with drives redirection.

We are currently studying a migration to Azure WVD.
Unfortunately, the MSTSC client is not compatible with this solution, and we should have to force our clients to install the "Windows Desktop" thick client so that clients can access their RemoteApp.
Using the HTML5 client is not possible as this client does not have local drive redirection.
The only solution available to us currently would be to ask the customer to install the Windows Desktop client, which is counterintuitive since we are selling an application in RemoteApp which does not require installation on the client workstation.

Are there any solutions for this?
Could MSTSC client be WVD compatible so we can migrate our clients without worries?

For the moment, it is the dead end for us. Thank you !

2 Replies
best response confirmed by tpironneau (New Contributor)
Solution

@tpironneau Unfortunately the MSTSC client is not supported as you mentioned. The only option would be to use the Windows Desktop client which requires installation. Admins can also install the client for their users through standard MSI install processes but I'm not sure that's an option for you.

@David BelangerHello, this is a shame. Our RemoteApp application is used by many users of whom we do not have the control of the computer station. While Microsoft's policy is to push to migrate RDS On-premise to WVD, we lose a lot of flexibility on the client side. It is unthinkable to ask our customers to install an application to launch a cloud application ... Thank you anyway.