The application Perian is not allowed

[HodgeHi]

Hi all,

 

I have deployed Perian to my OS X clients using ARD. I copied the Pref.pane file into the system PreferencePanes folder and it seems to have taken fine.

 

But each time i run something that possibly requires quicktime it says

 

"The application Perian is not allowed."

Now the weird bit. I have managed preferences set for the allowed applications and the entire Applications folder is allowed. I have restricted the Utilities, Applescript and Server folders and that is all. I can open and use Quicktime itself and the error about Perian comes up. Where can i allow this app? It doesn't have an actual application in the Applications folder.

 

I have tried allowing the pref.pane file but this did not work. Is there anything in the plugins folder? I will look at that next...

 

 

Hope someone can shed some light on this.

 

Thanks.

[rolfea]

as it got it own player or something within the package contents?

 

I found with Flash I had to rumage around in the package contents to find the player...

[HodgeHi]

I have tried adding both the .component and the perian executable inside the package contents. Both no good. I am not sure if it is something to do with the update process needing permission. I am working on it at the moment.

 

It is basically a plugin that allows quicktime to play .swf files. It is very good but this part is annoying.

[rolfea]

are there any updates for perian?

 

 

also, when you added it, did it have com.perian or something like that?

 

i found on our permissions here if it hasn't got the com.*whatever* then it doesnt tend to work, some work without it but more often than not it doesnt

 

 

I have no idea what it is, if someone would like to explain it would be good..

just an observation

[HodgeHi]

I have just this second sorted it out.

 

What it was is the Check for update automatically was ticked. It seems that if an application launches that might possibly access perian (anything that uses Quicktime really) then perian will check for updates. The information was in the Console logs. Should have checked first to be honest.

 

So what i have done is this.

 

After configuring perian, i found the .plist that is created and then added it to the details section in WGM. I set it to always be managed.

 

So now when anyone logs into a machine the automatically check for updates is unticked by the managed prefs.

 

Thanks for all your help and suggestions though. Most appreciated.

[nicklec]

Just noticed this thread so sorry for the 'bump'.

 

Our macs have the occasional update messages but I think they are mostly up-to-date now, has anyone managed to get 1.1.3 to stop 'auto updating' - as far as I can tell the only .plist I can find doesn't play ball with WGM, is there a log somewhere of why the prefs don't show up in WGM?

 

*edit* - nevermind think it was a problem with that specific .plist - deleted it and restarted - the new one looks to work ok!

Edited June 30, 2009 by nicklec

[martin_hannah]

I know this is an old thread but I thought it could save me some time messing around if I can get a response from someone.. I've tried copying the Perian.prefpane to the machd->library->preferencepanes folder with ARD but it doesn't pick it up in sys preferences. I have a feeling that this isn't the only file that needs copying over but I can't find any preference files etc that might go with it when I manually install it on the test mac. I would also like to disable auto update on the clients but again don't know where the preference file is..

 

Any help/advice on deploying this would be greatly appreciated as i would like to push this round to the whole school.

 

Many thanks,

 

Martin

 

- I've now managed to get it to show up in sys pref but it says that it is not installed.. I have also found the org.perian.perian.plist pref but don't know if this contains the setting to enable/disable auto updates..

Edited April 5, 2011 by martin_hannah

[iSteve]

We have disabled management of applications through Workgroup Manager as it was causing problems when certain apps try to launch helper apps. We just moved applications we didn't want students to run to the Administrator's desktop, or deleted them completely.