<?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 agent not connecting after windows imaging with new updates. in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-agent-not-connecting-after-windows-imaging-with/m-p/595166#M5681</link>
    <description>&lt;P&gt;This looks like a cosmetic issue. Recommend to go with TAC.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 17 Aug 2024 08:07:40 GMT</pubDate>
    <dc:creator>Edsnow</dc:creator>
    <dc:date>2024-08-17T08:07:40Z</dc:date>
    <item>
      <title>global protect agent not connecting after windows imaging with new updates.</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-agent-not-connecting-after-windows-imaging-with/m-p/595145#M5680</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;
&lt;P&gt;We are facing issue with our global protect agent not connecting after windows imaging with new updates. We were suspecting windows KB5018410 to broke this, but this is not installed.&lt;/P&gt;
&lt;P&gt;The error we are seeing in logs is "client certficate not found". However, correct certficate chain is already present in the machines.&lt;/P&gt;
&lt;P&gt;It only works when we manually delete the certficates and re-install in the machine, and also we need to un-install and install GP clinet again to make this works.&lt;/P&gt;
&lt;P&gt;This is a big organization, we can not follow this workaround for every machine.&lt;/P&gt;
&lt;P&gt;We tried to upgrade the GP clinet to 6.2.3 as well, but no success.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Is there any other way to do that ?&lt;/P&gt;</description>
      <pubDate>Fri, 16 Aug 2024 20:40:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-agent-not-connecting-after-windows-imaging-with/m-p/595145#M5680</guid>
      <dc:creator>Jagdeep1</dc:creator>
      <dc:date>2024-08-16T20:40:47Z</dc:date>
    </item>
    <item>
      <title>Re: global protect agent not connecting after windows imaging with new updates.</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-agent-not-connecting-after-windows-imaging-with/m-p/595166#M5681</link>
      <description>&lt;P&gt;This looks like a cosmetic issue. Recommend to go with TAC.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 17 Aug 2024 08:07:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-agent-not-connecting-after-windows-imaging-with/m-p/595166#M5681</guid>
      <dc:creator>Edsnow</dc:creator>
      <dc:date>2024-08-17T08:07:40Z</dc:date>
    </item>
  </channel>
</rss>

