DDM OS Reminder (5.2.0)

Review the following before rolling out version 5.2.0.

• MinimumDiskFreeGB sample default raised from 26 to 35: A fully staged macOS update has been observed at 26.60 GB, so 26 no longer leaves room to install. Existing deployed plists and Configuration Profiles keep their current value, and assemble.zsh keeps an imported MinimumDiskFreeGB; raise it manually if yours is still 26. The script default (999) and 0 (disabled) are unchanged.
• New low-battery warning: When a Mac is running on its internal battery below MinimumBatteryPercentage (0–100; script and sample default 50; 0 disables), the dialog adds BatteryWarningMessage through the new {batteryWarningMessage} placeholder, asking the user to plug in. Desktops, Macs on AC or UPS power, and Macs whose battery charge can’t be read never show it. It is messaging only: PastDeadlineRestartBehavior Prompt / Force eligibility and timing are unchanged, and the warning also appears in the restart dialogs because a restart does not charge the battery.
  • Deploy the updated dor.zsh before, or together with, any Configuration Profile which contains {batteryWarningMessage}. Older scripts replace only the placeholders they know, so the dialog would show the literal text {batteryWarningMessage}.
  • Customized templates need the placeholder added by hand. Add {batteryWarningMessage} to customized Message, AggressiveModeMessage, and PreDeadlineThresholdMessage (after {diskSpaceWarningMessage}, before {supportAssistanceMessage}), and to PastDeadlinePromptMessage and PastDeadlineForceMessage (at the end), plus their Localized_<code> variants. Without it, the warning never appears. When assemble.zsh imports a prior .plist / .mobileconfig, it prints an ℹ️ line listing each imported template which lacks the placeholder (production builds repeat the list under Recommended review items); it never rewrites admin-authored copy.
  • Non-English battery strings are new and would benefit from native-speaker review.
• Client-side log lines changed: Scripts, Extension Attributes, or log searches keyed on Normal DDM resolver result, Resolver suppression summary, MDM fallback requirement, Version Comparison Result: No DDM enforcement log entry found, Installed macOS Version, Resolved DDM declaration, or Software Update handoff must be updated; key on DDM update check:, status=, No reminder shown:, Currently installed macOS, Opening Software Update, and DDM Emergency Fallback instead. Log line format is unchanged. (The bundled Jamf Pro Extension Attributes are not affected.)

Review the following before rolling out version 5.1.0.

• Scheduler state survives redeployment: All and Script keep /Library/Management/<rdnn>/dor-state.plist, so already-delivered pre-deadline threshold reminders and same-day Update Tonight suppression are not repeated after a redeploy. Only NextScheduledReminder is cleared, so the refreshed heartbeat still runs promptly; only Uninstall removes the file (matching the dor-aggressive-kill support kill switch).
• Low-disk-space warning now uses a fixed GB threshold: MinimumDiskFreeGB (sample default 26, raised to 35 in 5.2.0; 0 disables) replaces MinimumDiskFreePercentage. The warning appears when available space (the same Finder-aligned value shown in the infobox) is below that many GB, regardless of disk size.
• MinimumDiskFreePercentage is deprecated: When MinimumDiskFreeGB is not set, an existing MinimumDiskFreePercentage value is still honored and logged at [WARNING]; when both are set, MinimumDiskFreeGB wins. Support for MinimumDiskFreePercentage will be removed in 6.0.0. Re-run assemble.zsh with your prior .plist to generate configuration with MinimumDiskFreeGB; the import reports the replacement (for example, Replaced deprecated MinimumDiskFreePercentage (10%) with MinimumDiskFreeGB (35 GB, sample default)) and, in production builds, lists MinimumDiskFreeGB under Recommended review items.

Review the following before rolling out version 5.0.0; no preference keys, defaults, or precedence rules changed.

