Currently, the PMPC client collects data every 12 hours, which effectively results in only one meaningful check-in per day for end users. In many cases, the client scans before Intune has completed deploying updates from the previous night.
As a result, update compliance reporting in PMPC is often delayed or inaccurate, and it can take 1–2 days before the compliance status of a specific update is correctly reflected.
At the moment, this data is often more accurate and up to date in Intune, as devices typically sync more frequently than the PMPC client collects and reports its data.
This could be improved by allowing administrators to either:
Configure a custom data collection interval, or
Reduce the default interval so the client checks in at least 2–3 times per day
More frequent or flexible check-ins would provide more timely and accurate compliance data, especially in environments where updates are deployed overnight via Intune.
To clarify a bit: as Anandi said, we probably won't globally reduce the interval or let customers set one. However, we recognize that not all inventory items are created equal. For example, there's not a lot of value in real-time monitoring of the CPU make and model; it just doesn't change that often. However, for some inventory items such as update installation state the global interval is too large.
The solution here will likely be to identify those kinds of high-value inventory items and find ways of making them more responsive to changes on the local system beyond the global interval.
We are not planning to change the frequency of data collection but have noted this request.