I am getting this error upon login on Macs in my environment:


insecure startup item disabled



I'm believing this message is caused by a permissions conflict between that file and the OS. Permissions are set to 775 on ampagentbootup, but per Apple, the OS demands 755. I have a couple of questions on that note:

1.) Does the agent provisioning from the K1000 automatically append those permissions after installation?

2.) I have been having unrelated issues with the agent provisioning on mac platforms (the kbox thinks the agent is already installed, when it is not. I'm addressing this issue with engineering currently).

That being said, I'm having to install manually on a large percentage of macs here. To do so, I'm copying the installer .pkg out via ARD, and running a sh script against it: sh -c 'KACE_SERVER=%Server Address% installer -pkg /tmp/AMPAgent.pkg -target /'

For this manual installation, will adding a chmod 755 to that file address this issue? 

Thank you!


1 Comment   [ - ] Hide Comment


  • We also had to manually provision our MAC clients, we used the following via Apple Remote Desktop.

    No CHMOD required. Here is our ARD script we used after we transmitted the DMG to the client machine.

    sudo /Library/Application\ Support/Dell/KACE/bin/AMPTools stop
    rm -rf /Library/Application\ Support/Dell/*
    hdiutil attach /tmp/ampagent-5.4.10622.osx.all.dmg
    sudo sh -c 'KACE_SERVER=<someKboxServerFQDN> installer -pkg /Volumes/Dell_KACE/AMPAgent.pkg -target /'
    hdiutil detach '/Volumes/Dell_KACE'
    /Library/Application\ Support/Dell/KACE/bin/AMPTools stop
    /Library/Application\ Support/Dell/KACE/bin/AMPTools start
    /Library/Application\ Support/Dell/KACE/bin/runkbot 2 0
    • You're effectively achieving the same thing here, just adding intelligence to remove the agent properly prior to, and kickstart the service after install. i don't see anything in there that would resolve my issue, however. i do appreciate the response though - I will test it just in caase
Please log in to comment

Answer this question or Comment on this question for clarity



What AV solution are you using?  Perhaps the installer and files need to be whitelisted?

Answered 06/24/2013 by: jknox
Red Belt

Please log in to comment