• Self-extracting wrapper now forwards MDM script parameters: Wrappers generated by Resources/createSelfExtracting.zsh (2.4.0) pass Parameters 4–6 to the deployer. Values previously ignored on wrapper-based policies (reset mode, Uninstall, DDM Emergency Fallback) now take effect, so audit those policy parameters before rollout.
• swiftDialog path: The runtime and deployer invoke /Library/Application Support/Dialog/Dialog.app/Contents/MacOS/dialogcli; the runtime, deployer, dor-starter.zsh, and LaunchDaemon no longer include /usr/local or /usr/local/bin in PATH.
• Aggressive-mode kill switch survives redeployment: All and Script keep /Library/Management/<rdnn>/dor-aggressive-kill; only Uninstall removes it.
• Support assistance text (from 4.2.1): InfoButtonText=hide no longer hides {supportAssistanceMessage}; set HideSupportAssistanceMessage=true if you relied on the old behavior. Version 5.0.0 is the first stable release with this change.

Version 3.0.0 (and later) of assemble.zsh can import supported settings from a previously generated DDM OS Reminder .plist (or, 🆕 starting with 5.2.0, a hand-edited .mobileconfig), infer the RDNN and deployment lane (dev, test, prod), and generate a matched assembled script, organizational .plist, and unsigned .mobileconfig in a single pass.

Prior .mobileconfig import supports unsigned and CMS-signed profiles. The profile must contain exactly one DDM OS Reminder (*.dorm) preferences payload; Forced settings are preferred, and missing, multiple, or ambiguous payloads fail with a clear ❌ message. A ⚠️ warning flags a profile whose *.dorm domain disagrees with the RDNN in ScriptLog. Supply only one prior .plist or .mobileconfig.

zsh assemble.zsh drag-and-drop-prior.plist

zsh assemble.zsh drag-and-drop-prior.mobileconfig

zsh assemble.zsh '/Users/dan/Downloads/DDM-OS-Reminder-5.1.0/Artifacts/us.snelson.dorm-2026-10-13-073608.plist'

=====================================================================================
🧩 Assemble DDM OS Reminder (5.2.0)
=====================================================================================

📍 Full Paths:

        Reminder Dialog: ~/Downloads/DDM-OS-Reminder-main/reminderDialog.zsh
LaunchDaemon Management: ~/Downloads/DDM-OS-Reminder-main/launchDaemonManagement.zsh
      Working Directory: ~/Downloads/DDM-OS-Reminder-main
    Resources Directory: ~/Downloads/DDM-OS-Reminder-main/Resources

🔍 Checking Reverse Domain Name Notation …

    Reminder Dialog (reminderDialog.zsh):
        reverseDomainNameNotation = org.churchofjesuschrist
        organizationScriptName    = dorm

    LaunchDaemon Management (launchDaemonManagement.zsh):
        reverseDomainNameNotation = org.churchofjesuschrist
        organizationScriptName    = dor


⚠️  Prior plist is missing version metadata; continuing with documented 2.2.0+ compatibility on a best-effort basis
📥 Prior plist provided via command-line argument: '/Users/dan/Downloads/DDM-OS-Reminder-5.1.0/Artifacts/us.snelson.dorm-2026-10-13-073608.plist'

ℹ️  Importing supported values from: /Users/dan/Downloads/DDM-OS-Reminder-5.1.0/Artifacts/us.snelson.dorm-2026-10-13-073608.plist
🔎 Inferred RDNN from prior plist: 'us.snelson'

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🏷️  Using 'us.snelson' as the Reverse Domain Name Notation
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━


ℹ️  Prior plist supplied; skipping IT support, branding and restart policy prompts.


━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🛠️  Interactive Configuration
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🌐 Localization Artifact Mode
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Localization Output (Full / [M]inimal / [S]elected languages) [Full] (or ‘X’ to exit): S
Languages CSV (for example: en,fr or fr_CA,ja) [en,fr] (or ‘X’ to exit): en,fr

