[daniel.svensson]

I would start by checking if the settings actually composites correctly on the client.

Start by (on a client logged in as an admin) dirty the MCX-cache to force an update of the cache:
sudo /System/Library/CoreServices/mcxd.app/Contents/Resources/MCXCacher -d

Also wipe the existing settings, the will be redownloaded at the next login:
sudo rm -R /Library/Managed\ Preferences/

Now logout and log back in as a user and open the com.apple.homeSync.plist in /Library/Managed Preferences/short_name/ and verify that it corresponds to your settings in WGM.

The SyncedPrefFolders array is your login/logout settings and the SyncedFolders is the background/manual settings.

[daniel.svensson]

Yes, I’ve thinking of that too but haven’t found a clear way to do that. Any tips on this ?!

The setting you do in WGM at computer level that says “Update the pref cache every 17 days” only forces the clients to flush the cache no matter what after 17 days, its not a cache expiration setting. Or am I completely wrong on this !?

The thing is that the clients are not away from the network more than a day or so. They are using network resources almost every day so I don’t think that is the problem.
However all wireless clients login to the network using a 802.1x setting and it seems that MCXd have trouble updating the cache since there is no network available just then.

I’ve doing some testing with this by dirtying the cache on a client while not connected to the network and as soon as I connect an ethernet cable it updates the cache directly after the network change is posted. Every time, rock solid.

But when doing the same thing on a wireless network it updates sometimes and fails sometimes leaving the computer in an unmanaged state.

Br,
Daniel

[daniel.svensson]

Maybe managed to solve this “problem”, fingers crossed 😉

By changing the default sync-settings in /System/Library/CoreServices/mcxd/Contents/Resources/CinchDefaults.plist I think way have got what we wanted….

I simply removed the dictonary and string “path ~” in the syncedFolder array in this file on our clients.
Together with the above launchd job that sets the periodicSyncOn to 0 it does no longer start the background sync process even if the MCX cache expires.

If you try to do a manual sync you will get the “There is nothing to sync” message which is want we wanted at this point.

Br
Daniel

[daniel.svensson]

Any news about this one ?!

Still having this problem in 10.4.10 with the “golden triangle” setup.

Br,
Daniel

[daniel.svensson]

The options to do a custom install with the installer cmd only seems to be available in 10.5 (installer v1.5.0).

I tried to generate an xml file with the “installer -showChoicesXML” and then use this file as an input with “installer -applyChoiceChangesXML” but it then says it is in the wrong format….

Any ideas howto construct a valid XML file that can be used ? The man-page doesnt give much info…

Other than this its working pretty good!

Thanks,
Daniel S (not the same as Daniel 😉 )

[Author]

Posts