background preloader

DFS

Facebook Twitter

Hoangnh

DFS and ABE in Server 2008 and 2008 R2. This blogpost will be quite alot longer than other blogposts, but that’s not an issue in my opinion. Too many times I encounter a situation in which DFS is misconfigured for use with Access-based Enumeration. Some of the times I even encounter an environment in which the fileservers themselves are configured incorrectly. In this blogpost I will explain the following items: Installing Distributed File System. Configure a domain-based DFS Namespace. Creating a DFS Link (Target/Folder Target). Configuring Access-based Enumeration on the DFS Namespace and the DFS Links. I’ll assume the following items are running as they should/are available, so I’ll not go into them any further: A correctly working Active Directory infrastructure, running at least Windows Server 2008 Domain Functional Level.

Now, on with the fun stuff. 1. 1) Open Server Manager, click Roles and right-click on Roles. 2) Click Next. 3) Select File Services and click Next. 4) Click Next. 5) Select DFS Namespaces and click Next. 2. Using ABE with DFS - Ask the Directory Services Team. Hello, Dave here. Today I discuss the Access Based Enumeration (ABE) feature in Windows Server and how it may be implemented with Distributed File System Namespaces (DFSN).

First you may ask, "What is ABE, and why would I want to utilize it? " By default, all folders and files will be listed in a folder, even if the browsing user doesn't have permissions to them. For example, three users (Alice, Bob, and Cindy) have folders under a share on file server ‘FS1’. Each user's folder has permissions such that only the single user has access (icacls.exe output below): \\fs1\share\Alice CONTOSO\Alice:(OI)(CI)F \\fs1\share\Bob CONTOSO\bob:(OI)(CI)R \\fs1\share\Cindy CONTOSO\Cindy:(OI)(CI)R The following is what user “Bob” observes when browsing the UNC path \\fs1\share: If a user attempts to open another user's folder or file within that folder, they will be met with an error as they do not have sufficient permissions.

ABE is enabled for non-DFS shares via the "Share and Storage Management" snap-in. How to configure DFS to use fully qualified domain names in referrals. By default, a Microsoft Distributed File System Namespace (DFSN) root referral reply to a DFS root referral query is in NetBIOS name format (\\<>\<>). This is necessary in certain environments that rely on NetBIOS and makes it possible for clients that support NetBIOS-only name resolution to locate and connect to targets in the DFS namespace.

By default, Windows clients work fine with this. However, some clients do not use NetBIOS. Two examples are clients that are not running Windows and clients that operate in an environment without WINS or that use DNS name suffixes. Those clients are incompatible with the default DFSN behavior. In these cases, the client may be unable to resolve the server name that is returned from the root referral query. Note For namespace servers that are hosting only stand-alone namespaces, some steps that are described in this article are unnecessary. Steps for stage 3: Configure the DFSN server to respond by using FQDN referrals for root targets Applies to.