ℹ️  Localization mode set to: language subset: en,fr

🌐 Artifact Localization: language subset: en,fr


━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🚦 Select Deployment Mode:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  1) 🧪 Development - Keep placeholder text for local testing
  2) 🔬 Testing     - Replace placeholder text with 'TEST' for staging
  3) 🚀 Production  - Remove placeholder text for clean deployment

  [Press ‘X’ to exit ❎]

Specify Deployment Mode [1/2/3]: 3

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📦 Deployment Mode: prod
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🔧 Inserting reminderDialog.zsh into launchDaemonManagement.zsh  …

✅ Assembly complete [2026-10-20-111012]
   → Artifacts/ddm-os-reminder-assembled-2026-10-20-111012.zsh

🔁 Updating reverseDomainNameNotation to 'us.snelson' in assembled script …

🔍 Performing syntax check on 'Artifacts/ddm-os-reminder-assembled-2026-10-20-111012.zsh' …
    ✅ Syntax check passed.

🗂  Generating LaunchDaemon plist …
    🗂  Creating us.snelson.dorm plist from /Users/dan/Downloads/DDM-OS-Reminder-main/Resources/sample.plist …

    🔧 Updating internal plist content …
    🔓 Production mode: removing placeholder text for clean deployment
    🔧 Importing supported values from prior plist …
    ℹ️  Skipping 211 imported localized key(s) outside selected artifact mode (for example: "AggressiveModeMessageLocalized_de", "AggressiveModeMessageLocalized_es", "AggressiveModeMessageLocalized_it", "AggressiveModeMessageLocalized_ja", "AggressiveModeMessageLocalized_nl")
    ℹ️  Preserving imported ScriptLog: /var/log/us.snelson.log
    ℹ️  Imported templates without {batteryWarningMessage}; the low-battery warning will not appear in them until you add it:
        Message (+2 localized), AggressiveModeMessage (+2 localized), PreDeadlineThresholdMessage (+2 localized), PastDeadlinePromptMessage (+2 localized), PastDeadlineForceMessage (+2 localized)
    🌐 Removed 217 localized key(s) from generated plist
   → Artifacts/us.snelson.dorm-2026-10-20-111012-prod.plist

🧩 Generating Configuration Profile (.mobileconfig) …
   → Artifacts/us.snelson.dorm-2026-10-20-111012-prod-unsigned.mobileconfig

🔍 Performing syntax check on 'Artifacts/us.snelson.dorm-2026-10-20-111012-prod-unsigned.mobileconfig' …
    ✅ Profile syntax check passed.

🔁 Renaming assembled script …

🔁 Updating scriptLog path based on RDNN …

🏁 Done.

📦 Deployment Artifacts:
         Assembled Script: Artifacts/ddm-os-reminder-us.snelson-2026-10-20-111012-prod.zsh
     Organizational Plist: Artifacts/us.snelson.dorm-2026-10-20-111012-prod.plist
    Configuration Profile: Artifacts/us.snelson.dorm-2026-10-20-111012-prod-unsigned.mobileconfig

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
⚠️  Important Next Steps:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  Production Artifacts Generated:
    - All placeholder text removed (clean output)
    - Localization artifact mode: language subset: en,fr
    - Supported configuration values imported from prior plist
    - Prior plist: /Users/dan/Downloads/DDM-OS-Reminder-5.1.0/Artifacts/us.snelson.dorm-2026-10-13-073608.plist
    - ScriptLog resolved to '/var/log/us.snelson.log'

  Recommended review items:
    - Support team name, phone, email, website
    - DailyReminderTimes baseline schedule
    - AggressiveModePastDeadlineHours and AggressiveModeFrequencyMinutes
    - Add {batteryWarningMessage} to imported templates: Message (+2 localized), AggressiveModeMessage (+2 localized), PreDeadlineThresholdMessage (+2 localized), PastDeadlinePromptMessage (+2 localized), PastDeadlineForceMessage (+2 localized)
    - Localization key set matches intended artifact mode
    - Imported ScriptLog path and any carried-forward KB/help visibility
    - Organization overlay icon URLs
    - Button labels and dialog messages

  Files to review:
    - Artifacts/us.snelson.dorm-2026-10-20-111012-prod.plist
    - Artifacts/us.snelson.dorm-2026-10-20-111012-prod-unsigned.mobileconfig

