<?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 Question about NTFS volume processing ID in Ask The Experts</title>
    <link>https://community.netapp.com/t5/Ask-The-Experts/Question-about-NTFS-volume-processing-ID/m-p/154819#M1357</link>
    <description>&lt;P&gt;Need your suggestions on the Multi protocol implementation effort.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Currently client have hundreds of NTFS shares, We got requirement to provide access to single Linux host for all volumes part of auditing.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Currently every NTFS volumes has their own&amp;nbsp; processing/system ID's. For granting access to Linux host, mapping Unix to windows .&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can we create One global processing/System ID,&amp;nbsp; &amp;nbsp;Grant Processing ID access to all CIFS shares (associated with NTFS volumes)&amp;nbsp; ,&amp;nbsp; Map&amp;nbsp; &amp;nbsp; Linux UID to Windows Global processing ID , So that&amp;nbsp; Linux Host can have access to all NTFS volumes instead of Mapping to individual processing IDs ( resulted in avoiding hundreds&amp;nbsp; of mappings)&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please suggest best approach for granting access to all NTFS volumes ?&lt;/P&gt;
&lt;P&gt;Is this process has any complications and access issues ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It would be big effort. Really appreciate your response or assistance on this.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 09 Mar 2020 05:58:21 GMT</pubDate>
    <dc:creator>hk1213</dc:creator>
    <dc:date>2020-03-09T05:58:21Z</dc:date>
    <item>
      <title>Question about NTFS volume processing ID</title>
      <link>https://community.netapp.com/t5/Ask-The-Experts/Question-about-NTFS-volume-processing-ID/m-p/154819#M1357</link>
      <description>&lt;P&gt;Need your suggestions on the Multi protocol implementation effort.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Currently client have hundreds of NTFS shares, We got requirement to provide access to single Linux host for all volumes part of auditing.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Currently every NTFS volumes has their own&amp;nbsp; processing/system ID's. For granting access to Linux host, mapping Unix to windows .&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can we create One global processing/System ID,&amp;nbsp; &amp;nbsp;Grant Processing ID access to all CIFS shares (associated with NTFS volumes)&amp;nbsp; ,&amp;nbsp; Map&amp;nbsp; &amp;nbsp; Linux UID to Windows Global processing ID , So that&amp;nbsp; Linux Host can have access to all NTFS volumes instead of Mapping to individual processing IDs ( resulted in avoiding hundreds&amp;nbsp; of mappings)&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please suggest best approach for granting access to all NTFS volumes ?&lt;/P&gt;
&lt;P&gt;Is this process has any complications and access issues ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It would be big effort. Really appreciate your response or assistance on this.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 09 Mar 2020 05:58:21 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Ask-The-Experts/Question-about-NTFS-volume-processing-ID/m-p/154819#M1357</guid>
      <dc:creator>hk1213</dc:creator>
      <dc:date>2020-03-09T05:58:21Z</dc:date>
    </item>
    <item>
      <title>Re: Question about NTFS volume processing ID</title>
      <link>https://community.netapp.com/t5/Ask-The-Experts/Question-about-NTFS-volume-processing-ID/m-p/154828#M1361</link>
      <description>&lt;P&gt;You would need to map to a username that has access to all shares. Sometimes if you don't set permissions right a domain admin may not have access.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also, what you're describing is exactly what file policy (fpolicy) does. We have native APIs which work with various vendors. Perhaps that may be a better way of doing what you're looking for?&lt;/P&gt;</description>
      <pubDate>Mon, 09 Mar 2020 14:22:29 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Ask-The-Experts/Question-about-NTFS-volume-processing-ID/m-p/154828#M1361</guid>
      <dc:creator>paul_stejskal</dc:creator>
      <dc:date>2020-03-09T14:22:29Z</dc:date>
    </item>
  </channel>
</rss>

