Nightmare with saved credentials

[Guest JJ]

I'm using Remote Desktop Connection (mstsc.exe 6.0.6000.16386) on XP

Pro for remote administration of a number of Windows 2000 Server (SP2

and all the latest patches) and Windows Server 2003 machines.

 

I'm trying to get the client to remember credentials and passwords for

the remote connections so that I can simply click a shortcut to

connect to any one of the servers. I'm having mixed luck at doing

this. One of the odd things is that connections where it once

successfully remembered the credentials, it now no longer does.

 

For the Windows 2003 Servers, when I load a RDP file, or even just

type in the host name, I see:

 

--------------------------------------------------------------------------------------------------------------

The saved credentials for this remote computer wil be used to

connect. You can edit or delete these credentials.

 

[ ] Always ask for credentials

--------------------------------------------------------------------------------------------------------------

 

But on the other servers, I see only:

 

--------------------------------------------------------------------------------------------------------------

You will be asked for credentials when you connect.

--------------------------------------------------------------------------------------------------------------

 

And indeed, I am asked (on the client side). When I check "Rember my

password" the credentials are never remembered. I have no problems

logging in - that works perfectly. Just that the client machine

refuses to remember credentials for most of my remote computers.

[Guest Vera Noest [MVP]]

Re: Nightmare with saved credentials

 

There has been quite a design change in the new rdp client.

Here are the details:

 

Vista Remote Desktop Connection Authentication FAQ

http://blogs.msdn.com/ts/archive/2007/01/22/vista-remote-desktop-

connection-authentication-faq.aspx

 

Read this as well:

 

TS connection experience improvements based on RDP 6.0 client

customer feedback

http://blogs.msdn.com/ts/archive/2007/03/28/ts-connection-

experience-improvements-based-on-rdp-6-0-client-customer-

feedback.aspx

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

*----------- Please reply in newsgroup -------------*

 

JJ <jim.mcatee@gmail.com> wrote on 21 aug 2007:

> I'm using Remote Desktop Connection (mstsc.exe 6.0.6000.16386)

> on XP Pro for remote administration of a number of Windows 2000

> Server (SP2 and all the latest patches) and Windows Server 2003

> machines.

>

> I'm trying to get the client to remember credentials and

> passwords for the remote connections so that I can simply click

> a shortcut to connect to any one of the servers. I'm having

> mixed luck at doing this. One of the odd things is that

> connections where it once successfully remembered the

> credentials, it now no longer does.

>

> For the Windows 2003 Servers, when I load a RDP file, or even

> just type in the host name, I see:

>

> -----------------------------------------------------------------

> --------------------------------------------- The saved

> credentials for this remote computer wil be used to connect.

> You can edit or delete these credentials.

>

> [ ] Always ask for credentials

> -----------------------------------------------------------------

> ---------------------------------------------

>

> But on the other servers, I see only:

>

> -----------------------------------------------------------------

> --------------------------------------------- You will be asked

> for credentials when you connect.

> -----------------------------------------------------------------

> ---------------------------------------------

>

> And indeed, I am asked (on the client side). When I check

> "Rember my password" the credentials are never remembered. I

> have no problems logging in - that works perfectly. Just that

> the client machine refuses to remember credentials for most of

> my remote computers.

[Guest JJ]

Re: Nightmare with saved credentials

 

On Aug 21, 5:14 am, "Vera Noest [MVP]" <Vera.No...@remove-

this.hem.utfors.se> wrote:

> There has been quite a design change in the new rdp client.

> Here are the details:

 

I'm afraid they tell me nothing about why credentials aren't being

saved for some of the remote connections, while they are saved for

others.

 

One thing that is different is that they're in two different Windows

domains. The ones that I can save are for a W2k3 domain, while those

that can't be saved are in a W2k domain. The rdp client machine is in

neither of these domains. Is it possible that a domain policy in the

W2k domain is preventing the client machine from saving the

credentials locally?

 

If I muck about in the registry and populate it with username "hints"

then I can at least get the rdp client to populate the domain\username

and then I only have to enter a password.

[Guest Vera Noest [MVP]]

Re: Nightmare with saved credentials

 

JJ <jim.mcatee@gmail.com> wrote on 21 aug 2007 in

microsoft.public.windows.terminal_services:

> On Aug 21, 5:14 am, "Vera Noest [MVP]" <Vera.No...@remove-

> this.hem.utfors.se> wrote:

>> There has been quite a design change in the new rdp client.

>> Here are the details:

>

> I'm afraid they tell me nothing about why credentials aren't

> being saved for some of the remote connections, while they are

> saved for others.

 

I think that there are a number of causes described in those 2 blog

posts, but it's impossible for me to know exactly which one applies

to your situation without knowing exactly how you are making the

connection.

The second post also lists a number of design changes, based on

similar feedback as yours, which are inplemented in the 6.1 beta.

I do not know when 6.1 will be available for general download.

> One thing that is different is that they're in two different

> Windows domains. The ones that I can save are for a W2k3

> domain, while those that can't be saved are in a W2k domain.

> The rdp client machine is in neither of these domains. Is it

> possible that a domain policy in the W2k domain is preventing

> the client machine from saving the credentials locally?

 

Yes, that possible. Would be this hotfix:

 

839918 - Hotfix that lets you control whether a user can save a

password for Remote Desktop Connection sessions to a terminal

server in Windows XP or in Windows 2000

http://support.microsoft.com/?kbid=839918

> If I muck about in the registry and populate it with username

> "hints" then I can at least get the rdp client to populate the

> domain\username and then I only have to enter a password.

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___