SkieHow do I go back to an earlier version of a policy or setting?
Pick an earlier backup that holds the version you want, open that item, compare it with the current one in the restore preview, and restore. The older version becomes the current one and devices pick it up as they sync. It is the way to undo a change that looked fine at the time and turned out not to be.
A missing item is obvious. A bad edit is not. Someone loosens a rule for a lesson and forgets to put it back, or a well-meant change stops an app working in one class. By the time you notice, it has been saved over many times.
A previous version restore handles that. You choose a backup from before the change, open the item you want, and run the preview. The preview sets the older content beside the current content, so you can see what differs: perhaps one app was added, one schedule window moved, one protection switched off. Then you decide whether to restore the whole older version or to correct the current one by hand.
Use the audit log to find the date. It records who changed what and when, so you know which night's backup to look at. See audit log. If the change was made today, tonight's backup does not hold the earlier version yet, so use the audit log to recreate the old setting by hand, or choose the previous night's backup.
After restoring, devices take the older policy in the usual way. A signed bundle goes out, and online devices accept it within seconds. Insights shows how many are on the latest policy so you can see it settle.
Skie does not publish how many versions or how many days of backups are kept, and configurable retention is not available yet. Practical tip: for large changes, such as a new term's app lists, take a note of the date before you start so the right backup is easy to find.