<?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: Verify Global Protect Version in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/verify-global-protect-version/m-p/538259#M3921</link>
    <description>&lt;P&gt;Not sure if this is the right place to add this but I am trying to identify the best approach to keeping the GP client updated to the latest version.&amp;nbsp; Also need to try and do this witout client intervention. Can we upgrade in the background?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 11 Apr 2023 15:27:13 GMT</pubDate>
    <dc:creator>PNevs</dc:creator>
    <dc:date>2023-04-11T15:27:13Z</dc:date>
    <item>
      <title>Verify Global Protect Version</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/verify-global-protect-version/m-p/538238#M3917</link>
      <description>&lt;P&gt;Hello, im sure there is a document somewhere on how to do this but I cant seem to find it. &amp;nbsp;We have a requirement to ensure our users are on the most current version of GP. &amp;nbsp;Does anyone have a link to the document on how to set this up within the checks the FW runs when the users attempt to start a VPN connection?&lt;/P&gt;</description>
      <pubDate>Tue, 11 Apr 2023 12:49:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/verify-global-protect-version/m-p/538238#M3917</guid>
      <dc:creator>joes87</dc:creator>
      <dc:date>2023-04-11T12:49:59Z</dc:date>
    </item>
    <item>
      <title>Re: Verify Global Protect Version</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/verify-global-protect-version/m-p/538241#M3918</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/86753"&gt;@joes87&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;You can create a HIP object setup like the example that I've included in the message below. You can then setup a profile and use it within your rulebase or configuration selection criteria as desired.&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;              &amp;lt;entry name="GlobalProtect-6.1.1"&amp;gt;
                &amp;lt;host-info&amp;gt;
                  &amp;lt;criteria&amp;gt;
                    &amp;lt;client-version&amp;gt;
                      &amp;lt;contains&amp;gt;6.1.1&amp;lt;/contains&amp;gt;
                    &amp;lt;/client-version&amp;gt;
                  &amp;lt;/criteria&amp;gt;
                &amp;lt;/host-info&amp;gt;
              &amp;lt;/entry&amp;gt;&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would recommend that you create rules to allow clients meeting your outdated criteria enough access to upgrade through the client itself instead of forcing a redownload through the portal or anything like that. Makes it easier on the client since GlobalProtect tends to occasionally run into issues keeping itself updated.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Additionally I always use at least an N+1 supported agent configuration. The newest target GlobalProtect client version that I want everyone to have, and then the last target client version that those who might not have the latest upgrade would be running. Then I use a hip-notification to alert the user running the older release that the client is out of date and needs to be updated, but also that they won't have access to sensitive resources until they have the latest desired agent. Then just configure the policies as your organization requires and it's a fairly seamless transition from version to version.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Apr 2023 13:00:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/verify-global-protect-version/m-p/538241#M3918</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2023-04-11T13:00:28Z</dc:date>
    </item>
    <item>
      <title>Re: Verify Global Protect Version</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/verify-global-protect-version/m-p/538242#M3919</link>
      <description>&lt;P&gt;Thank you. &amp;nbsp;I figured it was done this way. &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Apr 2023 13:02:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/verify-global-protect-version/m-p/538242#M3919</guid>
      <dc:creator>joes87</dc:creator>
      <dc:date>2023-04-11T13:02:13Z</dc:date>
    </item>
    <item>
      <title>Re: Verify Global Protect Version</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/verify-global-protect-version/m-p/538259#M3921</link>
      <description>&lt;P&gt;Not sure if this is the right place to add this but I am trying to identify the best approach to keeping the GP client updated to the latest version.&amp;nbsp; Also need to try and do this witout client intervention. Can we upgrade in the background?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Apr 2023 15:27:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/verify-global-protect-version/m-p/538259#M3921</guid>
      <dc:creator>PNevs</dc:creator>
      <dc:date>2023-04-11T15:27:13Z</dc:date>
    </item>
  </channel>
</rss>

