Does 2008 have ABE turned on by default?

Yes it does. Access Based Enumeration allows Windows Server to hide folders in shares that a user does not have permissions to open. For example, lets say that we have a share named Public. Both Jack and Jill have change permission on the share. There are 2 folders inside of the Public folder. Jack has read permission to both folder 1 and folder 2. Jill only has write permission to folder 2. Without Access Based Enumeration, when Jill accessed the Public share, she would see both folders. With Access Based Enumeration, Jill would see only folder 2, but Jack will see both folder 1 and folder2. This is because Jill does not have any NFTS permissions on folder 1.

In Server 2008, Access Based Enumeration is turned on by default on network shares. For it to work, the users must access the data through a share. It will not function for locally logged on users accessing the data directly.

To manually enable/disable ABE:



Click Start  Administrative Tools 

Share and Storage Management



Right mouse click the share and select Properties.



Click the Advanced button.



Be default, the Enable Access-based enumeration check box should be checked.

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