WORKAROUND: Implementing the following to start the smartcard service on logon provides a workaround for client versions 1.2.790.0 & 1.2.945. All test cases exhibit the same symptoms.
I also validated against Windows 19 builds for the receiving host. Fails on 1.2.790.0 & 1.2.945.Īs 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).įor 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. 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 Belanger 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. 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. No error message appear in logs other than security logon failure 4625 with Sub Status: 0xC0000321 which would indicate a driver load failure.
Please report this error to your administrator." Additional details may be in the system event log. 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. version of the client, Smartcard login (using native MS stack - no third party mindriver etc) appears to have broken.
0 kommentar(er)
