Feature request: allow setting web client features from direct-launch-url
We use the "direct launch URL" feature of the AVD web client to deep link users to a session desktop (https://learn.microsoft.com/en-us/windows-app/direct-launch-urls?tabs=avd). One of the reason we use the web client is because we use AVD in exam halls on Chromebooks in kiosk-mode. The ChromeOS kiosk-mode only supports websites. Students are faced with a connection dialog in which they can toggle IME and Special Keys. The students have to enable IME, but since these are university-owned devices, they do not know and just click "Connect". We would like to be able to configure these client options automatically. For example, as query parameters in the direct-launch-url. Ideally, we would also skip the "Connect" dialog entirely and just go strait into the session once the direct-launch-url is loaded.
[Resolved] WVD web client connection errors in Google Chrome and Microsoft Edge (Chromium)
UPDATE: This issue has been resolved in Production. A fix for pre-production environments will roll out with normal service updates. A number of users have reported issues connecting to the WVD web client using both Microsoft Edge (Chromium) and Google Chrome. The February release of the new Chromium 80 engine - used by both Edge and Chrome - included changes SameSite cookie classification. More information can be found on the Chromium blog and Chromium developer guidance. We are working on rolling out a fix to production. In the interim, please use the following workarounds to continue using the web client: Use Mozilla Firefox In your Microsoft Edge (Edge://flags) or Google Chrome (Chrome://flags) browser, disable both the SameSite by default cookies and Cookies without SameSite must be secure flags. Please note the warning presented: "By enabling these features, you could lose browser data or compromise your security or privacy. Enabled features apply to all users of this browser." We will post an update on this thread when a fix is available in production.
Remote Desktop Web Client Import Existing Certificate
I am working through the process to setup the Remote Desktop Web Client as documented here, which all works fine when manually working through these steps: https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-web-client-admin I am also working to automate this process with some server deployments, which I can mostly do up to the step to import the certificate, which is this command: Import-RDWebClientBrokerCert <.cer file path> However, we already have a certificate seeded and setup on the certificate store on the server that I want to use, but this command provides no way to reference or use said certificate by thumbprint. Is there any other possible way to reference and use a certificate that is already on the server? I found I can't run the last command to publish until I do the certificate import: Publish-RDWebClientPackage -Type Production -Latest The certificate I have in place is one that I'm already using on the same server for the connection broker and session host roles. I did see further down some netsh commands regarding setting the certificate, but this doesn't really do anything as the port already has the certificate and it doesn't seem to matter for whatever is required to run the publish command. Is there any way to do this without importing a real certificate file?