Managed OS has been completely rebuilt, optimizing performance and reliability while introducing new features. The core Managed OS functionality has moved from the Kandji Agent to the Kandji server. Among the improvements that this release delivers:
Upon enrollment of a new device, Managed OS waits for its bootstrap token (if necessary) before initiating any actions that would otherwise fail. Once that token is received, Managed OS immediately checks for—and enforces, if appropriate—any updates.
The status of updates is now checked and reported every 3 minutes; changes are visible to admins in both the Library Item status in Kandji and the command history on a device record.
Previously, OS updates were visible to users just five days ahead of scheduled enforcement. Now updates are visible as soon as they have been cached on the device.
When the final 30 minutes of the enforcement window is reached, the Kandji server notifies the Agent in real time to prompt the user to update or upgrade.
Special notifications to the Agent now help remediate updates that might be stalled before their installation fails.
We’ve relaxed the timing for force-closing applications. As long as the user installs the update before the enforcement window closes, their apps reopen as normal following a restart. (If the user doesn't install the update before the enforcement timer runs out, Kandji force quits all open apps.)
When errors can not be remediated, Kandji initiates the fallback enforcement mechanism in the Kandji Agent instead of continuously retrying.
The new version of Managed OS is now live in all Kandji tenants worldwide. No action is required by admins to implement it.
Support for managing updates with Declarative Device Management is coming soon.