Home > Mac administration, macOS, Management Profiles > Management profile settings and OS upgrade implications
A question I’ve seen repeatedly in the Mac Admins Slack goes something like this:
“I installed this profile for macOS NewVersion onto macOS OldVersion, then upgraded from macOS OldVersion to macOS NewVersion. The setting didn’t work. Why didn’t it work?”
Why it didn’t work has to do with how management profile settings are handled. When a management profile is installed, the settings contained within that profile are applied.
This settings application occurs exclusively at the time of the profile installation. Those applied settings are never again re-read or re-applied as long as that profile is installed. The settings in a profile are applied only at the time of installation and that is the current state of things.
How is this relevant to settings you want to apply to macOS? Apple defines what OS version a setting was introduced for, which means it does not work for OS versions prior to that. For more information, please see below the jump.
An example of this is the management setting for iPhone mirroring:
This setting was introduced for macOS as of macOS 15 Sequoia. That means that the setting works on macOS Sequoia but what happens when you install a management profile like the one below which contains this setting onto a Mac running macOS 14 Sonoma?
Nothing.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<?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>PayloadContent</key> | |
<array> | |
<dict> | |
<key>PayloadDisplayName</key> | |
<string>Restrictions</string> | |
<key>PayloadIdentifier</key> | |
<string>com.apple.applicationaccess.DD8454BB-A1D6-4DD9-B1AC-C1B6ABA512E9</string> | |
<key>PayloadType</key> | |
<string>com.apple.applicationaccess</string> | |
<key>PayloadUUID</key> | |
<string>DD8454BB-A1D6-4DD9-B1AC-C1B6ABA512E9</string> | |
<key>PayloadVersion</key> | |
<integer>1</integer> | |
<key>allowiPhoneMirroring</key> | |
<false/> | |
</dict> | |
</array> | |
<key>PayloadDescription</key> | |
<string>Blocks the use of iPhone mirroring</string> | |
<key>PayloadDisplayName</key> | |
<string>Block iPhone Mirroring</string> | |
<key>PayloadIdentifier</key> | |
<string>D0B2E096-2C7F-4F2F-A1C0-FFE16919768B</string> | |
<key>PayloadOrganization</key> | |
<string>Company Name</string> | |
<key>PayloadScope</key> | |
<string>System</string> | |
<key>PayloadType</key> | |
<string>Configuration</string> | |
<key>PayloadUUID</key> | |
<string>D0B2E096-2C7F-4F2F-A1C0-FFE16919768B</string> | |
<key>PayloadVersion</key> | |
<integer>1</integer> | |
</dict> | |
</plist> |
A profile’s settings get applied at the time of installation. If the setting isn’t understood by the OS the profile is installed onto at the time of installation, the setting is ignored. In the context of the management setting for iPhone mirroring, macOS Sonoma doesn’t have the management option for managing iPhone mirroring so Sonoma will ignore the setting. It will remain ignored if the Mac gets upgraded to Sequoia because the setting only gets applied at the time of installation and the setting never gets re-evaluated to see if it applies to Sequoia. The outcome is that the setting does not get applied on Sequoia if the profile with the setting was installed on Sonoma.
How do you fix this? Remove the profile with the iPhone mirroring setting from the Sequoia Mac and re-install the profile. Once the profile is installed again, the setting will get applied as part of the install process. Sequoia has that setting as a management option, so Sequoia will then apply the setting from the profile and manage iPhone mirroring as defined by the profile’s settings.
So what does this mean for management settings you want to apply to macOS NewVersion? You’ll need to check what the introduction version is for the setting you want to apply. If it’s a brand new setting where the introduction is on macOS NewVersion, you’ll need to wait until the Mac is running macOS NewVersion before deploying a profile to manage that setting.
For Mac admins who want the capability to install a setting on macOS OldVersion and have it apply to macOS NewVersion, I recommend filing feedback with Apple to request it .