Posted on 04-17-2013 01:29 PM
The PDF mentioned in the title is here: http://www.jamfsoftware.com/libraries/pdf/white_papers/Deploying-CrashPlan-PRO-with-the-Casper-Suite.pdf
I'm not able to do step 3 in the "Configuring the CrashPlan PRO Client Installer" because the installer is no longer an .mpkg - It's a .pkg so I am not able to "View Contents" of the package or cd into the .../Contents/Resources/ directory within the package.
I noticed this white paper was written in July 2010 and I'm very new with Crashplan Pro. Did something change between the time the paper was written or with CrashPlan Pro?
By the way, I downloaded the client installer directly from our Crash Plan Pro server and directly off Crashplan's site. So far, all the installers are .pkg and not .mpkg files.
I have Pacifist and can see the contents of the installer package but the structure is not what I expected and I am not sure how to create a custom installer because I am not sure what to pull out and how to package it all up via Composer.
Can anyone provide any insight? Especially if you've recently made a custom CrashPlan Pro client installer with all the necessary info populated? Or if this has been discussed already, can someone point me in the right direction? I didn't find anything in my searches on here.
Thanks in advance! :)
Solved! Go to Solution.
Posted on 04-18-2013 07:01 AM
Sorry for this post. I realized my mistake was using the wrong white papers.
We're using CrashPlan PROe and I found the document "Administering the CrashPlan PROe with the Casper Suite" and I was able to create a custom install package but now I am having some minor issues with the new package.
I'll post my question in another post.
Sorry about this one!
Posted on 04-18-2013 07:01 AM
Sorry for this post. I realized my mistake was using the wrong white papers.
We're using CrashPlan PROe and I found the document "Administering the CrashPlan PROe with the Casper Suite" and I was able to create a custom install package but now I am having some minor issues with the new package.
I'll post my question in another post.
Sorry about this one!