Support

Endpoint management solution

Use your Mobile Device Management (MDM) or Unified Endpoint Management (UEM) solution to configure and deploy Nexthink Mobile.

This documentation uses Microsoft Intune admin center as an example; however, you can perform the same configuration using any other solution as well.

Creating an installation token in Nexthink

To configure Nexthink Mobile in your MDM or UEM solution and on mobile devices, you must first create an installation token in your Nexthink instance by completing the following steps.

1

Select Administration > Collector management:

Accessing Collector management
2

Select the Mobile tab:

Accessing the Mobile tab
3

Select Generate installation token and fill in the following values:

  • Name: Add a meaningful name for the token.

  • Valid until: Define an expiration date for the token. The maximum token validity is one year, which is also the default value.

4

Select Generate installation token to generate a new token.

Copying the installation token

Select Copy token in the action menu to copy it to the clipboard:

Copying the installation token

Use this token while creating an app policy in Intune and when manually setting the connection on mobile devices.

Configuring and deploying Nexthink Mobile in Intune

Adding Nexthink Mobile

Perform the following steps to add Nexthink Mobile to Intune.

1

Select Apps > Android > Create.

2

For App type, select Managed Google Play app:

3

In Google Play, go to the Search Play Store dashboard.

4

Search for the keyword "Nexthink Mobile" and install the app from the search result.

Creating an app configuration policy

Create an app configuration policy and assign it to your Entra ID groups by following the steps below.

1

Go to Apps > Manage apps > Configuration.

2

Select Create > Managed devices:

3

On the Create app configuration policy dashboard, fill in the following fields:

  • Name: Add a meaningful name for your policy.

  • Platform: Select Android Enterprise.

  • Profile type: Select the profile that is applicable to your organization.

4

Select Targeted app and select the previously created app from the list and proceed to Settings:

5

Select +Add and enable the Post notification permission with the Auto grant state to allow the app to run in the background:

6

In Configurations settings format, select Use configuration designer from the dropdown and select the lower +Add button:

7

Select the following configuration keys, and set the pertaining value types and configuration values:

Configuration key
Value type
Configuratoin value

Data Upload Network

choice

Choose one of the following options:

  • Upload Always: Includes Wi-Fi and mobile data

  • Upload only when not roaming: Includes Wi-Fi and mobile data

  • Upload only over wifi: Wi-Fi only

Force Show Settings Screen

bool

Select the checkbox.

Nexthink Installation Token

string

The installation token you generated for your Nexthink tenant.

Nexthink Proxy URL

string

The URL of your Nexthink tenant, such as instance.data.eu.nexthink.cloud.

Primary user UPN

variable

Select User principal name (UPN) in the Configuration value dropdown list.

Unique Device Identifier

variable

Select Intune Device ID in the Configuration value dropdown list.

⚠️ This is needed to ensure correct functionality with the connector.

8

Select Add groups and add the groups to which you want to assign the policy, then select Create to finalize the app.

Installing Nexthink Mobile on client devices

After creating an app configuration policy, you can define which device groups install Nexthink Mobile automatically and which ones must install it manually:

  • Fully company-managed devices can automatically install Nexthink Mobile through the MDM or UEM solution.

  • Bring-your-own devices (BYOD) must have a work profile on them and install Nexthink Mobile manually from the app store.

First, select Nexthink Mobile by following the steps below.

1

Select the app from the list of Android apps:

Select app to set up for automatic and manual installation
2

Select Properties, then Assignments > Edit.

Proceed with Automatic installation or Manual installation based on the specific device types.

Automatic installation

Select + Add group under Required, and set the Update priority to High priority:

Automatic installation groups

Device groups in this category will install Nexthink Mobile automatically the next time Intune syncs with the devices.

Manual installation

Select + Add group under Available for enrolled devices:

Manual installation groups

At this point, Nexthink Mobile will be available in your organization's company portal, from where users can install it directly on their client mobile devices.

Launching Nexthink Mobile automatically

By default, after the installation, the mobile device user must open Nexthink Mobile manually for the first time. This only has to be done once; after that, the app will automatically launch following each device reboot.

However, depending on the device manufacturer, you might use an OEM plugin, configured in Intune, to launch it automatically on user devices after installation. The following sections explain such use cases.

Samsung Knox Service Plugin

Prerequisites

  • The Samsung Knox Service Plugin is added to your organization’s app collection.

  • The plugin is deployed and installed on the target Samsung mobile devices.

Plugin configuration

1

In Intune, go to Devices > Managed devices > Configuration.

2

Select Create profile, add the following values and select Create:

  • Platform: Android Enterprise

  • Profile type: Templates

  • Template name: OEMConfig

3

Add a meaningful name for the profile, then click Select an OEMConfig app and select the Knox Service Plugin app.

4

Select the Knox Service Plugin profile type and configure a Device-wide policy:

Knox plugin device-wide policies
5

Configure the following settings:

  • Enable device policy controls: Set to true.

  • Application management policies: Select Configure and configure the following policies:

    • Enable application management controls: Set to true.

    • Battery optimization allowlist: Add the Nexthink Mobile package name.

    • Package Name for Auto-Launch: Add the Nexthink Mobile package name.

    • Enable permission controls: Set to true.

6

You do not need to define Scope tags; proceed to Assignments, and select + Add groups to define which device groups will be part of the policy.

Zebra OEM Plugin

Prerequisites

  • The Zebra OEMConfig Powered by MX is added to your organization’s app collection.

  • The plugin is deployed and installed on the target Samsung mobile devices.

Plugin configuration

1

In Intune, go to Devices > Managed devices > Configuration.

2

