Home Forums OS X Server and Client Discussion Open Directory Network Home Directory’s and New iMovie 7.1 from iLife 08

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #370653
    Nick
    Participant

    Hi All

    I am having problems with the new version of iMovie and network home directory’s . The new app wants to write to the local drive iMovie folder even though a network user is logged in. It will not give you a choice.
    It wants to create the Movie Events folder locally, and we don’t let them write to the local hard drive.
    Have tried going into the iMovie package and looking for a plist file with a path… but am not having any look. We recently upgraded from 60 emacs to 60 iMacs with this new version on… needless to say the old one worked fine!!….. Hmmm

    Any help/advice please…. we have lots of different users on these machines, and I don’t want to open them up.. to start saving locally…
    Thanks
    Nicola Clarke

    #371933
    bryanmmch
    Participant

    Hey, how did you get on with this problem? we have just stuck the same issue…

    thanks.

    #372136
    trice
    Participant

    I usually make the folder locally on each machine – the following commands should do the trick

    mkdir /iMovie\ Events.localized
    chown root:admin /iMovie\ Events.localized
    chmod 1777 /iMovie\ Events.localized

    All users will be able to write and edit the contents of the folder but not delete the folder itself. We’re not overly concerned with the security of the contents of this folder (if need be users are reminded to move their info someplace else after its imported) so we don’t normally take any precautions beyond this. In fact the contents of this folder are regularly purged, via a login/logout hook if need be.

    Using ARD’s send unix feature these commands can be easily sent to all your machines at once.

    tom

    #374162
    skaffen
    Participant

    I’ve come across the same problem today, had a look through the iMovie 7 plist to see if there was something I could push out. Found a key called “captureVolumePath” which looked promising but doesn’t seem to actually make any difference. Think that that is more of a cached path rather than something that you can change to set a new path.

    Anyone come across any way to solve this that doesn’t involve something a bit messy with symlinks?

    Skaff

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.

Comments are closed