The reason I chose to do this is that using AutoPkg to create these additional installer packages should help ensure any changes that Palo Alto makes to GlobalProtect’s uninstall and System Extension enablement will automatically be available whenever a new version of GlobalProtect is picked up by AutoPkg.
An installer which enables the System Extension for GlobalProtect.An installer which uninstalls GlobalProtect.An installer which installs GlobalProtect.Using these options, I was able to build recipes for AutoPkg which would automatically build three installer packages:
For example, here’s the installer choices XML file for enabling only the option to uninstall GlobalProtect: The options to uninstall GlobalProtect and enable the System Extension for GlobalProtect can be managed by using an installer choices XML file to selectively enable only the desired option. I made the change to the image to hopefully make more clear which option I was discussing. Note: In the image above, I’ve done some photoshopping because checking the third option to enable the System Extension for GlobalProtect also enables the option to install GlobalProtect. The third configuration is the option to enable the System Extension for GlobalProtect, which is disabled by default: The second configuration is the option to uninstall GlobalProtect, which is disabled by default: The first configuration is the option to install GlobalProtect, the default enabled configuration: One is enabled by default and the other two are disabled by default.
Palo Alto provides an installer package for GlobalProtect, but it has some interesting characteristics as the installer includes three installation options. As part of some recent testing, I needed to do some work with Palo Alto’s GlobalProtect VPN software.
0 kommentar(er)
