# Over-the-Air (OTA) deployment ## What is Over-the-Air (OTA) deployment? Over-the-air (OTA) deployment is the process of delivering software updates, configuration changes, or policy modifications to endpoints without requiring a technician to be physically present or the device to be connected to a local network. It is widely used for mobile devices, laptops, rugged hardware, and managed fleets because it allows updates to reach devices remotely and consistently regardless of where they are located. OTA deployment is a core operational capability when an organization needs to patch, reconfigure, or update a distributed device fleet quickly while minimizing disruption to users. ## Why does it matter? Modern device fleets are distributed across locations, time zones, and working conditions that make physical update delivery impractical at scale. A single IT team cannot physically access every endpoint, so remote update delivery is a foundational operational capability rather than a convenience. Without OTA deployment, patching and rollout windows become slower, more disruptive, and harder to coordinate. Critical updates may be delayed because a device is not in the office, creating compliance gaps and security exposure that could have been avoided with remote delivery. ## What is the difference between an OTA software update and a local tethered update? A local tethered update requires the device to be physically connected to a computer or update server, typically via USB or a direct network connection in a controlled environment. It offers more reliable delivery in low-bandwidth or high-security contexts but requires physical access and is not scalable for large or geographically distributed fleets. An OTA update delivers the same payload over a wireless or internet connection without physical access, enabling updates to reach devices wherever they are located. OTA is more scalable but depends on network availability and requires appropriate security controls to ensure the integrity of what is delivered. ## Why is OTA deployment essential for managing remote and mobile device fleets? Remote and mobile devices by definition cannot be consistently brought to a central location for updates. If updates depend on physical access, remote employees and field teams will fall behind on patches, configuration changes, and policy updates at precisely the moments when their devices are most exposed to risk. OTA deployment closes that gap by ensuring that update coverage is determined by enrollment status and network reachability rather than by physical proximity to the IT team. ## Silent vs. interactive OTA deployments: When should each method be used? Silent deployments install updates in the background without requiring user interaction or awareness. They are appropriate for security patches, configuration changes, and non-disruptive updates that do not require a restart or visible change to the user environment. Interactive deployments notify the user, may require their consent, and often schedule restart events around the user's working hours. They are more appropriate for significant software upgrades, OS updates, or changes that require a reboot and could interrupt active work if applied without warning. The choice between them depends on the nature of the update and the impact it will have on the user during their working session. ## Relevance for IT admins For IT administrators, OTA deployment is one of the capabilities that makes managing a distributed fleet operationally realistic rather than dependent on physical logistics that do not scale. [Endpoint Central's](https://www.manageengine.com/products/desktop-central/?it&securityglossary) remote software deployment and patch management capabilities deliver OTA updates to managed devices over the internet, allowing administrators to push security patches, software installations, and configuration changes to endpoints regardless of their location, without requiring those devices to connect to the corporate network first. That coverage is what keeps remote and field devices aligned with the same patch and policy standards as office-based endpoints, rather than accumulating compliance gaps between in-person support visits. ## Related articles - Lifecycle: [Out-of-the-box experience](https://www.manageengine.com/products/desktop-central/glossary/out-of-the-box-experience.html) - Foundations: [Distributed workforce](https://www.manageengine.com/products/desktop-central/glossary/distributed-workforce.html) - Operations: [Bandwidth throttling](https://www.manageengine.com/products/desktop-central/glossary/bandwidth-throttling.html)