Waxell

Does an AI endpoint agent need MDM, and how does it update?

On Windows, usually not: an RMM that can push an installer works. On Mac, MDM is the clean path. Plus the update questions to ask before you roll out.

Part of: Shadow AI: how to see which AI tools your staff use

Logan Kelly8 min read

It depends on the operating system. On Windows, an AI endpoint agent that ships as a standard installer can go out through whatever you already use, an RMM (remote monitoring and management) tool, Intune or a script, so mobile device management (MDM) is not a requirement. On a Mac, the parts of the agent that watch network traffic need approvals that only MDM can grant silently, so MDM is the clean path and anything else means someone clicking "Allow" on every machine.

Updates are the second half of the question, and the one that bites later. Before you deploy, find out who owns the version on the machine: the vendor's own updater, your RMM or MDM, or both. Two systems pushing versions at once is a known source of conflict. For the wider question of seeing which AI tools staff use at all, see the guide to shadow AI.

Why Windows and Mac are different

The difference comes from how each operating system lets software watch the machine.

Windows. Many endpoint agents ship as an MSI (Microsoft Software Installer) package. Windows Installer can run an MSI with no screens at all: msiexec /i with the /qn switch, which Microsoft documents as "no UI during the installation process." Any tool that can run a command as an administrator can do that. NinjaOne, for example, documents installing MSI and EXE files on Windows endpoints, and Intune accepts an .msi as a line-of-business app. So if you can push an app and run a script from your RMM, you can usually deploy the agent without adding an MDM.

Mac. Since macOS 10.15, Apple has steered security and monitoring tools onto system extensions, including network extensions for tools that watch traffic. Apple's deployment guide says a device management service can allow an extension to load "without user interaction." Without that, macOS shows an authentication dialog that needs an administrator to approve it. Pre-approving privacy permissions, such as access to protected files, is also an MDM job: Apple's Privacy Preferences Policy Control settings list "Requires a device management service to install." Without it, the user grants each permission by hand.

Your RMM can still copy the installer onto a Mac. NinjaOne documents PKG and DMG installs on Mac endpoints. Copying the package is not the same as approving it: unless your RMM also acts as the MDM for those Macs, the extensions and permissions the agent needs still wait for someone at the machine. That is why a Mac rollout without MDM tends to stall at the first prompt.

The browser. If the agent uses a browser extension to see AI use in the browser, where people use ChatGPT, Claude and Gemini, that extension is deployed separately. Chrome's ExtensionInstallForcelist policy installs an extension "silently, without user interaction," and users cannot uninstall or turn it off through Chrome. Two limits matter. Google calls that prevention "best efforts," and the policy does not apply to Incognito mode. On macOS, an extension from outside the Chrome Web Store can only be force-installed if Chrome is managed through MDM, joined to a domain or enrolled in Chrome Enterprise Core.

Windows vs Mac at a glance

StepWindowsMac
Install the packageAny RMM, MDM or script (MSI)Any RMM or MDM (PKG)
Approve monitoring extensionsNot applicableMDM profile, or a local admin per machine
Pre-approve privacy permissionsNot applicableMDM profile, or the user per machine
Force-install the browser extensionChrome policy; non-store extensions need an Active Directory or Entra ID join, or Chrome Enterprise CoreChrome policy; non-store extensions need MDM or Chrome Enterprise Core

A worked example: a 40-seat client, mostly Windows

Say you run IT for a 40-person firm: 32 Windows laptops managed through your RMM, 8 Macs that nobody enrolled in anything. The partner wants to see which AI tools staff are using.

  1. Windows first. Package the agent's MSI and any setup script in your RMM, test it on one machine with the silent switches, then push it to a pilot group. No MDM needed.
  2. Check the Macs before you promise a date. Find out whether any MDM covers them. If none does, you have two honest options: enroll them in an MDM first, or install by hand and have a local admin approve each prompt. The second works for eight machines. It does not scale, and you will repeat some of it at removal.
  3. Push the browser extension by policy, not by asking users. On Windows, use your existing policy tool. On the Macs, this is one more thing that needs MDM or Chrome Enterprise Core.
  4. Decide who updates the agent before go-live, not after the first version bump (next section).

