<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Allow users full access to CIFS shares and files/folders without admin access to filer itself in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Allow-users-full-access-to-CIFS-shares-and-files-folders-without-admin-access-to/m-p/48424#M4462</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I noticed you wrote the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;"My question is, when I move the files over to a CIFS share on a filer,&amp;nbsp; in order to maintain the ability for the group to manage the files, I&amp;nbsp; need to make them members of the local Administrators group on the filer&amp;nbsp; itself"&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I d suggest to you that the storage admins should not have to do CIFS permissioning. In most big evnironments I have been to its not seen as secure nor scalable to have&lt;/P&gt;&lt;P&gt;the storage admins doing CIFS permissioning.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The way I have seen this been done in the past is that the storage guys create a cifs share wide open, then its grabbed by the windows team that will set permissions and&lt;/P&gt;&lt;P&gt;deal with any issues. After all the windows guys will have access to AD admin accounts and thus will be in a good position to fix any issues. They will also have the&lt;/P&gt;&lt;P&gt;knowledge about how permissions should be fixed to fit current security requirements etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My two pennies worth, which would void having to deal with your current issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Eric&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 30 Aug 2010 03:10:30 GMT</pubDate>
    <dc:creator>eric_barlier</dc:creator>
    <dc:date>2010-08-30T03:10:30Z</dc:date>
    <item>
      <title>Allow users full access to CIFS shares and files/folders without admin access to filer itself</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Allow-users-full-access-to-CIFS-shares-and-files-folders-without-admin-access-to/m-p/48414#M4460</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Basically, we are migrating file servers to CIFS shares on our filer.&amp;nbsp; There is a group of file server admins in an AD group.&amp;nbsp; This AD group is a member of the local Administrators group on the file server, which is given so they can manage all the files on the server.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;My question is, when I move the files over to a CIFS share on a filer, in order to maintain the ability for the group to manage the files, I need to make them members of the local Administrators group on the filer itself.&amp;nbsp; But I don't want to them to have the ability to manage the filer itself...either through CLI, Filerview, System Manager, etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible to do this?&amp;nbsp; If not, I would have to use xcacls or some similar utility to modify the ACL on all files/folders to give that group admin access, but I would rather not have to do that.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:10:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Allow-users-full-access-to-CIFS-shares-and-files-folders-without-admin-access-to/m-p/48414#M4460</guid>
      <dc:creator>kungfujoe23</dc:creator>
      <dc:date>2025-06-05T07:10:22Z</dc:date>
    </item>
    <item>
      <title>Re: Allow users full access to CIFS shares and files/folders without admin access to filer itself</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Allow-users-full-access-to-CIFS-shares-and-files-folders-without-admin-access-to/m-p/48418#M4461</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;User capabilities are defined by roles. By default group Administrator is given “admin” role that has following priviliges:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Name: Administrators&lt;/P&gt;&lt;P&gt;Info: Members can fully administer the filer&lt;/P&gt;&lt;P&gt;Rid: 544&lt;/P&gt;&lt;P&gt;Roles: admin&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Name:    admin&lt;/P&gt;&lt;P&gt;Info:&lt;/P&gt;&lt;P&gt;Allowed Capabilities: login-&lt;STRONG&gt;,cli-&lt;/STRONG&gt;,api-&lt;STRONG&gt;,security-&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So you could create another role and assign it to group Administrators instead of default role “admin”; if you will not include login-* in this group, users in this group will not be able to log into filer using any available protocol. Actually, it is quite possible that for your purpose you can remove &lt;STRONG&gt;all&lt;/STRONG&gt; capabilities from this group, because it sounds like you only need it as placeholder for file ACLs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please check TR-3358 for more in-depth description of role based access control.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is not tested. One thing I miss – how RBAC plays together with Windows management API.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Aug 2010 05:11:54 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Allow-users-full-access-to-CIFS-shares-and-files-folders-without-admin-access-to/m-p/48418#M4461</guid>
      <dc:creator>aborzenkov</dc:creator>
      <dc:date>2010-08-17T05:11:54Z</dc:date>
    </item>
    <item>
      <title>Re: Allow users full access to CIFS shares and files/folders without admin access to filer itself</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Allow-users-full-access-to-CIFS-shares-and-files-folders-without-admin-access-to/m-p/48424#M4462</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I noticed you wrote the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;"My question is, when I move the files over to a CIFS share on a filer,&amp;nbsp; in order to maintain the ability for the group to manage the files, I&amp;nbsp; need to make them members of the local Administrators group on the filer&amp;nbsp; itself"&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I d suggest to you that the storage admins should not have to do CIFS permissioning. In most big evnironments I have been to its not seen as secure nor scalable to have&lt;/P&gt;&lt;P&gt;the storage admins doing CIFS permissioning.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The way I have seen this been done in the past is that the storage guys create a cifs share wide open, then its grabbed by the windows team that will set permissions and&lt;/P&gt;&lt;P&gt;deal with any issues. After all the windows guys will have access to AD admin accounts and thus will be in a good position to fix any issues. They will also have the&lt;/P&gt;&lt;P&gt;knowledge about how permissions should be fixed to fit current security requirements etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My two pennies worth, which would void having to deal with your current issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Eric&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Aug 2010 03:10:30 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Allow-users-full-access-to-CIFS-shares-and-files-folders-without-admin-access-to/m-p/48424#M4462</guid>
      <dc:creator>eric_barlier</dc:creator>
      <dc:date>2010-08-30T03:10:30Z</dc:date>
    </item>
  </channel>
</rss>

