Question Locked

Allowing anyone to join an Active Directory domain; Good Thing? Bad Thing?

0 helpful
23 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

So, by default any AD user has the right to add 10 computers to the domain. My initial reaction to that factoid caused me to erupt my first sip of coffee all over my monitor. "This is on by DEFAULT?!" I howled as I searched for how to stop that behavior.

A colleague of mine told me to simmer down. His take was that if a user added a machine to the domain, it would allow the domain admins to control it as well as apply all of our GPOs to it, which would (supposedly) be a good thing.

I can see things from that perspective, but I still bristle at the idea. Any opinions that you folks would like to share on this topic? Have you changed that default? Ever had anyone join computers that you were unaware of?

Okay, so if someone plugs a computer into the network, whatever digital ills that machine has are now on the network. If it's a Windows machine and the person feels compelled to join it to the domain (we have a few savvy users that can and have done that) the computer is now ostensibly under our control (insert ominous laughter here) which should mitigate some of those threats. I guess. Hmmmm. >:-|

23 replies

by cmiller5400

I am a control freak, so no, it should not be enabled by default.

by cg it

If he is, play a practical joke on him.

From Ms Technet:

Add workstations to domain
Description
This security setting determines which groups or users can add workstations to a domain.

This security setting is valid only on domain controllers. By default, any authenticated user has this right and can create up to 10 computer accounts in the domain.

Adding a computer account to the domain allows the computer to participate in Active Directory-based networking. For example, adding a workstation to a domain enables that workstation to recognize accounts and groups that exist in Active Directory.

Default: Authenticated Users on domain controllers.

But you need to try it to see if it works.

Meaning open up the authenitcated users group and see who is a member of this group.

Can you find the authenticated users group in Active Directory domain security groups?

Domain users can't add computers to the domain because they aren't members of the authenticated users group, which, btw, is on the domain controller. Rather they are members of the domain users group therefore have insufficent privileges.

by nonapeptide

Truly odd.

I'll have a look at the Auth Users group when I get back to work to see if domain membership has been tweaked.

I used my domain user (not domain admin) account to join some computers to the domain a while back (experimenting with this very subject) and another user had joined a machine to the domain without IT assistance (which caused us, the IT department, a few priceless moments of blankly staring at eachother with the Dear In The Headlights look).

I'll report back.

by cg it

shouldn't happen.

remember that it's the authenticated users group on a domain controller. the security policy is in the domain controllers local user rights assignments. It's not the domain security policy nor a privilege or right for domain users. the add workstations to the domain local user rights assignments is not defined by default.

However domain users should not have the logon local rights to the domain controller. Authenticated users do but then who are authenticated users to a domain controller? only those users with an account ON the domain controller. Usually only the domain administrator's account has an account on a domain controller to log on locally to it thus would be an account that can authenticate to a domain controller.

open up the systems property page and then click advanced tab, then click user profiles. these are the user accounts that can authenticate to the domain controller. if you have anyone in there that isn't a member of the domain adminsitrators group or enterprise administrators group, you got a big problem.

by rob miners

ordinary Users will get an "Access Denied" because the are not members of the Authenticated Users. I normally create an account named SOE that I use to install workstations. Add the user to the section in the GPO, add workstations to the domain.

by link470

From my understanding, "Authenticated Users" is any user who authenticates to the domain controller, a domain user, a domain user in a different Security Group or a domain administrator. Or do you mean LocalDomainController\Username instead of DomainName\Username.

by cg it

There is the authenticate to the domain and then there is authenticate to the local machine domain controller. Only the domain admins or enterprise admins typically have local domain controller login rights thus are considered authenticated users which are then granted the add workstations to the domain right on the domain controller.

what one needs to look at is the domain security policy, add workstations to the domain user rights assignments. by default this is not defined. When one delegates authority, for instance a manager of a particular deparment, then one creates an GPO that grants the domain security policy of adding workstations to the domain for only those computers within the OU you apply the GPO/MMC to.

if one logs on to a domain controller in an Active Directory domain and looks at the local machine user accounts one should see the / user name. If not

Big Trouble.....

Might have to get Robert Preston into the act who so happens to have passed away in 1987.

