> 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.md). # Installing Collector Install an endpoint agent on every device you want to connect to the Nexthink platform. To learn what each agent collects and how it works, see the [Understanding Collector](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/collector-overview.md) documentation. Work through the following decisions in order. Together, they determine the right agent, installation method, and guide for your environment. {% stepper %} {% step %} ### Choose your deployment scenario You are choosing between two scenarios: * **Initial setup** — you are configuring and installing endpoint agents for the first time. Continue with the decisions below. * **Updating an existing setup** — you are modifying an existing installation. Follow the same guide and method you used for the initial setup, for example a manual reinstallation on Windows or a Jamf redeployment on macOS. ```mermaid %%{ init : { "theme" : "default", "flowchart" : { "curve" : "linear" }}}%% flowchart LR d{"Deployment
scenario?"} d -->|Initial setup| n["▶️ Continue with
the decisions below"] d -->|Updating an existing setup| u["🔁 Re-run your
original method"] classDef decision fill:#0B1441,stroke:#0B1441,color:#FFFFFF; classDef neutral fill:#EEF3F7,stroke:#1046A8,color:#221F20; class d decision; class n,u neutral; ``` {% endstep %} {% step %} ### Identify your infrastructure scale You are choosing between two scales, which determine how you install Collector: * **Small-scale setup** — a few devices, proof-of-value scenarios, or unmanaged devices. Install Collector manually. * **Medium to large-scale setup** — managed environments with hundreds or thousands of devices. Deploy Collector automatically with tools such as Microsoft Intune or Jamf. ```mermaid %%{ init : { "theme" : "default", "flowchart" : { "curve" : "linear" }}}%% flowchart LR s{"Infrastructure
scale?"} s -->|"A few devices, PoV,
or unmanaged"| m["🔧 Manual
installation"] s -->|"Managed, hundreds or
thousands of devices"| a["⚙️ Automated
deployment"] classDef decision fill:#0B1441,stroke:#0B1441,color:#FFFFFF; classDef manual fill:#00B1A9,stroke:#00B1A9,color:#FFFFFF; classDef automated fill:#1046A8,stroke:#0B1441,color:#FFFFFF; class s decision; class m manual; class a automated; ``` {% endstep %} {% step %} ### Identify your infrastructure type You are choosing the environment your devices connect to, which determines the agent you install: * **Non-virtual** — all devices connect to a non-virtual environment. Install **Nexthink Collector** on the devices. * **Virtual (VDI)** — devices connect to virtual machines. Every device that connects to a VDI environment needs the VDI Client Extension: * **Company-managed devices** receive it automatically as a component of Nexthink Collector. Install **Nexthink Collector** on the devices and VMs. * **Personal or self-managed devices running Microsoft Windows** install it as a standalone, lightweight agent. See the [Installing Nexthink VDI Client Extension](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-vdi-environment/installing-the-nexthink-vdi-client-extension.md) documentation. * **Hybrid** — some devices connect to a non-virtual environment and others to virtual machines. Install **Nexthink Collector** on the devices and VMs. ```mermaid %%{ init : { "theme" : "default", "flowchart" : { "curve" : "linear" }}}%% flowchart TD t{"Infrastructure
type?"} t -->|Non-virtual| c1["📦 Nexthink Collector
on devices"] t -->|"Virtual,
company-managed"| c2["📦 Nexthink Collector
on devices and VMs"] t -->|"Virtual, personal
or self-managed
(Windows only)"| e["🧩 Standalone
VDI Client Extension"] t -->|Hybrid| c3["📦 Nexthink Collector
on devices and VMs"] classDef decision fill:#0B1441,stroke:#0B1441,color:#FFFFFF; classDef collector fill:#3194F7,stroke:#1046A8,color:#FFFFFF; classDef ext fill:#00B1A9,stroke:#00B1A9,color:#FFFFFF; class t decision; class c1,c2,c3 collector; class e ext; ``` {% endstep %} {% step %} ### Choose your operating system You are choosing the operating system running on your devices. Open the guide that matches it: * **Windows** — see the [Installing Collector on Windows](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/installing-collector-on-windows.md) documentation. * **macOS** — see the [Installing Collector on macOS](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/installing-collector-on-macos.md) documentation. {% hint style="info" %} If your infrastructure includes both Windows and macOS devices, follow each guide that applies. {% endhint %} ```mermaid %%{ init : { "theme" : "default", "flowchart" : { "curve" : "linear" }}}%% flowchart LR o{"Operating
system?"} o -->|Windows| w["💻 Installing Collector
on Windows"] o -->|macOS| m["💻 Installing Collector
on macOS"] classDef decision fill:#0B1441,stroke:#0B1441,color:#FFFFFF; classDef guide fill:#3194F7,stroke:#1046A8,color:#FFFFFF; class o decision; class w,m guide; ``` {% endstep %} {% endstepper %} ## Deployment reference table Use the table below for a quick reference to find the applicable documentation for your deployment use case. | Your environment | Install | Read | | --------------------------------------- | ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Windows physical or non-virtual devices | Nexthink Collector | [Installing Collector on Windows](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/installing-collector-on-windows.md) | | macOS devices | Nexthink Collector | [Installing Collector on macOS](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/installing-collector-on-macos.md) | | VDI — company-managed devices | Nexthink Collector (the VDI Client Extension is bundled in, with no separate installation) | [Installing Collector on Windows](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/installing-collector-on-windows.md) | | VDI — personal or self-managed devices | VDI Client Extension (standalone lightweight agent) | [Installing Nexthink VDI Client Extension](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-vdi-environment/installing-the-nexthink-vdi-client-extension.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.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.