It was answer (while incorrect), which led me to the solution. I thought it would be the server that dictates what the client is allowed to do. It was at the same time both subtle, and obvious.Īs mentioned in the question, when i was modifying the following Remote Desktop Connection Client Group Policy settings: Microsoft Forums: Remote Desktop Connection not using saved credentials.Stackoverflow: Windows 7 Remote Desktop Connection Save Credentials not working.MSDN Remote Desktop Services Blog: Saved credentials do not work.: Saving your logon credentials in Remote Desktop Connection.: Saving and changing logon credentials in Remote Desktop Connection.Windows Seven Forums: Windows 7: Remote Desktop Connection Automatic Log On - Allow or Prevent.SuperUser: Remote Desktop connection is ignoring saved credentials.KB281262: How To Turn On Remote Desktop Automatic Logon in Windows XP. *indicates it will use saved credentials, but must re-enter password at 2000 login screen Bonus Reading Windows Server 2003 R2: Yes (Domain controller).The problem is limited to Server 2008, 2008 R2, and 2012: i was wrong when i said it fails on any connection to Server 2003. Results of connecting to every server i can find. The resultant set of policy ( rsop.msc) on the client has Always prompt for password on connect set to Disabled: All machine are joined to the same domain. It also happens when connecting to Windows Server 2008, and Windows Server 2012 (all from Windows 7 client). The client has authenticated the identity of the server: The client is Windows 7, connecting to Windows Server 2008 R2, over RDP 7.1, with the server using an auto-generated certificate: everything from Background on is just filler to make it look like i "attempted some research effort" you can ignore it including this line which talks about ignoring this line.tried setting the group policy on the domain controller.tried both modern and legacy \ian username formats.This needlessly reduces the security of applications.Įither way: it didn't work. Although Kerberos has been available for many years many applications are still written to use NTLM only. NTLM is an outdated authentication protocol with flaws that potentially compromise the security of applications and the operating system. NTLM is an outdated, insecure, and should not be used: People suggest this without realizing that it only applies to NTLM authentication. I tried enabling the "Allow delegating saved credentials with NTLM-only server authentication" for TERMSRV/* in gpedit.msc on the client (e.g. So the question is: How do save credentials when connecting to a machine? Additional things tried You will be asked for your credentials when you connect Notice that Remote Desktop Connection client refuses to save my password, noting: Repeat the above steps 4 or 5 times, on the 6th time creating screenshots for a stackoverflow question. Which default to allowing passwords to be saved, and default to not prompting for credentials, are forced to allow passwords to be saved, and forced to not prompt for passwords:Īnd i run gpupdate /force to ensure the forced off security settings are in use.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |