Monitoring and Automatic Restart of Netskope Client Services monitors the primary Netskope Client service (stAgentSvc) on supported Windows versions. If the service stops unexpectedly, the monitor service automatically restarts it. This reduces manual recovery steps and helps restore normal Client operation quickly.
The monitor service recovers a stopped service. It does not replace troubleshooting for connectivity, UI, upgrade, or operating-system issues.
Supported OS and Client Versions
-
Supported OS: Windows devices with Netskope Client installed
-
Minimum Client version: 137.0.1 or later
Automatic Restart Services Workflow
Once Netskope enables the feature in your tenant:
-
The monitor service starts 60 seconds after the endpoint starts.
-
The monitor service checks the Client service every 60 seconds.
-
If the service is running, the monitor takes no action.
-
If the service stops and no Client upgrade is in progress, the monitor restarts the service.
-
After the service resumes, normal monitoring continues.
Because the monitor service checks every 60 seconds, it can take up to about a minute to detect a stopped service before it starts the restart.
When automatic recovery occurs, users may notice a brief interruption while the Netskope Client service restarts. Depending on timing and endpoint conditions, the user experience may include:
-
A temporary loss of client connectivity.
-
A brief change in tray icon or Client status.
-
Automatic restoration of normal behavior after the service comes back up.
Recovery timing depends on when the Client detects the stopped state and how quickly the endpoint can restart the service.
Upgrade Behavior
The monitor works alongside Client upgrades. During upgrade activity, the monitor suppresses restart attempts to avoid installation conflicts. After the upgrade finishes, the monitor checks that the Client service is running and resumes normal monitoring. A stopped or restarting service during an upgrade does not always indicate a failure.