Windows Server 2003 & RDP6.0

[Kqueno]

We are running a Windows 2003 Server with terminal services. We use Windows RDP 6.0 to get into our terminal server.

The small problem we are having for our users is:

When they open up rdp to log into the server, it shows

username
password
(local computer)

It is confusing our users because they don't know to select the domain from the drop down window.

I want it to default to the domain every time but I have no clue how to do that.

Would any of you have any ideas?

 

[nessus]

Save a .rdp file with the correct settings to the user's desktop. Have them double-click that to lauch their session.

 

[Kqueno]

I tried that but in RDP 6.0 there is no place to save the domain to log into every time.

All this used to work fine but somehow the Domain got changed to the local machine for every computer that logs into that server.

Another thing, for every rdp 6.0 we have out there, we have edited it with notepad and type in enablecredsspsupport:i:0 so it will look the same as the rdp 5.0 log in (without the login credentials bs). Our users get confused so easy.

 

[Azhar]

have you tried using domain\user in the username box then saving the profile instead of selecting a domain from the drop menu?

for instance, instead of

johndoe
pass1234
TehDomain

you would use

TehDomain\johndoe
pass1234

then save the profile

 

[Kqueno]

Yes ive tried that but our users are too stupid and would call us about it. That works but it is still confusing for them.

I am thinking it is a windows update that somehow changed everything to default to the local machine, RDP 6.0 sux PERIOD

 

[Azhar]

yes at the moment it does.

but RDP's got a big facelift coming with TS Gateway using port 443, and I'm really looking forward to it.

Citrix simply cost too fucking much money

(I've also been thinking about 2X Application Server, but I don't know anyone who use it and I don't want to be the first lol)

I can't think of anything else to suggest to you. Our company use an intranet and sharepoint site defaulted as our employee's home startup page. On the main page is tips and announcements. Maybe you can throw up a reminder how to find your company domain name which is needed for many things, not just RDC.

Exchange use domain/user, as do Sharepoint and Windows log-in and other Active Directory related authentication.

 

[nessus]

Yes ive tried that but our users are too stupid and would call us about it. That works but it is still confusing for them.

I am thinking it is a windows update that somehow changed everything to default to the local machine, RDP 6.0 sux PERIOD

Why do your users have access to Windows Update? Even if you let the users source their updates from there instead of a location on your LAN, you should at least have a WSUS server set up so that you control which patches they are allowed to access. If you are just using it to present which patches are avaiable, and then let the clients actually pull the files fro the MS Widows Update site, it takes very few resources. Even using it to host files for 5000 clients doesn't take much of a box.

The RDP 6.0 client has some great features, but if you don't have anything on the backend set up for it there is no benefit and a lot of change from an end user perspective. We still haven't deployed it to our end user environment.

 

[Kqueno]

We do have WSUS and I think one of the update patches changed RDP 6.0 to want to default to the Local Account login instead of wanting to login to the domain. It used to work fine and default to the domain every time, I just cant think of anything else that would have changed it. It was either a RDP 6.0 patch or a Windows Terminal Server patch.

It's more of an annoyance to me than a problem. We have some pretty dumb users though