GlobalProtect
User-Initiated Pre-Logon Connection
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.3
- 6.3
- 6.2
- 6.1
- 6.0
- 5.1
User-Initiated Pre-Logon Connection
Enable end users to initiate the GlobalProtect pre-logon connection manually on Windows
10 endpoints.
Where Can I Use This? | What Do I Need? |
---|---|
|
|
Enable end users to initiate the GlobalProtect Remote Access VPN with Pre-Logon connection manually on Windows 10
endpoints. User-initiated pre-logon requires that you Use Single
Sign-On in your portal configuration. In this deployment, users can
initiate the pre-logon connection only when their endpoint requires access to the
corporate network before login, such as when new employees connect to the network
remotely for the first time or when administrators must remotely connect and
troubleshoot issues on the endpoint. To initiate the pre-logon connection, users
must Start GlobalProtect Connection from the GlobalProtect
credential provider logon screen after the endpoint boots up.
If users are
unable to establish the pre-logon connection using this option,
the pre-logon connection status remains Disconnected.
When
users log out of their endpoint, the VPN tunnel is not renamed from
the user tunnel back to the pre-logon tunnel. Instead, the tunnel
disconnects.
Use the following steps to enable users
to initiate the pre-logon connection manually:
You can
configure this option only in the Windows Registry. This configuration
can be done either manually after GlobalProtect is installed or
pre-deployed as part of the Windows image that includes the GlobalProtect
software.
- Configure remote access VPN with pre-logon.Use one of the following options to configure remote access VPN with pre-logon:
- If your end user will be connecting to the GlobalProtect portal before using this feature (for example, an existing employee who has previously connected to GlobalProtect), you can configure remote access VPN with pre-logon in the portal configuration.To enable users to initiate the pre-logon connection manually, you must configure the following options in your portal configuration:
- Specify a portal IP address (NetworkGlobalProtectPortals<portal-config>General).
- Set the GlobalProtect Connect Method to Pre-logon (Always On) or Pre-logon then On-demand (NetworkGlobalProtectPortals<portal-config>Agent<agent-config>App).
- Set the Use Single Sign-On option to Yes to enable GlobalProtect to use Windows login credentials to automatically authenticate users upon Active Directory login (NetworkGlobalProtectPortals<portal-config>Agent<agent-config>App).
- If your end user will not be connecting to the GlobalProtect portal before using this feature (for example, a new employee who is connecting to the network remotely for the first time), you must pre-deploy the pre-logon settings in the Windows Registry:
- From your Windows endpoint, launch the Command Prompt.
- Enter regedit to open the Windows Registry.
- In the Windows Registry, go to: HKEY_LOCAL_MACHINE\SOFTWARE\Palo Alto Networks\GlobalProtect\PanSetup\.
- Specify a portal address:
- From the list of PanSetup options, right-click Portal and then select Modify... to update the portal address.
- Enter the portal address in the Value data field.
- Click OK to save your changes.
- Enable pre-logon:
- From the list of PanSetup options, right-click Prelogon and then select Modify....
- To enable pre-logon, set the Value data to 1.To disable pre-logon, set the Value data to 0.
- Click OK to save your changes.
- Enable single sign-on (SSO):When you enable single sign-on, GlobalProtect uses Windows login credentials to automatically authenticate users upon Active Directory login.
- Select EditNewString Value to add the option to use single sign-on.
- When prompted, set the Name to use-sso.
- Right-click Use-SSO and then select Modify... to update the single sign-on settings.
- To enable single sign-on, set the Value data to yesTo disable single sign-on, set the Value data to no.
- Click OK to save your changes.
- From the Windows Registry, enable the option to display the Start GlobalProtect Connection button on the GlobalProtect credential provider logon screen.
- From your Windows endpoint, launch the Command Prompt.
- Enter regedit to open the Windows Registry.
- In the Windows Registry, go to: HKEY_LOCAL_MACHINE\SOFTWARE\Palo Alto Networks\GlobalProtect\PanSetup\.
- Select EditNewString Value to add the button display option.
- When prompted, set the Name to ShowPrelogonButton.
- Right-click ShowPrelogonButton and then select Modify... to update the button display settings.
- To enable the GlobalProtect credential provider to display the Start GlobalProtect Connection button, set the Value data to yes.To disable the ShowPrelogonButton option, set the Value data to no. Alternatively, you can right-click ShowPrelogonButton to Delete the option.
- Click OK to save your changes.
- Verify that the GlobalProtect credential provider displays the Start GlobalProtect Connection button so users can initiate the pre-logon connection manually.Depending on which option you used to configure remote access VPN with pre-logon (step 1), use one of the following options to verify that the GlobalProtect credential provider displays the Start GlobalProtect Connection button:
- If you configured remote access VPN with pre-logon on your firewall, use the following steps to verify that the button is displayed:
- From you Windows endpoint, launch the GlobalProtect app.
- Connect to GlobalProtect to download the portal agent configuration that you configured instep 1.
- Reboot your Windows endpoint.
- When the GlobalProtect credential provider logon screen appears, ensure that the Start GlobalProtect Connection button is displayed and the pre-logon connection status is Disconnected.
- If you pre-deployed the pre-logon settings in the Windows Registry, use the following steps to verify that the button is displayed:
- Reboot your Windows endpoint.
- When the GlobalProtect credential provider logon screen appears, ensure that the Start GlobalProtect Connection button is displayed and the pre-logon connection status is Disconnected.