GP User-logon (Always On) doesn't connect

[${userLoginName}]

We are preparing configuration of GP for Windows based terminals which need to connect automatically when Windows AutoLogon happens. But in most cases GP remains disconnected because it tries to connect too early when network isn't fully connected yet. If I click on Connect it connects immediately. But of course this isn't an option,

Any ideas how to make this work? How to make GP client to try to connect constantly even if it fails a few times first? Or how to delay GP to try to connect a bit later? 

One idea was to make a script which would trigger GP Connect a bit later but to my big dissapointment I read somewhere that GP doesn't support any commands from CMD.

Any other ideas please?

GlobalProtect 

[kiwi · Accepted solution]

Hi @${userLoginName} ,

Sounds like you're running into a race condition where the GlobalProtect service starts before the network stack is fully initialized.

Have you tried delaying the startup ?

You should be able to locate the PanGPS service in services.msc and change the startup type from "Automatic" to "Automatic (Delayed Start)".

This should tell Windows to wait a while after all critical system services have started before it runs the PanGPS service, giving the network stack plenty of time to initialize. If I'm not mistaken the default is 2minutes delay.

Hope this helps,

-Kim.

[${userLoginName} · Accepted solution]

Thank you for the info. I didn't know this "Automatic (Delayed Start)" for Windows services. And yes, delayed start for PanGPS service solves the issue.

Another way (as there are no CMD commands possible for GP now) is to restart the PanGPS service (net stop PanGPS; timeout /t 5 >nul ; net start PanGPS).

But I would still like to know default behavior of GP client in the mentioned scenario (User-logon (Always On) with Windows AutoLogon but no network connection at service start). I have opened a TAC case for this, will post the findings here once I get something useful.