Usage guide: Zscaler (VPN) assisted troubleshooting
Last updated
Was this helpful?
Last updated
Was this helpful?
This page outlines various ways to use the pack, including use case examples.
Administrators can refer to the Configuration guide to set up and customize the installed content.
The Zscaler (VPN) assisted troubleshooting library pack enables IT teams to:
Gather information about the Zscaler client status.
Remediate common issues by resetting the Zscaler connection or prompting user reauthentication.
Update the ITSM ticket with the progress and results of the troubleshooting process.
Jump to Use cases on this page to see relevant scenario applications.
Use the library pack content for the following purposes.
This library pack focuses on the Zscaler (VPN) assisted troubleshooting workflow. It gathers information on the local Zscaler status and provides remediation where required.
An ITSM ticket is updated at each step of this process.
This workflow is intended to be launched on a specific device during a call with an employee or in response to an issue raised by an employee experiencing Zscaler stability issues. This can be achieved using device view (as shown below) or from Amplify. The workflow uses the Incident number parameter to track progress.
An ITSM ticket should be raised before launching the workflow, as it will be updated during its operation.
Workflow parameter: This workflow has one parameter, Incident number. This ITSM ticket reference will be used throughout the workflow as information is added. It should be entered manually when the workflow is executed.
The Zscaler (VPN) Assisted Troubleshooting workflow follows a sequence of steps to diagnose and resolve issues efficiently.
The workflow begins by verifying whether Zscaler is running on the endpoint using the "Get Zscaler Status" remote action. Then, it retrieves the ITSM ticket sys_id based on the provided incident ticket number.
The workflow determines the next steps based on the Zscaler status. If Zscaler is not running, the ITSM ticket is updated, and the workflow concludes. If Zscaler is running, the workflow assesses the status of private and public access services.
The workflow evaluates various Zscaler service conditions, including authentication errors, captive mode states, firewall block errors, and captive portal fail-open states.
If the detected errors require user reauthentication, the workflow notifies the user via Microsoft Teams and prompts them to reauthenticate.
If a firewall block or captive down error is detected, the workflow updates the ITSM incident with relevant details.
If a captive portal failure or other general errors are identified, the workflow attempts to restart the VPN for Windows devices. The user is informed via Microsoft Teams before the restart, and the ITSM ticket is updated accordingly.
The process involves disabling and re-enabling the Zscaler adapter, with a cautionary note that VPN traffic will be disrupted while the adapter is disabled. Only the ITSM ticket is updated for macOS devices, and no automatic remediation is performed.
RELATED TOPICS
