<?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 Minimum supported GlobalProtect version and compatibility in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/minimum-supported-globalprotect-version-and-compatibility/m-p/313977#M81023</link>
    <description>&lt;P&gt;Greetings all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This morning I moved our GlobalProtect from a 4.0.x release to 5.0.7. We're planning on a maintenance tonight to upgrade our firewalls to 9.0.6 and I noticed that there is a minimum supported GlobalProtect version of 4.1 for the 9.0 platform.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I upgrade the firewalls tonight and there are users who still have the older 4.0.x GlobalProtect version installed (i.e. they haven't updated yet) will they still be able to sign in to the client and be prompted to upgrade? Or will the 9.0.6 firewall prevent them from connecting and essentially force them to go download the updated client from the VPN portal?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I don't have any HIP checks configured currently to check for a minimum version and the client is currently configured to prompt for an update.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Mon, 02 Mar 2020 18:47:59 GMT</pubDate>
    <dc:creator>jsalmans</dc:creator>
    <dc:date>2020-03-02T18:47:59Z</dc:date>
    <item>
      <title>Minimum supported GlobalProtect version and compatibility</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/minimum-supported-globalprotect-version-and-compatibility/m-p/313977#M81023</link>
      <description>&lt;P&gt;Greetings all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This morning I moved our GlobalProtect from a 4.0.x release to 5.0.7. We're planning on a maintenance tonight to upgrade our firewalls to 9.0.6 and I noticed that there is a minimum supported GlobalProtect version of 4.1 for the 9.0 platform.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I upgrade the firewalls tonight and there are users who still have the older 4.0.x GlobalProtect version installed (i.e. they haven't updated yet) will they still be able to sign in to the client and be prompted to upgrade? Or will the 9.0.6 firewall prevent them from connecting and essentially force them to go download the updated client from the VPN portal?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I don't have any HIP checks configured currently to check for a minimum version and the client is currently configured to prompt for an update.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 02 Mar 2020 18:47:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/minimum-supported-globalprotect-version-and-compatibility/m-p/313977#M81023</guid>
      <dc:creator>jsalmans</dc:creator>
      <dc:date>2020-03-02T18:47:59Z</dc:date>
    </item>
    <item>
      <title>Re: Minimum supported GlobalProtect version and compatibility</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/minimum-supported-globalprotect-version-and-compatibility/m-p/314023#M81029</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/39461"&gt;@jsalmans&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;The users agents will upgrade to the active package without issue, they shouldn't need to redownload the package from the portal.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 02 Mar 2020 22:13:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/minimum-supported-globalprotect-version-and-compatibility/m-p/314023#M81029</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2020-03-02T22:13:25Z</dc:date>
    </item>
  </channel>
</rss>

