domain:s: parameter for RDP

[Guest Stephen Jones]

Has anyone got any workarounds for the domain parameter (as used in .rdp),

which stopped working in RDP 6.0?

 

We are a multi-domain, multi-terminal server environment with services

across trusts. It is simply unviable and unreasonable for users to maintain

lists of which domain they should log on to for which terminal server. We

make extensive use of 'hardcoding' the domain so that this is always

corrected listed when they remote desktop.

 

ta in advance,

Steph

[Guest Bart Van Vugt]

RE: domain:s: parameter for RDP

 

I'm also searching for a solution about this issue. But as far as I know it's

not possible due to security reasons.

 

"Stephen Jones" wrote:

> Has anyone got any workarounds for the domain parameter (as used in .rdp),

> which stopped working in RDP 6.0?

>

> We are a multi-domain, multi-terminal server environment with services

> across trusts. It is simply unviable and unreasonable for users to maintain

> lists of which domain they should log on to for which terminal server. We

> make extensive use of 'hardcoding' the domain so that this is always

> corrected listed when they remote desktop.

>

> ta in advance,

> Steph

>

[Guest Stephen Jones]

RE: domain:s: parameter for RDP

 

Ta Bart,

 

Though I'm not sure what 'security' issue is compromised just by wanting to

code the domain name into an RDP which is inside the network? I can

understand it with hardcoding of usernames or passwords in an RDP file, but

not domain name?

 

Here's hoping for a fix but I get the feeling the Terminal Services Team @

MS are not interested - too busy playing with new features all the time.

 

S

 

 

"Bart Van Vugt" wrote:

> I'm also searching for a solution about this issue. But as far as I know it's

> not possible due to security reasons.

>

> "Stephen Jones" wrote:

>

> > Has anyone got any workarounds for the domain parameter (as used in .rdp),

> > which stopped working in RDP 6.0?

> >

> > We are a multi-domain, multi-terminal server environment with services

> > across trusts. It is simply unviable and unreasonable for users to maintain

> > lists of which domain they should log on to for which terminal server. We

> > make extensive use of 'hardcoding' the domain so that this is always

> > corrected listed when they remote desktop.

> >

> > ta in advance,

> > Steph

> >