What is mdmclient?

mdmclient is the MDM client. Its man page says it receives profiles and commands from a management server after a user enrols by installing a management profile.

Fix this with your agentCopies a prompt for Claude Code, Codex or any agent that can use Terminal.

I want to know what mdmclient is doing on my Mac and whether its network use is normal. Read https://kilobat.app/processes/mdmclient.md and work through it with me. Install the Kilobat CLI if it’s missing: brew install seifip/kilobat/kilobat. Run the guide’s Terminal and kilobat checks yourself and tell me what you find. List the steps only I can do. Ask before you change any setting.

Process: mdmclientMade by AppleApplies to: Checked on macOS 27.2.Checked: 7 November 2026

Short answer

Part of macOS. Its man page says it talks to a Mobile Device Management server. It works for an organisation that manages the Mac.

Don’t block

Do not block it on a managed Mac. Your admin cannot manage the device, and security settings may change.

Path
/usr/libexec/mdmclient
launchd label
com.apple.mdmclient.daemon.runatboot com.apple.mdmclient.daemon com.apple.mdmclient.agent
Signing identifier
com.apple.mdmclient

What it is

The program is /usr/libexec/mdmclient, signed by Apple. Three launchd jobs use it: com.apple.mdmclient.daemon.runatboot, com.apple.mdmclient.daemon and the user agent com.apple.mdmclient.agent.

The man page says it is used internally and is part of Managed Client. It warns that all arguments are private and can change without notice.

The daemon registers push services with production and development names, and one for DEP. The agent starts on events about cloud configuration and Managed Apple Account changes.

Apple's deployment guide lists MDM topics: configuring devices to work with APNs, several enrolment methods, declarative device management and managed app distribution.

Apple's host list has a Device management section. It names *.push.apple.com, deviceenrollment.apple.com, mdmenrollment.apple.com, iprofiles.apple.com and gdmf.apple.com.

Why it uses the network

  • Push from the management server. The push service names tie the daemon to APNs. Apple lists APNs configuration for MDM.
  • Check-ins and commands. The man page says it receives profiles and commands from the server.
  • Automated enrolment. The agent reacts to cloud configuration events. Apple lists enrolment hosts under Device management.

How much is normal

Apple gives no figure for its traffic.

Check-ins with a server are expected to be small and periodic. Apple does not state this.

Large flows come from the apps or profiles that your admin pushes.

When it uses a lot, and why

  • Managed app or profile installs. Apple lists managed app distribution as an MDM topic.
  • A new enrolment. The first check-in downloads configuration.

Is it safe to block?

Don’t block

Do not block it on a managed Mac. Your admin cannot manage the device, and security settings may change.

What breaks if you block it

  • Configuration profiles and commands from your organisation stop arriving.
  • Managed apps may not install or update.
  • Compliance checks by your admin may fail.

Blocking means a firewall rule that refuses its connections. Don’t quit or disable a macOS process to save data: macOS starts it again, and other features depend on it.

Reduce its use

  1. Ask your IT admin if the Mac is managed.

  2. Open System Settings and search for Profiles to see installed profiles.

  3. On a hotspot or a capped plan, turn on Low Data Mode. Choose Apple menu › System Settings › Wi-Fi. Click Details next to the network, then turn on Low Data Mode.

  4. Do not quit mdmclient in Activity Monitor. macOS starts it again.

See how much it uses

  1. Open Activity Monitor from Applications › Utilities. Click Network.

  2. Type mdmclient in the search field. The Sent Bytes and Rcvd Bytes columns show what it moved since it started.

  3. In Terminal, watch only this process. Press d to show the change per second, and q to quit.

    nettop -p 'mdmclient' -P

With Kilobat

  1. In the Kilobat app list, search for mdmclient. Its row shows the live rate and what it moved today.

  2. In Connections, click the ⓘ button on one of its rows. The popover shows this page’s short answer, without going online.

  3. In Terminal, ask the same question. Add --json for scripts and agents.

    kilobat explain 'mdmclient'
  4. Show its traffic over one day.

    kilobat bandwidth 'mdmclient' day
  5. Through MCP, an AI agent asks explain_connection with the process name. It gets the same facts.

The live view and the explanations are free. History in the app needs Kilobat Pro. Blocking needs Pro and the network filter: see the network filter, Protection and the hotspot data saver.

Hosts it contacts

Apple and the maker document these hosts for this feature. A process can also contact others; Kilobat’s Connections tab shows what it actually opens on your Mac.

What isn’t documented

Apple's documentation checked does not say which hosts mdmclient contacts. The host list names hosts per feature.

Apple warns that the command's output can change without notice.

Apple does not describe how often it checks in.

Questions

Is my Mac managed if mdmclient runs?

Not necessarily. The launchd jobs are part of macOS. A management profile decides whether it talks to a server, as the man page says.

What does mdmclient send?

Apple's documentation checked does not say.

Is mdmclient a virus?

No. It is signed by Apple and has a man page.

Sources

Checked on 7 November 2026.