Skip to main content

Prevent Authenticated Users from adding a workstation to a domain.

For whatever reason, standard user accounts can add a workstation to your domains. I have yet to figure a good reason out for this one. Microsoft does limit this to 10 computers per user account by default. That is little comfort for IT Professionals who are trying to maintain security on their networks. Here are two ways to close this security hole.

Change the number of workstations the users can add to your network. In this case, change it to zero.

· Click Start.

· Type ADSIEdit.msc and press Enter.

· Right mouse click ADSI Edit and select Connect to..

· Click OK

· Expand Default naming context.

· Right mouse click the distinguished name of your network and select Properties.

· Click ms-DS-MachineAccountQuota

· Click Edit.

· Set the number to 0.

The other option is to remove Authenticate Users from the User Right to add workstations to the domain.

· On your Domain Controller, Click Start à Administrative Tools à Group Policy Management.

· Either create a new GPO and link it to the Domain Controllers OU, or edit the Default Domain Controller Policy

· Expand Computer Configuration à Policies à Windows Settings à Security Settings à Local Polices à User Rights.

· Double click Add workstations to domain.

· Add in a group of users whom you want to be able to add workstations to the domain.

· Remove Authenticated Users from the policy.

· Click OK.

Comments

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.