Hey everyone, we are prepping for a massive migration from a mix of Intune and workspace one over to Hexnode. I want to entirely avoid situations where the two management agents conflict over the same registry keys, as well as the battery drain caused by leftover profiles from the old UEMs.
How does hexnode actually ensure we don’t end up with orphaned devices during the uninstallation? What happens if a device drops off the network right in the middle of the cleanup script?
41 Views
Hey @harold, I was worried about the exact same thing, but Hexnode has some pretty strict validation logic to prevent orphaned devices.
If you check out their docs here: https://www.hexnode.com/mobile-device-management/help/mdm-migration-cleanup/. It explains that the automated cleanup won’t even trigger unless the new Hexnode agent is already fully active, connected, and compliant. Basically, it verifies it has full control over the OS before it attempts to rip out the old MDM.
As for network drops, the doc mentions a built-in failsafe. If the device loses connectivity while the script is running, it halts right away and waits for a stable connection. When you do run it, definitely deploy in staged waves (like 1,000 test devices first, then 5k, etc.) instead of blasting your whole fleet at once.
Adding to Porter’s point, what I really appreciated during our rollout was that it doesn’t just run a basic uninstall of the old agent. It actually stops the old background services and completely wipes the leftover folders.
It also rips out the old Wi-Fi and VPN certificates from the previous MDM, which saved us from those annoying connection loops we were seeing. It even cleans up the leftover registry keys so the old profiles are totally gone. Honestly, once all that old MDM bloat was removed, we noticed a solid improvement in battery life and boot times across our fleet.
Don't have an account? Sign up
