Skip to main content

MDM-Based macOS Management in SuperOps

Learn how SuperOps combines Agent and MDM capabilities for comprehensive macOS device management.

SuperOps manages macOS devices using a hybrid approach, combining the strengths of a native macOS agent with Apple’s Mobile Device Management (MDM) framework. This allows teams to balance real-time operational control with deep OS-level enforcement and compliance.

At a high level:

  • MDM is used where Apple requires system-level authority or user-independent enforcement

  • Agent-based management is used where flexibility, third-party tooling, or custom workflows are required

  • Certain areas intentionally support both, giving administrators the ability to choose the most appropriate approach

With SuperOps’ multi-tenancy feature, you can set up and manage specific access restrictions for each client.

This article explains how macOS management is split across MDM-based controls and Agent-based controls, and where each applies. For agent-based controls, please refer to this article.

Accessing Mac Policies

To configure these settings, navigate to Settings > Policy Management. Here you will see options for both Mac Server and Mac Workstation Policies.

Note : If you are using the Advanced Policy Framework, you can create child policies under a root policy. This allows you to apply different configurations to different clients or device groups at scale.

Uploaded image 0

MDM-based controls

Certain policies in SuperOps are enforced purely through Apple MDM. These settings require OS-level authority and cannot be implemented through an agent alone. Once applied, they are enforced directly by macOS after device enrollment.

MDM Restrictions

The MDM Restrictions section covers device-level restrictions and security controls that are enforced by the operating system.

  • General: Controls core OS features like Account Modification, AirDrop, and Bluetooth settings.

  • Security: Manages authentication and lock screen settings, such as Touch ID, Auto Unlock, and password modification.

    Uploaded image 3

  • Apps: Restricts specific applications and services, such as the iBook Store, Safari autofill, or Siri.

    Uploaded image 4

  • iCloud & Apple ID Settings: Manages cloud synchronization features, including iCloud Drive, Keychain sync, and document sync.

    Uploaded image 5

MDM Configurations

These configurations rely entirely on Apple’s MDM APIs and are ideal for baseline compliance and zero-touch provisioning.

  • ADE Profile: Configures the Automated Device Enrollment experience, including supervision behavior and Setup Assistant screens. These settings are defined in advance so that when devices are enrolled through ADE, the specified options are automatically applied during onboarding.

    Uploaded image 6

  • Password: Enforces passcode requirements such as complexity, minimum length, auto-lock timing, and password rotation rules.

    Uploaded image 7

  • Network: Allows pre-configuration of Wi-Fi and proxy settings so devices can connect automatically during setup.

    Uploaded image 8

2. Mixed Model: Configurations Section

The Configurations section in SuperOps is designed as a hybrid layer where both MDM-based and Agent-based capabilities coexist. This primarily applies to software management and OS patch management.

Software Management

Software management in SuperOps is split based on how applications are distributed and managed on macOS.

Apps and Books (MDM-based)

  • Uses Apple Business Manager and Apple’s Apps and Books framework

  • Applications are assigned and installed via MDM

  • Ideal for App Store and VPP-managed applications

  • Fully aligned with Apple’s recommended deployment model

Homebrew and Custom Software (Agent-based)

  • Managed through the SuperOps macOS agent

  • Supports Homebrew packages, non-App Store applications, and custom installers or scripts

  • Provides greater flexibility for third-party tools and internal software

Note: If an application is installed via Homebrew and the same application is also available through Apps and Books, the Apps and Books version will take precedence. In this case, the app will be managed through MDM and treated as a licensed application.

OS Patch Management

MDM-managed patching

  • Uses Apple’s native software update mechanisms

  • Ideal for enforcing macOS updates and Rapid Security Responses (RSR)

  • Best suited for newer macOS versions and compliance-driven environments

Agent-managed patching

  • Driven by the SuperOps macOS agent

  • Enables granular scan schedules, approval workflows, and controlled deployment windows

  • Useful for MSPs that require operational flexibility and phased rollouts

Both approaches can be used together, ensuring patching does not disrupt business continuity while maintaining security and compliance

Agent-managed features

All remaining policy features not explicitly listed under MDM controls continue to be managed through the SuperOps agent. These features operate as documented in the agent-specific articles.

Summary

SuperOps embraces the realities of Apple’s ecosystem by using the right control mechanism for each capability:

  • MDM Restrictions and Core Configurations
    Fully MDM-based for security, compliance, and zero-touch provisioning

  • Software Management
    Hybrid approach
    MDM for App Store applications
    Agent for Homebrew and custom software

  • Patch Management
    Hybrid approach
    MDM for native OS enforcement
    Agent for operational flexibility

  • Monitoring and operational workflows
    Agent-based for real-time visibility and control

Did this answer your question?