<?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: CIFS Setup best practices? in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-Setup-best-practices/m-p/73113#M6619</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Gave,&lt;/P&gt;&lt;P&gt;If you want then you can go ahead and setup a singly cifs shares. there is no issue.&lt;/P&gt;&lt;P&gt;But this would be&amp;nbsp; good that saperate share for saperate deparment would help you to easily manage the access for it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have some shares where thousand of user accessing it without any problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Bhola Gond&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 04 Feb 2013 16:01:17 GMT</pubDate>
    <dc:creator>bondbhola</dc:creator>
    <dc:date>2013-02-04T16:01:17Z</dc:date>
    <item>
      <title>CIFS Setup best practices?</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-Setup-best-practices/m-p/73107#M6616</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm gonna throw this one out there.&amp;nbsp; We are setting up CIFS for file share access and user home folders with AD.&amp;nbsp; Whats the best way to approach this?&amp;nbsp; Basically my client wants to have one big CIFS share with folders beneath that.&amp;nbsp; This is to minimise the amount of mapped drives in windows.&amp;nbsp; Are there any problems with setting up CIFS in this way?&amp;nbsp; Or maybe problems I might face later on?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The other option which I was opting for was multiple CIFS with multiple qtrees on a per department basis.&amp;nbsp; Granular and segregated.&amp;nbsp; The reason behind this approach is basically, If there is an issue with one volume its only going to affect that volume and not the rest of the fileserver estate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thoughts on this would be appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gav&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:10:56 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-Setup-best-practices/m-p/73107#M6616</guid>
      <dc:creator>GLOBELEQ</dc:creator>
      <dc:date>2025-06-05T06:10:56Z</dc:date>
    </item>
    <item>
      <title>Re: CIFS Setup best practices?</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-Setup-best-practices/m-p/73113#M6619</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Gave,&lt;/P&gt;&lt;P&gt;If you want then you can go ahead and setup a singly cifs shares. there is no issue.&lt;/P&gt;&lt;P&gt;But this would be&amp;nbsp; good that saperate share for saperate deparment would help you to easily manage the access for it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have some shares where thousand of user accessing it without any problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Bhola Gond&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Feb 2013 16:01:17 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-Setup-best-practices/m-p/73113#M6619</guid>
      <dc:creator>bondbhola</dc:creator>
      <dc:date>2013-02-04T16:01:17Z</dc:date>
    </item>
  </channel>
</rss>

