RDP not saving do not prompt again

I have a workstation that has a local administrator, which when I rdp into another server, it does not prompt to connect anyway.  I added a domain user, to the local adiminstrators group on the pc.  When I log on as the domain user and build the rdp connection, then save it.  I put the check mark in not to prompt again, then I close out, go back in using my saved rdp icon and it asks again.  Every time!  I have found in the registry where it should be updating and the domain user (with local admin rights (built-in Administrators)) won't save the setting like the 'local' administrator.  This is for Windows 7 Pro, 64-bit op system.  What am I missing?  Thanks, Mike
sborchersAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
sborchersConnect With a Mentor Author Commented:
I found the only way to get this to work was rename the Registry Key Terminal Server Client.  Then make a new Terminal Server Client key.  Once I did that it would save my prompt to not ask me again to verify I wanted to connect.  The key is located in HKCU\Software\Microsoft\Terminal Server Client.
0
 
JohnBusiness Consultant (Owner)Commented:
Check in the expanded RDP settings to see if you are saving credentials there.

Windows-7-RDP-Settings
Also look in Control Panel, Credential Manager. Are the credentials in there? I think they should be.

You can try running System File Checker to see if that corrects Windows issues. Run SFC /SCANNOW and allow to complete. Restart and test.

.... Thinkpads_User
0
 
KwoofCommented:
I agree with above...click show option in the lower left and check the box as Thinkpads_User indicated.

When connecting to a server...also consider whether you want to use the /admin switch to take over the console session as well, instead of creating a separate login session on that server.
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
KwoofCommented:
That's a good solution, although I am wondering what was causing the original key to fail.  I use RDP a lot, and have never run into that situation.
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
Maybe the key is write-protected :D
0
 
sborchersAuthor Commented:
I checked the permissions for the key and the user had Full Access.  There was no reason for it to fail, but it was.  I know I shouldn't have had to do it, but I had spent about 4 hours trying everything else.  Thanks, Mike
0
 
chanderpal singh rathoreMicrosoft Exchange EngineerCommented:
Hi,

You can use mREMOTEng software it will help you to solve your problem, this will remember our all credentials.
0
 
sborchersAuthor Commented:
Ended up trying this, and it worked.  Nothing else had worked up until this point.  Including the suggested solutions.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.