@Mick_Ball wrote: The "enforce GlobalProtect" option boosted our service desk calls bt 45 million (approx) so we took it off. mainly because of issues with captive portal etc but we do prevent open browsing by the use of a proxy.pac config. pretty much got this down to a fine art as we generally only get 1 or 2 calls per week regarding GP. most resolved as users not joining guest networks correctly but hardly ever due to a GP fault. we also run a couple of pre and post VPN scripts but this is just to enforce a few proxy settings and ipconfig/flushdns as this was not part of the early GP versions. @Mick_Ball you should give 5.0.2 a try. I have spent a lot of time together with Paloalto to report, solve and test fixes for issue you describe here. Of course 5.0.2 will not be bug-free, but right not it runs pretty good with enforce enabled. Captive portals are no longer a problem even with this option and in my setup we even have MFA with RADIUS configured which made the whole situation even more difficult. Anyway, if you do test it with 5.0.2 any maybe also with the enforce option, please write your feedback/issues to this post, where I try to collect informations about 5.0.2: https://live.paloaltonetworks.com/t5/General-Topics/Global-Protect-5-0-2-working-deployments-configurations-open/m-p/260183#M73745
... View more