Solved

Question: Do we really need to train our *remote* users that their Username needs to be the full DOMAIN\Username?

Posted on 2013-02-05
3
299 Views
Last Modified: 2013-02-08
ExampleMS Remote Desktop Connection clients, MS Remote Desktop Services 2008 R2.

Objective:  We want ALL of our remote users to log directly into their DOMAIN accounts, not any local RDS PC host machine accounts.

Question: Do we really need to train our *remote* users that their Username needs to be the full DOMAIN\Username?  

We tried #1:  RDC host server's registy:  [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]   "DefaultDomainName"="DOMAIN"   The remote client RDC program (both 6.1x and 6.2x) does not seem to honor this host registry setting.

We tried #2: The RDC host server's option for RDP-Tcp properties, "Log on Settings", "Always use the following log on info, Domain:".   Yeah this works, BUT this FORCES a DOUBLE Login process everytime for the remote users which is very annoying.  Would have been nice if this functionality would have allowed in the passed thru credentials for username & pw which it apparently does not.

Question:  Is there a way to absolutely force Remote User to domain DOMAIN?

Any comments and hints would be really appreciated!

Thanks,

John
0
Comment
Question by:JReam
3 Comments
 
LVL 57

Assisted Solution

by:giltjr
giltjr earned 100 total points
ID: 38856390
Assuming you are using exchange for e-mail have you tried using the full e-mail address as the userid?

     email@domain.com
0
 
LVL 6

Accepted Solution

by:
sconstable earned 400 total points
ID: 38856452
There is no easy way to do this that I am aware of, howeverplease keep in mind that the DOMAIN\<Usename> notation is very legacy.

I try my hardest to use SPN logins.  SPN logins can be universal across any domain and even if you had to migrate the user to a different domain their SPN login can follow.

As the previous user said, by default SPN logins can be set to the same as their email address, however the default is more like

<username>@domain.  Like an email address, without you can however make the "domain" part whatever you want it to be.

Generally you set this to be the users email address or something else they can relate to and then say "That is your login name" no matter where or what your trying to login to.  Then when you have the RDP isse described above you no longer have an issue.
0
 
LVL 1

Author Closing Comment

by:JReam
ID: 38868088
Thank you.  We're going to adopt the use of:  Username@Domain
0

Featured Post

Simplifying Server Workload Migrations

This use case outlines the migration challenges that organizations face and how the Acronis AnyData Engine supports physical-to-physical (P2P), physical-to-virtual (P2V), virtual to physical (V2P), and cross-virtual (V2V) migration scenarios to address these challenges.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Lync meeting or Lync conferencing is what many organizations would like to deploy to allow them save money. But companies are now giving up for various reasons, one of which is that they cannot join external meetings (non-federated company meetings)…
Having trouble getting your hands on Dynamics 365 Field Service or Project Service trial? Worry No More!!!
The viewer will learn how to use a discrete random variable to simulate the return on an investment over a period of years, create a Monte Carlo simulation using the discrete random variable, and create a graph to represent the possible returns over…
The viewer will learn how to create two correlated normally distributed random variables in Excel, use a normal distribution to simulate the return on different levels of investment in each of the two funds over a period of ten years, and, create a …

713 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question