Delete USMT user state after successful deployment or on timer
Just paint this picture: 300+ Win 7 Clients are to be upgraded (scanstate, wipe+load, loadstate) to Win 10 using the SDA (and build in tasks). The list of possible user states to restore will be to long to click "Start Installation" after three or so upgrades.
Suggestion: Mark USMT user state as to be deleted after a successfull restore. On timer (once per night?) delete marked user states.
Possible plus: Add a checkbox to the USMT user state's details page: "Don't cleanup"
Christian Tenner
shared this idea
-
WilliamM
commented
We have been having storage capacity and clutter issues with USMT scan states uploaded to our K2000. 90% of these have been migrated because the K2000 selects all profiles for migration by default and my peers will quite often zip through this without de-selecting profiles not needed. This will result in a lot of garbage data being captured as well as create duplicate local user accounts and profiles. This can form in to a very long list that takes up a lot of space that we have to manually clean up on each of our RSA(s).
Would it be possible to add the following features?
- Server Global setting or Task-Specific option to not auto-select profiles for migration when doing a manual deployment?
- Option to cleanup scanstates after X days paired with the ability to flag a capture for retention? E.G. automatically remove all scanstates that have been on the server longer then 45 days a long as they are not flagged for retention?