jamf PRO Configuration profiles are supported with GlobalProtect 5.1.6 and onwards only.

macOS Catalina 10.15.4 or later / macOS BigSur 11.

If network extensions are already enabled manually via GlobalProtect pop-up’s than using configuration profile, via jamf PRO, to enable network extensions will create a duplicate network extension entries. Note: This document assumes that the macOS endpoint does not have network extensions enabled manually. The workflow can be used for any other Mobile Device Manager (MDM) provider which supports deploying configuration profiles. Objective of this document is to utilize GlobalProtect 5.1.6 signed configuration profiles and deploy them using jamf PRO to suppress macOS 10.15.4 or later system and network extension pop-ups. If you have configured split tunnel on the gateway or enforced GlobalProtect connections for network access on the portal, the System Extension Blocked notification message displays on the app during the installation, prompting users to enable and allow the system extensions in macOS that are blocked from loading to use these GlobalProtect features.

When GlobalProtect app is installed on a macOS Catalina 10.15.4 or later device for the first time or is upgraded to GlobalProtect app 5.1.4, they must now enable the system extensions. GlobalProtect App starting 5.2 uses system extensions on macOS Catalina 10.15.4 or later endpoints for enabling capabilities such as: Enforce GlobalProtect connections for network access (see GlobalProtect App Customization) without requiring kernel extensions.

Split tunnel based on the destination domain name and application process name.GlobalProtect App starting 5.1.4 uses system extensions on macOS Catalina 10.15.4 or later endpoints for enabling capabilities such as:

Mac create new file extensions