Skip to main content

This article applies to CrashPlan PROe version 4.

Code42 Support

CrashPlan app installer on OS X does not apply custom settings

This article applies to CrashPlan PROe version 4.


When preparing to deploy version 3.6.4 of the CrashPlan app on OS X, the CrashPlan app may not correctly apply your custom settings if a required folder is not present. This issue is fixed in version 3.7 of the CrashPlan app, and we recommend deploying the latest version of the CrashPlan app. However, this article describes a solution for preparing version 3.6.4 of the CrashPlan app for deployment.


Administrators preparing the CrashPlan app for deployment using version 3.6.4 of the CrashPlan app on OS X

Recommended solution

To successfully deploy the CrashPlan app on OS X using version 3.6.4:

  1. Open the script that is included in the deployment resources.
  2. Locate the end of the section labeled Variables to set.
  3. Add the following line after that section in order to create the required folder:
    mkdir -p "/Library/Application Support/CrashPlan"

User info script reference

Customize this script as needed for your environment. This example is provided only to show the proper placement of the mkdir command.


# Optional script by which you can control the user installation.
# Variables to set:
#   startDesktop: set to false if you don't want the desktop to start up immediately after installation
#      CP_USER_HOME: Allows the app to start scanning the user's home folder immediately after installation
#      user:         Used to properly set file permissions
#      userGroup:    Also used for file permissions
#      CP_USER_NAME: This will become the unique ID for the user in the PROe Server database.
#                    Leave CP_USER_NAME blank to require the user to enter it.
#                    If set this value, you'll want to set the username="" attribute of <authority ... /> tag in default.service.xml to username="${username}"

mkdir -p "/Library/Application Support/CrashPlan"

# Set to false if you don't want the desktop UI to start up.

# When installing from the root account (for example) you will need to populate
# some or all of these variables differently than is done below.
# Note: whoami *always* returns "root" for this package so we had to get creative to find the installing user.
# Also: You will want to populate CP_USER_NAME with the right email address unless you don't want your users or admins receiving reports and alerts.
user=`basename $CP_USER_HOME`
userGroup=`id -gn "$user"`