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

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.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Jason Yoder, MCT

Search This Blog