Palo Alto Networks' Cortex XDR documentation shows the same pattern from a security vendor's side: on a Mac, its endpoint security extension, network extension and network content filter each require user approval, and each prompt can be suppressed in an MDM profile. Removal is stricter. Palo Alto says Apple requires user approval and a password for each system extension when its agent is removed, and that in the current macOS release this cannot be suppressed in the MDM profile.

How does the agent update?

There are three common models. Ask the vendor which one they use, on each platform.

  1. The agent updates itself. The vendor pushes new versions, and the agent installs them in the background. Low effort, but you do not choose the timing.
  2. You push the new version. You upload the new installer to your RMM or MDM, and it upgrades the existing install in place. More work, but you control timing and can stage it.
  3. Both, with one switched off. Many agents can self-update, and your tooling can also push versions. Pick one owner.

Why one owner matters: Microsoft's Intune documentation describes a race condition when an app is updated by its developer and by Intune at the same time. "Both might try to enforce a version of the app," which creates a conflict. Intune's fix is an "Ignore app version" setting for self-updating apps. Whatever tool you use, the principle holds: one system decides the version.

On a Mac, ask one more question: does an update change the system extensions? Palo Alto's documentation says that if the extensions were already approved at install, there is nothing to approve during an upgrade. If a new version adds an extension, expect a new prompt on every unmanaged Mac.

Also separate the agent's software version from its content or rule updates. On July 19, 2024, CrowdStrike released a content configuration update for its Windows sensor that crashed Windows systems. Microsoft estimated that 8.5 million Windows devices were affected. In its preliminary review, CrowdStrike said it would stage these updates, starting with a canary deployment, and give customers "greater control over the delivery" of them. Ask any agent vendor whether you can delay or stage both kinds of update.

Questions to ask any AI endpoint agent vendor

  • On Windows, can it deploy through any RMM or MDM, or only named ones?
  • What does the setup script do, and does it need to run before the installer?
  • On Mac, what works without MDM, and what needs an MDM profile?
  • Which system extensions, network filters and privacy permissions does it ask for?
  • How is the browser extension installed and kept from being removed?
  • Does it update itself, wait for you to push versions, or both? Can self-updating be turned off?
  • Do updates ever add new permissions that need approval again?
  • Are rule or content updates delivered separately from software updates, and can you stage them?
  • What does removal look like on each platform?

How Waxell handles this

Waxell Endpoints follows the same split. On Windows, it deploys through any MDM or RMM: a provisioning script, then the signed MSI. On a Mac, MDM gives full coverage. A Mac RMM script gives browser and coding-agent coverage only, with no desktop-app capture.

If you deploy it, the planning advice above holds: check which client Macs sit under an MDM before you set a date. Endpoints runs on macOS (Apple Silicon, signed and notarized) and Windows (x64, OV-signed MSI). There is no Linux agent and no mobile agent.

FAQ

On Windows, usually yes, if the agent ships as an MSI or another installer that runs silently. Your RMM runs the install command and any setup script.

On a Mac, your RMM can install the package. Approving the system extensions and privacy permissions the agent needs is an MDM job, so unless your RMM also manages those Macs as an MDM, a local admin approves them on each machine.

macOS requires approval before a system extension loads and before an app gets certain privacy permissions. Apple lets a device management service grant those approvals without user interaction. Without MDM, someone must approve them at the machine.

On managed Macs with the right MDM profile, the extension prompts can be suppressed. On unmanaged Macs, expect several, for example one per extension. Windows MSI installs can run with no interface at all.

It depends on how much control you want over timing. Self-updating is less work. Pushing versions yourself lets you test on a pilot group first. Do not run both at once: Microsoft documents version conflicts when an app's own updater and Intune both enforce a version.

If the agent uses one, yes. A browser extension is installed by browser policy, such as Chrome's force-install list, not by the desktop installer. It does not cover Incognito mode, so check how the vendor handles private windows.

Sources

If you are planning an AI endpoint rollout across client machines, book a 30-minute demo and bring your platform mix.