Expiring Today—Celebrate National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17


Remote Desktop Connection, “The server’s authentication policy does not allow connection requests using saved credentials. Please enter new credentials.”

Published on
3,409 Points
1 Endorsement
Last Modified:
Resolving an irritating Remote Desktop connection that stops your saved credentials from being used.

My goal was to have a thin client connect automatically to the terminal server when it was started without intervention, but I was stopped by a persistent request for Remote Desktop credentials, even though they were set to save and I could manually type in the password to successfully connect. 

Investigation online revealed several solutions for similar issues, but the actual fix was simple and not mentioned elsewhere, which is why I wrote this article.

The thin clients are running Windows 7 embedded Standard addition. The terminal server is running Windows Server 2008 SP2 (32-bit). This is in a Workgroup environment.  

The pop up error looks like this:

To resolve the issue, perform the following steps on the terminal server.

  1. At a command prompt edit the Group Policy settings by typing "gpedit"
  2. Under the Local Computer Policy, drill down to Computer Configuration>Administrative Templates>Windows Components>Terminal Services>Terminal Server>Security
  3. Disable "Always prompt for password upon connection"
  4. At a command prompt update the group policy by typing "gpupdate"

The Group Policy change is pictured here:

Making this simple change allowed the thin client to auto logon using saved credentials and I was able to place the saved .RDP file in the startup folder, so a connection is automatically made as soon as the thin client powers up.

With just this one change the thin client was able to logon to the terminal server without intervention, allowing reconnect anytime there is a power disruption stopping connection to the terminal server. The same saved .RDP file was left on the thin client’s desktop in case connection was lost by some other means. This solution provides an easy and secure method for thin clients to gain access to a terminal server.

Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
LVL 42

Expert Comment

I am glad you figured it out. I was going to say that the behavior is by design. In fact, I have that setting specifically enabled... :-)

Featured Post


Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Join & Write a Comment

Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…
In this video, viewers are given an introduction to using the Windows 10 Snipping Tool, how to quickly locate it when it's needed and also how make it always available with a single click of a mouse button, by pinning it to the Desktop Task Bar. Int…

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month