Changes to Default Behavior in GlobalProtect App 6.0
Focus
Focus
GlobalProtect

Changes to Default Behavior in GlobalProtect App 6.0

Table of Contents

Changes to Default Behavior in GlobalProtect App 6.0

Changes to default behavior in GlobalProtect app 6.0.
The following topic describes changes to default behavior in GlobalProtect app 6.0:

Changes to Default Behavior in GlobalProtect App 6.0.10

There are no changes in default behavior in GlobalProtect app version 6.0.10.

Changes to Default Behavior in GlobalProtect App 6.0.8

There are no changes in default behavior in GlobalProtect app version 6.0.8.

Changes to Default Behavior in GlobalProtect App 6.0.7

There are no changes in default behavior in GlobalProtect app version 6.0.7.

Changes to Default Behavior in GlobalProtect App 6.0.6

There are no changes in default behavior in GlobalProtect app version 6.0.6.

Changes to Default Behavior in GlobalProtect App 6.0.5

Beginning with GlobalProtect app 6.0.5, the first time users launch the GlobalProtect app for Android, they will be prompted to read and acknowledge a disclosure about the information that may be collected by the app.

Changes to Default Behavior in GlobalProtect App 6.0.4

ADEM agent installer has been bundled with GlobalProtect installer since GlobalProtect version 5.2.6. ADEM installer bundled with GlobalProtect version 6.0.4 has been updated and contains the new ADEM Self-Serve feature due to which there is a notable increase in the size of the GlobalProtect installer.

Changes to Default Behavior in GlobalProtect App 6.0.3

There are no changes to default behavior in GlobalProtect app 6.0.3.

Changes to Default Behavior in GlobalProtect App 6.0.2

There are no changes to default behavior in GlobalProtect app 6.0.2.

Changes to Default Behavior in GlobalProtect App 6.0.1

There are no changes to default behavior in GlobalProtect app 6.0.1.

Changes to Default Behavior in GlobalProtect App 6.0.0

(Windows only) Starting with GlobalProtect app 6.0, the GlobalProtect virtual adapter name on Windows endpoint has been changed from PANGP Virtual Ethernet Adapter to PANGP Virtual Ethernet Adapter Secure. The addition of the keyword secure ensures that Microsoft delivery optimization and peer caching can identify that a device is connected to a VPN. This change ensures that delivery optimization and peer caching work properly for a large number of Windows updates, upgrades, and application downloads.