<?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: Global Protect client install in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-install/m-p/248854#M70778</link>
    <description>&lt;P&gt;&amp;nbsp;would say no because this is used for the "Default" portal as per palo help below...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class="p"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="p"&gt;PORTAL&amp;nbsp;=&lt;/DIV&gt;&lt;DIV class="p"&gt;This setting specifies the default portal IP address (or hostname).&lt;/DIV&gt;&lt;DIV class="p"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="p"&gt;when you add an additional portal manually it not only goes into the users registry setting but it's also under a different key name.&lt;/DIV&gt;&lt;DIV class="p"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="p"&gt;you may be able to this via group policy or perhaps a post login script that adds the portal address to HKEY_Users&lt;/DIV&gt;</description>
    <pubDate>Tue, 05 Feb 2019 08:38:42 GMT</pubDate>
    <dc:creator>Mick_Ball</dc:creator>
    <dc:date>2019-02-05T08:38:42Z</dc:date>
    <item>
      <title>Global Protect client install</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-install/m-p/248752#M70761</link>
      <description>&lt;P&gt;Global Protect silent install - Can you specify mutable portals during a silent MSI install of Global Protect?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;msiexec.exe /i GlobalProtect64-4.1.9.msi/qn PORTAL=gpgateway-a.companyname.com, gpgateway-b.companyname.com&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class="contents"&gt;&lt;DIV class="section"&gt;&lt;DIV class="sectionBody"&gt;&lt;DIV class="sectionContents"&gt;&lt;DIV class="subsection"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 04 Feb 2019 15:41:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-install/m-p/248752#M70761</guid>
      <dc:creator>Marty.Amaral</dc:creator>
      <dc:date>2019-02-04T15:41:48Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect client install</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-install/m-p/248854#M70778</link>
      <description>&lt;P&gt;&amp;nbsp;would say no because this is used for the "Default" portal as per palo help below...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class="p"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="p"&gt;PORTAL&amp;nbsp;=&lt;/DIV&gt;&lt;DIV class="p"&gt;This setting specifies the default portal IP address (or hostname).&lt;/DIV&gt;&lt;DIV class="p"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="p"&gt;when you add an additional portal manually it not only goes into the users registry setting but it's also under a different key name.&lt;/DIV&gt;&lt;DIV class="p"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="p"&gt;you may be able to this via group policy or perhaps a post login script that adds the portal address to HKEY_Users&lt;/DIV&gt;</description>
      <pubDate>Tue, 05 Feb 2019 08:38:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-install/m-p/248854#M70778</guid>
      <dc:creator>Mick_Ball</dc:creator>
      <dc:date>2019-02-05T08:38:42Z</dc:date>
    </item>
  </channel>
</rss>

