Remote Desktop Connection not using saved credentials

[Tamas]

Subsequent to I had installed the Remote Desktop correlation 6.0 client to bring up to date (update 925876), I might experience one or additional of the subsequent symptoms: Remote Desktop correlation 6.0 prompts you for credentials previous to I establish a remote desktop correlation. Despite having saved credentials, users are tranquil prompted to enter credentials on the remote server’s winlogon screen. Even although I have comprise and clicked "edit" and place it in my credentials Windows 7 Remote Desktop correlation does not mechanically utilize them. The checkbox "always ask for credentials" is not checkered. When I attach from additional Windows clients to the similar target apparatus their saved credentials are used appropriately. Is this a Windows 7 Remote Desktop correlation bug or am I doing incredible wrong I need some help here related to the topic.

[Sabastiaan]

From here I had been able to get lot of feedback regarding the innovative authentication characteristics introduced in the most recent version or description of the Remote Desktop correlation client. These characteristics are part of our efforts to improve sanctuary for Terminal Services (TS) in Windows Vista and Windows Server code name “Longhorn”, on the other hand some users have comprise and run into a variety of tribulations that have comprise and caused aggravation. In order to alleviate a number of the frustrations, beneath is an FAQ on various symptoms users have run into, along by means of solutions and workarounds.

[Visala28]

When using Remote Desktop Client 6.0 to attach to a Windows 2003 apparatus, some users have comprise to enter credentials double. On one occasion previous to correlation they determine to observe if they comprise Windows XP or Windows Server 2003 as the client if they are using Windows Vista as the client. This is the majority probable the result of the method the remote server is configured. There are two probable settings that might be causing this. The majority probable is the “Always prompt for password” setting is facilitated on the server. In order to put out of action to the setting, the administrator of the server which you are concerning to must run Terminal Server Configuration administrative tool (tscc.msc) and you have to twice hit it off on RDP-Tcp. In the “Logon Settings” tab, there is an alternative labeled “Always prompt for password”.

[teenQ]

On the other hand for the Windows Server 2003, an administrator might comprise to set the group policy situated at: “Administrative Templates\Windows Components\Terminal Services\Encryption and sanctuary\Always prompt client for password upon correlation”. For Vista, this similar policy is situated “Administrative Templates\Windows Components\Terminal Services\Terminal Server\Security\Always at the appointed time client for password upon correlation.” You have to make a note this policy is set as not configured by defaulting; if this has been set retain information it might have been configured moreover on the local group policy or a domain based group policy.

[Candace]

When moreover the alternative in Terminal Server arrangement administrative tool (tscc.msc) is preferred or the group policy is facilitated, the TS server determine to always demonstrate a winlogon prompt, regardless of what version or description of the Remote Desktop Client the user is working. Prompted for Authentication Twice when concerning to Terminal Services in Windows 2000 Server he setting in tscc.msc mentioned in the primary query is facilitated by defaulting on Windows 2000. The administrator be supposed to put out of action this setting to fix the undesired behavior. Afterwards, the user be able to anticipate to not run into the winlogon screen or duplicate prompts.

[David23]

The on top of performance is caused when winlogon on the TS server not be able to validate your credentials. This might be from a number of reasons: For illustration, the password or username might be inaccurate. Additional times, (and this might be the most frustrating to users), the domain might be in a format that is not predictable by the TS server. The most excellent thing to do, when entering credentials into the credentials dialog, is to create certain that the domain, username, and password are the entire in a format that the server determine to recognize.

[MK++]

Again: Screw Microsoft.

The problem happens when administrators who care about security enable this GP Security setting:

[Network access: Do not allow storage of passwords and credentials for network authentication]

This, as misleading as it is, should mean ONLY SMB-related authentication. But, NO, the lame designer @M$ made it a global SessionManager setting: it affects all credentials even those of RDP connections!!!!

SCREW Microsoft!

[EINSTEIN_007]

Again: Screw Microsoft.

The problem happens when administrators who care about security enable this GP Security setting:

[Network access: Do not allow storage of passwords and credentials for network authentication]

This, as misleading as it is, should mean ONLY SMB-related authentication. But, NO, the lame designer @M$ made it a global SessionManager setting: it affects all credentials even those of RDP connections!!!!

SCREW Microsoft!

The error that you are getting is a security setting that determines whether Stored User Names and Passwords saves passwords, credentials, or .NET Passports for later use when it gains domain authentication. If it is enabled, this setting prevents the Stored User Names and Passwords from storing passwords and credentials. For more information visit this site.