When you create a blueprint, you specify the access points that devices use to connect to the internet. You can either allow the device to connect to only specific SSIDs (also known as the Wi-Fi network name or access point), or enable devices to connect to any network available. In most cases, you’ll want to restrict access to just a few trusted networks to ensure the integrity of your fleet.
In this article:
Adding Wi-Fi SSIDs
In a blueprint, go to Connectivity and ensure that Allow Wi-Fi is enabled.
Then, click on Add Wi-Fi Access Point to add the SSIDs and, if applicable, credentials. Previously added Wi-Fi Access Points are available in the list.
Understanding Wi-Fi Sources
In Esper, devices receive Wi-Fi sources from the SSIDs in their physical location, from users in Android Settings, or from their blueprint.
Note: SSIDs added by users manually through Android Settings are not removed from devices.
Blueprints affect Wi-Fi behavior in various ways. When a new SSID is added to the blueprint, the device will disconnect from its current Wi-Fi network, cache it, and then try to connect to the SSID present in the blueprint. Then, one of two things can happen:
- Success: Once the device connects to any of the blueprint’s SSIDs, it will remove all other SSIDs that are not part of its blueprint.
- Failure: If the device can't connect to any of the blueprint’s SSIDs, it will revert to the network it was previously on. The blueprint will show a failure message for that device in the Console.
Understanding Wi-Fi Sync Scenarios
In Blueprints 2.0, we introduced a new setting called Strict Wi-Fi Access Point Synchronization. With this setting, users can now:
- Decide whether or not devices carry over SSIDs from other Esper sources or strictly from the blueprint.
- Reduce the need to make multiple blueprints to solve Wi-Fi sync issues.
Strict mode
In the following table, we explain the scenarios that occur when devices converge to the Blueprint if Strict Wi-Fi Access Point Synchronization is enabled or if the device is on Esper Agent Version 7.13.0240 or below.
About the table:
- * denotes a Wi-Fi network the device is connected to before applying the new blueprint.
- Network A was added manually through Android Settings. All other networks are added through a blueprint unless otherwise specified.
Are you migrating from Templates to Blueprints? Learn how Wi-Fi access points are affected by migrations.
| Previous Blueprint SSIDs | New Attempted Blueprint SSIDs | SSIDs (or network) connected after applying the new blueprint | Status Message | Explanation |
| A, C*, D | E, F | E or F | Success | A, C, and D are removed from the device. E or F is now connected. |
| A, C*, D | C, E, F | C | Success | D is removed from the device. The device will stay connected to C. |
| A, C*, D | E, F | C | Failure | The device failed to connect to E and F. It reverts to C and the blueprint shows a failure message. |
| A*, C, D | E, F | A | Success | C and D are removed from the device. E and F are added to the device but are not connected. |
| A, C*, D, Mobile Data | E, F | Mobile Data | Success | C and D are removed from the device. E and F are added to the device but are not connected. The device will use Mobile Data after the new blueprint is applied. |
| A, C*, D, Ethernet | E, F | Ethernet | Success | C and D are removed from the device. E and F are added to the device but are not connected. The device will use Ethernet after the new blueprint is applied. |
| A, C*, D | C | C | Success | D is removed from the device. The device will stay connected to C. |
| A, C*, D | E | C | Failure | Since the device was not able to connect to E, the blueprint will fail. The device will stay connected to C. |
| A, C*, D | E | E | Success | C and D will be removed from the device. E is now connected. |
When strict mode is used with "Use only saved Wi-Fi Access Points"
When strict mode is enabled with "Use only saved Wi-Fi Access Points," devices will only be able to connect with the SSIDs specified in the blueprint. In addition:
- This restriction begins at the onboarding step.
- Device users will not be able to add Wi-Fi networks manually. However, if the user has access to Admin mode through the Esper Settings app, they will be able to add new Wi-Fi access points. Any Wi-Fi access points added this way will need to be added to the blueprint.
- If the device cannot connect to the specified network, it will disconnect from Esper.
Ensure you have a reliable backup network available when using these two options.
Lenient mode
When strict mode is disabled, and the device is on 7.13.0240 or above, the device is considered in lenient mode. These devices will retain any previous Esper-managed networks during a sync with their blueprint. Esper will add the Wi-Fi SSIDs from the blueprint to the device's saved networks, but the device will remain on its current network.