Is it possible to FQDN exclude your local domain *.localdomain when enforcing network Global Protect connection? Could this be used as a workaround for not having pre-logon configured?
How/why is there not a enforce global protect connection only while "outside" of the network?
This would be for updates in the case a user is not signed in/signed out. Machine would lose connection if no prelogon is setup until user authenticates I think? Mostly regarding updates when a user is not signed into a machine. But if internal it appears it still enforces sign on for network connectivity even when inside a trusted network.
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!