Skip to content
C-MDM
Menu

Android and Windows, one console

Manage every phone and PC your company owns.

C-MDM enrolls, secures and supports your Android devices and Windows PCs from one console: policies, remote support, apps, kiosk mode and location. Self-hosted, so your device data never leaves your servers.

  • Self-hosted
  • Role-based access
  • Remote support built in

Android

Company-owned phones, tablets and rugged scanners, provisioned by QR code, zero-touch or Knox Mobile Enrollment as fully managed devices.

Windows

Laptops and desktops, with a lightweight agent that runs as a Windows service and deploys with Group Policy, Intune or SCCM.

Features

Everything IT needs to run a device fleet

From the first boot to the day a device is retired, without switching tools.

How it works

From unboxing to managed in minutes

  1. 1

    Enroll

    Scan a QR code during Android setup, or run one command on a Windows PC. For a whole delivery, pre-register serials from a CSV.

  2. 2

    Apply a policy

    Pick a policy and the device enforces it within a minute, then reports what applied. Change the policy and every device follows.

  3. 3

    Support and act

    Open a remote session, push an app, reset a passcode, locate a device or wipe it, for one device or a whole group.

Security and privacy

Your devices, your servers, your rules

C-MDM runs in your own infrastructure. Credentials are shown once and never stored in plain text, and every action lands on an audit trail.

Questions

Which devices does C-MDM manage?

Android phones and tablets (Android 9 and later, enrolled as fully managed devices) and Windows PCs. Kiosk mode on Windows needs Pro, Enterprise or Education.

Where is our data stored?

On your servers. C-MDM is self-hosted: the server and its database run in your own infrastructure, and devices talk only to it.

Can we support users remotely?

Yes. Admins and operators can see and control a device’s screen from the browser. A policy decides whether the user approves each session, sessions run unattended, or remote access is off.

How do we roll it out to many devices at once?

Use a reusable enrollment token with a policy and groups, print a QR sheet for Android, deploy the Windows script with Group Policy, Intune or SCCM, and optionally pre-register serial numbers from a CSV.

Who can do what in the console?

Admins can change everything. Operators manage devices and send commands. Viewers can look but not change anything. Sensitive actions such as wipes, local accounts and policy changes are admin-only.

See C-MDM with your own devices

We’ll walk you through enrollment, policies and remote support on an Android phone and a Windows PC.