October 2026 Summaries

4 posts from Esper

Filter
Month: Year:
Post Summaries Back to Blog
Esper Airwave firmware delivery begins when a build is approved, which makes it available rather than immediately forcing installation across a fleet. Devices discover updates during configurable polling intervals, typically every 24 hours or after reboot, provided they are registered, online, and not already processing or verifying another update. Airwave determines eligibility according to a device’s hardware model, current firmware version, and available full or delta packages, selecting the highest newer eligible build and preferring a delta package when it reaches the same target as a full package. Even eligible updates may wait for local conditions such as maintenance windows, postponement policies, and a configurable battery threshold that defaults to 30 percent, while devices without physical batteries bypass the charge check. Once conditions are met, the agent installs the update without an additional consent prompt and verifies it after reboot. The Airwave Console distinguishes devices waiting for an update opportunity from those whose installation attempts have failed, with device logs and update status information supporting failure investigation.
Oct 24, 2026 1,279 words in the original blog post.
Organizations moving off Windows 10 IoT LTSB 2016 can remain on a supported Windows release, use Extended Security Updates temporarily, migrate qualifying existing hardware to Android, or reimage or replace devices with Linux, depending on application compatibility, vendor support, hardware, peripherals, and operational requirements. A Linux migration requires more than installing a new image, as fleets need centralized enrollment, configuration, software deployment, telemetry, remote diagnostics, access controls, and recovery procedures. Esper Deploy is presented as a management platform for dedicated Linux, Windows, and Android devices, offering role-controlled custom support actions, remote viewing and terminal access, file management, script execution, package operations, and first-boot provisioning for supported Linux images. The source emphasizes testing representative hardware and applications, including peripheral behavior, remote support workflows, recovery, encryption-key handling, and reimaging processes, while noting that systemd-based images are currently the standard path and nonstandard configurations may require additional compatibility work. During a gradual transition, mixed operating-system fleets can be managed from one console, but organizations must map Windows policies to equivalent Linux controls and validate that support teams can operate the new environment independently before retiring legacy systems.
Oct 14, 2026 1,571 words in the original blog post.
Apple’s Declarative Device Management (DDM) shifts device management from a server-driven command-and-response model to an on-device desired-state model, allowing Apple devices to locally enforce policies and report status changes with less polling, network traffic, and reliance on real-time server connectivity. For unattended dedicated devices such as kiosks, restaurant ordering systems, hotel tablets, and warehouse equipment, DDM is particularly significant because it can enforce OS updates without requiring user action, although updates remain operationally risky if they occur during business hours. Apple’s update declarations specify a target OS version and enforcement deadline, persist through offline periods, and can suppress most user-facing notifications on supported iOS, iPadOS, and tvOS versions, but they do not provide bounded installation windows and may begin enforcement after an offline device restarts. Esper describes building scheduling and orchestration safeguards around Apple’s native capabilities, while noting that Apple’s agentless architecture limits MDM vendors to functions exposed by the operating system. Because DDM is asynchronous and dependent on factors such as power, connectivity, battery level, and available storage, operators must monitor status and rollout progress rather than treat policy acceptance as immediate completion. Esper is introducing DDM support gradually, separating persistent update posture in Blueprints from time-bound OS update campaigns with rollout rings and monitoring, and emphasizing API-based automation for large dedicated-device fleets.
Oct 14, 2026 1,468 words in the original blog post.
Android devices may be built with Google Mobile Services (GMS), a licensed suite including Google Play, Maps, authentication, and commonly used APIs, or as non-GMS devices based solely on the Android Open Source Project (AOSP). GMS-certified devices offer access to Google services, Android Enterprise support, compatibility testing, and generally stronger expectations for security patches, but certification is costly, time-consuming, tied to recent Android versions, and can limit firmware control while making device owners dependent on OEM update schedules. AOSP devices provide greater flexibility to customize hardware, firmware, provisioning, operating-system versions, and update timing, making them potentially suitable for kiosks, signage, industrial equipment, and other dedicated single-purpose deployments, but they require careful management of app compatibility, third-party APK sourcing, security, firmware quality, and supplier contracts. Applications reliant on GMS packages may need redesign or direct use of Google APIs to work on AOSP, while devices that genuinely require Google services should use certified GMS hardware; organizations can also operate mixed fleets. The choice depends on required apps and APIs, device scale, hardware sourcing, update and security needs, deployment environment, and the degree of control desired over the device software stack.
Oct 03, 2026 2,580 words in the original blog post.