Skip to main content
Question

Installation path not found and BOM errors

  • October 7, 2011
  • 3 replies
  • 9 views
T
Forum|alt.badge.img+21

Hi

Has anyone else had this before? Trying policies for the first time via http of a DP attached to an Apple server. One policy installs launch daemons I packaged up with Composer and they install fine.

The problem is with another policy to install the scripts, half way down I get errors. I ve also tried afp but same thing happens on two different machines!

I have tried propegating permissions on the share and I don't have a jss utility on the 10.7.1 server which used to fix most problems.

Tim Kimpton

Systems Engineer

E: Tim.Kimpton at rufusleonard.com

D: +44 (0)20 7956 3014

W: http://www.rufusleonard.com

F: facebook.com/rufusleonarduk

T: twitter.com/rufusleonard

??
?

Rufus Leonard limited is a company registered in England and Wales with company number 3348509. Vat number: 691308528

    3 replies

    R
    Forum|alt.badge.img+4
    • ryanhollitz
    • Contributor
    • October 10, 2011

    I haven't seen this issue yet, but have you tried good ole' "chown -R" on the share, with your share owner and group?

    ryan

    T
    Forum|alt.badge.img+21
    • tkimpton
    • Author
    • Honored Contributor
    • October 10, 2011

    I have established iit s not to do with http, aft and smb

    It seems a problem with more than one policy running.

    I have two policies

    1. Install-Mngment-LaunchDaemons-LDN-Workstations

    These are launch daemons and they are all a priority 8 in the jss and set to
    any so I can run the jamf policy from terminal

    1. Install-Mngment- Scripts-LDN-Workstations

    These are scripts and they are all priority 5 in the jss and set to any so I
    can run the jamf policy from terminal

    When running the jamf policy from terminal I can see the
    Install-Mngment-LaunchDaemons-LDN-Workstations policy always runs first.
    Then the Install-Mngment- Scripts-LDN-Workstations policy runs and this is
    where about half way down I am getting the errors.

    If I disable the Install-Mngment-LaunchDaemons-LDN-Workstations policy and
    manually trigger the jamf policy. I can see the scripts get installed fine.

    Even though the priority is set in the packages the way I want them. In
    other words for the scripts to install first. Is there any way to prioritise
    which policy should run first? I think what is happening is that the launch
    daemons get installed and run the scripts if they are already installed on
    the machine and some scripts are failing to install because they are
    currently being run by the launch daemons.

    T
    Forum|alt.badge.img+21
    • tkimpton
    • Author
    • Honored Contributor
    • October 11, 2011

    Thanks Ryan

    The good ole chown ­R 775 on the share and this did the trick

    I've now set a launch daemon to run this every hour.

    Tim Kimpton
    Systems Engineer
    E: Tim.Kimpton at rufusleonard.com
    D: +44 (0)20 7956 3014
    W: http://www.rufusleonard.com
    F: facebook.com/rufusleonarduk
    T: twitter.com/rufusleonard

    Rufus Leonard limited is a company registered in England and Wales with
    company number 3348509. Vat number: 691308528

    ![external image link](attachments/6898d7eae7b042979835126f51bfd68a)
    ![external image link](attachments/355f5fe82de54f77b37eb79544345910)
    ![external image link](attachments/352682261f1e4b3aba2b477cbd712460)

    Terms & ConditionsCookie settingsAccessibility statement