> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/installing-collector-on-macos.md).

# Installing Collector on macOS

The following sections explain the Collector installation and deployment methods in detail.

See the [Installing Collector](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector.md) documentation to learn how to decide on the installation and deployment method applicable to your infrastructure.

## Before you begin <a href="#installingcollectoronmacos-prerequisites" id="installingcollectoronmacos-prerequisites"></a>

Nexthink distributes Collector for macOS as a disk image DMG file with the following content:

* A predefined installation package file for installing Collector from a graphical user interface.
* The `csi.app` application for installing Collector from the command line interface.
* A reporter shell application that gathers system information for troubleshooting purposes.
* An uninstaller application to remove Collector when it is no longer needed.

After the installation, as a sanity check, optionally [verify the status of the TCP connection between Collector and the Nexthink cloud platform](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/managing-collector-agents/querying-the-collector-tcp-connection-status.md).

Collector runs in user mode and does not ask the user for permissions to install any kernel extension. Running in user mode avoids having to reboot the devices after updates or uninstallation.

### Prerequisites <a href="#installingcollectoronmacos-prerequisites" id="installingcollectoronmacos-prerequisites"></a>

Ensure you have the following before the installation:

* The Nexthink Collector `Nexthink_Collector_<version>.dmg` intallation package file.
* The customer key in the `Customer Key.txt` file, which you receive in your welcome email from Nexthink.
* Access to the full storage device (Full Disk Access enabled).
* URL of your Nexthink instance, including `data` in the path:\
  `<instance>.data.<region>.nexthink.cloud`\
  For more information about the URL, see the [Connectivity requirements](/platform/configuring_nexthink/before-you-begin/technical-requirements/connectivity-requirements.md).
* TCP port number for the connection; default: 443.
* Optionally, a third-party automated deployment tool. This documentation covers Jamf and Intune.
* Download the macOS Collector DMG file directly from the product on the [Collector management](/platform/user-guide/administration/system-configuration/collector-management.md) dashboard under **Administration > Collector management > Downloads**.

### Installation package file

To obtain the predefined installation package file:

{% stepper %}
{% step %}
Click the downloaded file `Nexthink_Collector-<version>.dmg` file.
{% endstep %}

{% step %}
Extract the `Nexthink_Collector-<version>.pkg` package.
{% endstep %}
{% endstepper %}

## Installation procedure overview <a href="#installingcollectoronwindows-prerequisites" id="installingcollectoronwindows-prerequisites"></a>

On a high level, the procedure includes the following steps:

```mermaid
%%{ init : { "theme" : "default", "flowchart" : { "curve" : "linear" }}}%%

flowchart LR
 n2(Obtain<br>Collector)
  --> n3(Configure<br>permissions)
  --> n4{Choose installation<br>path}
  --> n5(Install manually) -. When applicable .-> n6(Deploy in Jamf)
  n4 --> n7(Deploy in Intune)
```

## Choosing the installation path

Use one of the following paths to deploy Collector:

* **Manual installation** for a small pilot or unmanaged macOS devices when:
  * You are running a proof of value
  * You manage only a few macOS devices
  * You do not use a UEM solution for these devices
* **Jamf deployment** if your macOS devices are managed in Jamf and when:
  * Your macOS devices are already managed in Jamf
  * You want Jamf to push both permissions and package deployment
* **Intune deployment** if your macOS devices are managed in Intune and when:
  * Your macOS devices are already enrolled in Intune
  * You want Intune to push policies and run the Collector install script

{% hint style="info" %}
You only need one enterprise deployment tool: Either Jamf or Intune.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nexthink.com/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/installing-collector-on-macos.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
