Update announcements are loud; continuity is quiet. If you run Endpoint Central, here is the reassuring half of the 2025 story: the platform you licensed is the platform you still have. And one common misunderstanding — that upgrading switches licence features on or off — gets cleared up.
A year of service packs and one headline add-on can make it sound as if Endpoint Central was rebuilt in 2025. It was not. The year's changes were additive and maintenance-shaped: an experience layer arrived beside the existing modules, and the builds underneath kept your edition, your licence and your daily workflows exactly where they were. This page is the inventory of what did not move.
A service-pack upgrade applies on top of your existing, licensed installation. It does not reset your edition, shrink your endpoint count, or demand a fresh licence file because the build number moved.
Licence renewals and annual maintenance run on their own separate clock, as they always have. If applying an update ever appears to trigger a sales conversation, something has gone off-script — stop and read what is actually on screen.
Patch management still patches, software deployment still deploys, inventory still inventories, and remote control still connects the way your technicians know. The 2025 story added DEX beside these modules — a new lens on the same fleet — not a replacement for any of them.
That continuity is worth stating plainly because it is what makes the upgrade low-drama: your team's habits, saved views and approval workflows survive the build change untouched.
DEX joined the add-on family in 2025 the same way the security add-ons — the DLP and device-control class of capabilities — already worked: updating the server does not silently grant them. Each is a deliberate trial-and-licence step, taken when you decide the capability earns its cost.
This cuts both ways, happily. Skipping an add-on costs you nothing you already had; adopting one later does not require re-upgrading anything. The platform grows by addition, on your decision.
The official upgrade path — the one in the video — is built around a simple promise: update the server without losing data or configurations. Groups, policies, configurations and patch approvals ride through a properly performed upgrade.
The pre-upgrade backup still matters, but understand its role correctly: it is insurance against a rare bad day, not an admission that loss is expected. Well-run upgrades are boring precisely because the process was designed to preserve everything.
An upgrade is not a migration to the cloud edition, not an edition change, not a renewal, and not a re-implementation. It is the same server, the same data, running a newer build of the same product.
Keeping that straight is what makes update day a routine instead of a project — and routines are what keep a management platform healthy for years.
See the process that carries your configurations forward — backup, service stop, UpdateManager, verify.
▶️ Watch Full VideoA service-pack upgrade runs on your existing licence. You revisit licensing when your edition, endpoint count or annual maintenance changes — not because the build number moved.
No. DEX is an add-on with its own trial and licensing. Updating makes the platform current; enabling DEX is a separate, deliberate step.
Yes — preserving data and configurations is the point of the official upgrade path. The pre-upgrade backup exists for the rare bad day, not because loss is expected.