<?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 PC Files Server on Windows being access from SAS on Linux in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/PC-Files-Server-on-Windows-being-access-from-SAS-on-Linux/m-p/273140#M5087</link>
    <description>&lt;P&gt;I admin a grid environment in Linux. Users need to be able to access Excel and Access files on Windows CIFS shares. &amp;nbsp;I installed PC FIles Server on a Windows server and set to run as a service (with no authentication). &amp;nbsp; However, I noticed that when I use the PC Files server (making a connection or whatever) it's running as the service account that I used to installed it, not as the user making the connection. &amp;nbsp;Hence the permissions for the PC Files session is not that of the user but that of the service account on the server. &amp;nbsp;So I basically the user won't be able to access files on CIFS shares that are locked down by AD groups becuase the service account doesn't have that access.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I tried setting up with authentication, but I'm a bit confused on how this portion works. &amp;nbsp;I added my own account to the server as a basic user of the computer, but when I try to make a connection (this time adding SERVERUSER= and SERVERPASS= to the connection) it declines my connection every time.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm fuzzy on how this piece works, and I'm not a Windows person at all, so I need a little guidance. &amp;nbsp;Can I set it run as a service and still have the connections/sessions start up under user IDs so they can access files they have permissions for? &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please let me know what other info you might need. &amp;nbsp;Thanks!&lt;/P&gt;</description>
    <pubDate>Wed, 25 May 2016 21:00:11 GMT</pubDate>
    <dc:creator>Timmy2383</dc:creator>
    <dc:date>2016-05-25T21:00:11Z</dc:date>
    <item>
      <title>PC Files Server on Windows being access from SAS on Linux</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/PC-Files-Server-on-Windows-being-access-from-SAS-on-Linux/m-p/273140#M5087</link>
      <description>&lt;P&gt;I admin a grid environment in Linux. Users need to be able to access Excel and Access files on Windows CIFS shares. &amp;nbsp;I installed PC FIles Server on a Windows server and set to run as a service (with no authentication). &amp;nbsp; However, I noticed that when I use the PC Files server (making a connection or whatever) it's running as the service account that I used to installed it, not as the user making the connection. &amp;nbsp;Hence the permissions for the PC Files session is not that of the user but that of the service account on the server. &amp;nbsp;So I basically the user won't be able to access files on CIFS shares that are locked down by AD groups becuase the service account doesn't have that access.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I tried setting up with authentication, but I'm a bit confused on how this portion works. &amp;nbsp;I added my own account to the server as a basic user of the computer, but when I try to make a connection (this time adding SERVERUSER= and SERVERPASS= to the connection) it declines my connection every time.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm fuzzy on how this piece works, and I'm not a Windows person at all, so I need a little guidance. &amp;nbsp;Can I set it run as a service and still have the connections/sessions start up under user IDs so they can access files they have permissions for? &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please let me know what other info you might need. &amp;nbsp;Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 25 May 2016 21:00:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/PC-Files-Server-on-Windows-being-access-from-SAS-on-Linux/m-p/273140#M5087</guid>
      <dc:creator>Timmy2383</dc:creator>
      <dc:date>2016-05-25T21:00:11Z</dc:date>
    </item>
    <item>
      <title>Re: PC Files Server on Windows being access from SAS on Linux</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/PC-Files-Server-on-Windows-being-access-from-SAS-on-Linux/m-p/273290#M5095</link>
      <description>&lt;P&gt;Ok, so apparently I missed page 47 in the installation and configuration document (&lt;A href="http://support.sas.com/documentation/cdl/en/pcfsicg/67728/PDF/default/pcfsicg.pdf" target="_self"&gt;http://support.sas.com/documentation/cdl/en/pcfsicg/67728/PDF/default/pcfsicg.pdf&lt;/A&gt;). &amp;nbsp;This explains how to configure Windows security policy so authenticated users will have their connections/sessions run under their IDs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 May 2016 15:13:30 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/PC-Files-Server-on-Windows-being-access-from-SAS-on-Linux/m-p/273290#M5095</guid>
      <dc:creator>Timmy2383</dc:creator>
      <dc:date>2016-05-26T15:13:30Z</dc:date>
    </item>
  </channel>
</rss>