=====================================================================================

As always, carefully review each deployment artifact and distribute the appropriate files to a single test Mac via your MDM. (See Steps 2.2 through 2.4.)

Author’s Highly Opinionated Thought: There are enough changes since version 2.1.0 (and earlier) that it’s best to just start-from-scratch — first uninstalling earlier versions — rather than attempting to upgrade to the latest version.

AI-generated documentation is available in the GitHub repository

Diagrams: Comprehensive, AI-generated visual diagrams to augment this documentation

1. Executive Overview: High-level lifecycle view for Mac Admins who need the big picture first
2. System Architecture: Complete ecosystem overview from development through runtime execution
3. Runtime Decision Tree: Complete decision logic executed each time the LaunchDaemon triggers
4. Deadline Timeline: Visual representation of how user experience changes as deadline approaches
5. Deployment Workflow: Step-by-step guide for administrators deploying DDM OS Reminder
6. Configuration Hierarchy: 3-tier preference system showing precedence rules
7. Configuration Reference: Complete reference for all configurable preferences

A number of Mac Admin quality-of-life scripts are available in the GitHub repository

Scripts

1. The assemble.zsh script creates combined, deployable artifacts of your customized scripts
2. Create Self-extracting encodes the most recently assembled script for easier deployment with some MDMs; version 2.4.0 extracts into a private mktemp -d directory and forwards MDM Script Parameters 4–6 (real-world testing and feedback welcome)
3. Create .plist creates .plist and .mobileconfig, based on your customizations to reminderDialog.zsh (real-world testing and feedback welcome)
4. Extension Attributes were created for and tested on Jamf Pro and can most likely be adapted for other MDMs
5. Jamf-getDDMstatusFromCSV.zsh (version 1.4.0 keeps API credentials and bearer tokens out of process arguments); See: DDM Status from .CSV (1.3.0)
6. Diagnose client state (diagnoseReminderState.zsh) reads uploaded client files and prints a redacted fact sheet of effective settings, install.log declaration evidence, and the last run’s recorded resolver result; it writes nothing and pairs with the AI Diagnose Skill. 🆕 Version 1.4.0 reads both new and pre-5.2.0 log lines, lists the runtime Battery: and Disk space: lines, and shows each run’s No reminder shown: or [QUIT] reason

Special thanks to Max Sundell for his write-up

Create and deploy a macOS configuration profile (.mobileconfig)

Beginning with version 5.1.0, the diagnose-client-state agent skill helps answer the most common support question — “Why didn’t my user see a reminder?” (or “Why did they see one?”) — from files uploaded from the affected Mac, without live access to that Mac.

