CIFS setup in a Cluster-Mode environment differs from CIFS setup in 7-Mode in a few important ways.
- CIFS server
- In a Cluster-Mode environment, you must create a CIFS server to enable access to your storage system by CIFS clients. When you use the Vserver create wizard, the CIFS server is created for you if you select CIFS as a protocol.
- Export policies
- In Cluster-Mode, every volume has an export policy. This is a change from 7-Mode, where exports are used only with NFS clients.
Export policies permit you to control access to volumes in ways that are not possible with share-level controls. For example, you can define an export policy that prevents connections from clients in specific subnets, or can create access rules that apply equally to NFS and CIFS clients.
If you prefer to use traditional methods of controlling access for CIFS clients, you can define an open export policy and use Windows-based authentication and share-level access controls.
- Default CIFS shares
- When you set up CIFS, Data ONTAP creates default CIFS shares for interprocess communication and administrative purposes. The administrative IPC$ share is created in both 7-Mode and Cluster-Mode environments. However, the ETC$ share that is created in 7-Mode is not created in Cluster-Mode because the /etc directory that it maps to does not exist in Cluster-Mode.
- Home directory shares
- As in a 7-Mode environment, in Cluster-Mode you can use the Data ONTAP home directory functionality to create users' home directories and automatically offer each user a dynamic share to their home directory without creating an individual CIFS share for each user.
However, home directory shares are defined differently in Cluster-Mode than they are in 7-Mode. In Cluster-Mode, home directory share names are specified when you create or modify a share, and use patterns to match users to shares. This permits you more flexibility than the static configuration options that are available to you in 7-Mode using the options cifs.home_dir_namestyle registry option.