> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/configure-cortex-xdr/data-management/broker-vm/manage-broker-vm-data-collector-applets.md).

# Manage Broker VM data collector applets

Manage applets installed on Broker VM.

Learn more about managing your Broker VM data collector applets from the Broker VMs page.

After you activate a Broker VM data collector applet, you can make additional changes as needed to the specific applet configured on the Broker VM or cluster. Select **Settings** → **Configurations** → **Data Broker** → **Broker VMs** to view detailed information regarding your registered Broker VMs in either the **Brokers** or **Clusters** tab. To modify a configuration, left-click the Broker VM applet in the **APPS** column to display the data collector applet settings and view detailed information regarding your applet. For more information on configuring these specific applets, see [Broker VM data collector applets](/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/generic-on-premise-data-collectors/broker-vm-data-collector-applets.md).

{% hint style="info" %}

#### Note

For more information on the Broker VM applet connectivity status, see [Manage Broker VM](/cortex-xdr-5.x/configure-cortex-xdr/data-management/broker-vm/manage-broker-vm.md).
{% endhint %}

### Configuration options available for all Broker VM data collector applets

The following options are available to select for all data collector applets:

* **Configure**: Enables you to redefine the Broker VM data collector configurations.
* **Deactivate**: Disables the Broker VM data collector. Cortex XDR provides the ability to maintain the Broker VM applet configurations whenever an applet is deactivated. This ensures that whenever the applet is reactivated the saved configuration is restored. When the dialog box is displayed to confirm deactivating the Broker VM data collector applet, leave the Save applet configuration checkbox selected (default) to maintain the applet configuration; otherwise, if this checkbox is unmarked, the applet configuration is deleted.
* **Update**: Initiates a manual upgrade for the specific applet. This option is only visible in the applet hovering menu when a new version is available.

### Configuration options available to specific Broker VM data collector applets

The following additional options are only available to specific Broker VM data collector applets:

* Network Mapper:
  * Scan Now: Initiates a scan.
* Windows Event Collector:
  * Collection Configuration: Enables you to view or edit existing events or add new events to the collect.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/configure-cortex-xdr/data-management/broker-vm/manage-broker-vm-data-collector-applets.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.