Overview
This article describes the recommended best practices for deploying the CrashPlan app alongside a gold image (also known as a base, clone, system, or desktop image), as well as an alternative workaround for environments with strict imaging requirements.
Considerations
Before including the CrashPlan app in your deployment workflow, please review the following best practices and limitations:
- Adding the CrashPlan app to a gold image is not recommended. As a best practice, install the CrashPlan app after distributing a device to a user.
- To include the CrashPlan app in your gold image, you must use a deployment policy with a custom user detection script that excludes the usernames of administrators deploying the CrashPlan app.
- For help with customization and scripts for CrashPlan app installers, contact your Account Executive to engage the Professional Services team.
Using a user detection script with a gold image
If your organization requires all applications to be included in a gold image, you must use a custom user detection script. This script must be modified to explicitly exclude the usernames of the administrators who are building and deploying the image.
Excluding these administrator users ensures the CrashPlan app waits to install until the actual end user signs in to the device for the first time.
Sample user detection script excerpts
Sample excerpts of customer user detection scripts with excluded administrator users are listed below. See Deployment script and command reference for complete details on implementing these scripts.
Windows script excerpt
#Add users to this list that CrashPlan should not register with
$ExcludedUsers = @(
'system'
'user1'
'user2'
'user3'
'admin'
'Administrator'
'admin-*'MacOS script excerpt
if [[ "$user" =~ ^(admin1|admin2|admin3)$ ]] || [[ -z "$user" ]]; then
writeLog "Excluded or null username detected ($user). Will retry user detection in 60 minutes, or when reboot occurs."
exit