Wrong permissions on ~/Library/Application Support/Adobe/OOBE?

Hi,

I have been battling with some problems when I tried to perform a test rollout of the new Creative Cloud applications on our Mac's. For some reason I couldn't activate the products and the Adobe Applicatoin Manager asked for a serial and I couldn't log in with Creative Cloud Desktop because I was getting an "Unknown server error".

After many hours of trial and error I discovered that the problem was the previously installed Creative Suite 6 that was created with AAMEE. When installed on Mac OS X 10.7 and 10.8, then it creates the folder ~/Library/Application Support/Adobe/OOBE in each user and it contains the file opm.db. For some reason it sets the owner as root and because the permissions are 755, then it's only root who can make changes the folder.

That doesn't create any problems for Creative Suite 6 but when I try to activate the Creative Cloud applications that are rolled out with Creative Cloud Packager then it needs to write to that folder (at least when your using Creative Cloud for Teams) and fails. Our users are not local administrators and it even fails for a local administrator account. The solution is of course to correct the permissions so that the owner is the user that the folders belongs to. To fix that manually on multiple computers is a pain so I have created a small script that can fix it in all users home folders.

This is it:

#!/bin/sh

# Corrects permissions on ~/Library/Application Support/Adobe/OOBE so that

# Adobe Creative Cloud can be activated. Creative Suite 6 (at least installations

# created with AAMEE) sets the owner to root which is a problem when Adobe Creative Cloud

# is installed.

#

# Script by René Frej Nielsen, rfn@rfn.dk

_USERS=$(dscl /Local/Default -list /Users UniqueID | awk '$2 >= 500 { print $1; }')

for u in $_USERS

do

        _dir="/Users/$u"

        if [ -d "$_dir" ]

        then

                chown -R "$u" "/Users/${u}/Library/Application Support/Adobe/OOBE" > /dev/null 2>&1

        fi

done

Save that as an executable script, fx. fix_OOBE_permissions.sh and set the executable bit (chmod +x fix_OOBE_permissions.sh) and push it with your preferred tool. It has to be run as root.

It extracts all non-system users (users with an UID above 500) on the computer and looks for their home folders. If a home folder exists then it sets the owner on the OOBE folder to the correct user. This isn't the most pretty script since it performs the chown command on all home folders without checking if the OOBE folder exists, but since it doesn't do any harm and I discard all errors then it works just fine .

If your users are created from a network directory (AD or OD) then they have an UID above 1000 and then you can change the number 500 to 1000. Then the script will only try the fix on their home folders and leave the local users alone.

I'm assuming a couple of things with this script:

1. The users home folders are located in /Users
2. The name of the users home folder is the same as their short name

If the above isn't true in your environment then you'll have to change the script.

I hope this is usefull for someone! If you're not seeing this problem in your environment and have an idea why it's like this here then I'm all ears...

Regards,

René Frej Nielsen