End-of-Life (EoL)

GlobalProtect App 4.1.1 Addressed Issues

GlobalProtect app 4.1.1 addressed issues
The following table lists the issues that are addressed in GlobalProtect app 4.1.1.
Issue ID
Description
GPC-6154
Fixed an issue on Windows UWP endpoints where the GlobalProtect app intermittently failed to connect to the GlobalProtect gateway when the UWP plugin was set to Always On.
GPC-6150
Fixed an issue on Windows endpoints where, after end users logged in to Windows, the GlobalProtect app stopped running and Windows Error Reporting (WER) displayed the following error:
GlobalProtect client stopped working
.
GPC-6149
Fixed an issue on Windows 8 endpoints where the GlobalProtect login page displayed the password field above the username field after you enabled
Interactive Logon: Do not display last username
in the Windows Local Group Policy Editor (
Local Computer Policy
Computer Configuration
Windows Settings
Security Settings
Local Policy
Security Options
).
GPC-6121
Fixed an issue on MacOS endpoints where the GlobalProtect app couldn't detect processes that had more than 16 characters in their names.
GPC-6080
Fixed an issue where remote desktop connections over existing VPN tunnels disconnected after you configured the GlobalProtect portal to use a
Certificate Profile
for authenticating clients (
Network
GlobalProtect
Portals
<portal>
Authentication
) and set
Save User Credentials
to
Save Username Only
in the app (agent) configurations (
Network
GlobalProtect
Portals
<portal>
Agent
<agent>
Authentication
).
GPC-6079
Fixed an issue where the GlobalProtect app continuously tried to connect to external GlobalProtect gateways and displayed
connecting
or
still working
status even though the GlobalProtect portal configuration didn’t have external gateways defined (
Network
GlobalProtect
Portals
<portal>
Agent
<agent>
External
).
GPC-6076
Fixed an issue on Android endpoints enrolled with AirWatch where Host Information Profile (HIP) checks failed because the manifest file for the GlobalProtect app was missing the mobile_id value.
GPC-6068
Fixed an issue where HIP matching failed because HIP reports included the wrong characters for antivirus software that had Unicode names.
GPC-6049
Fixed an issue where, even though you configured
No direct access to local network
in the GlobalProtect gateway, the GlobalProtect app reverted to its local DNS to resolve domain names after the DNS servers that the gateway provided failed to resolve the names (
Network
GlobalProtect
Gateways
<gateway>
Agent
Client Settings
<client_settings_configuration>
Split Tunnel
Access Route
).
GPC-6040
Fixed an issue where end users who had special characters associated with XML markup (<, >, &, ', ") in their password couldn't connect to the GlobalProtect gateway after an upgrade to GlobalProtect app 4.1.0.
GPC-6037
Fixed an issue where the GlobalProtect app failed to automatically install VPN tunnel routes and the routes then required manual installation.
GPC-6036
Fixed an issue where the GlobalProtect app failed to authenticate to the GlobalProtect portal through the Proxy Login prompt when the endpoint browser used a proxy auto-config (PAC) file to automatically select a proxy server.
GPC-6010
Fixed an issue where the GlobalProtect app displayed an empty dialog instead of the portal detection message after the end user logged into a network through its captive portal and then followed the instructions to log off and reconnect through a pre-logon VPN tunnel.
GPC-6002
Fixed an issue on MacOS endpoints where the GlobalProtect app failed to automatically populate the username in the GlobalProtect gateway authentication prompt.
GPC-5986
Fixed an issue on Windows endpoints where end users could add, modify, or delete GlobalProtect portal addresses even after you set the
Allow User to Change Portal Address
option to
No
(
Network
GlobalProtect
Portals
<portal>
Agent
<agent>
App
).
GPC-5985
Fixed an issue where, after you installed a GlobalProtect app using the Windows Installer (Msiexec), a popup window displayed
Portal not found. Please re-enteror contact an administrator for help
, but the portal connection succeeded when you clicked
OK
to close the popup.
GPC-5952
Fixed an issue in GlobalProtect deployments configured for multi-factor authentication where end users couldn't activate the
Submit
button in the GlobalProtect Login page by pressing the Enter key on their keyboard.
GPC-5946
Fixed an issue where the GlobalProtect login prompt allowed only 24 characters for usernames and 21 characters for passwords. With this fix, you can enter up to 256 characters for usernames and passwords.
GPC-5935
Fixed an issue where, whenever Windows endpoints rebooted and end users logged in, the GlobalProtect app displayed a popup window that users had to click to close even after you configured the app not to
Show System Tray Notifications
or
Display GlobalProtect Icon
(
Network
GlobalProtect
Portals
<portal>
Agent
<agent>
App
).
GPC-5933
Fixed an issue on Linux endpoints where certificate imports failed when you ran the GlobalProtect CLI command in prompt mode:
user@linuxhost:~$
globalprotect
>>
import-certificate --location
<file-path>
GPC-5925
Fixed an issue where GlobalProtect endpoints failed to authenticate to the GlobalProtect gateway on the first connection attempt (subsequent attempts succeeded) after you configured cookie authentication for the GlobalProtect portal and gateway.
GPC-5922
Fixed an issue where Windows endpoints failed the HIP check after you upgraded Norton Internet Security to version 22.12.x.x.
GPC-5909
Fixed an issue where, if you configured the option to
Allow User to Disable GlobalProtect
and then specified a
Disable Timeout
value to restrict the amount of time for which users could disable the app (
Network
GlobalProtect
Portals
<portal>
Agent
<agent>
App
), the GlobalProtect app for macOS endpoints did not automatically enable after reaching the
Disable Timeout
value.
GPC-5879
Fixed an issue on T-Mobile LTE networks where endpoints running iOS 10.12 or a later iOS release couldn’t connect to GlobalProtect gateways that were configured with only IPv4 addresses because T-Mobile now assigns only IPv6 addresses to those endpoints.
GPC-5866
Fixed an issue on Windows endpoints where users couldn’t upgrade the GlobalProtect app using the Windows Installer (Msiexec) because the GlobalProtect setup file couldn’t overwrite existing GlobalProtect app software packages when the GlobalProtect service (PanGPS) was running.
GPC-5865
Fixed an issue on Windows endpoints where the GlobalProtect app incorrectly reported server certificate warnings for unknown errors. With this fix, the app displays the following message for unknown errors:
GlobalProtect has encounteredan internal error. Please contact your IT administrator
.
GPC-5629
Fixed an issue where GlobalProtect apps that you installed in a non-default location couldn’t connect to the GlobalProtect portal after you set
Enforce GlobalProtect Connection for Network Access
to
Yes
(
Network
GlobalProtect
Portals
<portal>
Agent
<agent>
App
).
GPC-5416
Fixed an issue where DNS suffixes were removed from Windows 10 endpoints due to an error in the read/rewrite function that directly modified the DNS suffix search list in the Windows registry key.
GPC-5286
Fixed an issue on Windows 10 endpoints where GlobalProtect apps with the
Connect Method
set to
User-logon (Always On)
didn't automatically connect to the GlobalProtect portal after network availability went from down to up (
Network
GlobalProtect
Portals
<portal>
Agent
<agent>
App
).

Recommended For You