This feature has been rolled out to all tenants.
What is Blueprints 2.0 (the new blueprints experience)?
Blueprints 2.0 is the latest iteration of Esper’s device management. They allow users to configure, update, and manage devices at scale. Now with 2.0, you have the added bonus of switching between configurations instantly, tighter controls over drift management, and much more.
Will I be forced to move from Templates to Blueprints by a certain date?
No. You can still use Templates for the foreseeable future. In fact, you can use Templates and blueprints at the same time, and convert your templates into blueprints at your own pace.
What are the benefits of using Blueprints?
Blueprints are an improved version of Templates. Blueprints are editable, have clearly defined sync rules, and are easier to manage in the Console with an improved UI.
What Esper Agent Version and device versions do I need to be on to use Blueprints?
Blueprints require an Esper Agent Version of 7.8.7718. If your devices were provisioned after August 2022, they will be compatible with Blueprints 2.0.
My organization was already on Blueprints. How is this experience different from the previous version of Blueprints?
This experience addresses many of the issues found in the previous Blueprints experiences. We’ve included many changes such as:
- An overall more thoughtful design for the relationship between blueprints, groups, and devices
- A new Blueprints Management section that makes it easier to locate blueprints and the devices they’re linked to
- Clear expectations for application, Wi-Fi, and File syncs
If my organization was already on Blueprints, do I need to switch to the new version?
We’ll be rolling out the new experience over the coming months. As part of this, customers on Blueprints tenants will have their tenants upgraded to the new experience.
Will the Templates experience still be supported?
While we will address any bugs or performance issues related to Templates, we will not release any new functionality for those still on the Templates experience. All new functionality will be available on Blueprints.
Can I switch to the new Blueprints experience if I’m on Templates?
Yes. In fact, you’ll be able to do that right from the console. In addition, you can choose which devices you’d like to switch over, meaning you’ll have control of when and how you upgrade to the Blueprints experience.
Can I still change settings at a device or Group level without changing the Blueprint?
Yes! You can still change device or Group settings.
Ideally, your devices should remain in a Desired State as much as possible. However, we realize you may want to change settings occasionally when you debug devices, or for other tasks.
If you want to return your device to its Desired State, converge it to its blueprint.
How will Directory Records work for the new Blueprints experience?
We’ve decided to do away with Directory Records. This feature caused too much confusion among our users. Instead, devices will appear in the Console as devices. You’ll be able to perform limited actions on them before they are fully provisioned.
Can I have a more detailed description of how the old Blueprints experience differs from the new one?
| Feature | Blueprints 2.0 | Blueprints |
| Group Behavior |
|
Devices needed to be part of a group and blueprints were optional. |
| Blueprint Behavior |
|
Whenever a blueprint was updated, the devices linked to it were automatically updated. |
| Locating Blueprints | Blueprints now have their own section in the console called the Blueprints Manager section. View and manage your blueprints in one convenient place. | You needed to find the group linked to the blueprint in order to access the blueprint. |
| Blueprint Settings | When creating a blueprint, you can now choose between Templates behavior (apply the setting during Provision Only), classic Blueprints behavior (Always Apply), or Ignore the setting completely. | Settings were always applied to the devices they were linked to–regardless of whether or not they needed to be. |
| Changing a Device’s Blueprint | You can change a device’s blueprint from the Devices & Groups section or add it to a group with a new blueprint–no factory reset required! | Devices needed to be factory reset to change their blueprint. |
| Blueprint Version Control | You’ll be able to revert back to any saved version of a blueprint. | No version control. |
Can I have a more detailed description of how the Template experience differs from the Blueprint 2.0 experience?
- One of the biggest challenges for Templates users was applying Compliance Policies to update device settings. With Blueprints, users will no longer need to apply Compliance Policies. They can simply update a blueprint and Converge those changes on their devices. No more having to deal with a dozen Compliance Policies for small or big changes – everything is managed in the blueprint.
- With Blueprints 2.0, you’ll now see when the device shifts from its intended configuration. The new concept, called drift, is covered in our Introduction to Blueprints 2.0.
- The provisioning experiences for Blueprints and Templates were different, leading to confusion for some users. We’ve combined the provisioning experience under a unified UI so that you can clearly select your method, template or blueprint, and additional provision settings.
- We’ve made decisions for how devices will sync with Wi-Fi, content, and applications for Blueprints 2.0. Now you’ll clearly understand how scenarios affect your devices so you can make the best decisions for your fleet.
- Speaking of Wi-Fi, we’ve added a new setting to Blueprints 2.0. Enable Wi-Fi strict mode on your devices to control the device's access points. Learn more about Strict Mode for Wi-Fi List.
I was previously on the Blueprints experience. I didn’t assign my devices a blueprint. What should I do?
For those customers on the previous Blueprints experience, the devices without blueprints will be assigned a “Zero Blueprint" or "Default Blueprint."
A “Default Blueprint” is a blueprint that will ignore all settings currently on the device (meaning your device will continue to function the same way it did before).
Change this device’s blueprint at any time by locating it in Devices & Groups, clicking on the ellipsis (...), and selecting Change Blueprint.
I just saved a blueprint. Why aren’t the changes showing up on my device?
There might be a few reasons for this:
- If you created a blueprint from a template, you’ll need to Converge devices to that template. Find that device in Devices & Groups. It should have an Upgrade Now option. Click on Upgrade Now and then choose the blueprint it’ll be assigned to.
- If you updated a blueprint, you’ll need to Converge those changes to the devices linked to that blueprint. Locate the device in Devices & Groups and click on the ellipsis under Actions, then select Converge.
- If you created a new blueprint, you can provision a device with that blueprint or change the blueprint of that device. Provision a device through the Provisioning Methods section.
- You can also change a device’s blueprint in Devices & Groups. Click on the ellipsis (...) under the Actions heading and select Change Blueprint.
Can I revert a device back to Templates if I upgraded it to Blueprints?
Yes. You’ll need to Factory Reset the device and provision it with a Template.
What happens when a device upgrades from Template to Blueprints? Is there any downtime?
A message will appear on your device letting you know an upgrade happened. Upgrade times may vary depending on the applications added to the new blueprint and your network connection.
What does {this} error message mean?
We have an article that explains our most common error messages.
What else has been updated besides Blueprints?
We’ve updated the Devices & Groups section for both our Templates and Blueprints experiences.
If you were on the Blueprints experience previously, you’ll no longer need to hunt for blueprints in the Devices & Groups section.
Now, from a single view, see which devices belong to which Templates, which devices are in drift, and which devices can be upgraded to the new Blueprints experience.
To see the Templates view, enable the toggle in the Devices & Groups section. Keep in mind that you'll only see Blueprints-based devices in the Blueprints view.
After removing an app from a blueprint, I'm unable to delete that app. How do I delete it?
If you used the app in a previous version of the blueprint, then it may be needed if you ever restore that version of the blueprint. Therefore, you won't be able to delete apps if they were ever in a previous version of a blueprint.