For the credentials, you are running into an issue with a security feature that MS has implimented.
If the user's browser (machine) is not on the same domain (LAN) as the web server then the browser will not pass encrypted credentials to the web server. You have verified this by enabling BASIC authentication and seeing it work. As you stated, this is not a secure way to handle this. BUT you can do this over SSL and you would be fine. If you have any control over the workstations then you can add the server and domain of the IIS server to the trusted server list in the intranet security settings of the client browsers. This will then let the browser pass the credentials encrypted to the IIS server.
As for the domain portion being entered already ... I'm not sure, I have not done this. There are a couple of options on the configuration page for the security settings that let you enter a domain reference ... I am thinking it in one of these entries where you need to enter the domain info to get it to use that as the default ... BUT I am not sure on this.
Main Topics
Browse All Topics
by: partnersmvzPosted on 2009-09-13 at 11:03:08ID: 25321183
also, pre R2, while it was called TS Services, when launching RemoteApp's, it filled in domain\ for the username, now in RD it doesnt, thats what im most concered about.
Ive read and conducted the steps to enable SSO, no dice, credentials keep popping. Ive gotten it down to one login (have to put in domain still) by telling the session host server to always log in as a specific user.