# Data Enricher (classic)

## Overview <a href="#dataenricher-classic-overview" id="dataenricher-classic-overview"></a>

The Data Enricher is a software component that complements the information about [users](/platform/references/references-classic/glossary-classic/user-classic.md) and [destinations](/platform/references/references-classic/glossary-classic/destination-classic.md) that Collectors send to the Nexthink Cloud.

<figure><img src="/files/TkVK479OH4NiaZQfMe7m" alt=""><figcaption></figcaption></figure>

[Install the Data Enricher on a Windows Server](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/api-and-integrations-classic/data-enricher-classic/installing-data-enricher-classic.md) that is connected to the Active Directory and DNS servers within your corporate intranet.

## Information retrieved <a href="#dataenricher-classic-informationretrieved" id="dataenricher-classic-informationretrieved"></a>

The Data Enricher gets the following information from your servers:

* User information from Active Directory:
  * Distinguished Name
  * Name
  * Full name
  * Department
  * Job title
  * Location
  * Locality name
  * Country code
  * Organizational unit name
* Destination information from reverse DNS lookup:
  * Fully Qualified Domain Name

These data are similar to the data retrieved by Engine in an on-premises setup. The user fields Location, Locality name, Country code, and Organizational unit name are however available on Nexthink Experience only.

## Estimated processing time <a href="#dataenricher-classic-estimatedprocessingtime" id="dataenricher-classic-estimatedprocessingtime"></a>

For an available network bandwidth of 25 Mbps, the following times have been measured for a partial update, with the Data Enricher running on a Windows Server 2016 in an Azure VM (Standard\_F4s - 4 CPU cores, 8 GB memory).

Measured time for retrieving user information from AD:

| Number of users | Duration     |
| --------------- | ------------ |
| 500 k           | < 7 min      |
| 250 k           | < 3 min 30 s |
| 100 k           | < 1 min 30 s |
| 50 k            | < 40 s       |
| 20 k            | < 20 s       |
| 10 k            | < 10 s       |
| 1               | < 5 s        |

Measured time for retrieving the FQDN of destinations from the DNS server:

| Number of destinations | Duration |
| ---------------------- | -------- |
| 500 k                  | < 20 min |
| 250 k                  | < 10 min |
| 100 k                  | < 4 min  |
| 50 k                   | < 2 min  |
| 20 k                   | < 1 min  |
| 10 k                   | < 30 s   |
| 1                      | < 5 s    |


---

# Agent Instructions: 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:

```
GET https://docs.nexthink.com/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/api-and-integrations-classic/data-enricher-classic.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.