Removing/Deleting a Revision
What
You can delete a Fileset revision when it is no longer needed.
When/Why
Keep the previous revision when you may need it for rollback. Older revisions that are no longer useful can be removed to reduce clutter and save disk space. Deleting a revision is not the rollback action: if you only need devices to use an earlier version, follow Fileset Revisions: Test, Roll Out, and Roll Back Updates and keep the revisions you still need.
Before deleting a revision that is still assigned, identify the affected devices and decide whether they should lose that assignment or receive a tested replacement revision. A revision change reevaluates the Fileset and runs applicable scripts, including uninstall scripts from the revision being removed. It is not just a change to the revision name.
How
In FileWave Central, open Manage Revisions from the Fileset Editor, Script Editor, or Fileset Properties window. Select the revision and click the minus button to remove it. If no associations use that revision, FileWave shows a confirmation prompt:
If associations still use the revision, the dialog offers to delete those associations or assign them to another revision. Review the destination and the summary before confirming: the example below moves all v81 associations to v79, not only one selected device. These screenshots show the legacy Associations workflow; use the linked rollout and rollback guide when working with Deployments:
No comments to display
No comments to display