If you’re on the Templates experience and would like to try out the Blueprints experience, you can make a copy of your template and create a new blueprint from it. Because Blueprints and Templates have 100% parity, all of your settings will transfer to the new blueprint. In addition, any device you provide with the blueprint will have all the settings they have in the template.
For a step-by-step guide, see Introduction to Migrating from Templates to Blueprints.
Device Requirements and Considerations
| Esper Agent Version | System Guidelines | Feature Support |
| 7.8.7877 | Minimum | Eligible for Upgrade to Blueprints |
| 7.17.0402 | Recommended |
|
- For seamlessly provisioned devices, the serial number will be mapped to the new blueprint.
In this article:
Step 1: Create a Blueprint from a Template
To create a blueprint from a template, go to the Blueprints Manager and click on Create Blueprint.
Then select Create Blueprint from Template.
Choose the template, optionally select the compliance policy applied to the device, name the blueprint, and add a description. Compliance Policy settings will take precedence over Template settings if applied.
Preview or edit the newly created blueprint.
For a complete guide to blueprint settings, see Creating a Blueprint.
You can change settings at the step, but doing so will create a device experience different from the Template.
Blueprints allow you to set device configurations in the following ways:
- Always Apply - the setting is applied when the device converges with the blueprint. Recommended for most use cases.
- Provision Only - the setting is applied at the provisioning step, but won’t be applied at other steps. This option mimics Templates.
- Ignore - the setting is ignored. Intended for settings that have no impact on the device experience. These settings can be changed by the device user or a Console user at any point.
Once you are done previewing or editing the blueprint, click Save.
When you migrate a Template to a blueprint, settings listed in the Compliance Policy will be automatically set to Always Apply. All other settings will be set to Provision Only to mimic the Template functionality. You can always change these settings while you’re editing the blueprint.
Step 2: Upgrade Devices to Blueprints
After creating the blueprint from the template, you’ll need to upgrade your devices to the new blueprint experience. Go to Devices & Groups and locate the device you’d like to migrate. Eligible devices will have an Upgrade button.
For a single device, click on Upgrade Now. If you don't see it, you may need to select the Blueprint Upgraded column in View > List: Devices > Customize List View.
To select multiple devices, click on the checkbox next to the device. Then click on the Actions button and choose Upgrade to Blueprint.
Wi-Fi access point behavior
Note: If the device is connected to a Wi-Fi access point before upgrading, and there are no access points specified in the blueprint, or if the device has trouble connecting with the new access point, the device will connect to mobile, Ethernet, and then to the last known access point. If an access point is found, the device will provision with it, even if it is not in the blueprint. However, if the device fails to connect to any access points, the upgrade will fail.
Upgrading the device
Then click Upgrade Now.
Choose the blueprint you’d like to apply to the device. You can change the blueprint as often as you like after upgrading.
Then click Upgrade.
Allow the devices a few moments to complete the upgrade. You will see a message if the upgrade was successful or not. You can also use the device’s Event Feed to check on the upgrade’s status. After upgrading the device, it will be in a Drift state. Click on the ellipsis (...) in the Actions column and select Converge to resolve the Drift.