Update:
Try to edit your .rdp file and change the following parameter from 0 to 1:
use redirection server name:i:1
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
KB5018410 on W10 21H2 with its new mstsc.exe kills our local Single-Sign-On experience on a Server 2019 RDS farm which has worked for several years. KB5017380 (the 2022-09 preview update that was on WSUS for one day in September) did the same.
Clients without that update are still working fine. An affected client is working again after uninstalling the update or manually replacing the mstsc.exe and corresponding dll from a client that has not yet received the update.
We are using one 2019 RDS Broker with a valid certificate and several RDSH. GPO sets the delegation of standard credentials as well as the trusted SHA thumbprint of the cert. No Web Access or gateway in use, only local connections.
When trying to log on using a predefined .rdp file and the logged-in client user credentials (SSO), the server shows "Other user: invalid username or password" on a regular Windows 2019 login screen with picture background. After clicking OK, the username field is already filled and when you type your password manually, you get logged in. The session itself seems to work properly, once logged in.
Broker eventvwr shows lots of event IDs 4625/4648 with code 0xC000006D/0xC0000064. No matter which RDSH an affected clients gets redirected to, result is the same. It's clearly related to the mstsc.exe build (.2075) of the client. Servers did not get installed 2022-10 updates yet. Similar for W11 clients that got updated.
Other admins on different forums have confirmed they are having the same issue, no solution yet.
Disabling UDP does not change this.
Any ideas? Thanks!
Update:
Try to edit your .rdp file and change the following parameter from 0 to 1:
use redirection server name:i:1
Experiencing the same problem. Do you have any links to other threads where you have read about this?
Hi Nielsen,
for example: https://www.reddit.com/r/sysadmin/comments/y0z1xa/comment/iso9gf8/
This one is using Server 2022, but i assume it's not related to the server OS version.
Best regards
I encountered this problem with a Windows Server 2019 RDS farm. Surprisingly, the same workstations don't experience the problem with an identically configured Windows Server 2016 RDS farm.
We encounter the same issue and
use redirection server name:i:1
did not help.
Any other hints on how getting this issue solved?