by rob miners

the ordinary users are not authenticated to add workstations to the domain. I have an ordinary user named tester. I have only recently rebuilt my server and I have not modified any GPO's. This is a standard setup.
When I went in to change computer name or connect to a domain, I used this account and recieved the "access is denied" message.

by cg it

they aren't authenticated users to the domain controller.

They may authenticate to the domain by their Active Directory user account, but they aren't authenticating to the local machine domain controller.

as a test, open up your domain security policy MMC and add your testor account to the add workstation to the domain settings.

Then see if that domain user account [limited rights] can add a computer to the network.

by rob miners

ran gpupdate /force and went to the workstation and still recieved "access denied"

by cg it

because they aren't a member of the authenticated users group in the local machine domain controllers.

Now if you open up the domain controllers security policy, and you look at the add workstations to the domain security setting, you'll see authenticated users.

try to log on to a domain controller with a domain user account. you shouldn't be able to. Thus you domain user account isn't authenticated to the local machine domain controller, thus isn't an authenticated user.

You won't find the authenticated users group in Active Directory domain security groups.

by rob miners

knew that the User would not have the required permissions. I was just trying to point out the fact that without proper "authentication" standard Users have no control. You do a much better job at explaining than I can. I am one of those people that can do it and say it but when it comes to explaining on paper I seem to have a few problems.

Edit: Probably due to the fact that I left shool at the age of fourteen to help support my family. Not having access to secondary education has had its drawbacks.

by nonapeptide

[i]remember that it's the authenticated users group on a domain controller.the security policy is in the domain controllers local user rights assignments.[/i]

What befuddles me is that I've had it drilled into me that there are no user accounts local to the DC, with the exception of the Directory Services Restore Mode user.

[i]However domain users should not have the logon local rights to the domain controller.[/i]

See above.

::looks for Tylenol bottle::

[i]Authenticated users do but then who are authenticated users to a domain controller?[/i]

Ummmmm...

[i]only those users with an account ON the domain controller.[/i]

Users... accounts... local... on a domain controller?

::Madly gulps fistfuls of pills::

by cg it

there really aren't local user accounts on a domain controller.

BUT log on to the domain on a machine that is a DC with a domain administrators account and volia! you can. Thus your authenticating to the domain controller , thus a member of the authenticated user group therefore has the user right of adding workstations to the domain.

I agree it's pretty wonko when you think about it.

There is some logic to this because you can delegate authority to add users and even computer accounts though I would stress that such authority be done by GPO and OU and not via domain. Allow some people the add workstations to the domain privilige domain wide and you got a whale of a problem.

Pretty soon someone who should is gonna know the user name and password with the privileges and badda bing badda boom! there's all these computer belonging to the domain that know one knows anything about.

by nonapeptide

[i]BUT log on to a DC with a domain administrators account and volia! you can.[/i]

Okay, according to my schooling anyway, you're not actually logging on to the DC, you're using the DC computer to log on to the domain using domain credentials... not local credentials as the case could be with a client machine. The only users that log on to the domain using the DC computer are members of the domain and enterprise admins group. According to my understanding of the topic, you're not actually logging on locally. It's no different than going to a client machine and logging on with a domain account. The logon attempt is verified by the DC, and then a user profile gets created on the client machine when the authentication is verified. However, one can always log off of a domain account and then log on with a local account, say the local Admin for example. A DC has no local accounts, only domain accounts can log on. No?

[i]I agree it's pretty wonko when you think about it.[/i]

Wonko... let me write that down.

So it boils down to this. If you can log on to a DC, you can add a machine to the domain. Only Domain and Enterprise admins can log on to a DC... so therefore only they can add computers to the domain.

However, if you change the GPO that is linked to the DC's OU (had enough acronyms yet?) to allow domain users to authenticate to the DC... then your average Joe / Jane can add their computer to the domain... but they can also log on to the domain controller (decidedly not a best practice).

Confusing? Yes. But not as bad as trying to following IPSec's flow chart of ISAKMP, IKE, Oakley, etc..

by cg it

IPSec... don't wanna go there... makes my head hurt....

This discussion is closed to new replies.