Non Administrator Quarantine Issue

sign the applications if you are creating them or Have you opened the application prior to packaging it so that you set the quarantine flag before packaging it?

You need to clear the quarantine attribute before packaging up the application, assuming you're either capturing or drag and dropping the application into an app like Composer to package it.

One simple way to do this is launch the application at least once under your admin account before dragging into Composer to package it. You'll see the "downloaded from internet" warning, but once you acknowledge under and admin account it should clear the setting and not appear again. I usually just run it a second time for good measure to ensure I don't see the quarantine warning again. This is by far the simplest way.

However, since you've already deployed some apps out there that need to be fixed, use the following syntax. This could be sent via policy Run Command or from Casper Remote, or even through ARD if you happen to use that.

xattr -dr com.apple.quarantine /path/to/application/app-name.app/

I am packaging these apps from my Mac, and have run them several times on my Mac. And I thought I tried using the xattr command on my Mac prior to packaging as well. That's where my confusion has come in. I've been wondering if it is some rights issue, where they might not have right to the correct preference file.

That warning has nothing to do with any preference files. The OS sees the quarantine flag on any application downloaded from the internet and will send up that warning unless/until the flag is cleared. Somehow that isn't being cleared. I would try running the xattr command again on an affected system and see what that does.

Other than very occasionally forgetting to launch an app prior to packaging, I haven't run into this issue very often. And either of the above steps typically corrects it.

Ok, thanks for the clarification. I created a Policy that would use xattr to clear the Quarantine flag on all files in the /Applications folder and that seems to clear up the issue, so this does seem to be an issue with the flag. I'll keep following up on applications we distribute to see if I can figure out any commonality when this happens.

Tim

Aah, that's probably it. I frequently make packages using the drag 'n' drop method with Composer. I'll go in and change the permissions on the files and see if that fixes it.

Thanks for a new direction to look.