GlobalProtect
GlobalProtect App 6.2.8 Windows and macOS Addressed Issues
Table of Contents
Expand All
|
Collapse All
GlobalProtect Docs
-
10.1 & Later
- 10.1 & Later
- 9.1 (EoL)
-
- How Does the App Know Which Certificate to Supply?
- Set Up Cloud Identity Engine Authentication
- Configure GlobalProtect to Facilitate Multi-Factor Authentication Notifications
- Enable Delivery of VSAs to a RADIUS Server
- Enable Group Mapping
-
-
- GlobalProtect App Minimum Hardware Requirements
- Download the GlobalProtect App Software Package for Hosting on the Portal
- Host App Updates on the Portal
- Host App Updates on a Web Server
- Test the App Installation
- Download and Install the GlobalProtect Mobile App
- View and Collect GlobalProtect App Logs
-
-
- Deploy App Settings in the Windows Registry
- Deploy App Settings from Msiexec
- Deploy Scripts Using the Windows Registry
- Deploy Scripts Using Msiexec
- Deploy Connect Before Logon Settings in the Windows Registry
- Deploy GlobalProtect Credential Provider Settings in the Windows Registry
- SSO Wrapping for Third-Party Credential Providers on Windows Endpoints
- Enable SSO Wrapping for Third-Party Credentials with the Windows Registry
- Enable SSO Wrapping for Third-Party Credentials with the Windows Installer
- Deploy App Settings to Linux Endpoints
- GlobalProtect Processes to be Whitelisted on EDR Deployments
-
-
- Mobile Device Management Overview
- Set Up the MDM Integration With GlobalProtect
- Qualified MDM Vendors
-
-
- Set Up the Microsoft Intune Environment for Android Endpoints
- Deploy the GlobalProtect App on Android Endpoints Using Microsoft Intune
- Create an App Configuration on Android Endpoints Using Microsoft Intune
- Configure Lockdown Mode for Always On Connect Method on Android Endpoints Using Microsoft Intune
-
- Deploy the GlobalProtect Mobile App Using Microsoft Intune
- Configure an Always On VPN Configuration for iOS Endpoints Using Microsoft Intune
- Configure a User-Initiated Remote Access VPN Configuration for iOS Endpoints Using Microsoft Intune
- Configure a Per-App VPN Configuration for iOS Endpoints Using Microsoft Intune
-
-
-
- Create a Smart Computer Group for GlobalProtect App Deployment
- Create a Single Configuration Profile for the GlobalProtect App for macOS
- Deploy the GlobalProtect Mobile App for macOS Using Jamf Pro
-
- Enable GlobalProtect System Extensions on macOS Endpoints Using Jamf Pro
- Enable GlobalProtect Network Extensions on macOS Big Sur Endpoints Using Jamf Pro
- Add a Configuration Profile for the GlobalProtect Enforcer by Using Jamf Pro 10.26.0
- Verify Configuration Profiles Deployed by Jamf Pro
- Remove System Extensions on macOS Monterey Endpoints Using Jamf Pro
- Non-Removable System Extensions on macOS Sequoia Endpoints Using Jamf Pro
- Uninstall the GlobalProtect Mobile App Using Jamf Pro
-
- Configure HIP-Based Policy Enforcement
- Configure HIP Exceptions for Patch Management
- Collect Application and Process Data From Endpoints
- Redistribute HIP Reports
-
- Identification and Quarantine of Compromised Devices Overview and License Requirements
- View Quarantined Device Information
- Manually Add and Delete Devices From the Quarantine List
- Automatically Quarantine a Device
- Use GlobalProtect and Security Policies to Block Access to Quarantined Devices
- Redistribute Device Quarantine Information from Panorama
- Troubleshoot HIP Issues
-
-
- Enable and Verify FIPS-CC Mode on Windows Endpoints
- Enable and Verify FIPS-CC Mode on macOS Endpoints
- Enable and Verify FIPS-CC Mode Using Workspace ONE on iOS Endpoints
- Enable FIPS Mode on Linux EndPoints with Ubuntu or RHEL
- Enable and Verify FIPS-CC Mode Using Microsoft Intune on Android Endpoints
- FIPS-CC Security Functions
- Resolve FIPS-CC Mode Issues
-
-
- Remote Access VPN (Authentication Profile)
- Remote Access VPN (Certificate Profile)
- Remote Access VPN with Two-Factor Authentication
- GlobalProtect Always On VPN Configuration
- Remote Access VPN with Pre-Logon
- User-Initiated Pre-Logon Connection
- GlobalProtect Multiple Gateway Configuration
- GlobalProtect for Internal HIP Checking and User-Based Access
- Mixed Internal and External Gateway Configuration
- Captive Portal and Enforce GlobalProtect for Network Access
- GlobalProtect on Windows 365 Cloud PC
-
- About GlobalProtect Cipher Selection
- Cipher Exchange Between the GlobalProtect App and Gateway
-
- Reference: GlobalProtect App Cryptographic Functions
-
- Reference: TLS Ciphers Supported by GlobalProtect Apps on macOS Endpoints
- Reference: TLS Ciphers Supported by GlobalProtect Apps on Windows Endpoints
- Reference: TLS Ciphers Supported by GlobalProtect Apps on Android 6.0.1 Endpoints
- Reference: TLS Ciphers Supported by GlobalProtect Apps on iOS 10.2.1 Endpoints
- Reference: TLS Ciphers Supported by GlobalProtect Apps on Chromebooks
- Ciphers Used to Set Up IPsec Tunnels
- SSL APIs
-
- View a Graphical Display of GlobalProtect User Activity in PAN-OS
- View All GlobalProtect Logs on a Dedicated Page in PAN-OS
- Event Descriptions for the GlobalProtect Logs in PAN-OS
- Filter GlobalProtect Logs for Gateway Latency in PAN-OS
- Restrict Access to GlobalProtect Logs in PAN-OS
- Forward GlobalProtect Logs to an External Service in PAN-OS
- Configure Custom Reports for GlobalProtect in PAN-OS
-
6.3
- 6.3
- 6.2
- 6.1
- 6.0
- 5.1
-
- Download and Install the GlobalProtect App for Windows
- Use Connect Before Logon
- Use Single Sign-On for Smart Card Authentication
- Use the GlobalProtect App for Windows
- Report an Issue From the GlobalProtect App for Windows
- Disconnect the GlobalProtect App for Windows
- Uninstall the GlobalProtect App for Windows
- Fix a Microsoft Installer Conflict
-
- Download and Install the GlobalProtect App for macOS
- Use the GlobalProtect App for macOS
- Report an Issue From the GlobalProtect App for macOS
- Disconnect the GlobalProtect App for macOS
- Uninstall the GlobalProtect App for macOS
- Remove the GlobalProtect Enforcer Kernel Extension
- Enable the GlobalProtect App for macOS to Use Client Certificates for Authentication
-
6.1
- 6.1
- 6.0
- 5.1
-
6.2
- 6.3
- 6.2
- 6.1
- 6.0
- 5.1
- Features Introduced
- Changes to Default Behavior
- Associated Software and Content Versions
-
- GlobalProtect App 6.2.8 Windows and macOS Known Issues
- GlobalProtect App 6.2.7 Windows and macOS Known Issues
- GlobalProtect App 6.2.6-c857 Windows and macOS Known Issues
- GlobalProtect App 6.2.1-c31 Linux Known Issues
- GlobalProtect App 6.2.6 Windows and macOS Known Issues
- GlobalProtect App 6.2.5 Windows and macOS Known Issues
- GlobalProtect App 6.2.4 Windows and macOS Known Issues
- GlobalProtect App 6.2.3-c287 Windows and macOS Known Issues
- GlobalProtect App 6.2.3 Windows and macOS Known Issues
- GlobalProtect App 6.2.2 Windows and macOS Known Issues
- GlobalProtect App 6.2.1 Linux Known Issues
- GlobalProtect App 6.2.1 Windows and macOS Known Issues
- GlobalProtect App 6.2.0 Linux Known Issues
-
- GlobalProtect App 6.2.8 Windows and macOS Addressed Issues
- GlobalProtect App 6.2.7 Addressed Issues
- GlobalProtect App 6.2.6-c857 Windows and macOS Addressed Issues
- GlobalProtect App 6.2.1-c31 Linux Addressed Issues
- GlobalProtect App 6.2.6 Windows and macOS Addressed Issues
- GlobalProtect App 6.2.5 Windows and macOS Addressed Issues
- GlobalProtect App 6.2.4 Windows and macOS Addressed Issues
- GlobalProtect App 6.2.3-c287 Addressed Issues
- GlobalProtect App 6.2.3 Windows and macOS Addressed Issues
- GlobalProtect App 6.2.2 Windows and macOS Addressed Issues
- GlobalProtect App 6.2.1 Linux Addressed Issues
- GlobalProtect App 6.2.1 Windows and macOS Addressed Issues
- GlobalProtect App 6.2.0 Linux Addressed Issues
GlobalProtect App 6.2.8 Windows and macOS Addressed Issues
GlobalProtect App 6.2.8 Windows and macOS Addressed Issues
The following table lists the addressed issues in GlobalProtect app 6.2.8 Windows and macOS.
|
Issue ID
|
Description
|
|---|---|
|
GPC-22894
|
Fixed an issue where GlobapProtect did not detect the correct version
of Kaspersky Endpoint Security.
|
|
GPC-22847
|
Fixed an issue where GlobalProtect did not detect Qualys for patch
management.
|
|
GPC-22764
|
Fixed an issue where wa_3rd_party_host_xx.exe attempted to connect to
Microsoft’s update servers for information and the patch information
was not sent in the HIP report. This occured even though HIP
Exceptions for patch management were configured to exclude Windows
updates agent.
|
|
GPC-22740
|
Fixed an issue where macOS computers displayed both the new and old
versions of the GlobalProtect welcome page.
|
|
GPC-22688
|
Fixed an issue for proxy-only mode where customers were unable to
access websites when the computer woke up from sleep.
|
|
GPC-22638
|
Fixed an issue where Global Protect HIP did not detect the drive
state when using Trellix Drive Encryption 8.0.
|
|
GPC-22620
|
Fixed an issue where GlobalProtect was not working correctly and
blocked internet access.
|
|
GPC-22589
|
Fixed an issue where the Report an Issue functionality did not send
the troubleshooting log to the administrator’s Strata Logging
Service instance.
|
|
GPC-22542
|
Fixed an issue where the embedded browser shown as part of SAML
authentication was blank.
|
|
GPC-22487
|
Fixed an issue where Norton 360 was not compatible with GlobalProtect
causing the device to fail the HIP check.
|
|
GPC-22443
|
Fixed an issue where the GlobalProtect agent showed as connected even
when the virtual adapter was down.
|
|
GPC-22437
|
Fixed an issue where the GlobalProtect macOS client experienced a
keep-alive timeout, preventing the tunnel from connecting.
|
|
GPC-22412
|
Fixed an error where virtual adapter is not set correctly during
tunnel creation.
|
|
GPC-22297
|
Fixed an issue where the Customer was getting "A valid client
certificate is required for authentication" even though they had a
valid client certificate installed.
|
|
GPC-22264
|
Fixed an issue where the GlobalProtect HIP report did not detect the
last full scan time for Avast antivirus software.
|
|
GPC-22245
|
Fixed an issue where transparent upgrade from GlobalProtect version
6.2.4 or 6.2.5 to version 6.2.6 failed on some Windows endpoints
with error 1618.
|
|
GPC-22237
|
Fixed an issue where GlobalProtect shut down unexpectedly on Windows
11 devices running multiple versions of GlobalProtect 6.3. The issue
was caused by the firewall sending invalid IPv6 packets to
GlobalProtect, which did not have a validation method before
processing.
|
|
GPC-22235
|
Fixed an issue where users were unable to connect to the app after
the system woke up from sleep mode.
|
|
GPC-22233
|
Fixed an issue where the users were unable to connect the
GlobalProtect app after performing the resolution of CVE-2024-5921.
The app displayed the following error, “The certificate CN name
mismatch.”
|
|
GPC-22126
|
Fixed an issue where GlobalProtect version 6.2.6-838 was stuck
intermittently during the connection process.
|
|
GPC-22123
| Fixed an issue where the GlobalProtect app got stuck and users faced connection issues after the system woke up from sleep mode even though the internet connection was stable. |
|
GPC-22092
|
Fixed an issue where the GlobalProtect app failed to validate the
server certificate when the portal or gateway sent only the leaf
certificate.
|
|
GPC-22061
|
Fixed an issue where the GlobalProtect client displayed an error when
using an ECDSA certificate with explicit EC parameters in FIPS mode.
|
|
GPC-22043
|
Fixed an issue where Okta push notification shows incorrect Windows
OS, when Okta SAML authentication is enabled in GlobalProtect.
|
GPC-22036 | Resolved an issue where GlobalProtect did not populate the internal routes in the user's routing table.
|
GPC-22028 | Fixed an issue where the disconnect reason for macOS users was getting cached.
|
|
GPC-21988
|
Fixed an issue where the GlobalProtect Client displayed a download
prompt or was updated even with an "upgrade disallow" configuration.
|
|
GPC-21979
|
Fixed an issue where the included domain traffic was routed through
the physical interface when split tunnel was configured.
|
|
GPC-21961
|
Fixed an issue where, after upgrading to GlobalProtect version 6.2.5,
the app triggered authentication and opened multiple browser tabs
when the computer woke from sleep.
|
|
GPC-21960
|
Fixed an issue where the HIP check failed to detect the Norton
anti-malware version 24.11.9615.0.
|
|
GPC-21955
|
Fixed an issue where the HIP notification pop-up on macOS looked
different from that on Windows.
|
|
GPC-21938
|
Fixed an issue where, when the GlobalProtect app version 6.3.x was
installed on devices running macOS, the HIP check failed to detect
ESET Endpoint Security version 8.
|
|
GPC-21918
|
Fixed an issue where, when the patch management category was excluded
for HIP checks, HIP checks were still happening for missing patches
which consumed CPU resources on users' machine.
|
GPC-21938 | Fixed an issue where, when the GlobalProtect app version 6.3.x was installed on devices running macOS, the HIP check failed to detect ESET Endpoint Security version 8.
|
GPC-21775 | Fixed an issue where GlobalProtect users on macOS were disconnected immediately after sending the HIP report.
|
|
GPC-21771
|
Fixed an issue where the GlobalProtect HIP check incorrectly detected
Malware Definition Date for Trend Micro Deep Security Agent, which
caused the device to fail the HIP check.
|
GPC-21743 | Fixed an issue where a user was randomly prompted with a \"Login Successful\" message when connecting to GlobalProtect (GP), even though GP was not connected.
|
|
GPC-21695
|
Fixed an issue where the GlobalProtect embedded browser could not
utilize a new PIV certificate for SAML authentication if multiple
certificates were available.
|
|
GPC-21677
|
Fixed an issue where GlobalProtect configured for Always-on Pre-logon
may not display the captive portal page if there is a delay with
network access or Internet connectivity.
|
|
GPC-21653
|
Fixed an issue where the GlobalProtect virtual adapter was not set up
correctly.
|
GPC-21639 | Fixed an issue where the GlobalProtect macOS client did not extend the session even though the user clicked the Extend Session button.
|
GPC-21627 | Fixed an issue where the Report an Issue feature failed to work for a specific user whose username contained Japanese character.
|
|
GPC-21615
|
Fixed an issue where the GlobalProtect agent
(wa_3rd_party_host_64.exe) modified the __PSLockDownPolicy registry
key from 4 (secure language mode) to 0 (full language mode) after a
reboot.
|
GPC-21571 | Fixed an issue where the hyperlink in HIP notification opened up in Webview2 instead of the default browser.
|
GPC-21565 | Fixed an issue where the SAML embedded browser did not remember the username after sign-out, even when the user had selected the check box “Remember Me" on the SAML embedded browser,
|
|
GPC-21527
|
Fixed an issue where the firewall did not exclude the APIPA
(169.254.0.0/16) range from GlobalProtect when the Endpoint Traffic
Policy Enforcement feature was enabled with the exclude option. As a
result, traffic to the APIPA range was sent over GlobalProtect
instead of the local interface.
|
GPC-21467 | Fixed an issue where the Transparent Upgrade with Proxy only mode did not work as expected and no tunnel was established with the gateway.
|
GPC-21453 | Fixed an issue where the GlobalProtect app window displayed "static" instead of the connected gateway name.
|
GPC-21222 | Fixed an issue where the GlobalProtect HIP check incorrectly detected the Real Time Protection Status and Last Full Scan for Avast application, which caused the device to fail the HIP check.
|
GPC-21090 | Fixed an issue where GlobalProtect only displayed ADEM information for approximately 120 users even though more than 600 ADEM users were connected to GlobalProtect.
|
GPC-20967 | Fixed an issue where, when the GlobalProtect app was installed with the Conditional Connect method, users had to click the Connect button twice to connect to an external gateway after a system reboot.
|
|
GPC-20632
|
Fixed an issue where GLobalProtect was stuck in connecting mode after
the customer manually selected a gateway that hit the maximum user
limit. This was a multi-gateway environment with SAML/CAS
authentication method.
|
GPC-20621 | Fixed an issue where users from overseas locations were disconnected from GlobalProtect due to the HIP report not being sent with manual gateway selection.
|
GPC-18587 | Fixed an issue where, when the GlobalProtect was installed on Windows devices and Connect Before Logon was deployed, users were unable to log in to the device using the User Principal Name (UPN). This issue occurred when the GlobalProtect credential provider was selected and the device was offline.
|