CrashPlan ProE

msardes
New Contributor III

CrashPlan pulling Casper account for user when deployed though remote. Any help would be appreciated

userinfo has the following command as dictated in the document provided at
http://www.jamfsoftware.com/libraries/pdf/white_papers/Administering-CrashPlan-PROe-with-the-Casper-Suite.pdf

P_USER_HOME="$HOME"
user='last -1 | awk '{print $1}'`
userGroup=id -gn "$user"
CP_USER_NAME="$user"

6 REPLIES 6

msardes
New Contributor III

noone bump...

msardes
New Contributor III

nevermind got it.

agirardi
New Contributor II

Curious to know what you did to solve this issue. Seem to be struggling with the same thing here.

gregneagle
Valued Contributor

I think the "right" solution might vary from organization to organization. Our user info script queries an internal database to find out the "primary" user of a machine. Your org might store that in LDAP or AD. Or you might be able to get away with looking at the contents of /Users and using the folder name that isn't "Shared" and isn't a management account name. Or you might sort the output of `ac -p` and assume the user with the highest number of hours is the primary user (doesn't really help with newly deployed machines, though). Or you might need to use some combination of techniques.

agirardi
New Contributor II

Thanks for the feedback Greg.

My issue was actually resolved to one discussed a few days ago here:
https://jamfnation.jamfsoftware.com/discussion.html?id=6393

Copying the whole CrashPlan folder and removing everything but .Custom allowed the instructions here to work:
http://www.jamfsoftware.com/libraries/pdf/white_papers/Administering-CrashPlan-PROe-with-the-Casper-...

My only nit picky thing is that by default when opening crashplan for the first time they are prompted as a "new user" when they are an "existing user" in CrashPlan.

krispayne
Contributor

Try this instead:

P_USER_HOME="$HOME"
user=`last -1 | awk '{print $1}'`
userGroup=`id -gn "$user"`
CP_USER_NAME="$user"

The backtick instead of single quote in line 2 thing really messed me up for a while.