End-of-Life (EoL)
GlobalProtect App 4.1.6 Addressed Issues
The following table lists the issues
that are addressed in GlobalProtect™ app 4.1.6.
Issue ID | Description |
|---|---|
GPC-7394 | Fixed an issue on Windows 7 and Windows
10 endpoints where the GlobalProtect app remained in a connecting
state for an extended period of time. |
GPC-7351 | Fixed an issue on Windows endpoints where
end users experienced delays when authenticating to a GlobalProtect
portal due to an issue with the NetUserGetInfo API call. |
GPC-7346 | Fixed an issue on Windows and macOS endpoints
where the GlobalProtect agent was not enabled after the Disable Timeout had
expired and the endpoint was rebooted after this time. |
GPC-7337 | Fixed an issue on endpoints running Android
8.0 and later releases where AirWatch Agent was unable to register
to GlobalProtect due to a mismatch between the ANDROID_ID for AirWatch
Agent and the ANDROID_ID for the GlobalProtect app. This issue occurred
because the ANDROID_ID in Android 8.0 and later releases is unique
for each combination of apps, users, and endpoints. |
GPC-7269 | Fixed an issue where, if a user disabled
the GlobalProtect app before entering a GlobalProtect portal, the
app was disabled but appeared as if it was trying to connect. Now,
an end user cannot disable GlobalProtect if a portal is not specified. |
GPC-7260 | Fixed an issue on Windows endpoints where
the GlobalProtect app caused delay or packet loss when processing
packets and while internet upload link speeds were high. |
GPC-7239 | Fixed an issue with SAML authentication
on Windows endpoints where GlobalProtect displayed an authentication
error after the refresh configuration timeout expires and GlobalProtect
tried to reconnect. Now, when the refresh configuration timeout
expires, GlobalProtect instead displays a notification that it is
trying to connect. |
GPC-7233 | Fixed an issue on Windows endpoints where
the GlobalProtect app did not detect real-time protection when Norton
Security Anti-Virus/Anti-Spyware is installed and indicated the
value in the Host Profile as N/A . |
GPC-7223 | Fixed an issue on Windows 10 endpoints where
the GlobalProtect credential provider did not accept a user name
in User Principal Name (UPN) with an alternative domain suffix,
such as username@domainname.local. |
GPC-7215 | Fixed an issue where, if you configured
the GlobalProtect app to Save User Credentials (Network GlobalProtect Portals <portal-config> Agent <agent-config> Authentication # ) sign to passwords when requesting
and saving user credentials for GlobalProtect gateway authentication.
This issue caused subsequent GlobalProtect connections to fail because
the app used the incorrect saved passwords for portal and gateway
authentication. |
GPC-7144 | Fixed an issue on Windows endpoints that
use the Enforce GlobalProtect feature where,
due to connection establishment delays, internal users were prevented
from accessing internal resources following initial sign-on. |
GPC-7092 | Fixed an issue on macOS endpoints where
the GlobalProtect app did not detect the last time a full antivirus
scan was run on the endpoint and therefore indicated the value of Last
Full Scan Time in the Host Profile as N/A . |
GPC-6985 | Fixed an issue with resilient VPN where
GlobalProtect failed to reconnect when an end user transitions from
one network to another (for example, from LAN to Wi-Fi). |
GPC-6964 | Fixed an issue on macOS endpoints where
GlobalProtect did not recognize Carbon Black software as Anti-Virus/Anti-Spyware
software and indicated the value as N/A in the Host Profile. |
GPC-6951 | Fixed an issue in the HIP profile where
GlobalProtect did not identify and display the Last Full
Scan Time when Bitdefender Antivirus ran on macOS endpoints. |
GPC-6899 | Fixed an issue using CAC smart cards for
authentication on Windows 10 endpoints where GlobalProtect remained
connected after the CAC smart card was removed and the option to Retain Connection
on Smart Card Removal was set to No . |
GPC-6879 | Fixed an issue on Windows endpoints where
the GlobalProtect app displayed an unnecessary pop-up showing HTTP/1.1 200 OK response
upon successful SAML authentication. |
GPC-6820 | Fixed an issue on Windows endpoints where
the HIP Profile did not identify the patch management software in
the patch-management check. This prevented the firewall from applying
security policy to traffic when using patch management as a HIP
object. |
GPC-6779 | Fixed an issue where GlobalProtect prompted
end users to enter their one-time password (OTP) but required users
to manually click into the text-input field before they could enter
their password. |
GPC-6735 | Fixed an issue on Linux endpoints where
the GlobalProtect app indicated it was connected to an internal
gateway when authentication to the portal had failed due to an expired
authentication cookie. |
GPC-6692 | Fixed an issue in the HIP profile where
GlobalProtect did not identify and display the Last Full
Scan Time when System Center Endpoint Protection ran
on macOS endpoints. |
GPC-6665 | Fixed an issue on Windows and macOS endpoints
where the GlobalProtect multi-factor authentication notification
did not clear automatically after an end user authenticated. |
GPC-6526
| Fixed an issue on Windows and macOS endpoints
where an end user could not highlight and copy Troubleshooting information
from the GlobalProtect app. |
GPC-6483 | Fixed an issue on Windows 10 endpoints where
the GlobalProtect app did not send traffic through the VPN tunnel
after resuming from sleep. When this occurred, the GlobalProtect
app also displayed the status as connected while the virtual Ethernet
adapter had no configuration. |
GPC-6469 | Fixed an issue using the Pre-logon
then On-demand connect method and a Pre-logon tunnel rename
timeout of 0 (which specifies that the GlobalProtect app should disconnect
the tunnel immediately following login) where the GlobalProtect
app left the pre-logon tunnel up after an end user logged in to
the Windows endpoint. |
GPC-6354 | Fixed an issue on Linux endpoints, were
using the show --e <tab> command autocompleted
to show --errors instead of the supported command show --error . |
GPC-6285 | Fixed an issue on Windows endpoints where
the GlobalProtect status panel displayed persistently when users
established a GlobalProtect connection for the first time. This
issue occurred even when users clicked outside the status panel
to attempt to close it manually. With this fix, you can now suppress
the status panel by setting the Display Status Panel
at Startup (Windows Only) option to No in
the portal agent configuration (Network GlobalProtect Portals <portal-config> Agent <agent-config> App Yes , the status
panel displays automatically when users establish a GlobalProtect
connection for the first time. Users can then click outside the
status panel to close it manually. |
GPC-6258 | Fixed an issue on Windows endpoints where
the GlobalProtect window remained active after an end user cancels
the connection to an invalid GlobalProtect portal. |
GPC-6066 | Fixed an issue where if you had an explicit
exclude route configured, the GlobalProtect app did not enforce
split tunneling and instead forwarded all traffic to the firewall. |
GPC-6046 | Fixed an issue where the GlobalProtect app
experienced connection delays when using a client certificate that
contained an OCSP URL for revocation checks. With this fix, the
GlobalProtect app now applies the value you configure for the Portal Timeout as
an Online Certificate Status Protocol (OCSP) timeout to manage delays. |
GPC-5959 | Fixed an issue on Windows endpoints where
using the tab key skipped the Password field
and instead made the Sign In button the active
selection on the GlobalProtect login screen. |
Most Popular
Recommended For You
Recommended Videos
Recommended videos not found.
