Version 1.2.945 of the Windows Desktop client for WVD has been released to all users!

[David Belanger]

This morning we released the April update of the Windows Desktop client (MSRDC) to all users.

Check out What’s New in this release.

[#2]

Is there a registry setting to enable admins to set the display setting during installation?

[#3]

@David Belanger 

Hi David, FYI...
Since the 1.2.6.7.5.1955 version of the client, Smartcard login (using native MS stack - no third party mindriver etc) appears to have broken. Both versions 1.2.7 and this1.2.9 release fail to read the smartcard upon connection with erro displayed to the user "This smartcard could not be used. Additional details may be in the system event log. Please report this error to your administrator."

No error message appear in logs other than security logon failure 4625 with Sub Status: 0xC0000321 which would indicate a driver load failure.

Smartcard logon can be made successful with these client version by manually starting "SCardSvr" (on the target) when the user is trying to log on. This would also suggest that connections with the new clients are not initating the triggers for necessary services for either hardware driver initiation or certificate propagation.

When using msrdc (1.2.7 or 1.2.9) with vendor minidrivers installed it will randomly connect successfully but the session typically crashes (not always) after logon with no mainstream logs showing any errors.
S.

[#4]

@sayl01 just to make sure so we can review the list of changes. Did the issue appear in version 675, 790 or 945?

[#5]

@David Belanger 

Version 1.2.675.0 works fine. Fails on 1.2.790.0 & 1.2.945.

As 1.2.675 does not enumerate apps from the ARM URL, its not viable for anyone testing the Spring 2020 WVD release to downgrade the client (workaround below).

For further testing, I used msrdc.exe with a custom RDP file to connect directly to the Win10 clients to rule out the WVD gateway /session host infrastructure encapsulation and redirection. I also validated against Windows 1909 and 1903 builds for the receiving host. All test cases exhibit the same symptoms. (1.2.675.0 works fine with smartcard. Smartcard logon fails on 1.2.790.0 & 1.2.945)

WORKAROUND: Implementing the following to start the smartcard service on logon provides a workaround for client versions 1.2.790.0 & 1.2.945. Not ideal but it works..

Create a scheduled task to execute on Application Event ID=9027 (Source: Desktop window Manager):

Command= "net.exe"

Arguments = "start SCardSvr"

Let me know if I can help with any further diagnostics details. 

S.

[#6]

@msft_jasonparker You can set the default Display Settings using custom RDP properties:

https://docs.microsoft.com/en-us/azure/virtual-desktop/customize-rdp-properties

[#7]

Thanks @sayl01 . For reference, I filed the following to investigate: Bug 26364594 : Smart cards stopped working starting in 1.2.790.

[#8]

Renamed the "Update" action for Workspaces to "Refresh" for consistency with other Remote Desktop clients.
You can now refresh a Workspace directly from its context menu.
Manually refreshing a Workspace now ensures all local content is updated.
You can now reset the client's user data from the About page without needing to uninstall the app.
You can also reset the client's user data using msrdcw.exe /reset with an optional /f parameter to skip the prompt.
We now automatically look for a client update when navigating to the About page.
Updated the color of the buttons for consistency.

[#9]

@David Belanger 

Just deployed spring update in a CX environment. Can use the web client with no issue but the thick client cannot authenticate. Ticket open with support, but seeing if this group may know what to check here. DNS is pointed at the on-prem servers and ExpressRoute is being used. Desktop client v1.2.945 is receiving the attached error message

[#10]

See the following post for information on this issue and current workaround.
https://techcommunity.microsoft.com/t5/windows-virtual-desktop/windows-client-for-spring-update-2020...

[#11]

Does the MSRDC allow only Windows endpoint devices to be able to remote into WVD or is it for non windows endpoint devices be able to remote into WVD as well?

[#12]

There are clients for various Client OS including a web client that works with any HTML 5 compatible browser. The clients have varying features for redirection support. Its worth checking the following URL to check the features per OS:
https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-deskto...

Individual Client links
Windows Desktop client: https://docs.microsoft.com/en-us/azure/virtual-desktop/connect-web
Web client: https://docs.microsoft.com/en-us/azure/virtual-desktop/connect-web
Android client: https://docs.microsoft.com/en-us/azure/virtual-desktop/connect-android
macOS client: https://docs.microsoft.com/en-us/azure/virtual-desktop/connect-macos
iOS client: https://docs.microsoft.com/en-us/azure/virtual-desktop/connect-ios