S
Simon White
Guest
I have secure website used by clients to connect to terminal servers. When
they click a link a dynamically created RDP file is returned launching their
Remote Desktop Connection. However, they are now prompted for a password
despite the fact that it was supplied in the RDP file. The terminal servers
all use SSL and I have turned off the prompt for credentials item in the RDP
file.
If they login and save their password then it appears to work fine on
subsequent connections however the problem is that they usually do not know
the password having not needed it in the past. I would actually prefer not
to give it to them so that I can change them on a regular basis without
having to tell them.
So is my problem related to a "User name hint" bug I read about or is there
no way now to automate connection to a terminal server without user
intervention?
The clients are using RDC v6 connecting to Window 2003 servers.
they click a link a dynamically created RDP file is returned launching their
Remote Desktop Connection. However, they are now prompted for a password
despite the fact that it was supplied in the RDP file. The terminal servers
all use SSL and I have turned off the prompt for credentials item in the RDP
file.
If they login and save their password then it appears to work fine on
subsequent connections however the problem is that they usually do not know
the password having not needed it in the past. I would actually prefer not
to give it to them so that I can change them on a regular basis without
having to tell them.
So is my problem related to a "User name hint" bug I read about or is there
no way now to automate connection to a terminal server without user
intervention?
The clients are using RDC v6 connecting to Window 2003 servers.