Currently Being ModeratedMay 14, 2012 7:27 AM (in response to RichardElGuru)
Repairing the permissions of a home folder in Lion is a complicated procedure. I don’t know of a simpler one that always works.
Back up all data now. Before proceeding, you must be sure you can restore your system to its present state
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the page that opens.
Drag or copy — do not type — the following line into the Terminal window, then press return:
chmod -R -N ~
The command will take a noticeable amount of time to run. When a new line ending in a dollar sign ($) appears below what you entered, it’s done. You may see a few error messages about an “invalid argument” while the command is running. You can ignore those. If you get an error message with the words “Permission denied,” enter this:
You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up.
Next, boot from your recovery partition by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
When the recovery desktop appears, select Utilities ▹ Terminal from the menu bar.
In the Terminal window, enter “resetpassword” (without the quotes) and press return. A Reset Password window opens. You’re not going to reset the password.
Select your boot volume if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select ▹ Restart from the menu bar.
Currently Being ModeratedMay 17, 2012 9:01 AM (in response to RichardElGuru)
seems to me the trick here would be to set the ownership of the droplet to root/wheel - that way it would have admin access and work as advertised. can you do that or do you need IT to do it for you?