I’m managing Android Enterprise Device Owner devices in Hexnode and wanted to power them off remotely after an app update is pushed. Is remote shutdown supported for standard Android Enterprise Device Owner devices? If not, what is the recommended alternative?
Android Enterprise Device Owner remote shutdownSolved
Replies (5)
Hello @maevee ,
Remote shutdown is not supported on standard Android Enterprise Device Owner devices. In Hexnode UEM, the Power off device action is available only in either of these cases:
- Samsung Knox devices with a KPE Premium license
- Devices where Hexnode is installed as a system app
For regular Android Enterprise Device Owner enrollment, Hexnode cannot be manually converted into a system app. Installing Hexnode as a system app typically requires either OEM pre-installation in the device firmware or rooting the device and moving the app into the system partition. Rooting is not compatible with standard Android Enterprise Device Owner management and can break the enrollment model.
For your app update use case, the recommended alternative is to restart the device after the update is completed: Manage > select the device > Actions > Device Control > Restart device.
Restart device is supported on standard Android Enterprise Device Owner devices and is usually the safer option after app updates.
Regards,
Simon Scott
Hexnode UEM
Okayy got it, I was hoping shutdown would be possible without Knox, but if rooting breaks Android Enterprise, restart is probably the better route.
I’m also trying to add a browser shortcut to the device that opens a specific website. Can I set a custom icon for the website shortcut?
Yes. You can use a Web App to create a browser shortcut with a custom icon. When creating the Web App, you can specify the app name, website URL, and upload a custom icon.
The deployment method depends on whether the device is in kiosk mode:
- If the device is in kiosk mode, create the Web App directly in Hexnode UEM from: Apps > +Add Apps > Web App. Hexnode’s kiosk launcher can display and launch the Web App once it is included in the kiosk policy.
- If the device is not in kiosk mode, for a standard Android home screen, create the shortcut as a Managed Web App through Managed Google Play. After it is created and approved, deploy it to the device using a Required Apps policy.
This difference exists because Android handles web shortcuts differently in kiosk launcher mode and in the regular launcher environment.
Got it. One more thing, does the Android Enterprise enrollment QR code expire? It looks like the QR code refreshes when I go back to the enrollment screen.
The Android Enterprise enrollment QR code does not have an expiration time.
If the QR code appears to refresh visually when you revisit the enrollment screen, that is normal behavior and does not mean the enrollment configuration has expired. You can continue using the QR code for Android Enterprise Device Owner enrollment unless the enrollment configuration itself is changed or removed.