Re: Editing Term Services RDP File to stop blocking credentials

Ok, re-reading the thread I am brain dead.

Yes, I am using the v6.0 client. but the link doesn't work to get to the
information you mentioned, let me see if I can get to it through a search.

"Vera Noest [MVP]" wrote:

But now it looks to me as if you are talking about the new rdp 6.0
client (aka the Vista client) and not the rdp 5.2 client which
comes with XP SP2.

Can you verify exactly which rdp client version you are running?

And if you are running version 6, then you'll want to read this:

Vista Remote Desktop Connection Authentication FAQ
http://blogs.msdn.com/ts/archive/2007/01/22/vista-remote-desktop-
connection-authentication-faq.aspx

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?S2VuIE1vbnRnb21lcnk=?=
<KenMontgomery@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 06 feb 2007:

Thanks for the replies Vera but that doesn't make Microsoft's
product viable.

I work in a healthcare environment with standardized logins for
most of my nursing and physician PC's. There is an application
that works via Terminal Services/RDP. This application requires
a specific user login and in the past we have setup an RDP file
on the first client for each Windows user ID -let me try to
explain that clearer... say a physician workstation - We give
it a Windows login (physician) and password, set the unit to
auto-login. On the desktop then we saved an RDP connection,
including username and password.

The new version of RDP won't allow you to even ENTER the
credentials, let alone save them. It from the get go says that
credentials will be entered when you connect, which when you do
that, even if you tell it to save them, it erases them and you
have to enter them every time.

This is not at all practical in my environment, since the
application requires a login as well.

Any thoughts?

"Vera Noest [MVP]" wrote:

How exactly are you storing the credentials?
Maybe you are trying to copy a preconfigured rdp file to your
users? That won't work. For security reasons, the password is
encrypted in such a way that only the same user, on the same
machine, can decrypt it.
You'll have to teach the users that they type in their password
on first connection, and save it into the rdp file.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?S2VuIE1vbnRnb21lcnk=?=
<KenMontgomery@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 05 feb 2007
in microsoft.public.windows.terminal_services:

The RDP Client with Windows XP Service Pack 2... sorry can't
recall the version

"Vera Noest [MVP]" wrote:

Which version of the rdp client are you using, Ken?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?S2VuIE1vbnRnb21lcnk=?=
<KenMontgomery@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 05 feb
2007 in microsoft.public.windows.terminal_services:

I have seen the posts on here regarding saving of
credentials and hard coding them into the RDP file. Well,
that doesn't seem to work with Windows XP SP2 and a
Windows 2000 Terminal Services server. The hard-coded
credentials are ignored... any ides how I can get around
this, I really don't want my physicians trying to remember
another password for this application.

.

Relevant Pages

  • Re: How to stop prompt for Credentials?
    ... Microsoft MVP - Terminal Server ... Virtual Client Solutions ... password and the RDC just uses what it finds in the RDP file. ... Vista Remote Desktop Connection Authentication FAQ ...
    (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: Terminal Services Client 6.0 Authentication
    ... The problem we are having is that the username that is being cached is ... Each one is a unique machine, and as such the client should ... allow you to save a set of credentials for each. ... Credentials are not stored in the rdp file any more. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: saving password in rdp file
    ... forced to enter their new password in the rdp file anyway, ... local TS account or the domain account). ... MCSE, CCEA, Microsoft MVP - Terminal Server ... for the rdp client software. ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal Services Client 6.0 Authentication
    ... The new client can give roughly the same auth behavior as the old client, it just works a little different on the front end. ... Connect to your XP Pro machine, but stop at the Log On to Windows prompt, with your user name pre-filled and the password box blank? ... In order to do this, you need to open up the client (manually, not specifiying .rdp file) and connect to your XP Pro machine using the same computer name stored in your .rdp file. ... What is the point to the "Remote Desktop Connection" dialog? ...
    (microsoft.public.windowsxp.work_remotely)