macOS 11 machines seem to be ignoring the Jamf configuration profile
We are testing SUPER with various versions of macOS, and a consistent one we're seeing is that SUPER seems to be ignoring settings from a pre-installed configuration profile from Jamf. Maybe I'm doing something wrong? I have included the configuration profile along with log files from one OS 11 Mac.
<?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>AuthJamfComputerID</key>
<string>$JSSID</string>
<key>InstallMacOSMajorUpgrades</key>
<true/>
<key>InstallMacOSMajorVersionTarget</key>
<string>14</string>
<key>InstallRapidSecurityResponses</key>
<true/>
<key>InstallNonSystemUpdatesWithoutRestarting</key>
<true/>
<key>DeferralTimerDefault</key>
<string>60</string>
<key>DeferralTimerMenu</key>
<string>15,60,240,1440</string>
<key>DeferralTimerFocus</key>
<string>120</string>
<key>DeferralTimerError</key>
<string>60</string>
<key>DeferralTimerWorkflowRelaunch</key>
<string>360</string>
<key>ScheduleWorkflowActive</key>
<string>MON:09:00-18:00,TUE:09:00-18:00,WED:09:00-18:00,THU:09:00-18:00</string>
<key>DeadlineCountFocus</key>
<string>5</string>
<key>DeadlineCountSoft</key>
<string>7</string>
<key>DeadlineDaysFocus</key>
<string>3</string>
<key>DeadlineDaysSoft</key>
<string>7</string>
<key>DialogTimeoutDefault</key>
<string>600</string>
<key>DisplayUnmovable</key>
<string>ALWAYS</string>
<key>DisplaySilently</key>
<string>INSTALLNOW</string>
<key>DisplayHideProgressBar</key>
<string>DEADLINE,INSTALLNOW</string>
<key>DisplayNotificationsCentered</key>
<string>DEADLINE,INSTALLNOW</string>
<key>DisplayIconSize</key>
<string>128</string>
<key>DisplayIconFile</key>
<string>/Library/Management/super/Icons/DH-ICON-square.png</string>
<key>DisplayIconLightFile</key>
<string>/Library/Management/super/Icons/DH-ICON-square.png</string>
<key>DisplayIconDarkFile</key>
<string>/Library/Management/super/Icons/DH-ICON-white-square.png</string>
<key>DisplayHelpButtonString</key>
<string>https://jira.deliveryhero.com/plugins/servlet/desk/portal/1</string>
<key>AuthAskUserToSavePassword</key>
<true/>
<key>AuthCredentialFailoverToUser</key>
<true/>
<key>AuthMDMFailoverToUser</key>
<string>ALWAYS</string>
<key>VerboseMode</key>
<true/>
</dict>
</plist>
Any help would be appreciated. C02C18SZMD6T-g.lee-2024-12-12-15-37-15.zip
Is there any additional information I could provide to help troubleshoot this issue?
Superman uses a main plist file found at /Library/Management/super where it holds all of the current settings for any active workflows. Those settings are pulled from the configuration profile or from command line parameters. When super is initially installed on the device, it will pull any settings that come from the configuration profile and set them in the main plist file. However, you can write over those settings using command line parameters in later deployments. Super will only reread the configuration profile and pull in those settings again if you throw in a --super-reset command.
For example. I have a config profile that uses the InstallMacOSMajorVersionTarget = 15. Whenever 16 comes out. None of my macs will update to 16 until I change and push out the configuration profile for every device followed by a --reset-super command. The config profile might have been changed on their devices. But super needs the main plist to be updated before it realizes that something is different in the config profile.
See if you can determine if that's happening correctly.
Sorry for the delayed response, are you sure that you are using the correct preference domain for the super config profile?
Also the latest version of super added a feature that can help identify configuration issues. Specifically in v5.1.0-beta2 or later super --config-stauts will show you the status of the various config files used by super. https://github.com/Macjutsu/super/releases/tag/v5.1.0-beta2
Kevin,
Would you mind explaining more what you mean by "correct preference domain"? Is there a particular key I should be looking at?
Also, we're using Jamf to deploy the configuration profile, then installing the Super script.
Scott