macOS Scan Apps completed but app version inventory stays staleSolved

Participant
Discussion
5 days ago Nov 17, 2026

I’m trying to track a macOS app rollout using Hexnode’s application inventory, but the reported version is not matching what is installed on the Mac.

The app is Tailscale. On the device, the standalone build shows version 1.102.3, but Hexnode still shows older versions such as 1.98.10 in both the device inventory and the API response. I ran Scan Apps and Scan Device multiple times from the portal. The actions show Completed in Action History, but the app version and the last scanned/last reported timestamps do not update.

This is affecting rollout tracking because dynamic device groups are based on the app version shown in Hexnode. If the device has already updated but the inventory remains stale, I can’t tell whether the update actually failed or whether Hexnode just has cached/old inventory data.

There are also two Tailscale entries involved: the standalone build and the App Store/VPP build. What is the correct way to get accurate app version reporting and target only Macs running the outdated standalone app?

Replies (3)

Marked SolutionPending Review
Hexnode Expert
5 days ago Nov 17, 2026
Marked SolutionPending Review

Hi @elena ,

For macOS devices, it is important to distinguish between the remote command status and the application inventory data shown in the portal.

When Scan Apps or Scan Device is triggered, Hexnode UEM sends the scan command to the Mac through Apple’s MDM channel. The action can show Completed once the device acknowledges the command. However, the application version shown in the portal depends on the inventory data that is collected and uploaded from the Mac. If that inventory payload has not been refreshed or ingested yet, the device record, dynamic groups, and API can continue to show the previous app version for some time.

For the Tailscale case, also verify which bundle identifier your group is evaluating:

  • Standalone Tailscale build: io.tailscale.ipn.macsys
  • App Store/VPP Tailscale build: com.tailscale.ipn.macos

If the Mac was updated using the standalone package, but the dynamic group checks the VPP/App Store bundle identifier, the device may not match the expected group even though the standalone app is updated.

For targeting outdated standalone builds, create or update the dynamic device group with criteria similar to:

  • Application Identifier equals io.tailscale.ipn.macsys
  • Application Version does not equal 1.102.3

Once the inventory reflects the updated version, run Sync Now on the dynamic group if you need the group membership refreshed immediately instead of waiting for the periodic sync.

Regards,
Isabel Lora
Hexnode UEM

Marked SolutionPending Review
Participant
4 days ago Nov 17, 2026
Marked SolutionPending Review

That makes sense for the bundle ID part, but in my case the device card itself was still showing the old version. Group sync would only refresh membership, not fix the stale Applications inventory. Is there any way to force the Mac to resend its local app inventory without touching the endpoint?

Marked SolutionPending Review
Hexnode Expert
4 days ago Nov 17, 2026
Marked SolutionPending Review

If the inventory on the device card itself is stale, group criteria changes will not correct that record. The device inventory needs to update first.

As a practical workaround, the local Hexnode UEM agent on the Mac can be restarted or prompted to sync so that it re-collects the application list and uploads the latest inventory. On macOS, this can be done locally or through a script command if script execution is available in your environment, for example by restarting the Hexnode agent service.

After the app inventory on the device page shows the correct version, the dynamic group can be synced again to update membership.

For rollout management, the recommended workflow is:

  1. Confirm whether the deployment uses the standalone package or the VPP/App Store app.
  2. Use the matching bundle identifier in the dynamic group.
  3. For standalone apps, upload the updated PKG/DMG under Apps tab and deploy it through a Required Apps policy or Actions > Applications > Install Application.
  4. For VPP apps, use Actions > Applications > Install Application and select the VPP app to send an explicit install/update command through Apple’s MDM framework.
  5. Use the app inventory after it refreshes as the completion metric.

Regards,
Isabel Lora
Hexnode UEM

Save