A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize request, please see:
What Criteria Does Patch My PC Use to Prioritize New Applications and Features?
View the Public Roadmap for Patch My PC
Patch My PC Publisher Release Notes
I am currently using custom log injection with Azure Log Analytics to monitor PMPC app updates and then do some actions. So I have a request (talked to Justin about this)Today you log this before you start processing a new app:
Updating Zoom Meetings 4.6.20033.0407 [PMPCAppID] with Zoom Meetings 4.6.20559.0413 [PMPCAppID]
If you could add one item to your logs looking something like this to separate from the before process AFTER it has successfully uploaded the new app and assigned it accordingly:
Updated Zoom Meetings 4.6.20033.0407 [AppID] with Zoom Meetings 4.6.20559.0413 [AppID]
Then I would know that the app is ready in Intune at that stage, now I really don’t know, and this is the only log entry that refers to both old and new app version.
This is available in today's preview build 188.8.131.52, and will be in the next production build.
The «Updating» line reference the PackageID found in our catalog. The «Updated» line reference the ID generated by Intune.
Is the App ID reference in the "Updated" one actually the Intune App ID as well? I see they have different values in your log here.
Looks good. Is it possible to move it even further down. After assignment, after Application sent to Intune Server. So that this entry is the last one on the list? To make sure no error happens after you log that the update is ready.