The newly released (https://cloudblogs.microsoft.com/enterprisemobility/2018/03/28/remote-desktop-web-client-public-preview/) HTML5 client should support Web Application Proxy and ADFS. Doing so we'd have the ability to provide MFA and externally (securely) publish the resources.

Allow for copying and pasting files between client and server.

Create static URLs to specific resources. This would allow for bookmarking specific resources in a browser and even putting those shortcuts on end-user desktops and start menus. If Windows Hello SSO were used for initial authentication then the process of clicking on a link to a resource would be seamless.

We need a simpler CSS so that we can adapt the basic look and feel (primarilly colors and logo) to make the site look like a company site.
Also simple ways of changing support mail and support URL to point to local IT support. The language files are great right now, but the CSS is more or less unreadable...

Hi All. We have scenario, where would like RDWeb HTML5 to work with Multiple monitors. Our client prefers the HTML solution over RDP but unfortunately multiple monitors does not work with HTML5.

A 2 factor authentication option (like Google authenticator) to more secure the HTML client from the web would be nice.

Support redirection of local microphone, like the traditional RDP client does

Support RD Gateway Pluggable Authentication and Authorization (PAA)
just like Windows RDP client (8.1) can authenticate against RD Gateway by using PAA cookie from "gatewayaccesstoken" RDP file property.
It would be removing a roadblock for the use of the HTML client, when you introduce support of PAA and "gatewayaccesstoken" property supported in HTML client.

Is it possible to do so that in full-screen we can extend the display on several screens?

Allow opening attachemnts and links (URLs) on local machine.
1. PDF, Word, Excel documents available on remote machine to be opened in local installation of respective applications
2. Links available in remote applications (in hard clients) to be opened in new tabs of local web browsers.

On the old client, you can have the option to ask user to change its password on the first login.

On the new HTML5 client this option is missing and IMHO it's a must have

Hosting partners / Companies may want to offer WVD based desktops / apps to customers through their branded portal. It would be cool if the WVD part / client side code could be integrated into an existing own hosted web app.

We are using custom RDP properties on some RD-Session collections and the WebClient does not seem to support that.

Example: We use the folowing command to set another RD Gateway for a specific collection.

"Set-RDSessionCollectionConfiguration -CollectionName "CollectionNaem" -CustomRdpProperty" "gatewayhostname:s:gw2.domain.com"

Any future plans to support custom RDP properties on the WebClient?

/Andreas

Enable Windows Hello auth on the initial sign-in page.

Use the login from the initial sign-in page to allow SSO to all published RemoteApps and Session Hosts.

Please can a Product Roadmap be published so that customers can see that the product is actively being developed/supported as well as the direction that the solution is taking.

Today the keyboard/language is always set to Eng/US for the desktop regardless of what language the browser is set to, what language the user selects on the web page or the language previously selected by the user in the application/desktop. Suggest that the system remebers the language/keyboard layout selected by the user or sets the same as the browser language if the user has not done a selection in the application/desktop.

On the classic remote desktop web access, one can enable Basic authentication on the application in IIS to sign on. I would like to have this working on this new web client too. (It allows scenario's where a reverse proxy/external loadbalancer handles authentication and sends it inside the http header)

How about this feature?

I would like to be able to open a new application window in a new browser tab rather than having to switch between different windows inside one tab.

This would enable us to deliver HTML5 remote apps more like Office365 apps

We have many descriptive names for our RemoteApps, which makes them too long when showing up in the web client, so I have to hover over the app to get the full name.