Select Create profile, add the following values and select Create:

  • Platform: Android Enterprise

  • Profile type: Templates

  • Template name: OEMConfig

3

Add a meaningful name for the profile, then click Select an OEMConfig app and select the Zebra OEMConfig Powered by MX app.

4

Select the Zebra OEMConfig Powered by MX profile type and open the Package Configuration:

Adding a Package Configuration
5

Add a new setting:

Adding a new setting
6

Add the Nexthink Mobile package name com.nexthink.mobile.nexthinkapp.internal, and app signature:

Adding package name and certificate
7

Select Feature Variances and add a new feature variance:

Adding a feature variance
8

Add a new setting and select the Exempt from Battery Optimization variance type:

Adding Exemp from Battery Optimization feature variance
9

To make sure the Nexthink Notification is not shown on Zebra devices to users, add a new feature variance and select the Hide Notification variance type.

Adding Hide Notifications featrure variance
10

To enable auto-launch for Nexthink Mobile, add a new feature variance and select the Launch app after install/upgrade variance type.

Adding Launch app feature variance

Certificate signature

When asked for a certificate signature for Nexthink Mobile, provide the value in the expandable section below.

Certificate signature value
MIIFiDCCA3CgAwIBAgIUHVc+VqiZWjAe4xyihjANZosI9PMwDQYJKoZIhvcNAQEL
BQAwdDELMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFjAUBgNVBAcT
DU1vdW50YWluIFZpZXcxFDASBgNVBAoTC0dvb2dsZSBJbmMuMRAwDgYDVQQLEwdB
bmRyb2lkMRAwDgYDVQQDEwdBbmRyb2lkMCAXDTI1MDYyNzEyNTIyN1oYDzIwNTUw
NjI3MTI1MjI3WjB0MQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5pYTEW
MBQGA1UEBxMNTW91bnRhaW4gVmlldzEUMBIGA1UEChMLR29vZ2xlIEluYy4xEDAO
BgNVBAsTB0FuZHJvaWQxEDAOBgNVBAMTB0FuZHJvaWQwggIiMA0GCSqGSIb3DQEB
AQUAA4ICDwAwggIKAoICAQCJvu1DCMycVhWHj5ScvOs9uhILhXczWvxmQWTC/vTh
Miqi7zDhIzJH71gXitZJqaPjdqFwitjUwp8QKWbYdBWrJ4nQKTVx8UtKOP+dbhWY
GMy3ptztKU0l2zxiYhoDmEncHmiMJ8MPq9J0ufO/tg9PC5C5nG7kATqdal/7qmxc
ajrNc8J/JYpitcGdz5ek9MNoyn949lhIIeIUAJfXihbHWAw1zJzP0Zp3Sq7D+gf3
SQ6WkSmoVzJEOPdMVotkQUWA6pSDI2J8PiH1qap2ovYK8B+uKcq7XcELYwOMVpc3
zQVH9YX2md+/B+VBf7siXt1LHtV0bKB+ROtnzOD1zYbLfymD7TGkgf5dGQFUd75C
SL7vsNvonC847V1W/g1cql7elmFVmtjHa9g1WEDmRULh/mYfPaJRnJap9FqsZ8Ga
40n33AeFE6BAUHChPCMz2ypK+TnnKFEFSTvxUrkvDW1T2OsrqXKeNPds4G2t9gw5
qUrkcNwh2VZZT9BONJq6igoa26Tusd5jx7Tbb2RqCKO9J/ueDV4VVshd5/75FbOX
In52dB4dJbrKnq70YqgxLAuJ2f+2UVPEfMGytskPkysBXpXhV6Uzqq2vYz7oVR6X
rguuBplXplfxwCQdjoDIqS8MMFGMtJNNE5WxhNV73KZVUxrYKsQDRP1v7DckRGDh
TwIDAQABoxAwDjAMBgNVHRMEBTADAQH/MA0GCSqGSIb3DQEBCwUAA4ICAQAra2Rl
LkX3VdY1cqvR2IB5GtPSLad0kVapQe1+waFbyvLBeskJoAtCYBVduN9VZ4v147Ib
m7x9iqB+7ZrlHNesDeq0eT2rt1KA25zGLC0KILiUdKJC3Oecdqb6dTbnDrqgDY8A
Lyu1ef0nZFQsrHyfzwPTGJ0NE3U0oA12KQx7aQcUsyiKDRZFmLSUcjYbe+HSF1dp
krhZ++qFTQrhW09F/38ImSf5V+x92DlvgVZxwsQ4pu3hZNsS6+7ZZi66FQEquk3O
yGPFBZQgGce8/jdR/p0RAIbfYFiRZk+9NnpxBJU0Kpa6IrYkvoA7P84E/Bghf0T3
QMv/vuAEaIAFz9VG1vXN7zm5OD86XogPzL7NlElMibc+GRGk+Kz+Sh+ZooGEn+gI
ffghajHx1lDbXcUVBAh4cubVDJRm8ToY9UPcg0IfehfVJu6R0bijW0gw3cpqf1gc
+TVbceQv4Gwqkktks/sdDiUqRmDifiUbLvY5LosJmD4RQVkQsCeiEo7ZttJZFZKk
4FK6ogk7OCb+y6ckJpVRuuV+0hZmXWvFBtRJgn9D6VlAt6KkhKzjq6KcC/kVCDR5
VvrWfRkRZ0dIJJs4YJmnlC7bDBkK7Z/Nwxqrub/nVlsoyLUbAZiLMn5zRPkoFog8
L/qi3C675rhbXUeBuS9zFxiBlgM/c4Ya/72ieA==

Last updated

Was this helpful?