Posted on 03-08-2023 11:32 AM
61381
Created On 08/26/20 21:16 PM - Last Modified 03/21/22 18:33 PM
Symptom
Background
GlobalProtect App starting 5.1.4 uses system extensions on macOS Catalina 10.15.4 or later endpoints for enabling capabilities such as:
GlobalProtect App starting 5.2 uses system extensions on macOS Catalina 10.15.4 or later endpoints for enabling capabilities such as:
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. 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.
Objective:
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. The workflow can be used for any other Mobile Device Manager (MDM) provider which supports deploying configuration profiles.
Note: This document assumes that the macOS endpoint does not have network extensions enabled manually. 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.
Environment
Prerequisite:
Resolution
Table of Contents:
Enable GlobalProtect System Extension
Enable GlobalProtect Network Extension on macOS Catalina 10.15.4 and later Endpoints
Enable GlobalProtect Network Extension on macOS BigSur 11 Endpoints
Steps for Adding a Configuration Profile for Enforcer on jamfPro v10.26.0
Verify Configuration Profiles
Steps for Adding a Configuration Profile to remove System Extensions on macOS Monterey 12 Endpoints
Enable GlobalProtect System Extension:
Note: To enable System Extensions immediately after installation of the GlobalProtect App, use the following command:
sudo installer -pkg GlobalProtect.pkg -applyChoiceChangesXML install_system_extensions.xml -target /
The content of install_system_extensions.xml is
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<array>
<dict>
<key>attributeSetting</key>
<integer>1</integer>
<key>choiceAttribute</key>
<string>selected</string>
<key>choiceIdentifier</key>
<string>third</string>
</dict>
<dict>
<key>attributeSetting</key>
<integer>1</integer>
<key>choiceAttribute</key>
<string>selected</string>
<key>choiceIdentifier</key>
<string>com.paloaltonetworks.globalprotect.systemext.pkg</string>
</dict>
</array>
</plist>
Enable GlobalProtect Network Extension on macOS Catalina 10.15.4 and later Endpoints:
(Note: Enforcer mobileconfig provided in this document will not work on jamfPro v10.26.0, but it works on other jamfPro versions. Click here for steps on how to add Enforcer mobileconfig on jamfPro v10.26.0)
Enable GlobalProtect Network Extension on macOS BigSur 11 Endpoints:
Steps for Adding a Configuration Profile for Enforcer on jamfPro v10.26.0.
Jamf Pro v10.26.0 introduced the Content Filtering payload for macOS devices. It appears that this work also introduced an issue (JAMF Bug# PI-009162) which prevents the ability to upload profiles that include this payload (for example, GlobalProtect Enforcer mobileconfig), both via the GUI and the API. At this time, the only workaround available is to construct the profile using the GUI that’s now available in Jamf Pro v10.26 and later. Following are the steps to configure GlobalProtect Enforcer mobileconfig using the GUI.
Verify Configuration Profiles:
Steps for Adding a Configuration Profile to remove System Extensions on macOS Monterey 12 Endpoints:
Note: The system will still pop up a dialog box asking for Admin password for removing system extensions during GP uninstallation via pkg file
Attachments
Posted on 03-09-2023 08:33 AM
Note: To enable System Extensions immediately after installation of the GlobalProtect App, use the following command:
sudo installer -pkg GlobalProtect.pkg -applyChoiceChangesXML install_system_extensions.xml -target /
The content of install_system_extensions.xml is
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<array>
<dict>
<key>attributeSetting</key>
<integer>1</integer>
<key>choiceAttribute</key>
<string>selected</string>
<key>choiceIdentifier</key>
<string>third</string>
</dict>
<dict>
<key>attributeSetting</key>
<integer>1</integer>
<key>choiceAttribute</key>
<string>selected</string>
<key>choiceIdentifier</key>
<string>com.paloaltonetworks.globalprotect.systemext.pkg</string>
</dict>
</array>
</plist>
Has anyone been able to get this to work? I've followed this exactly and have still been getting the pop up that the system extension has been blocked.
Posted on 08-09-2023 11:01 AM
Hi @Jmazzuca182 ,
Are you missing the Config Profile for the system extension?
I've created a custom pkg in Composer that places the GlobalProtect.pkg and install_system_extensions.xml in a folder location, eg /Users/Shared. Then within a policy I have the custom pkg install and use a script to run the installer and xml from the /Users/Shared.
If the config profile is applied, I do not get prompted for the system extension. Hope this helps.
08-09-2023 11:41 AM - edited 08-09-2023 11:44 AM
.