Administering CrashPlan PROe with the Casper Suite Technical Paper Casper Suite v9.0 or Later 19 August 2014
JAMF Software, LLC 2014 JAMF Software, LLC. All rights reserved. JAMF Software has made all efforts to ensure that this guide is accurate. JAMF Software 301 4th Ave S Suite 1075 Minneapolis, MN 55415-1039 (612) 605-6625 The Casper Suite, Casper Admin, Composer, JAMF Software, the JAMF Software logo, and the JAMF Software Server (JSS) are trademarks of JAMF Software, LLC, registered in the United States and other countries. CrashPlan and CrashPlan PROe are trademarks of Code 42 Software, Inc. Mac OS X is a registered trademark of Apple Inc., in the United States and other countries. Oracle and Java are registered trademarks of Oracle and/or its affiliates. All other product and service names mentioned are the trademarks of their respective companies.
Contents Page 4 Introduction What s in This Guide Important Concepts Additional Resources Page 5 Requirements Page 6 Deploying CrashPlan PROe Customizing the CrashPlan PROe Installer Building a Custom Installation Settings Package Adding the Installer and the Custom Settings Package to Casper Admin Deploying the Installer and the Custom Settings Package Page 14 Reporting on CrashPlan PROe
Introduction What s in This Guide This guide provides step-by-step instructions on how to deploy and report on CrashPlan PROe with the Casper Suite. Important Concepts Administrators using this guide should be familiar with the following concepts related to the Casper Suite: Package management Policies and scope Advanced computer searches Managing directory bindings Additional Resources For more information on related topics, see the following documentation: Casper Suite Administrator s Guide http://www.jamfsoftware.com/resources/casper-suite-administrators-guide/
Requirements To administer CrashPlan PROe using the instructions in this guide, you need: The Casper Suite v9.0 or later The JAMF Software Server (JSS) Casper Admin Composer The CrashPlan PROe host server integrated with a directory service and managed computers bound to the same service For instructions on how to bind computers to a directory service using the Casper Suite, see Managing Directory Bindings and Binding to Directory Services in the Casper Suite Administrator s Guide. The installer media for CrashPlan PROe v3.5.2 or later Managed computers with OS X v10.5 or later and Java 1.6 or later
Deploying CrashPlan PROe Deploying CrashPlan PROe involves the following steps: 1. Customizing the CrashPlan PROe Installer. 2. Building a custom installation settings package. 3. Adding the installer and the custom settings package to Casper Admin. 4. Deploying the installer and the custom settings package. Customizing the CrashPlan PROe Installer The first step to deploying CrashPlan PROe is to customize the installer so that the installation process is completely automated and hidden from users. For more information on customizing the CrashPlan PROe installer, see the Customizing the CrashPlan App article from Code 42 Software: http://www.crashplan.com/enterprise/support/doku.php/customize_desktop 1. On an administrator computer, download the installer customization resource from your CrashPlan PROe server by navigating to: http://yourserveraddress:4280/download/crashplanproe_custom.zip Note: If the CrashPlanPROe_Custom.zip file does not exist on the CrashPlan PROe server, you can download it from: http://download.crashplan.com/installs/linux/install/crashplanproe/ CrashPlanPROe_Custom.zip 2. Open the CrashPlanPROe_Custom.zip file. 3. In the CrashPlanPROe_Custom directory, locate the userinfo.sh file and open it with a text editor. 4. To hide the installation from users, locate the startdesktop element and modify the value to look like this: startdesktop=false
5. To pass the username to the CrashPlan PROe server during installation, locate the user element and modify the value to look like this: user=`last -1 awk '{print $1}'` 6. Save and close the file. 7. Open Terminal and execute a command similar to the following: sudo sh /path/to/custom.sh The custom.sh file is located in the CrashPlanPROe_Custom directory. 8. When prompted, enter your password. 9. When asked whether to change settings, type yes. 10. When prompted, enter the primary address and port to the authority that manages the accounts and issues licenses. For example: YourPrimaryCrashPlanPROeServerHostname:4282 11. (Optional) When prompted, enter a secondary address and port to the authority that manages the accounts and issues licenses. For example: YourSecondaryCrashPlanPROeServerHostname:4282 To skip this question, press the Enter key. 12. When asked whether to hide the address from the user, type yes. 13. When asked whether to allow the user to change the server address in account settings, type no. 14. When prompted, enter your registration key. 15. When prompted to enter the username to use when authorizing a computer, type ${username}. 16. When prompted to enter the password to use when authorizing the computer, type ${deferred}. 17. When asked whether to connect to a proxy server, type yes or no as needed. 18. If you are connecting through a proxy, type the URL of the PAC configuration file when prompted. To skip this question, press the Enter key. 19. When asked if you are using single sign-on (SSO) authentication, type no. Note: If you are using SSO, contact CrashPlan PROe Support for assistance: http://www.crashplan.com/enterprise/support/ 20. When asked whether to change settings, type no.
21. When prompted, type the URL of the CrashPlan PROe server. When you are done, the following files are added to the CrashPlanPROe_Custom directory: CrashPlanPROe_Linux.tgz CrashPlanPROe_Mac.dmg CrashPlanPROe_Win.exe CrashPlanPROe_Win.zip The CrashPlanPROe_Mac.dmg file contains the CrashPlanPROe Installer (CrashPlanPROe.pkg) and a hidden.custom directory that contains the custom installation settings you just configured. These are the files you will use to deploy CrashPlan PROe. Building a Custom Installation Settings Package Use Composer to build a package of the custom installation settings package so you can deploy it using a policy. 1. In the CrashPlanPROe_Custom directory, find the CrashPlanPROe_Mac.dmg file and mount it by double-clicking it. 2. Copy the hidden.custom directory to /Library/Application Support/CrashPlan/ by executing: sudo cp -r /Volumes/CrashPlanPROe/.Custom /Library/Application\ Support/CrashPlan Note: Ensure that the command does not include a trailing slash. 3. Open Composer and authenticate locally. If you are prompted to choose a package creation method, click Cancel. 4. In /Library/Application Support/, locate the CrashPlan directory and drag it to the sidebar in Composer. Composer creates a package source from the file and displays it in the Sources list.
5. Double-click the package source and rename it to CrashPlanCustomInstallation. 6. In the toolbar, click Build as DMG. 7. Choose a location to save the package and click Save. Adding the Installer and the Custom Settings Package to Casper Admin Add the installer and the custom settings package to Casper Admin so you can deploy them using a policy. 1. Open Casper Admin and authenticate to the JSS. 2. Drag the installer (CrashPlanPROe.pkg) and the custom settings package (CrashPlanCustomInstallation.dmg) to the main repository in Casper Admin. The packages are displayed in blue text until you add them to a category. 3. Double-click the installer in the main repository.
4. Click the General tab and choose a category for the package. 5. Click the Options tab and choose a priority for the package. The recommended priority for the installer is 10. 6. Click OK. 7. Double-click the custom settings package in the main repository.
8. Click the General tab and choose a category for the package. 9. Click the Options tab and choose a priority for the package. The recommended priority for the custom settings package is 8. 10. Click OK.
Deploying the Installer and the Custom Settings Package Deploy the installer and the custom settings package using a policy. 1. Log in to the JSS with a web browser. 2. Click Computers at the top of the page. 3. Click Policies. On a smartphone or ipod touch, this option is in the pop-up menu. 4. Click New. 5. In the General payload, enter a display name for the policy. For example, Install CrashPlan PROe v3.5.2. 6. Select Login as the trigger. 7. Choose Once per computer from the Execution Frequency pop-up menu. 8. Select the Packages payload and click Configure. 9. Click Add for the installer. 10. Choose Install from the Action pop-up menu. 11. Click Add. 12. Click Add for the custom settings package. 13. Choose Install from the Action pop-up menu.
14. Click the Scope tab and configure the scope of the policy. 15. Specify a distribution point for computers to download the package from. 16. Click Save. CrashPlan PROe is installed on computers in the scope the next time they check in with the JSS and meet the criteria in the General payload. After CrashPlan PROe is installed, it starts backing up users home directories.
Reporting on CrashPlan PROe After deploying CrashPlan PROe, you can create and save an advanced computer search to report on computers that have CrashPlan PROe installed. 1. Log in to the JSS with a web browser. 2. Click Computers at the top of the page. 3. Click Search Inventory. On a smartphone or ipod touch, this option is in the pop-up menu. 4. Click New. 5. Select the Save this Search checkbox. 6. On the Search pane, enter a display name for the search. 7. Click the Criteria tab. 8. Click Add. 9. Click Choose for All Criteria, and then click Choose for Application Title. 10. Type CrashPlan PROe in the Value field. 11. Click Save. The results of a saved search are updated each time computers check in with the JSS and meet or fail to meet the specified search criteria. To view the search results, click View.