If you run through Terminal.

sudo rm -R /Library/StartupItems/ES1000Service

If you run it through Casper you don't need sudo as it will automatically run as root.

Thanks if I want to run it in casper dont I need the bin bash in front?

I like to give the full path to commands as well as to files. This assumes your partitions never get renamed from Macintosh HD. Always test.

#!/bin/sh



/bin/rm -rf /Volumes/Macintosh HD/Library/StartupItems/ES1000Service/

Since this is just a "one-liner", I would just copy + paste this into the "run command" field of the "Advanced" section where you create a policy. You could create an actual script and upload it to Casper but it's probably more work than what it's worth.

rm -R /Library/StartupItems/ES1000Service

Thanks immaging some new computers for Graphics and we noticed that one of the blasted Fiery packages creates this silly folder. In place of redoing everything I am just adding the post imaging script for the rest of the macs, and then pushing this script to the ones we deployed already.

It seems to have worked on so far.

Why not just use the "Files and Folders" object tin a policy to delete the folder?

@JimAllsop I posted this concern to the EFI forum and received a private response, hopefully we'll see an updated installer that addresses some concerns.

Fiery Command Workstation 5.7 concerns (OS X)

FYI...EFI responded to the thread. ;)

Hoping EFI responds sooner than later...

Woah, that was quick - thanks EFI!!!

Ether beer for EFI!!!

Or...

Don, thank you for pursuing that. Fiery software definitely makes me go grrrrrrrr.