Two different RDP sessions with different Usenames to same TS Server

  • Thread starter Thread starter benxxv via WinServerKB.com
  • Start date Start date
B

benxxv via WinServerKB.com

Guest
Hi,

I published RemoteAPP for two different applications in my TS Server 2008.

In the client computers, I need to save two different Windows usernames for
these two RemoteAPP sessions.

But, the problem is, the RDP RemoteAPP is able to save only one username for
both the sessions. Can anybody suggest how to do this as per my above
requirement.

Regards.

--
Message posted via WinServerKB.com
http://www.winserverkb.com/Uwe/Forums.aspx/windows-ts/200809/1
 
Re: Two different RDP sessions with different Usenames to same TS Server

From:

http://blogs.msdn.com/ts/archive/2007/03/28/ts-connection-
experience-improvements-based-on-rdp-6-0-client-customer-
feedback.aspx

Feedback #6: The pre-populated user name in the credentials dialog
does not match the user name that is in the RDP file.

Most users make a TS connection in one of two ways:

Style #1 by double-clicking a custom RDP icon published by your
admin or a custom RDP file authored by you.
Style #2 by launching the "Remote Desktop Connection" icon in the
Accessories folder on the Windows Start menu and typing in the
remote computer name and user name and then clicking the "Connect"
button, or by typing mstsc.exe from a command prompt. Whenever you
use this style, TS client uses the default.RDP file.

With the RDP 5.0 client, when you use a custom RDP file, it always
reads the user name from the file. It is optimized for users
following connection style #1. The downside with the RDP 5.0 client
is that if your connection style is #2, and you connect to five
different TS servers in a day, you will be required to enter the
user name again and again because it shows only the most recently
used computer name and user name.

In RDP 6.0 client, we have optimized it for connection style #2
users but we understand that this approach breaks the "TS Remote
Admin" scenario with connection style #1 where two different RDP
files with two different user names are used for the same TS
server, or where you want to use a custom RDP file with the user
name pre-filled for you by your administrator.

Here is a proposed new solution to address both these cases.
Whenever the TS client uses the default RDP file (this is the case
for connection style #2), it will always use the user name hint
from the registry. Whenever you use a custom RDP file (this is the
case for connection style #1), it will read from the RDP file if it
is available, or else it will read the user name hint from the
registry. With this proposed solution, we think we'll be able to
address both connection styles that customers use and all possible
edge scenarios supported by RDP 5.0 clients. Please let us know
your feedback.


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

"benxxv via WinServerKB.com" <u30064@uwe> wrote on 29 sep 2008 in
microsoft.public.windows.terminal_services:

> Hi,
>
> I published RemoteAPP for two different applications in my TS
> Server 2008.
>
> In the client computers, I need to save two different Windows
> usernames for these two RemoteAPP sessions.
>
> But, the problem is, the RDP RemoteAPP is able to save only one
> username for both the sessions. Can anybody suggest how to do
> this as per my above requirement.
>
> Regards.
 
Re: Two different RDP sessions with different Usenames to same TS Server

Dear Vera,

We found a workaround, which working fine now for the moment for our problem,
but we are monitoring this for a long run functionality.

================
Unfortunately, CredMan (a core Windows component which stores credentials for
RDP 6.0+) does not allow more than one set of saved credentials for a single
server. The .rdp file has nothing to do with it; the client looks up the
saved creds in CredMan based off the address of the server provided.

If you only need two sets of saved credentials, one workaround is to save one
set of credentials under the NetBIOS name, and another under the fully
qualified domain name.

Ex.

mycomp.domain.com

and

mycomp

can each have individually saved credentials, so if you are on a network
where mycomp will resolve to the same machine anyway, you can have two sets
of saved credentials by saving one set under each version of the server name.

The same approach would work if your machine is registered in your local DNS
under multiple aliases; each alias can have a different set of saved creds.

Reference URL:
http://social.technet.microsoft.com...S/thread/70a2c53d-cd70-4378-96d8-5b19bc5994ba

==================

Please provide your feedback.

Regards.


Vera Noest [MVP] wrote:
>From:
>
>http://blogs.msdn.com/ts/archive/2007/03/28/ts-connection-
>experience-improvements-based-on-rdp-6-0-client-customer-
>feedback.aspx
>
>Feedback #6: The pre-populated user name in the credentials dialog
>does not match the user name that is in the RDP file.
>
>Most users make a TS connection in one of two ways:
>
>Style #1 by double-clicking a custom RDP icon published by your
>admin or a custom RDP file authored by you.
>Style #2 by launching the "Remote Desktop Connection" icon in the
>Accessories folder on the Windows Start menu and typing in the
>remote computer name and user name and then clicking the "Connect"
>button, or by typing mstsc.exe from a command prompt. Whenever you
>use this style, TS client uses the default.RDP file.
>
>With the RDP 5.0 client, when you use a custom RDP file, it always
>reads the user name from the file. It is optimized for users
>following connection style #1. The downside with the RDP 5.0 client
>is that if your connection style is #2, and you connect to five
>different TS servers in a day, you will be required to enter the
>user name again and again because it shows only the most recently
>used computer name and user name.
>
>In RDP 6.0 client, we have optimized it for connection style #2
>users but we understand that this approach breaks the "TS Remote
>Admin" scenario with connection style #1 where two different RDP
>files with two different user names are used for the same TS
>server, or where you want to use a custom RDP file with the user
>name pre-filled for you by your administrator.
>
>Here is a proposed new solution to address both these cases.
>Whenever the TS client uses the default RDP file (this is the case
>for connection style #2), it will always use the user name hint
>from the registry. Whenever you use a custom RDP file (this is the
>case for connection style #1), it will read from the RDP file if it
>is available, or else it will read the user name hint from the
>registry. With this proposed solution, we think we'll be able to
>address both connection styles that customers use and all possible
>edge scenarios supported by RDP 5.0 clients. Please let us know
>your feedback.
>
>_________________________________________________________
>Vera Noest
>MCSE, CCEA, Microsoft MVP - Terminal Server
>TS troubleshooting: http://ts.veranoest.net
>___ please respond in newsgroup, NOT by private email ___
>
>"benxxv via WinServerKB.com" <u30064@uwe> wrote on 29 sep 2008 in
>microsoft.public.windows.terminal_services:
>
>> Hi,
>>

>[quoted text clipped - 9 lines]
>>
>> Regards.


--
Message posted via WinServerKB.com
http://www.winserverkb.com/Uwe/Forums.aspx/windows-ts/200809/1
 
Back
Top