CrashPlan Silent Install

Finally I had time to figure out why Jamf Pro wasn’t pushing the CrashPlan install properly. My configuration was correct, but it would die as it couldn’t find out who the user was properly

While trying to find out what was going wrong I found a log file Located at /Library/Logs/CrashPlan/install.log
In my case the log looked like this.

 
Mon Nov 15 06:54:06 PST 2016 : Found userInfo script: /Library/Application Support/CrashPlan/.custom/userInfo.sh
Mon Nov 15 06:54:06 PST 2016 : Installation failure. User does not exist on this computer: 
Mon Nov 15 06:57:23 PST 2016 : Found userInfo script: /Library/Application Support/CrashPlan/.custom/userInfo.sh
Mon Nov 15 06:57:23 PST 2016 : Installation failure. User does not exist on this computer: 

From this, reading the userInfo.sh it became clear why.

Here’s the default userInfo.sh

The script above, tries to define the user, when casper Jamf Pro does a silent install it tries with ROOT.

With a few modifications (and alot of trial and error…), I was able to make it behave as it should for my environment.

Here’s how my userInfo.sh looks:

I set this to a Recurring check in policy or network change. Volia CrashPlan installs!

I’ve posted the custom installer including the user info to github. You can get it here.

 

Edit: 03-13-2017 – As Owen Pragel pointed out the CP_USER_HOME could be better defined. Taking his advice i’ve updated the above to include the search.

No Comments

Leave a Comment