Hi,

I've been struggling for a while with 2012 R2 RDS deployments to negate the need for users to enter their domain when signing in.

I've customised the RDWeb so that domain is not needed to sign in to Web Access, using this guide: 

http://msfreaks.wordpress.com/2014/07/22/properly-removing-the-domain-prefix-requirement-from-rd-web-access-2012-r2/

However, users still have to enter DOMAIN\username in RDC.

If I edit the .rdp file in notepad and add "username:s:DOMAIN\", it works - users are prompted for username and password, but the domain is pre-populated. (NB. I have also seen in http://www.donkz.nl/files/rdpsettings.html that "domain:s:" is an RDP property, but it has never worked in any way for me.)

I run:

Get-RDSessionCollection | Set-RDSessionCollectionConfiguration -CustomRdpProperty "use multimon:i:0`nusername:s:DOMAIN\"

Get-RDSessionCollection | Set-RDSessionCollectionConfiguration | fl

...shows that the property has been added correctly. I also see it in the registry at

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal       Server\CentralPublishedResources\PublishedFarms. However, after an IISRESET, the property does not make it into the RDP file generated by RDWeb.

How can I add this seemingly simple property?

Hi Freddie,

However, after an IISRESET, the property does not make it into the RDP file generated by RDWeb.

What happens without the IISRET?

Here is a related article below for you:

Adding custom RDP properties in Windows Server 2012 RDS/VDI environments

http://microsoftplatform.blogspot.nl/2013/01/adding-custom-rdp-properties-in-windows.html

Best Regards,

Amy

Hi Freddie,

Do you have any updates at the moment?

Best Regards,

Amy

Hi Amy,

Thanks for your reply, though I don't know why you thought it would be helpful to *not* do an iisreset when I already have tested with an iisrest...? Feel free to enlighten me.

Get-RDSessionCollection | Get-RDSessionCollectionConfiguration | Set-RDSessionCollectionConfiguration -CustomRdpProperty "use multimon:i:1`ndomain:s:CMC"

I have, as before, tested every combination.

These settings do make it into the registry at HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\CentralPublishedResources\PublishedFarms\xxxx\DeploymentSettings

The updated "use multimon" setting makes it into the RDP file with just a page refresh in the browser, but neither "domain:s" nor "username:s" do.

If I test with another signed property, "alternate full address:s", my custom setting does make it into the RDP file.

I think that there is some default policy that filters these credential-related properties. If anyone has any pointers for tracking down this setting and nuking it, that would be great. We do loads of RDS deployments to small clients and we get a regular stream of helpdesk requests that are resolved by telling the cusers how to enter the domain. It's a policy that is poorly aligned with the needs of our clients.

Regards,

Freddie

Did you ever get anywhere with this? Having the exact same issue...

Negative... the next thing I did was to inspect the web page source.

In 2008R2, the web page served up an .rdp file from a location in (IIRC) wwwroot. Now, the file is generated dynamically by the web page code. I haven't inspected it properly because I don't think my company wants to customise that much- it might be overwritten by an update. It might be one of those solutions that is "too clever".

Good luck, and post back if you take this route.