How does PMP know to not create another update of the same package?
I am in a situation where we only update Chrome sporadically, so we don't want auto update on in Chrome or patching. I was wondering if I am able to take a previously created PMP update, rename it, and use that to update our computers, so that way when a new Chrome update comes out, the scoped groups won't automatically apply to the new one. Effectively "turning off" auto update for PMP.
Hello,
While doing it that way isn't quite possible, an easy way to do this would be to uncheck chrome in the publisher. This would then turn off the process for adding new updates to configuration manager, or superseding old ones.
Thanks for the explanation, I've been trying to search for automatic PMP disabling feature and still don't know it doesn't exist.
Not sure if this helps, but this year we have added a new feature, which will allow you to Pause Product Updates (https://patchmypc.com/custom-options-available-for-third-party-updates-and-applications#pause-product-updates).