Problem between MCX App limits and custom AppleScript Studio app that calls script

[jdyck]

I’m having a problem that perhaps someone can give me some advice on.

I’m working on an image for deployment to approximately 2500 MacBook laptops. The image is to be bound to Open Directory, which also manages which applications are able to be run. I pretty much have everything working, EXCEPT a custom developed AppleScript Studio application.

This application is basically a GUI to a shell script – it collects some user information, then when you click the button passes the username, password and school to the script which then runs an expect script that calls rsync and responds to the request for password. The Application runs fine when I allow it in WorkGroupManager Application settings, but as soon as I click the button that calls the expect script I get the error that the backupscript is not allowed to run, please talk to the administrator.

I’ve tried dragging in the script, adding it with the plus tool, even turning on the “Legacy” “Allow UNIX tools to run,” all to no avail. Best I understand it is the script is missing the BundleIdentifier that Workgroup Manager uses to say what can run.

Surely I can’t be the only one with this problem, so I’m hoping someone else out there might have an idea on how to allow this to run.

[jdyck]

I got this resolved by putting any troublesome applications into a folder and whitelisting the folder. Not the most elegant solution I suppose, but it works and that’s what really matters.

[Author]

Posts