<?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: Compatibility of New GlobalProtect Client with Older Firewall/Prisma Access Versions in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/compatibility-of-new-globalprotect-client-with-older-firewall/m-p/999341#M5292</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/401644031"&gt;@pvathare&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;This isn't an issue. If you have a version that is newer than that which is being deployed it'll function without issue* and the updated version won't be downgraded when you connect.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;* It's possible to limit which GlobalProtect versions are allowed to connect to the gateway via HIP. It's possible that someone limiting GlobalProtect to specific versions to force people to upgrade may not be accounting for versions newer than what is being deployed. This would be a local configuration that we wouldn't be able to tell you whether or not you'll be impacted by something like this. &lt;/EM&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 23 Dec 2024 16:06:47 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2024-12-23T16:06:47Z</dc:date>
    <item>
      <title>Compatibility of New GlobalProtect Client with Older Firewall/Prisma Access Versions</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/compatibility-of-new-globalprotect-client-with-older-firewall/m-p/999335#M5291</link>
      <description>&lt;P&gt;Will my newer GlobalProtect client software still work if my firewall or Prisma Access is using an older version of GlobalProtect?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 23 Dec 2024 14:06:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/compatibility-of-new-globalprotect-client-with-older-firewall/m-p/999335#M5291</guid>
      <dc:creator>pvathare</dc:creator>
      <dc:date>2024-12-23T14:06:56Z</dc:date>
    </item>
    <item>
      <title>Re: Compatibility of New GlobalProtect Client with Older Firewall/Prisma Access Versions</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/compatibility-of-new-globalprotect-client-with-older-firewall/m-p/999341#M5292</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/401644031"&gt;@pvathare&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;This isn't an issue. If you have a version that is newer than that which is being deployed it'll function without issue* and the updated version won't be downgraded when you connect.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;* It's possible to limit which GlobalProtect versions are allowed to connect to the gateway via HIP. It's possible that someone limiting GlobalProtect to specific versions to force people to upgrade may not be accounting for versions newer than what is being deployed. This would be a local configuration that we wouldn't be able to tell you whether or not you'll be impacted by something like this. &lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 23 Dec 2024 16:06:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/compatibility-of-new-globalprotect-client-with-older-firewall/m-p/999341#M5292</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2024-12-23T16:06:47Z</dc:date>
    </item>
  </channel>
</rss>

