<?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 TS Agent not working for Windows File Explorer in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ts-agent-not-working-for-windows-file-explorer/m-p/304366#M79139</link>
    <description>&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We found out, that it is not possible to track the user when he starts a Windows-File-Explorer via Citrix. Source-Port is used from the System-Context and not from the User-Context.&lt;/P&gt;&lt;P&gt;This behaivour is confirmed by Palo Alto, and it seems to be similar to&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/General-Topics/TS-Agent-no-port-mapping-when-using-windows-net-use/m-p/257607#M73083" target="_blank"&gt;https://live.paloaltonetworks.com/t5/General-Topics/TS-Agent-no-port-mapping-when-using-windows-net-use/m-p/257607#M73083&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClkCCAS" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClkCCAS&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So what I would like to know: Are we the only customers that try to provide a File-Explorer (also valid when e.g. opening files within Office-Products) via Citrix, trying to track the user using the TSA?&lt;/P&gt;&lt;P&gt;Wouldn't that be a base feature that should be provided and also tested before release of the product by Palo Alto as Vendor of the TSA?&lt;/P&gt;&lt;P&gt;At least such constraint should also be highlighted more clearly to the customers (e.g. directly in the white paper). As a user I would expect that such built in functionality of windows is also tested during the QA process.&lt;/P&gt;&lt;P&gt;It would be great if others could confirm that they have the same problem or suggest some workarounds. We really would like to avoid providing individual Terminal-Servers per User-Group accessing the server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kind Regards&lt;/P&gt;&lt;P&gt;Walter&lt;/P&gt;</description>
    <pubDate>Thu, 19 Dec 2019 14:03:26 GMT</pubDate>
    <dc:creator>LeFwAdmins</dc:creator>
    <dc:date>2019-12-19T14:03:26Z</dc:date>
    <item>
      <title>TS Agent not working for Windows File Explorer</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ts-agent-not-working-for-windows-file-explorer/m-p/304366#M79139</link>
      <description>&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We found out, that it is not possible to track the user when he starts a Windows-File-Explorer via Citrix. Source-Port is used from the System-Context and not from the User-Context.&lt;/P&gt;&lt;P&gt;This behaivour is confirmed by Palo Alto, and it seems to be similar to&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/General-Topics/TS-Agent-no-port-mapping-when-using-windows-net-use/m-p/257607#M73083" target="_blank"&gt;https://live.paloaltonetworks.com/t5/General-Topics/TS-Agent-no-port-mapping-when-using-windows-net-use/m-p/257607#M73083&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClkCCAS" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClkCCAS&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So what I would like to know: Are we the only customers that try to provide a File-Explorer (also valid when e.g. opening files within Office-Products) via Citrix, trying to track the user using the TSA?&lt;/P&gt;&lt;P&gt;Wouldn't that be a base feature that should be provided and also tested before release of the product by Palo Alto as Vendor of the TSA?&lt;/P&gt;&lt;P&gt;At least such constraint should also be highlighted more clearly to the customers (e.g. directly in the white paper). As a user I would expect that such built in functionality of windows is also tested during the QA process.&lt;/P&gt;&lt;P&gt;It would be great if others could confirm that they have the same problem or suggest some workarounds. We really would like to avoid providing individual Terminal-Servers per User-Group accessing the server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kind Regards&lt;/P&gt;&lt;P&gt;Walter&lt;/P&gt;</description>
      <pubDate>Thu, 19 Dec 2019 14:03:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ts-agent-not-working-for-windows-file-explorer/m-p/304366#M79139</guid>
      <dc:creator>LeFwAdmins</dc:creator>
      <dc:date>2019-12-19T14:03:26Z</dc:date>
    </item>
    <item>
      <title>Re: TS Agent not working for Windows File Explorer</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ts-agent-not-working-for-windows-file-explorer/m-p/304414#M79143</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/70953"&gt;@LeFwAdmins&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I (and I assume a lot more admins) had to learn this the hard way like you. Unfortunately so far this is a limitation by windows which so far cannot be changed ...&lt;/P&gt;&lt;P&gt;But I absolutely agree with you, this should be mentionned in a more obvious place rather than in a knowledgebase article which is not that easy to find ...&lt;/P&gt;</description>
      <pubDate>Thu, 19 Dec 2019 19:13:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ts-agent-not-working-for-windows-file-explorer/m-p/304414#M79143</guid>
      <dc:creator>Remo</dc:creator>
      <dc:date>2019-12-19T19:13:02Z</dc:date>
    </item>
  </channel>
</rss>

