Netskope Help

Netskope Client Deployment Options

There are a number of different deployment options.

  • Email Invite: The Client (or the mobile profile on iOS) can be installed via the email invitation sent from the Netskope admin console.

  • JAMF: The Client can be installed on user devices using JAMF scripts and JAMF policies.

  • Microsoft Endpoint Configuration Manager: The Client can be installed on devices using SCCM without any user intervention.

  • VMWare Workspace One: The Client can be installed using AirWatch on Active Directory (AD) connected macOS devices.

  • Microsoft Group Policy Object (GPO): The Client can be installed for Microsoft GPO using Directory Importer to fetch user information from AD.

  • Microsoft Intune: The Client can be installed on devices using Intune with Directory Importer or SCIM integration.

  • Deploy Netskope Client via IdP: The Client can be installed on devices using a SAML 2.0 supported IdP service.

Note

Deploying to Always On, Always Connected (AOAC) devices.

Netskope client disconnects tunnel when the AOAC device display is off and resumes connection when the AOAC device display switches on. This feature can be controlled by the m_enableAOACSupport feature flag . By default, the m_enableAOACSupport feature flag is set to disable/false.

  • If enabled (set to true) then the Netskope client will not disconnect the tunnel when the AOAC device display is switched off.

  • If disabled (set to false) then Netskope client will disconnect the tunnel when the AOAC device display is switched off and reconnect when the display is switched on..

Typical Deployment Workflow

The following flowchart illustrates a typical workflow of Netskope Client deployment.

deployment-workflow.jpg