> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-cloud/insights-intune/technical-references/client-data-collection.md).

# Client Data Collection in Patch My PC Advanced/Patch Insights for Intune

*Applies to: Advanced/Patch Insights for Intune*

This article documents the data collected by the Patch My PC (PMPC) Advanced/Patch Insights for Intune client.

## Inventory Data

The inventory data collected/processed has been separated into the following categories:

* [Hardware](/patch-my-pc-cloud/insights-intune/technical-references/client-data-collection/hardware-inventory-data.md)
* [Software](/patch-my-pc-cloud/insights-intune/technical-references/client-data-collection/software-inventory-data.md)
* [User](/patch-my-pc-cloud/insights-intune/technical-references/client-data-collection/user-inventory-data.md)

These definitions are based on the objects that exist within the PMPC Client code base or WMI.

The current schedules for the collection of this data are shown below.

<table><thead><tr><th valign="top">Task Action ID</th><th valign="top">Task Action Name</th><th valign="top">Action Description</th><th valign="top">Intervals</th></tr></thead><tbody><tr><td valign="top">00000000-0000-0000-0000-000000000001</td><td valign="top">Policy task</td><td valign="top">Checks if there is new policy on the service side, and if yes, it downloads it.</td><td valign="top">60 Minutes</td></tr><tr><td valign="top">00000000-0000-0000-0000-000000000101</td><td valign="top">Hardware Inventory</td><td valign="top">Collects hardware specific information.</td><td valign="top">1440 Minutes (24 Hours)</td></tr><tr><td valign="top">00000000-0000-0000-0000-000000000103</td><td valign="top">Computed Inventory</td><td valign="top">Collects various hardware, software, and OS data.</td><td valign="top">1440 Minutes (24 Hours)</td></tr><tr><td valign="top">00000000-0000-0000-0000-000000000104</td><td valign="top">Update Inventory</td><td valign="top">Collects OS and PMPC software update compliance data.</td><td valign="top">720 Minutes (12 Hours)</td></tr><tr><td valign="top">00000000-0000-0000-0000-000000000200</td><td valign="top">Client Status Inventory</td><td valign="top">Collects data on Client and schedule task status.</td><td valign="top">60 Minutes</td></tr></tbody></table>


---

# 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.patchmypc.com/patch-my-pc-cloud/insights-intune/technical-references/client-data-collection.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.