Skip to main content
Solved

Making a PKG to place config file in all user folders

  • April 15, 2015
  • 4 replies
  • 40 views
M
Forum|alt.badge.img+6

We have installed basICColor color management software on all our Macs, and now there is a specific configuration file (.dcj) that we need to place into a User Settings folder. The folder path is ~/Documents/basICColor display 5/UserSettings . What I want is to make a package that simply drops that file into that folder for all user folders on a given Mac.

I tried making the package in Composer by dragging the configuration file into the left sidebar under Sources, and building the package. I then placed the Package in Casper Admin, and made sure to turn on Fill Existing User directories. I then tested installing the pakage with Remote on my Mac and my coworkers Mac. It worked on mine but not his.

What am I doing wrong here? I'm thinking that its something to do with how I am building the package, in that it worked for me since it knew the exact path to install to as it was built on my machine. Is there a simpler way to tell Casper "Take this file and put it here for everyone"?

Thanks,

-Mike

Best answer by Josh_Smith

It sounds like you are doing it correctly except for one thing: You must build the package as a DMG, not a PKG.

DMGs allow you to use FEU and FUT, PKGs do not.

    4 replies

    P
    Forum|alt.badge.img+11
    • pblake
    • Contributor
    • April 15, 2015

    Can you post a screenshot of the Composer contents? Also check the permissions on the settings. If you left yourself as the owner, that could be the cause.

    J
    Forum|alt.badge.img+14
    • Josh_Smith
    • Contributor
    • Answer
    • April 15, 2015

    It sounds like you are doing it correctly except for one thing: You must build the package as a DMG, not a PKG.

    DMGs allow you to use FEU and FUT, PKGs do not.

    M
    Forum|alt.badge.img+6
    • michaelherrick
    • Author
    • Contributor
    • April 15, 2015

    P
    Forum|alt.badge.img+11
    • pblake
    • Contributor
    • April 15, 2015

    Look at the Owner and Group down there. I would set the owner to the local admin of the machine, the group to staff, and give group & everyone executable rights. That's my suggestion. I would also set this at the basiCColor Display 5 folder level and apply permissions down.

    Terms & ConditionsCookie settingsAccessibility statement