A blueprint is a set of configurations applied to one or more devices. These configurations include apps, update frequencies, volume and brightness levels, and more.
In short, a blueprint creates a uniform experience for device users and a desired state for device administrators.
If a device strays from its desired state, it’s in drift. This could be because the settings on the device were altered, or you edited the blueprint to create a new desired state.
When you apply a blueprint to a device, you converge it.
If a converge fails, the Event Feed will display the errors that occurred.
In this article:
- Converge a Single Device
- Converge Multiple Devices
- Converge a Group of Devices
- Converge: Immediate or Scheduled
- Default Event Feed Failures
Converge a Single Device
Option 1: To converge a single device, click on the ellipsis (...) in the device’s row, and select converge.
Option 2: Click on the device’s ID to see the device’s details. From the details page, click on Actions and select Converge.
Converge Multiple Devices
Option 1: To select multiple devices, click on the checkbox in the same row as the device. An Actions button should appear. Click on the Actions button and then select Converge.
Option 2: You may also select the checkbox on the header to select all devices on the page.
A message to select all devices will appear above the device table. Choose Select all to select all devices in the current filter.
Then click on the Actions button and select Converge.
All selected devices must meet the converge criteria in order for the Converge selection to appear:
- All devices must be on the Blueprints experience.
- The selected device count must be less than 1000 devices.
- The devices must be in the provisioned state.
Use filters to create a coverageable list of devices.
Converge a Group of Devices
Option 1: In the Groups view, click on the Actions button next to the group and select Converge.
Option 2: You can also converge from the group details page by clicking Actions at the top of the group page and selecting Converge.
Converge: Immediate or Scheduled
Immediate converge
To converge immediately, select Immediately Converge.
You can choose to include Provision Only blueprint settings by checking the box.
Scheduled converge
To schedule a converge, you can select Schedule Converge.
Create a schedule with the following:
- Device Time or Console Time: Selecting device time will converge according the device’s time. Generally useful when managing devices in a timezone that differs from your current timezone. Choose console time to converge devices according to your timezone. Console time will fire the converge devices command at the same time regardless of timezone.
- Start and End Time: Choose a start and end time for the converge to take place. The start time must be at least half an hour earlier than the end time.
Default Event Feed Failures
By default, if a blueprint fails to converge, you can keep track of failures in the Event Feed.
| Failures | Event Feed |
| Fails to uninstall the app during an app sync. | |
| Fails to install any enterprise apps. | |
| Timeout occurs while installing Google Play apps. | |
| Fails to restore the local version of the file during a file sync. | |
| Fails to download any content files. | |
| Fails to set the system update policy. | |
| Fails to set the screen timeout on the device. |
A success message is expected. |
| Fails to add or connect to Wi-Fi access points during a Wi-Fi sync. |
Use the Event Feed to diagnose converge failures.
See the expected behavior for: