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.
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.