[jvickers]

I have it syncing specific folders, or rather, excepting folders that match certain conditions.

By the way, I just learned that the fix I did yesterday didn’t work. Folders are still reappearing on my user’s desktop.

_josh

[jvickers]

After talking with an apple tech for a while, we discovered that we were able to again connect when we made the following change:

Open Server Admin and selected the affected server.
Select the SMB service, and then the Access tab.
Deselect “NTLMv2 & Kerberos.”
Restart the SMB service.

Evidently there is something about the windows 7 that makes it not want to bind to Kerberos. Unchecking this little box *seems* to have fixed the issue.

Thanks much, and hope that helps someone else.

_josh

[jvickers]

Well, I’m trying this little fix now. I’ll let you know if it works.

http://biotopia.info/wp/2010/12/14/osx-server-mobile-account-phds-sync-problems/

_josh

[jvickers]

[quote]Thanks for the pointer, macshome. Could you give me another hint, where to look for a generated script? And what did you do to find out, that Server Admin actually creates a script?[/quote]

As long as we’re seconding things, I’d like to second this request. 😛

I’ve actually just read through Josh Wisenbaker’s “Mac OS X Filesystem ACLs” whitepage, and learned a few things about Apple’s version of ACLs that appear to be slightly different from the *nix paradigm, much to my frustration.

I had just written a script that allows the user (me) to apply ACLs to all the folders in our file structure by using a provided excel sheet that will create chmod commands based on the user’s input. The idea being that we can use this same excel sheet for the existing folder structures of our different offices, without spending the time at the WGM to individually add ACLs. I noticed some funny things when I ran it (on a test volume, of course), however, that made me think twice. When I added entries such as “read”,”write”,”execute”, and “append”, I [i]wasn’t able to see the user’s permissions in the Effective Permissions Inspector.[/i]

I now know that those are added somewhat differently. I have run a few more tests, and I can see that running a recursive chmod command will add the correct “read”,”write”,”execute”, and “append” permissions to a file when I add the List, Traverse, Create Files, and Create Folders permissions to the containing folder. It’s sort of counter-intuitive if you’ve just been looking at ACLs on the CLI side, but if it works, I’m okay with it.

This means that I can change my “chmod +a ‘user allow permission'” command to a recursive “chmod -R +a ‘user allow permission'” command and fake propagation.
This is how I am proposing to fix my own script, so I hope it is also helpful to the rest of you. 😉

_Josh

[jvickers]

Ah. That’s what I get for being green. Thank you for your reply.

[Author]

Posts