Gives host applications transparent, continuous access to a share following a failover of the NAS server on the system (with the NAS server internal state saved or restored during the failover process).
NOTE:Enable continuous availability for a share only when you want to use Microsoft Server Message Block (SMB) 3.0 protocol clients with the specific share.
Protocol Encryption
Enables SMB encryption of the network traffic through the share. SMB encryption is supported by SMB 3.0 clients and above. By default, access is denied if an SMB 2 client attempts to access a share with protocol encryption enabled. You can control this by configuring the RejectUnencryptedAccess registry key on the NAS Server. 1 (default) rejects non-encrypted access and 0 allows clients that do not support encryption to access the file system without encryption.
Access-Based Enumeration
Filters the list of available files and directories on the share to include only those to which the requesting user has read access.
NOTE:Administrators can always list all files.
Branch Cache Enabled
Copies content from the share and caches it at branch offices. This allows client computers at branch offices to access the content locally rather than over the WAN. BranchCache is managed from Microsoft hosts.
Distributed File System (DFS)
(Read only) Lets you group files that are on different shares by transparently connecting them to one or more DFS namespaces. This simplifies the process of moving data from one share to another. This option is read-only in Unisphere because you manage DFS from Microsoft hosts. For information, see the Microsoft Distributed File System documentation.
Offline Availability
Configures the client-side caching of offline files:
Manual: Files are cached and available offline only when caching is explicitly requested.
Programs and files opened by users: All files that clients open from the share are automatically cached and available offline. Clients open these files from the share when they are connected to it. This option is recommended for files with shared work.
Programs and files opened by users, optimize for performance: All files that clients open from the share are automatically cached and available offline. Clients open these files from the share's local cache, if possible, even when they are connected to the network. This option is recommended for executable programs.
None: Client-side caching of offline files is not configured.
UMASK
(Applies to SMB shares of a file system that supports multiprotocol access with a UNIX access policy or a Native access policy.) A Bitmask that shows which UNIX permissions are excluded for files that are created on the share. The default permissions are:
666 for files, which allow read and write permissions for all.
777 for directories, which allow read, write, and execute permissions for all.
If UMASK is set to 022, following permissions are granted:
644 for files, which allow read and write permissions for the file owner, and read permission for everyone else.
755 for directories, which allow read, write and execute permissions for directory owners, and read and execute permissions for everyone else.
NOTE:If NFSv4 ACL inheritance is present, it takes precedence over the UMASK setting,
To change the excluded permissions, click
Modify, and then select or clear permissions.
To set the bitmask to the default value (022), click
Set default. A value of 022 allows only you to write data, but lets anyone read data. For more information, see the UNIX documentation.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\