Apr 28 2020 10:47 AM
Apr 28 2020 10:47 AM
May 04 2020 10:40 AM
May 07 2020 07:05 PM
Hi David, FYI...
Since the 126.96.36.199.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.
May 08 2020 04:53 PM
@sayl01 just to make sure so we can review the list of changes. Did the issue appear in version 675, 790 or 945?
May 11 2020 06:08 AM
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):
Arguments = "start SCardSvr"
Let me know if I can help with any further diagnostics details.
May 11 2020 08:30 AM
@msft_jasonparker You can set the default Display Settings using custom RDP properties:
May 11 2020 08:41 AM
Thanks @sayl01 . For reference, I filed the following to investigate: Bug 26364594 : Smart cards stopped working starting in 1.2.790.
May 11 2020 08:54 AM
May 11 2020 09:11 PM
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
May 20 2020 07:47 AM
Jun 03 2020 10:30 AM
Jun 03 2020 10:55 AM