Enrollment configuration in the RubusNode console.
Enrollment matched to the device, not a single flow
GMS-certified devices enroll through Android Enterprise with Android Device Policy, using QR code or zero-touch (OEM/reseller pre-registration for unattended first-boot enrollment). The RubusNode app is installed alongside as a managed companion.
- QR and provisioning-QR enrollment for supervised setup
- Zero-touch enrollment for unattended, at-scale rollout
- Fully managed and dedicated-device modes through Android Enterprise
- Shared device pool enrollment for check-in/check-out fleets
Capability-aware from the first check-in
RubusNode detects what a device can actually support at enrollment time — OEM, Android version, and management mode — and gates policy and command availability accordingly, so operators never issue a command a device cannot execute.
Lifecycle and inventory, not just a device list
Every enrolled device carries full inventory (model, OS, IMEI, policy assignment, trust signals) and lifecycle state (active, retiring, wiped, recovered), with recovery and inventory evidence available for audit.
- Full device inventory with policy and trust context
- Lifecycle states from enrollment through retirement
- Recovery workflows for lost, wiped, or reassigned devices
Common questions
What is Android MDM?
Android MDM (mobile device management) is the practice of centrally enrolling, configuring, monitoring, and controlling Android devices from a single management console. It works through OS-level APIs — Device Owner mode and Android Enterprise — that let a management platform enforce policies, distribute apps, and issue commands that regular apps cannot.
Which Android devices does RubusNode support?
GMS-certified Android devices, managed through Android Enterprise with Android Device Policy. Devices without Google Mobile Services, including AOSP builds, are not supported. Where a capability depends on the OEM, Android version, or management mode, the console shows that per device.
How does Android MDM differ from UEM?
UEM (unified endpoint management) manages Windows, macOS, iOS, and Android from one console — breadth over depth. Android-only MDM like RubusNode puts every engineering hour into Android specifically: enrollment edge cases, kiosk behavior, OEM and Android-version differences, and new Android Enterprise APIs as they ship. For Android-majority fleets, that depth usually covers more of what the fleet needs.
What happens if a device loses GMS availability after enrollment?
A device without GMS falls outside Android Enterprise management. RubusNode does not keep managing it; it reports the device as unsupported or unavailable instead of silently failing.
Can devices move between shared pools and dedicated assignment?
Yes — shared device pool assignment and dedicated ownership are both lifecycle states RubusNode tracks explicitly.
What enrollment methods does Android MDM support?
RubusNode supports Android Enterprise QR code enrollment, zero-touch enrollment (OEM/reseller pre-registration for unattended first-boot), and shared device pool enrollment for check-in/check-out fleets. Every path enrolls GMS-certified devices with Android Device Policy as the device policy controller.
See how RubusNode fits your endpoint fleet.
Get in touch about this capability and the rest of the platform.