The skill is read-only: it never writes preferences, scheduler state, LaunchDaemons, or logs on the affected Mac, and the only file it may create is the redacted findings report — and only after you confirm a path. (Issue #147)

Where it lives

The canonical instructions live at Resources/skills/diagnose-client-state/SKILL.md and pair with the read-only Resources/diagnoseReminderState.zsh fact-sheet helper. Symbolic links from .claude/skills, .agents/skills, and .github/skills let skill-aware coding agents (Claude Code, Codex and other AGENTS.md-compatible tools, and GitHub Copilot) discover it automatically when you open your local copy of the repository.

1. Collect files from the affected Mac

Gather the three required files — plus any optional files you have — using the following as an example, substituting your organization’s Reverse Domain Name Notation and your own admin account:

• Required: client-side log (/var/log/<rdnn>.log), /var/log/install.log (a full copy is fine; analysis uses the last 4,000 lines), and whichever client-side preferences exist (/Library/Managed Preferences/<rdnn>.dorm.plist and/or /Library/Preferences/<rdnn>.dorm.plist)
• Optional: dor-state.plist, dor-fallback-declaration.plist, SoftwareUpdateDDMStatePersistence.plist, /Library/LaunchDaemons/<rdnn>.dor.plist, and whether dor-aggressive-kill existed

###
# Collect DDM OS Reminder client files
#
# Run in an elevated Terminal session on the affected Mac
###

rdnn="org.churchofjesuschrist"
adminUser="dan"
uploadDir="/Users/${adminUser}/Desktop/dor-${rdnn}-$(date +%Y-%m-%d)"

mkdir -p "${uploadDir}"

# Required
cp -v "/var/log/${rdnn}.log" "${uploadDir}/"
cp -v /var/log/install.log "${uploadDir}/"
cp -v "/Library/Managed Preferences/${rdnn}.dorm.plist" "${uploadDir}/managed.dorm.plist" 2>/dev/null
cp -v "/Library/Preferences/${rdnn}.dorm.plist" "${uploadDir}/local.dorm.plist" 2>/dev/null

# Optional
cp -v "/Library/Management/${rdnn}/dor-state.plist" "${uploadDir}/" 2>/dev/null
cp -v "/Library/Management/${rdnn}/dor-fallback-declaration.plist" "${uploadDir}/" 2>/dev/null
cp -v /var/db/softwareupdate/SoftwareUpdateDDMStatePersistence.plist "${uploadDir}/" 2>/dev/null
cp -v "/Library/LaunchDaemons/${rdnn}.dor.plist" "${uploadDir}/" 2>/dev/null
ls -l "/Library/Management/${rdnn}/dor-aggressive-kill" 2>/dev/null && echo "dor-aggressive-kill: yes" || echo "dor-aggressive-kill: no"

chown -R "${adminUser}" "${uploadDir}"

2. Run the skill

1. Open your local copy of the DDM OS Reminder repository in a skill-aware coding agent
2. Invoke /diagnose-client-state (or simply ask the agent why a reminder did not appear) and attach the collected files; the skill asks for any required file which is missing, and treats a single unlabeled .plist as valid without inventing the other preference layer
3. When zsh and PlistBuddy are available, the agent runs diagnoseReminderState.zsh to extract facts — preference ranges, plist key names, and install.log source-type markers — then interprets them against the runtime rules in reminderDialog.zsh

Prefer to skip the agent? Run the helper directly for the same redacted fact sheet (printed to stdout; nothing is written):

zsh Resources/diagnoseReminderState.zsh \
    --client-log /path/to/<rdnn>.log \
    --install-log /path/to/install.log \
    --plist /path/to/<rdnn>.dorm.plist

Label preference layers when both exist, and add any optional files you collected:

zsh Resources/diagnoseReminderState.zsh \
    --client-log /path/to/<rdnn>.log \
    --install-log /path/to/install.log \
    --managed-plist /path/to/managed.dorm.plist \
    --local-plist /path/to/local.dorm.plist \
    --state-plist /path/to/dor-state.plist \
    --fallback-plist /path/to/dor-fallback-declaration.plist \
    --persistence-plist /path/to/SoftwareUpdateDDMStatePersistence.plist \
    --launch-daemon-plist /path/to/<rdnn>.dor.plist \
    --aggressive-kill no

3. Review the report

The skill writes a Markdown report in the following order:

1. Verdict in one sentence, from the last run: resolver suppression (missing, conflict, noMatch, invalidVersion), fallback selected, already compliant, outside the display window, quiet period, Update Tonight, meeting or Focus delay, threshold or aggressive dialog, dialog shown, fatal setup error, or not enough evidence
2. Files received — and files which were not in the upload
3. Identity: RDNN, script version, and installed macOS from the log
4. Effective settings for decision-critical keys, with source and any rejected raw value
5. DDM evidence from install.log, with timestamps
6. What the last run did, quoted from the (redacted) client log
7. Whether the client log and install.log agree
8. Likely cause and operator next steps
9. A reminder that the report is redacted and raw uploads should stay out of public issues

Rules the skill follows

• The client log’s DDM update check: line (5.2.0 and later) or Normal DDM resolver result: line (earlier) is what that Mac did, quoted along with any No reminder shown: and Next step: lines; install.log explains that result, and the skill never invents a different resolver status. When the two disagree, it says so and quotes both.
• Without SoftwareUpdateDDMStatePersistence.plist, install.log candidates are not dropped as uncorroborated; client-log warnings about uncorroborated trust are quoted when present.
• A quiet heartbeat is not automatically a failure: dor-starter.zsh exits 0 without a new run when NextScheduledReminder is FALSE, is still in the future, or dor.pid names a live process. If dor-state.plist was not uploaded, the report says so.
• --aggressive-kill yes means dor-aggressive-kill existed, so aggressive mode uses the normal cadence until that file is removed.
• The skill matches reminderDialog.zsh 5.2.0; when the client log’s dorm (<version>): differs, the checklist is labeled best-effort.

Privacy: The helper redacts usernames, first names, /Users/… paths, install.log computer names, and labeled serial numbers, while keeping RDNN, versions, deadlines, and preference keys.

Attach only the redacted report to a GitHub issue or Slack thread; keep the raw uploads and the fact sheet out of public channels. After the report, the skill offers to save it as ddm-os-reminder-<rdnn>-<YYYY-MM-DD>.md next to your uploads (outside the repository), and writes nothing until you confirm the path.

Maintainers: Re-check the bundled fixtures (compliant, conflict, invalid-times, managed-over-local, missing) after changing the helper or skill:

zsh Resources/skills/diagnose-client-state/check-fixtures.zsh

Conduct the following troubleshooting steps in an elevated Terminal session, on a test Mac in-scope of a pending Declarative Device Management-enforced macOS update from your MDM server.

System Settings > General > Device Management > MDM Profile > Device Declarations

No live access to the affected Mac? Collect its files and use the 4.4 AI Diagnose Skill instead.

1. Core Functionality

1. Define a rdnn variable to aid in completing the following steps:

rdnn="org.churchofjesuschrist"

2. Start monitorRemoteSession.zsh for one live view of the heartbeat LaunchDaemon, runtime files, scheduler state, PID, matching processes, aggressive-mode kill switch, and recent logs:

zsh Resources/monitorRemoteSession.zsh --rdnn "${rdnn}" --watch 5

3. Review the client-side LaunchDaemon for any obvious issues:

plutil -p /Library/LaunchDaemons/"${rdnn}.dor.plist"

launchctl print system/"${rdnn}.dor" 2>/dev/null | grep -E 'state =|last exit code =|program =|path ='

4. Confirm the deployed runtime assets exist and review scheduler state (for example, NextScheduledReminder and, when Update Tonight suppression is active, UpdateTonightSuppressionUntil); beginning with version 5.1.0, dor-state.plist persists across All and Script redeployments, which clear only NextScheduledReminder:

ls -l /Library/Management/"${rdnn}"/dor.zsh
ls -l /Library/Management/"${rdnn}"/dor-starter.zsh
ls -l /Library/Management/"${rdnn}"/dor-state.plist
ls -l /Library/Management/"${rdnn}"/dor.pid

plutil -p /Library/Management/"${rdnn}"/dor-state.plist

5. Review the client-side managed preferences .plist for any obvious issues:

plutil -lint /Library/Managed\ Preferences/"${rdnn}".dorm.plist

plutil -p /Library/Managed\ Preferences/"${rdnn}".dorm.plist

6. Review the script’s log for warnings and errors:

scriptLog=$(/usr/libexec/PlistBuddy -c 'Print :ScriptLog' "/Library/Managed Preferences/${rdnn}.dorm.plist" 2>/dev/null || /usr/libexec/PlistBuddy -c 'Print :ScriptLog' "/Library/Preferences/${rdnn}.dorm.plist" 2>/dev/null || echo "/var/log/${rdnn}.log")

grep -nE '^(dor|dorm) \([^)]*\): .* \[(WARNING|ERROR|FATAL ERROR)\]' "${scriptLog}"

# 5.2.0: DDM update check outcome, and why no reminder was shown (with next step)
grep -nE 'DDM update check:|No reminder shown:|Next step:' "${scriptLog}"

# 5.2.0: low-battery and low-disk-space evaluation
grep -nE 'Battery:|Disk space:|MinimumDiskFree|MinimumBattery' "${scriptLog}"

7. Review the /var/log/install.log for relevant DDM and Software Update entries:
   • Space : next page
   • Arrow keys : scroll horizontally or vertically
   • q : quit

tail -n 1000 /var/log/install.log | grep -nE 'declarationFromKeys\]: Falling back to default applicable declaration|Found DDM enforced install \(|EnforcedInstallDate:|requestedPMV=|MADownloadNoMatchFound|pallasNoPMVMatchFound=true|No available updates found\. Please try again later\.|setPastDuePaddedEnforcementDate|Removed [0-9]+ invalid declarations|No updates found for DDM to enforce|Found product with requested PMV|Armed DDM activity scheduler|SUOSUInstallTonightManager|SUOSUScheduler' | less -S

8. Beginning with version 5.0.0, confirm the active softwareupdated DDM declarations used to corroborate install.log candidates, then check the script’s log for corroboration warnings:

plutil -p /var/db/softwareupdate/SoftwareUpdateDDMStatePersistence.plist | grep -E 'TargetOSVersion|TargetLocalDateTime'

grep -nE 'softwareupdate DDM state|absent from softwareupdate DDM state' "${scriptLog}"

9. To more easily validate the DDM declaration parsing logic, run the following Jamf Pro Extension Attribute scripts locally and confirm the reported date and version match the pending DDM-enforced macOS update from your MDM server (both apply the same softwareupdated corroboration as the runtime):
   • Resources/JamfEA-Pending_OS_Update_Date.zsh
   • Resources/JamfEA-Pending_OS_Update_Version.zsh

root@XDT8675309 DDM-OS-Reminder-main # zsh Resources/JamfEA-Pending_OS_Update_Date.zsh
<result>2026-07-14 18:00:00</result>

root@XDT8675309 DDM-OS-Reminder-main # zsh Resources/JamfEA-Pending_OS_Update_Version.zsh
<result>26.5.2</result>

---

When troubleshooting user-interface issues, leverage swiftDialog’s dialogcli binary and your client-side managed preferences .plist values.

2. User-interface Issues

1. Confirm dialogcli is installed and working as expected (beginning with version 5.0.0, DDM OS Reminder invokes swiftDialog from its app bundle, not /usr/local/bin/dialog):

"/Library/Application Support/Dialog/Dialog.app/Contents/MacOS/dialogcli" --title "Dialog Test" --message "swiftDialog is installed and can render a basic dialog." --icon /System/Library/CoreServices/Finder.app --infotext

2. Define a rdnn variable to aid in completing the following steps:

rdnn="org.churchofjesuschrist"

3. Use Resources/reminderDialogPreferenceTest.zsh when you want to validate deployed preferences:

zsh Resources/reminderDialogPreferenceTest.zsh --rdnn "${rdnn}"

# 5.2.0: preview the low-battery warning on a desktop or AC-powered Mac
zsh Resources/reminderDialogPreferenceTest.zsh --rdnn "${rdnn}" --battery-percentage 15