

In this release, we fixed some customer-reported bugs and issues reported by telemetry. We fixed a crash that happened when users moved hidden windows in RemoteApp scenarios.We addressed overactive Azure Virtual Desktop diagnostics reporting.We've improved smart card redirection performance.We resolved some customer-reported time zone redirection mismatches.We've also made some additional fixes and performance improvements, including the following:

In this release, we've added some new features to Teams redirection for Azure Virtual Desktop and Windows 365 scenarios:

I have no such registry post on my RDSH2019-servers, so there is nothing to delete. I don't see any beta client there, we alredy run: Version 10.3.4 (1688)ģ. Ip Address of the end point = RFC1918-address"Ģ. It feels like it tries to connect to the session host and sure the broker gives the following in the log: "Remote Desktop Connection Broker Client successfully redirected the user DOMAIN\user to the endpoint RDSH01.ad. If this keeps happening, contact your network administrator for assistance. Error Code: 0x907).Ġ圆07 = "Your session ended bacause of an error. Contact your network administrator for assistance. 0x907 = "Your session ended because of unexpected server authentication certificate was recieved from the remote PC.
