Closed dayglojesus closed 10 years ago
Is this on 10.10? I tested supporess_icloud_setup successfully with 10.9 sometime last week.
By the way, syslog displays this message all the time form me after applying mcx settings with managedmac.
Jul 29 18:23:14 vvrantchan.C02LH12CFFT3 ManagedClient[25757]: MCX.getComputerInfoFromStartup: MCXCCacheGraph() == -2 (MCXCCacheGraph(mcx_puppet, dsRecTypeStandard:Computers): The record "mcx_puppet" (dsRecTypeStandard:Computers) interferes with the computer cache. Delete this record to resume caching.)
http://www.mactech.com/articles/mactech/Vol.26/26.03/2603MacEnterprise-LocalMCXRevisited/index.html
@gregneagle has linked a couple articles he's written about Local MCX and the default node.
https://managingosx.wordpress.com/2010/03/12/yet-again-with-the-local-mcx/ https://managingosx.wordpress.com/2010/03/07/local-mcx-update/ https://managingosx.wordpress.com/2010/03/07/mcx-in-non-default-local-nodes/
I have previously used a mobileconfig to suppress the iCloud setup. Perhaps it's a 'safer' way to do things?
I am working on a replacement for the managedmac::mcx class that will take care of all of this. It will use MCX in Profiles, and it will be done by the end of the day -- though I may not have time to upload it to the forge.
On Jul 30, 2014, at 7:57 AM, Brian Warsing notifications@github.com wrote:
I am working on a replacement for the managedmac::mcx class that will take care of all of this. It will use MCX in Profiles, and it will be done by the end of the day
Why so slow?
-- though I may not have time to upload it to the forge.
— Reply to this email directly or view it on GitHub.
I am a terrible human being.
Branch 0.4.7 should address this and provide enhanced support for profiles of all types.
I am going to leave this open for awhile and hold off on publishing to the forge, in case there are any issues.
If you have time to test it, I would appreciate hearing the results.
0.5.0 contains this and other patches
This setting is being applied, but it's not having the indented effect.
Not sure why at this point, but it's probably because we are applying policy to the mcx_puppet node which is in the Default node. Fix likely requires an additional provider or code that establishes a separate DSLocal domain for MCX.