Re: Terminal Services Client 6.0 Authentication

Thanks for the tips, I have another question.

The problem we are having is that the username that is being cached is
not correct.

The first time I login to ts.mydomain.com I use
username
password

The next time I login it cached
ts.mydomain.com\username

The correct username would be
mydomain.com\username

This is annoying and worst of all users don't know what is wrong.

Is there a way to make the machine cache the correct username?

Thanks
Ben
TP wrote:
You are not doing anything wrong. I am drafting a response
to Rob Leitman regarding a different issue where I plan to
bring this up. The credentials are stored on a per-name
basis, and not only that they do not take into account custom
ports.

So, for example, you can have several TS servers/XP Pro
machines addressable through one ip address, like so:

ts.contoso.com
ts.contoso.com:6000
ts.contoso.com:6001
ts.contoso.com:6002

Each one is a unique machine, and as such the client should
allow you to save a set of credentials for each. Instead it only
allows *one* set of credentials, because they all have the
same name: ts.contoso.com.

Credentials are not stored in the rdp file any more. Of course
it would be possible for MS to modify the client so that it
could store a unique credential set for each unique rdp file.

You can run the 5.2.3790.x client version alongside the 6.x
version if you want without problems. The new version will
use credentials that were stored in the .rdp file by the old
version.

Keep in mind that the primary reason the new client exists
is to allow you to use the new features when connecting to
Vista and Longhorn server. It is an optional update.

Also, saving credentials in a text file is not considered
secure, even though the password is encrypted. Even the
new method of storing them is a security risk and there is
a Group Policy to disable the feature.

-TP

dwgeis@xxxxxxxxx wrote:
TP, I have a question about the saved credentials. The credentials
seem to be saved by *machine* not by RDP file.

In other words, if I want to create two RDP files to connect to the
same machine with two different sets of credentials it does not work.
Every time I changed the saved credentials in the one RDP file, it
changes them in the other file. This used to work. What am I doing
wrong?

.

Relevant Pages

  • Re: Editing Term Services RDP File to stop blocking credentials
    ... choose Client Configuration on the menu on the ... MCSE, CCEA, Microsoft MVP - Terminal Server ... have setup an RDP file on the first client for each Windows ... credentials, let alone save them. ...
    (microsoft.public.windows.terminal_services)
  • Re: RDP6 .rdp files no longer allow for saved passwords?
    ... version 6 of the Remote Desktop Client does *not* store credentials in the .rdp file. ... If you have an existing .rdp file (created w/5.x client) with crendentials already stored, ... The *primary* reason for version 6 is to allow you to use the new features when connecting to Vista and Longhorn Server. ...
    (microsoft.public.windows.terminal_services)
  • Re: Modifying default behaviour of MS VPN client
    ... Would you be willing to completely disable CredentialCaching? ... > username and password and have the client retrieve the login credentials ...
    (Focus-Microsoft)
  • Re: Launching RDP session from script
    ... So you have saved your connection settings, including your username ... Does it work when you double-click the rdp file manually? ... And the client OS needs to be XP for you to be able to ...
    (microsoft.public.windows.terminal_services)
  • Re: Editing Term Services RDP File to stop blocking credentials
    ... I am using the v6.0 client. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... credentials, let alone save them. ... Maybe you are trying to copy a preconfigured rdp file to your ...
    (microsoft.public.windows.terminal_services)