You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Those credentials will be used automatically in the Hyper-V enhanced session mode. If you want to enable autologon in the Hyper-V basic session mode, set the following registry keys:
54
+
Those credentials will be used automatically in the Hyper-V enhanced session mode, and inside a RDP session with RDP NLA disabled. Here are a few example user names with their correct mapping for reference:
For regular RDP, a credential provider can only *complement* RDP NLA but not *substitute* it. The only way to really perform autologon in RDP where the client sends no credentials is to disable RDP NLA on the client and server.
82
+
83
+
With mstsc.exe, save your .RDP file (Default.rdp) and add or edit the following line to it: `enablecredsspsupport:i:0`.
84
+
85
+
In the RDP server, ensure RDP NLA enforcement is disabled:
You should now be able to connect with no credentials sent from the client, with a server that will perform automatic logon with the saved credentials.
92
+
93
+
## RDP with NLA
94
+
95
+
RDP NLA performs NTLM or Kerberos authentication *before* the full credentials are delegated to the server and sent to Winlogon. This means it is unfortunately not possible for the server to just connect without authenticating, and have the credential provider perform autologon on behalf of the client. The only thing the credential provider can do is customize the authentication with additional steps, but it cannot fully replace it. For this reason, the current credential provider does nothing useful with RDP NLA.
96
+
63
97
## Logging
64
98
65
99
To enable logging, set the **LogEnabled** registry key. The log files will be located in "%ProgramData%\RdpCredProv":
0 commit comments