• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5324
  • Last Modified:

How to set a default domain name RemoteApp login??

I have a question that I have not been able to find an answer to anywhere. We are starting to use Terminal Services remote app. Everything is working fine except that it requires the user to enter their fully qualified domain name. (see attached image). Is there anyway to default this to a certain domain?

Thanks!
remoteapplogin.PNG
0
armfull
Asked:
armfull
  • 2
  • 2
1 Solution
 
DiscusfishCommented:
Have you tried this:
Q: How do I enforce the domain name in the logon dialog box?
Last modified: January 18, 2008

A: By default, the value for Domain/Computer in the logon dialog box is taken from the last logon that was used on the console. You can override this and force the correct domain name in the login box i Terminal Services Configuration:

   Start - Administrative tools - Terminal Services Configuration - right-click RDP-tcp connection -
   Properties - Logon Settings - select "Always use the following information"

Leave the User name and Password fields blank and enter the domain name you would like as the default in the Domain field.
Also make sure that you check the box for "Always prompt for password".

From:
http://ts.veranoest.net/ts_faq_configuration.htm#logondomain
0
 
armfullAuthor Commented:
I had read that document but just assumed that it was for RDP only and not RemoteApp.
0
 
Cláudio RodriguesCommented:
To change the login page to include the domain name:
1.     Login to the Remote Desktop Web Access role-based server with local administrative permissions.
2.     Navigate to the following location: %windir%\Web\RDWeb\Pages\<The Language of Your Location>\
3.     Backup the login.aspx file to another location.
4.     Right click the login.aspx file, and select Edit. The file will be opened with Edit status in your default HTML editor.
5.     Change the original code section:
<input id=DomainUserName name=DomainUserName type=text class=textInputField runat=server size=25 autocomplete=off />

to be:

<input id=DomainUserName name=DomainUserName type=text class=textInputField runat=server size=25 autocomplete=off value=domainname\ />

6.     Save the modification. Backup the modified version.

That will do what you want.

Cláudio Rodrigues
Citrix CTP
0
 
Cláudio RodriguesCommented:
The original thread where the solution was posted and discussed is here for your reference:
http://social.technet.microsoft.com/Forums/en/winserverTS/thread/f02bd61f-d6fd-4c05-b17a-deffcc61a4e9

Cláudio Rodrigues
Citrix CTP
0
 
armfullAuthor Commented:
@tsmvp thanks for your replies. Here is the problem:

I have tried the solution in your first reply, but that doesn't help much. The first log in box does not require a domain to be entered. It is only the second that requires it. You only make it to the second log in box if you don't have at least RDP 7.0 installed.

In the thread you listed, a couple people point this out, but there is really never a fix listed. "Ross CP' list some html that will check the clients RDP version. His code doesn't quite run correctly though because it falsely tells the user that they have 7.0 installed before it can download the ActiveX control to actually check it. I know you can edit one of the Java files that were listed in the thread to check the domain name on the second dialog box. That in itself has been unstable.

The best work-flow in my eyes would be this:

>User goes to RemoteApp web address.

>Before signing in on the page (or a redirect page beforehand) the clients RDP version would be checked.

>If the RDP version was not at least 7.0, be able to post a link to the download location.

It is unbelievable that MS hasn't done something to fix some of these problems. I see literally hundreds and hundreds of people complaining about the same thing. But in seeing that I would think someone would have came up with a decent workaround by now.

Thanks
0

Featured Post

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now