Terminal server client saved credentials issue
I have the following problem: I use to connect and reconnect to several servers many times, every day. When connecting for the first time after startup to each server mstsc does not use saved password . It prompts :You will be asked for credentials ...." I save them, and on subsequent connections credentials can be reused, edited and deleted -- the normal behaviour After restarting the computer, it forgets all passwords I saved !!!. The usernames for each server are still remembered. This happens only for ONE user account, that is exactly the account I use every day. If I log as other user, be it "Administrator" or else, with admin rigts or else, this phenomenon does not occur, credentials are remembered correctly after restarting, I tried .RDP files that work, created with under other accounts that work, I've browsed through the registry with no result. The policy settings contain only one setting that refers to terminal server and it is the same for all accounts and any fidling with it did not have any efect. All may searches for a hint were in vain. Could anyone help? I use XP sp3, mstsc reports version 6.0 , but I understood that it is 6.1 (from posts I read) - anyway it is the latest version that does not store passwords in the RDP files, but somewhere else (where might that be?) Thanks Dan N
March 26th, 2010 5:51pm

I am having this EXACT same issue. Have you found a resolution yet? I really need to get this fixed! Having retype dozens of alpha-numeric gibberish everyone morning is getting REALLY old!
Free Windows Admin Tool Kit Click here and download it now
May 6th, 2010 10:27pm

I am having this EXACT same issue. Have you found a resolution yet? I really need to get this fixed! Having retype dozens of alpha-numeric gibberish everyone morning is getting REALLY old! well, no. Not yet at least. To be sure you have the same exact problem: I have only one discriminated user that can't store his passwords overnight (over restart or logout) but keeps them saved during the session. The other users work ok. Try to create an new user. I do my work under other username and keep the faulty one for the purely academic curiosity to find a solution. Good luck Dan N
May 7th, 2010 8:51am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics