Every year admins ask two questions about Endpoint Central: what actually changed, and how do I upgrade without breaking the one server that manages every PC in the office. This page answers both honestly — what ManageEngine really shipped in 2025, and the safe upgrade routine the video demonstrates.
Here is the honest shape of Endpoint Central in 2025. There was one headline launch — digital employee experience (DEX) capabilities arrived in August 2025 — and the rest of the year on the on-premises 11.4.25xx build line was service packs and hotfixes: security fixes and stability work, the kind of update that rarely makes headlines but quietly keeps your server safe. This guide covers what is new, what did not change, and the upgrade order that keeps your data and configurations intact — the same order shown in the video above.
In August 2025 ManageEngine announced digital employee experience (DEX) capabilities for Endpoint Central. DEX watches the problems users feel but rarely report properly — slow boot times, application crashes, delayed logins, CPU spikes and memory pressure — and turns them into device and application health scores, with one-click and workflow-based fixes offered from the same console.
Two honest footnotes. First, DEX runs on the same single agent as the rest of Endpoint Central — no second monitoring tool to deploy. Second, it is an add-on, and ManageEngine also sells it standalone as the SaaS product DEX Manager Plus. Updating your server does not switch it on; there is a separate trial and licence decision, covered in its own guide in this series.
The on-premises line through 2025 was the 11.4.25xx build series, delivered as service packs (PPM files) and hotfixes rather than one giant release. Most entries in ManageEngine's published readme for these builds are fixes and hardening, not features.
One example worth remembering: the March 2025 build 11.4.2514.01 in ManageEngine's own service-pack readme fixed a Windows Product Installer component issue that could have allowed local privilege escalation, alongside a smaller Linux reboot-postpone fix. That is the real texture of a year of updates — unglamorous, and exactly the kind of thing you do not want to skip.
The video starts where every upgrade should: open your profile in the console and read the build number. If an update is available, the console shows a download option — and crucially, it offers the file that matches your build.
Endpoint Central upgrades are sequential. You apply the service pack meant for the build you are running, which may not be the newest file on the internet. Downloading a random newer PPM and forcing it is how upgrades fail; the console's own suggestion is the safe route.
The video's promise is an upgrade without losing data or configurations — and the backup is what makes that promise safe to keep. Before you touch the update file, take a backup of the server: a VM snapshot or full backup of the machine, including the product database.
If anything goes wrong mid-upgrade, there is no downgrade button. The backup is the way back. No backup, no upgrade — that rule has no exceptions, even for a small hotfix.
With the PPM downloaded and the backup safe, stop the product so its files are free to be replaced. Open services.msc, find the ManageEngine UMS Server service, and stop it — exactly as shown in the video.
Then open the bin folder inside your Endpoint Central installation folder and run UpdateManager.bat. Browse to the PPM file you downloaded, start the installation, and let it work. In the video the update takes roughly 30 minutes; larger databases take longer. Do not interrupt it, and do not restart the server mid-way.
When UpdateManager finishes, start the ManageEngine services again and open the console. Go back to the same profile screen from Step 1 and confirm the build number has changed to the one you intended.
Finish with two spot checks: confirm a few agents are checking in normally, and glance at one routine view you use daily — patches or inventory. If the console loads, the build is right and agents are reporting, the upgrade is genuinely done. The agents on your PCs pick up their new version as they check in with the upgraded server; you do not visit a single desk.
See the build check, the service stop and the UpdateManager run live on a real server, exactly as it happens.
▶️ Watch Full VideoIn the video the update itself takes roughly 30 minutes. Your time will vary with database size and server speed — plan a maintenance window of about an hour so the verification steps never feel rushed.
The upgrade process is designed to carry your data and configurations forward, and the video follows the data-safe order: backup first, then the service pack. The backup is your insurance — take it every time, even for small hotfixes.
Yes. The video notes the same UpdateManager process applies to Endpoint Central, Desktop Central and Patch Manager Plus, because they share the same upgrade mechanism — check the build, stop the service, apply the matching PPM, then verify.