ESUMDM

Mass Deployment Guide for Jamf Pro

Table of Contents

Introduction

ESUMDM leverages Configuration Profiles to define the functionality and user experience of the tool. Administrators should begin by building Computer Group scopes, then define customizations with Configuration Profiles, and lastly install the ESUMDM software. Use the following guide to deploy according to best practices.


Creating Scopes

Scoping ESUMDM objects in Jamf Pro is best done via Computer Smart Groups. Minor versions of macOS updates (e.g. 15.7.2) are defined on a per-release basis for each major version of macOS (e.g. 15.x), so EDUMDM preferences need to be enforced accordingly.

Smart Computer Groups

Administrators should begin by creating one Smart Group for each major version of macOS.


Configuration Profiles

The ESUMDM Managed Preference Domain is:

io.enterprisesoftwareupdate.esumdm

Administrators may choose to:

A) Deploy a Single Configuration Profile to each major version of macOS, or

B) Deploy Multiple Configuration Profiles to take a layered approach, deploying common settings with a single Configuration Profile to all Macs, then define and deploy target minor versions scoped to each major version of macOS (target_minos_version).

Configuration Profile Example

This example Configuration Profile includes a minimum configuration required to customize ESUMDM. Refer to the Preference Key Reference for specific details about each setting.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>mode</key>
	<string>macos_update</string>
	<key>target_minos_version</key>
	<string>27.0.1</string>
	<key>deadline</key>
	<date>2026-12-31T12:00:00Z</date>
</dict>
</plist>


Preference Key Reference


All preference keys available to configure esumdm are published here.

https://floatingorchard.github.io/esu-docs/esumdm/main/managed-preferences.html

Policies

ESUMDM activates by reading the Managed Preferences deployed via Configuration Profile and prompts users accordingly. To deploy via Jamf Pro, Administrators should first scope the Configuration Profile, then deploy the ESUMDM installer .pkg via a Jamf Pro Policy.

Below is an example of a Mass Deployment Policy.

via Mass Deployment Policy

Create a New Policy (Computers > Policies) with the name Install ESUMDM Once. In the below example, we’ll scope the policy to All Computers, however admins may choose to leverage a dedicated Smart Group containing Macs without the ESUMDM installer.

Options

  • General

    • Display Name: Install ESUMDM Once

    • Trigger: Recurring Check-in

    • Frequency: Once Per Computer

  • Packages

    • Add the latest version of ESUMDM
      (refer to Jamf Pro documentation on uploading packages)

Scope

  • All Computers