Allow editing and expiration of Third-Party Software Updates
Please add full functionality of SCUP to the Third-Party Software Update feature. Adobe Acrobat catalogs don't expire older updates and don't include supersedence information. I normally added supersedence settings through SCUP to mitigate this. Without the ability to edit this information or to expire old updates manually, deploying Acrobat updates becomes unwieldy. Unexpired updates that are not superseded will likely bloat and fill up the data shares. If you can publish it, you should be able to expire it.
Janek Kröger commented
This could also be very helpful if a third party software update is faulty and has been published by an admin.
With this functionality you can manually expire the update and prevent it from being deployed to the endpoints.
Micah Taylor commented
We need the ability to edit update command lines in order to add BIOS/EFI passwords to BIOS/EFI updates.
Lance I. commented
Without the ability to expire updates like we have in SCUP, it's holding off my migration away from it due to Adobe never expiring their content.
not being able to expire updates from a 3rd party means you end up with a bloat of updates which the vendor doesn't manage properly. As new updated drivers are produced we are required to scan for all drivers regardless of the implied supersedence.
Kym Dyer commented
Dell never expires their updates and the ADR which deploys based on "required" keeps adding the updates back to the deployments.
In my screenshot the deployed one is the most current, but all the others are showing as required ...
We've begun to investigate using Third Party updates to deploy driver and firmware updates for Dell and HP devices; however there is no way to keep the synced data clean because we are unable to expire anything. Please support expiration of TPU.