Upon completion of this course you should be able to:
Course Prerequisites:
NAS 106: Using NAS with Microsoft Windows
Students are expected to have a working knowledge of:
Shared Folders, Access Control
1. Introduction to Windows ACL
1.1 Do I need to enable Windows ACL?
2. Configuring Windows ACL
2.1 Enabling Windows ACL
2.2 Configuring Windows ACL permissions with ADM File Explorer
2.3 Configuring Windows ACL permissions with Windows Explorer
2.4 Windows ACL permission rules and precautions
2.5 Moving objects to your NAS while maintaining ACL permissions
Windows ACL is the 13 different types of file permissions designed by Microsoft for NTFS file systems which can be applied to specific users and groups. Within this type of infrastructure, administrators can make more detailed and precise access permission configurations.
Furthermore, in the Windows AD domain infrastructure (widely used by businesses), Windows ACL permissions can be applied to all users and groups in the domain. Users can use any computer in the network to log in, and as long as they use the same account name, all permissions will remain the same. IT staff will not need to configure permissions for each individual server and PC workstation, significantly increasing management efficiency.
In order to more closely integrate ASUSTOR NAS with AD domains, simplifying IT management and increasing productivity, ASUSTOR has deeply integrated the Windows ACL permissions system with ADM, providing the following unique features:
As described in the previous section, Windows ACL provides up to 13 different permission settings that can be applied to all users and groups on the NAS and on the domain (if the NAS has been added to a Windows AD domain). In the event of improper planning or configuration of permissions, there is the possibility that all users will not be able to access a certain folder or file. Obviously, this type of error can be resolved by using an administrator account, but the amount of wasted time from when the problem first occurs to when it gets resolved can be seen as a significant intangible cost to businesses.
ASUSTOR NAS was developed based on the Linux operating system, so ADM’s native settings utilize the Linux permission management mechanism:
The smaller number of options allows for simpler configuration. However, the flexibility and adjustability of the permissions is very limited. For example, when using the Linux permissions mechanism, it is not possible to give a user the ability to edit a file while not giving them permission to delete the file.
If you are only using your NAS between yourself and a limited number of family and friends, then it is recommended that you use ADM’s original permissions management mechanism. However, if your NAS is being used for business data storage, it is suggested you first consult with your IT staff to decide if it is appropriate to enable Windows ACL permissions and then complete a permissions deployment plan should you decide to use it.
We have provided the flexibility for you to enable or disable Windows ACL for single shared folders, which is very helpful for assessment and planning. You can create a shared folder for testing, enable Windows ACL and then configure permissions settings. Afterwards you can check if the results are what you expected them to be. Once you get the results that you require you can then apply the settings to the shared folder of your choice. This allows you to avoid any mistakes or errors in planning that could deny access to important data, affecting the operation of your business.
Creating a new shared folder:
Note: Shared folder access rights are the first layer of permissions checking. If a user or group has not been assigned “Read & Write” permissions here, any Windows ACL permissions assigned to them will be blocked. Therefore, it is recommended that you configure more lenient access rights for shared folders that have Windows ACL enabled and then use Windows ACL to further configure more specific permissions later.
Enabling Windows ACL for already existing shared folders:
After enabling windows ACL for a shared folder, the system by default will assign "Read & Write, but cannot Delete" permissions to "Everyone", "administrators" and the "admin" account. These permissions will be applied to the shared folder only and will not be inherited by objects below. These default permissions can be modified by using the [Edit] or [Remove] buttons.
Note: An individual file or folder can utilize up to a maximum of 250 Windows ACL permissions (including inherited permissions).
The management functions that you will be able to use here are as follows:
Add:
Edit:
Remove:
Effective Permissions:
First, use a Windows administrator account to map a Windows ACL enabled shared folder as a network drive. For more information, please see NAS 106: Using NAS with Microsoft Windows.
If an object simultaneously has inherited permissions from its parent and also explicit permissions, the inherited permissions will be checked in grey while the explicit permissions will be checked in black.
ACL Conflicting ACL permissions:
Rules for moving files and folders:
Exceptions: When data is deleted from an ACL enabled shared folder and moved to the Network Recycle Bin the rules from "B3" in the chart above will not apply. This is to prevent the situation where files with [Deny Access] permissions are deleted and moved to the Network Recycle Bin and then become fully accessible to all users. Taking privacy and security into consideration, files from ACL enabled folders that are moved to the Network Recycle Bin will be assigned the permission [Read & Write for Owners, Deny Access for all Other Users].
File deletion permissions:
There are 2 permissions associated with deleting files:
If any of the above permissions are configured as "Deny", then the user will not be able to delete the file. Only if neither of the above permissions has been configured as "Deny" and at least one of them has been configured as "Allow", will the user be able to delete the file.
Access Right of objects:
After Windows ACL has been enabled for a shared folder, each object (subfolders and files) contained within the folder will have an access right.
Person who have access right will be able to configure ACL permissions for it. For example, the admin in the graphic above, is the owner of the "ACL_Test" folder. Therefore, admin will be able to configure ACL permissions for the folder and the subfolder and files contained within it.For every newly added object, the creator of the object will be set as the access rights by default. Additionally, users in the administrator group will have the ability to modify the access rights. For example, if we wanted to transfer ownership of the "ACL_Test" folder in the graphic above to other users (i.e., testuser), admin and all users in the administrator group would have the ability to transfer ownership. Once testuser becomes an owner of the "ACL_Test" folder, she will be able to reconfigure permissions for its subfolders and files even if she did not originally have access permissions for them.
When all Windows PCs and NAS devices in a network environment have been added to the same Windows AD domain, all user accounts and permissions on the domain can be combined together. However, when moving files or folders from a PC server to a NAS, existing ACL permissions will not be retained (using the rules in previous section). This causes IT staff to have to reconfigure permissions.
If you wish to maintain existing ACL permissions when moving files or folders to your NAS, you can utilize Fastcopy, a 3rd party software. In the example below, we will demonstrate how to use this Fastcopy.