managed settings pushed through dscl are not appearing in /Library/Managed Preferences/ empty on Sequoia

Question

Created Nov ’24

Replies 2

Boosts 1

Participants 2

We are pushing some Chrome settings through Directory Services command line utility /usr/bin/dscl /usr/bin/dscl /Local/Default -mcximport /Computers/local_computer chrome_settings.plist /usr/bin/mcxrefresh -n root These commands created com.google.Chrome.plist in /Library/Managed Preferences on previous macOS versions. However on macOS 15.x Sequoia these commands intermittently fail to create the file in /Library/Managed Preferences though there is no error reported or any log entries that could indicate an error.

There could be other component on Sequoia that is preventing directory services tool to push the preferences but I am unable to locate it. It is not MDM because the machines are not enrolled (also have a setup where dscl and MDM both work). This is happening on a clean macbook setup but I have never seen it happen on mac mini.

Anyone have an idea what could be interfering with directory services to complete its task of pushing managed settings? DDM?

Boost

Answer 1

vachooho OP

Nov ’24

so on the computers that works ManagedClient logs 2 more lines which do not appear on the failing machines.

Below is the output from a working machine. The last 2 lines do not appear in the ManagedClient logs from the failing machine. MCXCCacheGraph seems to be related to the reading from the cache which contain our settings but are not populated to /Managed Preferences/

3135: 0x7a09 ManagedClient ManagedClient 12:29:11.290523-0800 MCX_ConfigCoreData.profilesForAllUsersAsCPProfile return zero configuration profiles.

3135: 0x7a09 ManagedClient ManagedClient 12:29:11.291013-0800 MCX recomposite prefs for user

3135: 0x7a09 ManagedClient ManagedClient 12:29:11.291135-0800 MCX.hasProfileConfigInfoForUser checking installed configuration profiles...

3135: 0x7a09 ManagedClient ManagedClient 12:29:11.291172-0800 MCX_ConfigCoreData.profilesForUserAsCPProfile COMPUTER profiles

3135: 0x7a09 ManagedClient ManagedClient 12:29:11.291379-0800 MCX_ConfigCoreData.profilesForUserAsCPProfile return zero profiles.

3135: 0x7a09 ManagedClient ManagedClient 12:29:11.291410-0800 MCX.hasProfileProvisioningInfo checking installed provisioning profiles...

3135: 0x7a09 ManagedClient ManagedClient 12:29:11.291418-0800 MCX_ConfigCoreData.profilesForAllUsersAsCPProfile ALL provisioning profiles

3135: 0x7a09 ManagedClient ManagedClient 12:29:11.291451-0800 MCX_ConfigCoreData.cp_profilesForPredicate executeFetchRequest returned objects = 0

3135: 0x7a09 ManagedClient ManagedClient 12:29:11.291475-0800 MCX_ConfigCoreData.profilesForAllUsersAsCPProfile return zero provisioning profiles.

3135: 0x7a09 ManagedClient ManagedClient 12:29:11.301601-0800 MCX_ConfigCoreData.profilesForUserAsCPProfile COMPUTER profiles

3135: 0x7a09 ManagedClient ManagedClient 12:29:11.301655-0800 MCX_ConfigCoreData.profilesForUserAsCPProfile return zero profiles.

**3135: 0x7a09 ManagedClient ManagedClient 12:29:11.921744-0800 <private>

3135: 0x7a09 ManagedClient ManagedClient 12:29:11.921757-0800 MCX.getComputerInfoFromStartup: MCXCCacheGraph() == -2 (<private>)**

Any idea why the cache is skipped and how to make MCX look into the cached settings?

0

Answer 2

Arthur-C-D OP

Nov ’24

Same issue since upgrading my machine to Sequoia.

I'm following the guidelines from the Chromium browser (https://www.chromium.org/administrators/configuring-policy-for-extensions/) in order to try to set some custom policies for my web extension.

I've tested on both Sequoia & Big Sur, and Sequoia seems to be the only affected version.

0