<?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 Windows 11 Global Protect App not booting at login screen for Prelogon Solution in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/windows-11-global-protect-app-not-booting-at-login-screen-for/m-p/1236639#M6991</link>
    <description>&lt;P&gt;Machines affected at the time of writing are running the following: OS Version: Windows 11&amp;nbsp;&lt;SPAN data-teams="true"&gt;Build # 10.0.22631.5624&lt;/SPAN&gt;&lt;BR /&gt;Global Protect Client Version: 6.2.7-1047&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are introducing our environment to our PA Prelogon Solution which is using a certificate to connect to the network and then LDAP credentials at the login screen. Which allows new users to login to that machine and have their AD profiles generate for the first time.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;What is occurring currently is if the machine is powered off or asleep for a longer period of time and is powered back up. The global protect application is not booting up at the login screen causing the Prelogon configuration to not work and will show the status attempting to connect only for a second before going back to the disconnect status every minute or so.&lt;BR /&gt;&lt;BR /&gt;A partial workaround that has been done is to login with a already generated AD profile or local profile and discovering that the global protect application is not starting up when it should even when logged is to manually boot the application. Then log back out which then will have the global protect client to automatically connect to the Prelogon.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Have done the following to configure the machines for Prelogon and to make sure the client starts when it should.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;A href="https://docs.paloaltonetworks.com/globalprotect/10-1/globalprotect-admin/globalprotect-quick-configs/remote-access-vpn-with-pre-logon" target="_blank"&gt;https://docs.paloaltonetworks.com/globalprotect/10-1/globalprotect-admin/globalprotect-quick-configs/remote-access-vpn-with-pre-logon&lt;/A&gt;&lt;BR /&gt;Followed step 11 and configured the proper registry strings for the Prelogon value and portal.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The global protect client is set to startup and also made sure to have registry startup strings in the following locations&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.microsoft.com/en-us/windows/configure-startup-applications-in-windows-115a420a-0bff-4a6f-90e0-1934c844e473" target="_blank"&gt;https://support.microsoft.com/en-us/windows/configure-startup-applications-in-windows-115a420a-0bff-4a6f-90e0-1934c844e473&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Startup apps in the registry&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;SPAN class="ocpCodeInline"&gt;HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Run&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;SPAN class="ocpCodeInline"&gt;HKLM\Software\Microsoft\Windows\CurrentVersion\Run&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;For applications that run at startup for the current user, the registry path&amp;nbsp;is:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;SPAN class="ocpCodeInline"&gt;HKCU\Software\Microsoft\Windows\CurrentVersion\Run&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN class="ocpCodeInline"&gt;String values for Global Protect is:&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="ocpCodeInline"&gt;Value Name:&amp;nbsp;GlobalProtect&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="ocpCodeInline"&gt;Value Data:&amp;nbsp;"C:\Program Files\Palo Alto Networks\GlobalProtect\PanGPA.exe"&lt;BR /&gt;&lt;BR /&gt;We are unsure what else could be the possible cause of the global protect client to not boot at startup? Any help with this issue would be greatly appreciated!&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 25 Aug 2025 16:53:54 GMT</pubDate>
    <dc:creator>RyanSmetzer</dc:creator>
    <dc:date>2025-08-25T16:53:54Z</dc:date>
    <item>
      <title>Windows 11 Global Protect App not booting at login screen for Prelogon Solution</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/windows-11-global-protect-app-not-booting-at-login-screen-for/m-p/1236639#M6991</link>
      <description>&lt;P&gt;Machines affected at the time of writing are running the following: OS Version: Windows 11&amp;nbsp;&lt;SPAN data-teams="true"&gt;Build # 10.0.22631.5624&lt;/SPAN&gt;&lt;BR /&gt;Global Protect Client Version: 6.2.7-1047&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are introducing our environment to our PA Prelogon Solution which is using a certificate to connect to the network and then LDAP credentials at the login screen. Which allows new users to login to that machine and have their AD profiles generate for the first time.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;What is occurring currently is if the machine is powered off or asleep for a longer period of time and is powered back up. The global protect application is not booting up at the login screen causing the Prelogon configuration to not work and will show the status attempting to connect only for a second before going back to the disconnect status every minute or so.&lt;BR /&gt;&lt;BR /&gt;A partial workaround that has been done is to login with a already generated AD profile or local profile and discovering that the global protect application is not starting up when it should even when logged is to manually boot the application. Then log back out which then will have the global protect client to automatically connect to the Prelogon.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Have done the following to configure the machines for Prelogon and to make sure the client starts when it should.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;A href="https://docs.paloaltonetworks.com/globalprotect/10-1/globalprotect-admin/globalprotect-quick-configs/remote-access-vpn-with-pre-logon" target="_blank"&gt;https://docs.paloaltonetworks.com/globalprotect/10-1/globalprotect-admin/globalprotect-quick-configs/remote-access-vpn-with-pre-logon&lt;/A&gt;&lt;BR /&gt;Followed step 11 and configured the proper registry strings for the Prelogon value and portal.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The global protect client is set to startup and also made sure to have registry startup strings in the following locations&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.microsoft.com/en-us/windows/configure-startup-applications-in-windows-115a420a-0bff-4a6f-90e0-1934c844e473" target="_blank"&gt;https://support.microsoft.com/en-us/windows/configure-startup-applications-in-windows-115a420a-0bff-4a6f-90e0-1934c844e473&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Startup apps in the registry&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;SPAN class="ocpCodeInline"&gt;HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Run&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;SPAN class="ocpCodeInline"&gt;HKLM\Software\Microsoft\Windows\CurrentVersion\Run&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;For applications that run at startup for the current user, the registry path&amp;nbsp;is:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;SPAN class="ocpCodeInline"&gt;HKCU\Software\Microsoft\Windows\CurrentVersion\Run&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN class="ocpCodeInline"&gt;String values for Global Protect is:&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="ocpCodeInline"&gt;Value Name:&amp;nbsp;GlobalProtect&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="ocpCodeInline"&gt;Value Data:&amp;nbsp;"C:\Program Files\Palo Alto Networks\GlobalProtect\PanGPA.exe"&lt;BR /&gt;&lt;BR /&gt;We are unsure what else could be the possible cause of the global protect client to not boot at startup? Any help with this issue would be greatly appreciated!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 25 Aug 2025 16:53:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/windows-11-global-protect-app-not-booting-at-login-screen-for/m-p/1236639#M6991</guid>
      <dc:creator>RyanSmetzer</dc:creator>
      <dc:date>2025-08-25T16:53:54Z</dc:date>
    </item>
  </channel>
</rss>

