With serial-based device persistence, a device keeps its Esper Device ID and device name after a factory reset and reprovisioning. The device's serial number is the identifier, so the device doesn't appear in the console as a new record.
Use this feature if factory resets or reprovisioning create duplicate devices in your tenant. Duplicates can happen when a device's Wi-Fi MAC address changes after a reset.
Availability: Enabled upon request.
How It Works
When the feature is enabled for your tenant, Esper uses the device's serial number as the primary identifier during provisioning. Esper no longer uses the Wi-Fi MAC address to resolve device identity for your tenant.
| Scenario | What happens |
|---|---|
| First-time enrollment | Esper creates a new device record and associates it with the serial number. |
| Re-enrollment after a factory reset | Esper finds the existing record for that serial number and reuses the same Device ID and device name. |
| Serial number matches multiple existing records | Registration fails with a validation error. Esper doesn't create a new record or modify any existing record. This protects against incorrect identity reuse. |
Note: Because Esper doesn't use the Wi-Fi MAC address to resolve identity, a MAC address change after a factory reset doesn't create a new device record.
Requirements
This feature isn't enabled by default. Your environment must meet all of the following requirements:
- Unique and stable serial numbers: Every physical device in your fleet must have a serial number that stays the same after a factory reset and is unique across your entire fleet. This step is verified by our team.
- Blueprint provisioning: Devices must be provisioned through the Blueprints onboarding flow. Legacy template-based provisioning isn't supported.
- Supported DPC version: Devices must run Esper Agent v9.3.2737+.
- Pre-enablement verification: Before activating the feature for your tenant, we verify that serial numbers are unique across your fleet and check for serial numbers already associated with multiple Device Names.
Known Limitations
- Esper doesn't automatically resolve existing duplicate device records. If a serial number in your tenant already maps to multiple Device IDs, those devices aren't eligible for identity reuse and receive a conflict error when they re-enroll.
- Tenants without the feature enabled use existing provisioning behavior, which doesn't guarantee that the Device ID and name persist across reprovisioning.
- Not supported for Templates-based provisioning (legacy).
Requesting the Feature
Contact Support or your Technical Account Manager to request evaluation and enablement for your tenant. We complete the prerequisite verification, then enable the feature for your tenant.