Skip to main content
D
declure1
Participating Frequently
February 25, 2014
Question

Solution: how to suppress the region/license confirmation for LightRoom 5.x Mac deployment

  • February 25, 2014
  • 2 replies
  • 1201 views

I couldn't find this as an actual solution, but I figured it might help others to have this posted.  Thanks goes to user UAL Desktop Services for the groundwork and clues:

Here are the files you need to modify:

/Users/<logged in User>/Library/Application Support/Adobe/Lightroom

/Users/<logged in User>/Library/Preferences/com.adobe.lightroom5.plist

/Users/<logged in User>/Library/Preferences/com.adobe.lightroom5.LSSharedFileList.plist

Copy them from a user that has already confirmed and accepted the region/license window, and move them to the "Global" Application Support and Preferences folders:

/Library/Application Support/Adobe/Lightroom

/Library/Preferences/com.adobe.lightroom5.plist

/Library/Preferences/com.adobe.lightroom5.LSSharedFileList.plist

Right click the .plist files and under "Sharing & Permissions" set Read-Write permission for everyone.

Do the same for the Lightroom folder, but also click the settings "cogwheel" icon below the permissions area and select "Apply to Enclosed Items".

The global settings will override the local user prefs and should suppress that screen.  Keep in mind, the license key can still be viewed from Help > Registration in both Mac and Windows still (if anyone has a solution for that I'd love to see it).

Optionally, you can suppress the catalog location window by specifiying it in the /Users/Shared folder, setting "everyone" Read-Write permissions on /Users/Shared/lrcat/, and "Apply to Enclosed Items" again.

There's no reason this couldn't also be scripted or captured via JAMF Composer for deployment, if needed.

    This topic has been closed for replies.

    2 replies

    D
    declure1Author
    Participating Frequently
    February 26, 2014

    So a few things:

    1. The "lrcat" folder I specified is really whatever folder you named it when you first set the catalog file location.  Whatever you named it, make sure "Wheel" also has read-write permissions, and "Apply to enclosed items".
    2. Check, double check, and triple check that the .plist files in /Library/Preferences continue to exist.  Every time this failed on me, I found them to be missing from the global preferences folder.  I'm not sure if I was copying them with insufficient permissions, or Gatekeeper blocked it, or something in the OS cleaned them up, but once I was SURE they were sticking around even through a reboot; it seemed to good to go.
    3. Don't "replace" copy the /Library/Application Support/Adobe/Lightroom folder, just delete it first so there's no folder merging going on - then move the one from the User's Library over.
    4. This should always be the last step: Run LR once more when you're satisfied and make sure the key wasn't lost in the shuffle.  Just re-enter the key if needed, no need to copy all the files again.

    Any other insights, updates, or failures are welcome.  Hopefully the next version fixes this as it sounds like is being promised.

    Follow Up: Success!  I was able to capture a composer package that does suppress all the start screens for all users, including new ones after the installation.

    Christopher Grande
    Christopher Grande
    Participating Frequently
    March 14, 2014

    The easiest solution is to run these two commands after installing Lightroom 5:

    defaults write /System/Library/User\ Template/English.lproj/Library/Preferences/com.adobe.Lightroom5 firstLaunchHasRun30 -bool true

    defaults write /System/Library/User\ Template/English.lproj/Library/Preferences/com.adobe.Lightroom5 RegistrationField_CountryRegion -string 1

    We deploy with munki so I have it set as a post install script.

    This sets the two needed default prefs that will get copied to each new user that logs in.

    This assums you are installing via the pkg created with CCP.

    D
    declure1Author
    Participating Frequently
    March 14, 2014

    That's a good solution for new deployments, but it may leave out some scenarios like distributing install packages to production machines in use.  The advantage of copying to the Global Preferences folder is you don't have to fuss over what user already has or doesn't have the correct settings - it won't matter.

    But yeah for imaging, really either way will work. 

    I honestly gave up on CCP - it caused CCDA to crash a LOT in its most recent build a week or two ago.  I just installed the trial, plugged in the key, ran the tweak above, and re-created it all into a package with Composer.  It's surprisingly stable, reliable, and agile enough for any deployment.

    D
    declure1Author
    Participating Frequently
    February 26, 2014

    Stay tuned....this worked flawlessly yesterday but I'm having trouble reproducing it today.  I'll repost this when I figure out what detail I'm missing....

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices