Dates: April 1, 2025
Esper Agent Version: 8.03.0898
New Features
-
App Sync: Introducing app sync modes in blueprints. You can now specify how you want blueprints to control applications. For example, do your devices need to stay in compliance? Use Default Mode. Or does your use case allow devices to run with different applications? You can choose to keep apps on the device.
- All current blueprints will continue to use the Default mode and there will be no change in behavior for devices on the Default mode.
- Devices must be on Esper Agent 8.0+ to switch between the different modes. Devices below 8.0 will use the Default mode.
- We’re rolling this out in batches, so expect to see Application Sync Modes in your tenant over the coming month.
Learn more about App Sync or see the App Sync FAQ. App Sync will be rolling out to tenants over the coming weeks, so be sure to check it out on a tenant near you.
-
EMM Enrollment Is Now Managed Google Play Services : You can now enroll or unenroll a device in Managed Google Play (formerly EMM) through a blueprint. Previously, devices couldn’t be unenrolled. You’ll now have the option to remove devices from Managed Google Play which means you can flexibly change their use case without a factory reset. Learn more about enrolling in Managed Google Play and setting Managed Google Play through a blueprint.
- This feature is available for GMS devices on Esper Agent 8.0+.
- This setting will default to Provision Only in existing blueprints, so you won’t see any changes to devices that are already enrolled.
- Going forward, new blueprints will continue to have this setting enabled by default as Provision Only.
- We’re rolling this out in batches, so expect to see blueprint-based Managed Google Play enrollment in your tenant over the coming month. As always, your AOSP and iOS devices will be unaffected by this change.
Managed Google Play will be available over the coming weeks, so check back soon.
Bug Fixes and Improvements
- We fixed an issue where devices provisioned with Templates would not have their group names displayed in the Blueprints Devices & Groups page. You’ll now see the device’s group information in both the Templates and Blueprint Devices & Groups view.
- We fixed a rare issue where a device couldn’t be moved into a group if it was added through seamless provisioning and then removed from the tenant.
- Added support for Default Update in a blueprint's System Updates.
- Fixed an issue in the Esper Agent where the bug report command was failing due to a timeout.
- Fixed an issue where the Esper Agent failed to properly clean up temporary files after use.
We’re excited to launch DevRel 160 over the coming days, and the Esper team is hard at work on the next release. Please contact Esper Support to share your thoughts on how Esper can improve future releases. (We understand that these notes came out April 1st, but this release is no joke.)