<?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: Terminal Server Agent service account issue. in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/terminal-server-agent-service-account-issue/m-p/78490#M42955</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Service accounts get access to the stack at a different level than user accounts, this means the TSAgent will not be able to control source ports assigned to service accounts.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 23 May 2016 08:57:43 GMT</pubDate>
    <dc:creator>reaper</dc:creator>
    <dc:date>2016-05-23T08:57:43Z</dc:date>
    <item>
      <title>Terminal Server Agent service account issue.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/terminal-server-agent-service-account-issue/m-p/78486#M42954</link>
      <description>&lt;P&gt;Configured a new TS on palo alto and installed agent on the server. Already have 2 TS configured on the PA and running fine.This new server has 2 service accounts with both needing internet access. These are adsync and centrify service accounts. I can see mapping of the users who are logging to TS server but service accounts are having issues. centrify wasn't able to access internet. Will TS also map service accounts in the same way as user accounts. When stopped agent on the server and deleted TS config from PA200( PANOS-7.6) it was working again.&lt;/P&gt;
&lt;P&gt;But i could see in user-ip mapping as if service accounts are knocking each other out as the mapping of ip to service account was changing between adsyn and centrify account. How could i get both service account working on the TS.&lt;/P&gt;</description>
      <pubDate>Mon, 23 May 2016 08:30:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/terminal-server-agent-service-account-issue/m-p/78486#M42954</guid>
      <dc:creator>inderjit21</dc:creator>
      <dc:date>2016-05-23T08:30:27Z</dc:date>
    </item>
    <item>
      <title>Re: Terminal Server Agent service account issue.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/terminal-server-agent-service-account-issue/m-p/78490#M42955</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Service accounts get access to the stack at a different level than user accounts, this means the TSAgent will not be able to control source ports assigned to service accounts.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 23 May 2016 08:57:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/terminal-server-agent-service-account-issue/m-p/78490#M42955</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2016-05-23T08:57:43Z</dc:date>
    </item>
  </channel>
</rss>

