Skip to main content

SnapBack

How SnapBack freezing works, and how to unfreeze IMA devices that are frozen by default after migration from iMinKit.

What is SnapBack

SnapBack automatically keeps configuration snapshots of a device, so that you can roll back to an earlier snapshot when a configuration change causes problems. Freezing is its protection mechanism: while a device is frozen, it does not run auto-remediation and does not receive group or global policies, so its current configuration is not overwritten.

Freeze and Unfreeze are in the Actions dropdown of each row in Device List and can only be performed from the console. Both require the device to be online.


​

A device migrated from iMinKit shows "Frozen". How do I unfreeze it?

Short answer: This is by design, not an error. Devices migrated from iMinKit to KiwiCloud are frozen by default, and an administrator unfreezes them from the console, one by one or in batches. The device must be online when you unfreeze it. No re-enrollment is needed.

Devices are frozen by default after migration so that a large batch of devices does not all apply the new KiwiCloud policies at the same moment, which could cause widespread issues. We recommend checking your policy configuration first, then unfreezing devices in batches and observing the results.

After unfreezing, the device resumes receiving its currently assigned policies. An IMA device does not restore its configuration automatically after unfreezing; push the policies again manually.


​

Steps to unfreeze

1. Open Device List and switch to the IMA tab.

2. Find the device with a lock icon and the "Frozen" label next to its name, and check that its online status is Online. Click Details next to the label to see the freeze information.

3. Open the Actions dropdown in that row, choose Unfreeze Device, and confirm in the dialog.

If the device is offline, wait until it comes back online.


​

Applies to

IMA devices migrated from iMinKit to KiwiCloud.

Did this answer your question?