<?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 UPDATE ISSUE in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-update-issue/m-p/1227701#M6722</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/799182503"&gt;@F.Pinar&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;The explanation that you received the first time&amp;nbsp;&lt;EM&gt;is&amp;nbsp;&lt;/EM&gt;correct and that is a requirement for the agent to actually upgrade properly. That isn't the only reason you can run into issues however.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What is the client-upgrade set to in your app-config? What is your connection method? Are you seeing the issue on&amp;nbsp;&lt;EM&gt;every&amp;nbsp;&lt;/EM&gt;user that connects?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 29 Apr 2025 22:02:41 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2025-04-29T22:02:41Z</dc:date>
    <item>
      <title>GLOBAL PROTECT UPDATE ISSUE</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-update-issue/m-p/1227569#M6719</link>
      <description>&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD width="150"&gt;
&lt;P&gt;Model&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="117"&gt;
&lt;P&gt;PA-1410&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;it does not allow updating the VPN to a current version in the equipment, when the users connect they try to update and it does not do any process and remains in version 6.2. 4 This case was reviewed on another occasion with you and I was indicated that the solution was that by using an FQDN to route traffic to the portal (either through the GP app or via web) that is mounted on a public IP, it is necessary that when connected to the VPN, these FQDNs are reached and successfully resolved by the DNS for the agent update is completed.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Apr 2025 16:26:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-update-issue/m-p/1227569#M6719</guid>
      <dc:creator>F.Pinar</dc:creator>
      <dc:date>2025-04-28T16:26:39Z</dc:date>
    </item>
    <item>
      <title>Re: GLOBAL PROTECT UPDATE ISSUE</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-update-issue/m-p/1227701#M6722</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/799182503"&gt;@F.Pinar&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;The explanation that you received the first time&amp;nbsp;&lt;EM&gt;is&amp;nbsp;&lt;/EM&gt;correct and that is a requirement for the agent to actually upgrade properly. That isn't the only reason you can run into issues however.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What is the client-upgrade set to in your app-config? What is your connection method? Are you seeing the issue on&amp;nbsp;&lt;EM&gt;every&amp;nbsp;&lt;/EM&gt;user that connects?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Apr 2025 22:02:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-update-issue/m-p/1227701#M6722</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2025-04-29T22:02:41Z</dc:date>
    </item>
  </channel>
</rss>

