> 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
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](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector.md) to identify the deployment path applicable to your infrastructure before starting.
{% hint style="info" %}
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.
{% endhint %}
## 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: `.data..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_.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
```mermaid
%%{ init : { "theme" : "default", "flowchart" : { "curve" : "linear" }}}%%
flowchart TD
A(["▶️ Start"]) --> B{"How are your macOS
devices managed?"}
B -->|Unmanaged or small-scale| C["🔧 Manual installation"]
B -->|Managed in Jamf| D["⚙️ Deploy in Jamf"]
B -->|Managed in Microsoft Intune| E["⚙️ Deploy in Intune"]
classDef start fill:#EEF3F7,stroke:#1046A8,color:#221F20;
classDef decision fill:#0B1441,stroke:#0B1441,color:#FFFFFF;
classDef manual fill:#00B1A9,stroke:#00B1A9,color:#FFFFFF;
classDef deployA fill:#3194F7,stroke:#1046A8,color:#FFFFFF;
classDef deployB fill:#1046A8,stroke:#0B1441,color:#FFFFFF;
class A start;
class B decision;
class C manual;
class D deployA;
class E deployB;
```
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.
{% hint style="info" %}
You only need one enterprise deployment tool: either Jamf or Intune.
{% endhint %}
## Deployment steps
Continue with the relevant page for your chosen path:
* [Installing Collector manually](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/installing-collector-on-macos/manual-installation-on-macos-tp.md)
* [Deploying Collector in Jamf](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/installing-collector-on-macos/jamf-deployment-tp.md)
* [Deploying Collector in Intune](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/installing-collector-on-macos/intune-deployment-tp.md)
* [Uninstalling Collector](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/installing-collector-on-macos/uninstalling-collector-mac-tp.md)
---
# 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=&goal=
```
`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.