Posted on 04-04-2013 07:19 AM
I'm working on a 10.8.3 image to be deployed using NetBoot and Casper Imaging. When building the image I can get everything so it's working fine. Network users can log in and access the appropriate resources without error. I've used Apple's Disk Utility and also tried Carbon Copy Cloner to compress the final DMG. The issue appears after deploying the compressed DMG using the above mentioned process. After imaging I bind to Active Directory and enroll in Profile Manager so new users are able to log in. I've got it set to create a mobile account when the user logs in (not sure if this is part of the cause, but I doubt it since the issue did not appear on the machine used to create the image).
Now, we've imaged and a new user logged in. Let's say this user tries to launch Microsoft Word. The application loads fine, but an error message appears stating, "You don't have permission to use the application 'Microsoft AU Daemon."
So my question is why is this happening/what could cause it and how can I fix it?
Solved! Go to Solution.
Posted on 04-08-2013 09:00 AM
Wow, it was as simple as OD being set to only allow applications from /Applications. After changing it to also allow /System and /Library the issue is resolved.
Posted on 04-05-2013 06:10 AM
Sounds like you're encountering the well-known problem with Network Home accounts and Microsoft Office.
https://discussions.apple.com/thread/3088536?start=0&tstart=0
http://osxadmin.blogspot.com/2008/11/folder-redirection-microsoft-office.html
http://serverfault.com/questions/83042/make-office-2008-run-smoothly-for-network-users
http://managingosx.wordpress.com/2008/02/13/managing-office-2008/
Posted on 04-08-2013 08:29 AM
The issue disappears when unbinding from Open Directory. Also, OD is set to create a mobile account when the user logs in using the local home template, not network home. And it's not specific to Office, also experiencing issues trying to launch SMART Notebook.
Posted on 04-08-2013 09:00 AM
Wow, it was as simple as OD being set to only allow applications from /Applications. After changing it to also allow /System and /Library the issue is resolved.