> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/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/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/installing-collector-on-windows/obtaining-collector.md).

# Obtaining Collector

## Downloading Collector

Nexthink Collector is available directly in the Nexthink platform. Download the Windows Collector ZIP file from the [Collector management](/user-guide/administration/system-configuration/collector-management.md) dashboard under **Administration > Collector management > Downloads**.

## Contents of the Windows Collector ZIP file

The `collector-<version>.zip` file contains the following folders and files:

```csharp
collector-<version>.zip
├── arm64/
│   └── signed/
│       └── NEXThink_Collector.msi
├── Installer/
│   └── Collector/
│       ├── Nexthink_Collector_Installer.exe
│       └── Nexthink_Collector_Installer_Silent.exe
├── x64/
│   └── signed/
│       └── NEXThink_Collector.msi
├── sha256s.txt
└── versions.txt
```

The ZIP file contains the following installer files:

* **Installer**: Contains the Nexthink Collector Installer, an executable that configures installation parameters through a graphical interface:
  * `Installer\Collector\Nexthink_Collector_Installer.exe`: The main installer.
  * `Installer\Collector\Nexthink_Collector_Installer_Silent.exe`: A silent version of the same installer.
* **arm64** and **x64**: Contain the Windows Installer (MSI) for Nexthink Collector, which requires a separate MST file for configuration:
  * `NEXThink_Collector.msi`: Available in separate versions for ARM64 and x64 CPU architectures.

## Selecting the installer file

Select the installer file type based on your deployment method:

| Deployment method                                                  |               Nexthink Collector Installer              |                 Windows installer (MSI)                 |
| ------------------------------------------------------------------ | :-----------------------------------------------------: | :-----------------------------------------------------: |
| <p>Microsoft Configuration Manager</p><p>(SCCM/MECM/ConfigMgr)</p> | <i class="fa-check" style="color:$success;">:check:</i> |      <i class="fa-x" style="color:$danger;">:x:</i>     |
| <p>Active Directory Group Policy</p><p>(GPO)</p>                   |      <i class="fa-x" style="color:$danger;">:x:</i>     | <i class="fa-check" style="color:$success;">:check:</i> |
| <p>Unified Endpoint Management</p><p>(Microsoft Intune)</p>        | <i class="fa-check" style="color:$success;">:check:</i> | <i class="fa-check" style="color:$success;">:check:</i> |

{% hint style="warning" %}
If your devices run on ARM64 CPUs, you must use the Windows Installer (MSI). The Nexthink Collector Installer supports x64 CPU architectures only.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.