New DEX certifications launch at Experience '26. Get certified and learn from experts in your field.
Register now
Ctrlk
LearnDocumentationSupportCommunity
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Installing Collector on macOS

This page describes the Collector installation and deployment process for macOS devices. The process covers three paths: manual installation for small-scale or unmanaged environments, and automated deployment using Jamf or Microsoft Intune.

Refer to the Installing Collector to identify the deployment path applicable to your infrastructure before starting.

Nexthink distributes Collector for macOS as a disk image (DMG) file. Collector runs in user mode and does not require a kernel extension; this avoids the need to reboot devices after updates or uninstallation.

Before you begin

Ensure you have the following before starting:

  • One or more macOS devices on which to install Collector.

  • The URL of your Nexthink instance, including data in the path. Refer to [Connectivity requirements] for more information.

    • Example: <instance>.data.<region>.nexthink.cloud

  • The customer key from the Customer Key.txt file received in your welcome email from Nexthink.

  • Administrator credentials in your Nexthink instance.

  • The Nexthink Collector installation package: Nexthink_Collector_<version>.dmg. Download it from the Collector management dashboard under Administration > Collector management > Downloads. Contents of the DMG file:

    • A predefined installation package for graphical wizard installation.

    • The csi.app application for command-line installation.

    • A reporter shell application for troubleshooting.

    • An uninstaller application.

  • Full Disk Access enabled for the Collector components, configured as part of the installation process.

  • TCP port for the connection; default: 443.

  • Optional: A third-party automated deployment tool. This documentation covers Jamf and Microsoft Intune.

Choose your installation path

Use the following guidance to select the correct path:

  • Manual installation: For a small pilot or unmanaged macOS devices; for example, when you are running a proof of value, managing only a few devices, or not using a UEM solution for these devices.

  • Jamf deployment: When your macOS devices are already managed in Jamf and you want Jamf to push both permissions and package deployment.

  • Intune deployment: When your macOS devices are already enrolled in Microsoft Intune and you want Intune to push policies and run the Collector install script.

You only need one enterprise deployment tool: either Jamf or Intune.

Deployment steps

Continue with the relevant page for your chosen path:

Last updated

Was this helpful?