- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
08-25-2025 09:53 AM
Machines affected at the time of writing are running the following: OS Version: Windows 11 Build # 10.0.22631.5624
Global Protect Client Version: 6.2.7-1047
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.
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.
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.
Have done the following to configure the machines for Prelogon and to make sure the client starts when it should.
https://docs.paloaltonetworks.com/globalprotect/10-1/globalprotect-admin/globalprotect-quick-configs...
Followed step 11 and configured the proper registry strings for the Prelogon value and portal.
The global protect client is set to startup and also made sure to have registry startup strings in the following locations
Startup apps in the registry
HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Run
HKLM\Software\Microsoft\Windows\CurrentVersion\Run
For applications that run at startup for the current user, the registry path is:
HKCU\Software\Microsoft\Windows\CurrentVersion\Run
String values for Global Protect is:
Value Name: GlobalProtect
Value Data: "C:\Program Files\Palo Alto Networks\GlobalProtect\PanGPA.exe"
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!
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!