Windows 2008 Terminal Server--How Do I Specify a Default Domain?
- Even though I've provided training documents to my users, no one prints them out or ignores them and I'm getting the same help desk tickets and calls about logging in to RemoteApp. Currently users have to log in to the server using the format "DOMAIN\username". If they don't do that, the server tries to log them in as a local user. What GP setting can I use to set a default domain for each TS in the farm?
Answers
Hi,
Actually, what you are witnessing is the expected behavior.
RemoteApp currently doesn’t support pre-population of the “USER” RDP field.
This may change in W7 SP1.As per the domain problem, are the clients and servers not on the same domain? Do they logon to the server itself, and not to the domain?
If you are using clients that support it, please try saving the creds.
After one successful login, the right credentials (including domain/user) should be stored locally.
(you can do the first connect to a full desktop session which supports the “USER” RDP field)Cheers,
MosheDisclaimer:
“This posting is provided "AS IS" with no warranties, and confers no rights”
- Marked As Answer byMoshe Z [MSFT]MSFT, ModeratorWednesday, October 14, 2009 6:14 AM
All Replies
- Please see if this forum post helps http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/f02bd61f-d6fd-4c05-b17a-deffcc61a4e9
Thanks, Vikash- Proposed As Answer byVikash BuchaMSFT, ModeratorWednesday, October 07, 2009 4:14 AM
- I tried adding:
username:s:<domain>\
To the "Custom RDP Settings" replacing <domain> with the name of my domain and it doesn't like it. I get an error when I try to apply it. - What error do you get?
Thanks, Vikash - I get an error box that shows me that there's a problem with the setting.
- Well,
I can add
domain:s:alpineskihouse
to an RDP file and it works fine. I have not been able to add this to RemoteApp Manager.
I get: "the following RDP settings are not recognized."
Still playing with this....hopefully more to come.- Proposed As Answer byKristin L. GriffinMVP, ModeratorWednesday, October 07, 2009 6:05 PM
- ok more testing. I compared the RDP file settings from:
RDP FILE A
- this was created just using mstsc, and saving the RDP file and then opening it in notepad.
If I add the username:s or the domain:s settings to this file, and save it, I can run it and it works as expected (ie, the username and domain are filled in).
RDP FILE B
- this was created using RemoteApp Manager. I opened this file up in notepad and added the two settings, and whe I run this file, they are ignored.
Additionally, we know that we cannot add them via RemoteApp Manager (per the errors expressed in this thread).
So I started running through all the settings comparing the two files and removing entries / changing them to see what affected this.
It turns out that if I remove the following lines from RDP FILE B then the username and domain settings are no longer ignored:
- remoteapplicationmode:i:1
- alternate shell:s:||EXCEL
- remoteapplicationprogram:s:||EXCEL
- remoteapplicationname:s:Microsoft Office Excel 2007
- remoteapplicationcmdline:s:
So what this tells me is that IF you have an RDP file set to pull up a remoteApp, then certain RDP file settings are ignored / not compatible with RemoteApps.
Mighty MSFT, can you comment on this?
Hope this helps,
Kristin L. Griffin
Co-Author of the Windows Server 2008 Terminal Services Resource Kit (and a SUPER BIG fan of the Microsoft RDV Team!!!) - So I found a bug???
- LOL
Not everything that is unexpected is a bug. Could be a very logical explanation.....but we will see.....:)
But, I am looking into this further. I will get an answer and get back to you. Hang tight!
Hope this helps,
Kristin L. Griffin
Co-Author of the Windows Server 2008 Terminal Services Resource Kit (and a SUPER BIG fan of the Microsoft RDV Team!!!) Hi,
Actually, what you are witnessing is the expected behavior.
RemoteApp currently doesn’t support pre-population of the “USER” RDP field.
This may change in W7 SP1.As per the domain problem, are the clients and servers not on the same domain? Do they logon to the server itself, and not to the domain?
If you are using clients that support it, please try saving the creds.
After one successful login, the right credentials (including domain/user) should be stored locally.
(you can do the first connect to a full desktop session which supports the “USER” RDP field)Cheers,
MosheDisclaimer:
“This posting is provided "AS IS" with no warranties, and confers no rights”
- Marked As Answer byMoshe Z [MSFT]MSFT, ModeratorWednesday, October 14, 2009 6:14 AM
- Hello,
Isn't it possible to add the registry key for DefaultDomainName on all Terminal Servers??
Robert - Hi Kristin,
Adding the defaultdomainname key on the terminal servers does not do the trick. I even added it on the server running the gateway and still no joy. The gateway login page comes blank and does not even store previous credentials, which makes sense except for the domain part. Do you have any updates?
Best Regards,
Amro - Hi Moshe,
So what you are suggesting is that there is no way or workaround for setting the domain name in remoteapp, at least currently?
Best Regards,
Amro - Hello Kristin
Thanks for all your work in trying to find workarounds for everyone.
It does seem strange that RemoteApp does not support the pre-population of the domain part.
My ideal solution would be that users would only need to log on once via the web interface but this double logon does confuse everyone when in all other locations the domain is not required.
I'm hoping Microsoft can address this in a future release as I can't really see any potential issue with allowing the default domain to be set as you can do it with everything else such as OWA.
This seems to be its only downfall as RemoteApp works really well apart from this.
Thanks
Robin
Robin Wilson
