Hidding folders users do not have access to

Through the years that I've spent supporting networks and their users, I've come across a common problem. I often have problems with having to give access to shared folders to users that also contain folders that they do not have access to. I'm of course the bad guy when I have to tell them that they do not have access to those folders. How dare I. Well, Windows Server 2008 (and Windows server 2003 SP 1with a plug in) offers a solution. It is called Access-Based Enumeration.

Access-Based Enumeration allows the operating system to filter out all the folders that the user does not have access to when the user browses to the shared folder. This helps to reduce user frustration, tech support calls, and increases user productivity by reducing the number of folders they see that do not apply to them.

So, how do you implement this magical wonder? Well, first off you need to have Distributed Files System installed and your distributed files configured. Next:

•Click Start --> Administrator Tools --> Share and Storage Management
•Open the properties for your distributed folder
•Click the Advanced button.
•Check Enable Access-based enumeration.

There is also a hotfix for Windows Server 2003 SP1 and Windows XP SP2 to be able to use DFS.

•http://support.microsoft.com/default.aspx?scid=kb;en-us;898900

Download for Windows Server 2003 SP1: http://www.microsoft.com/downloads/details.aspx?FamilyID=04a563d9-78d9-4342-a485-b030ac442084&DisplayLang=en

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