Messages

Thanks for the reply - is there anyway to manually unexpire a third party update from the catalog and have it remain unexpired after future syncs? Or are there any immediate plans to switch the catalog to use supersedence for third party updates?

We've had a lot of success with the trial catalog in our proof of concept testing and have been considering Patch My PC for production use, but the current expiration workflow wouldn't work for us

Piggybacking on this thread since we are also evaluating Patch My PC via the Trial Catalog, and have similar testing and deployment requirements. I'm wondering, if we download and deploy an update from the catalog (Chrome, for example), and the update gets marked 'expired' via a catalog update because a newer version becomes available, will the original update still continue to deploy? Would we be able to finish deploying the now 'expired' version?

It looks like updates that are marked as 'Expired' can no longer be downloaded and deployed if they weren't originally, but I'm wondering what happens to existing content and deployments when the catalog sync happens and the metadata changes to 'expired'.