Skip to main content
NetApp adopts Microsoft’s Business-to-Customer (B2C) Identity Management
Effective December 3 - NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources. For accounts that did not pre-register (prior to Dec 3) access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity. To learn more, Read the FAQ and Watch the video. Need assistance? Complete this form and select “Registration Issue” as the Feedback Category. 
NetApp Knowledge Base

The everyone permission has been added after applied sdname policy

Views:
186
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
cifs
Last Updated:

Applies to

ONTAP 9

Issue

  • The everyone permission has been added after applied sd (Security Descriptor) name policy.
  • Follows the below commands, the everyone permission is added in the /test1.

Example:

Cluster1::> vserver security file‐directory ntfs dacl add ‐ntfs‐sd sd1 ‐vserver svm_data1  ‐access‐type allow ‐account user1 ‐rights full‐control ‐apply‐to this‐folder
Cluster1::> vserver security file‐directory policy create ‐vserver svm_data1 ‐policy‐name  policy1
Cluster1::> vserver security file‐directory policy task add ‐vserver svm_data1 ‐policyname policy1 ‐path /test1 ‐security‐type ntfs ‐ntfs‐sd sd1  ‐ntfs‐mode propagate ‐indexnum 1 ‐access‐control file‐directory
Cluster1::> vserver security file‐directory apply ‐vserver svm_data1 ‐policy‐name policy1

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support

 

  • Was this article helpful?