Logic Pro X error - can't access File menu

[rad]

Current setup, please read all before commenting

IMac on latest version of OSX and Logic Pro X

Mac server which manages profile setup via Workgroup manager is two OS behind (Mountain Lion?)

 

I have other iMacs on old version and running fine.

 

So I have updated the iMac to test, updating all updates and working fine apart from Logic Pro won't allow access to file menu as it wants to access iTunes, which is blocked under policy.

 

Any idea what I need to change/set so that Logic works fine? If I login as local admin it all works fine as the account can access anything/everything.

[Brimstone]

Local user account I presume, not network?

[Brimstone]

Have you tried creating a test user not admin account?

[rad]

sorry for not replying, hectic day that means no time to browse EG.

 

I tested this with a student account and didnt allow me to access the File menu but everything else was fine.

Today I got permission to update the Server to El Capitan, await more threads when I cant work out why XXX doesnt work.

[Brimstone]

@rad,

 

I think I know the reason why you can't see the file menu, this version of Logic is set up in track view and not file view, have a look at the Apple support thread below...

 

https://discussions.apple.com/message/23310059#23310059

[rad]

 

Thanks @Brimstone for the link. Let me clarify more.

 

The iMac and Server are now both on El Capitan, Server software updated via App Store.

Logged on as local Admin, all works fine.

Logged on a student , iTunes is blocked by group policy. Logic Pro is all updated and will display the error message when using the program. It is blocking access to the file menu also. The menu doesnt show but every other one does.

I tried the prefrences but that didnt work.

 

I am on to Google to find an answer

[HodgeHi]

You need to log in as the local admin account and then check the console for the application name being denied. It may be easier filtering the logs by searching for the username that you logged in with. This will provide you with the direct path to the application that needs to be allowed through the restricted app policy.

 

I guess the policy is only applying to the standard/network accounts that you have set the profile at in Profile Manager/other MDM that supports this restriction.