Transcription
Deploying CrashPlan with the Casper SuiteTechnical PaperCasper Suite v9.0 or Later29 April 2016
JAMF Software, LLC 2016 JAMF Software, LLC. All rights reserved.JAMF Software has made all efforts to ensure that this guide is accurate.JAMF Software100 Washington Ave S Suite 1100Minneapolis, MN 55401-2155(612) 605-6625The CASPER SUITE , COMPOSER , the COMPOSER Logo , JAMF SOFTWARE , and the JAMFSOFTWARE Logo are registered or common law trademarks of JAMF SOFTWARE, LLC in the U.S.and other countries.Apple, the Apple logo, and OS X are trademarks of Apple Inc., registered in the United States andother countries.CrashPlan, Code42, and the stylized C are trademarks of Code42 Software, Inc. in the UnitedStates and other countries.All other product and service names mentioned are the trademarks of their respective companies.
Contents4 Introduction4 What's in This Guide4 Important Concepts4 Additional Resources5 Requirements6 Deploying the Code42 CrashPlan App6 Customizing the Code42 CrashPlan App Installer8 Building a Package of the Code42 CrashPlan Custom Installation Settings9 Adding the Installer and the Custom Settings Package to Casper Admin12 Deploying the Code42 CrashPlan Installer and the Custom Settings Package15 CrashPlan App Life Cycle15 Deployment of App Updates15 When to Update the Deployment Package16 Reporting on Code42 CrashPlan App Usage3
IntroductionWhat's in This GuideThis guide provides step-by-step instructions for deploying and reporting on Code42 CrashPlan withthe Casper Suite.Important ConceptsAdministrators using this guide should be familiar with the following concepts related to the CasperSuite:Package managementPolicies and scopeAdvanced computer searchesManaging directory bindingsAdditional ResourcesFor more information on applications, concepts, and processes related to the Casper Suite, see theCasper Suite Administrator’s Guide, available ocumentation/administrator-guides/For more information on deploying, configuring, and managing Code42 CrashPlan, viewdocumentation articles, available at:https://support.code42.com4
RequirementsTo administer Code42 CrashPlan using the instructions in this guide, you need:The Casper Suite v9.0 or laterThe JAMF Software Server (JSS)Casper AdminComposerCode42 CrashPlan 5.0 or laterCode42 CrashPlan Master ServerThe Code42 CrashPlan Master Server integrates with a directory service and managed computersbound to the same service. For detailed information on how to integrate the Code42 CrashPlanMaster Server with a directory service, see the LDAP Reference Code42 support article.Managed computers with:OS X v10.9 or laterBound to directory serviceFor 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 SuiteAdministrator’s Guide.5
Deploying the Code42 CrashPlan AppDeploying the Code42 CrashPlan app involves the following steps:1. Customize the Code42 CrashPlan App Installer.2. Build a package of the Code42 CrashPlan app custom installation settings.3. Upload the Code42 CrashPlan App Installer and the custom settings package to the JAMF SoftwareServer (JSS).4. Deploy the Code42 CrashPlan App Installer and the custom settings package using a policy.Customizing the Code42 CrashPlan App InstallerThis section explains how to customize the Code42 CrashPlan App Installer so that the installationprocess is completely automated and undisruptive to users. Code42 provides a script to make thiscustomization easy.Download and Modify the Code42 CrashPlan Installer1. Download the Code42 CrashPlan App Installer customization resources from your Code42 CrashPlanserver by navigating to: hPlan Custom.zip2. On an administrator computer, extract the Code42CrashPlan Custom.zip file.3. Open the userInfo.sh file in the Code42CrashPlan Custom directory with a text editor.4. To hide the installation from users, locate the startDesktop element and modify the value so thatit looks like this:startDesktop false5. To pass the username to the Code42 CrashPlan server during installation, locate the user elementand modify the value.Use the following command to select the user logged in last, before the deployment:user last grep console grep still awk '{print 1}' head -1 You can find more information on this in the userInfo.sh file or online in the Preparing TheCode42 CrashPlan App For Deployment Code42 support article.6. Save and close the userInfo.sh file.6
Create the Code42 CrashPlan Custom Installer Package1. Open Terminal.2. Navigate to the directory containing custom.sh.For CrashPlan apps version 5.x and later:cd /Users/admin/Downloads/Code42CrashPlan Custom3. Make the custom.sh file executable with the following command:chmod x custom.sh4. Run the following command:./custom.sh5. Review the default settings in the script. At the end, a prompt is displayed: Change settings(yes, no, or revert) [no]?6. Type "yes".7. When prompted for the “primary address and port to the authority that manages the accounts andissues licenses”, type the URL of your master server and press the Enter key. For example: "crashplanmaster.example.com:4282".8. When prompted for the “secondary address and port to the authority that manages the accounts andissues licenses”, type the second URL configured for your master server and press the Enter key. Forexample: "192.0.2.50:4282".9. When asked whether to hide the address from the user, type “yes“.10. When asked whether to “Lock server address setting so that user cannot change server address”, type“yes“.11. When prompted, type your registration key.Use the registration key specific to the default organization for new user registration. For example: "AAAA-BBBB-CCCC-DDDD".For more information on Code42 organizations, see the Organizations Reference Code42 supportarticle.12. When prompted for the username, press the Enter key.13. When prompted for the password, type “ {deferred}”.Note: In non-LDAP environments, a password can be automatically generated by the CrashPlan appby using {generated}. This will only work for the initial deployment, not for installation with analready known user.14. When a proxy is used, type “yes”. Otherwise, press the Enter key.15. (Optional) When a proxy is used, type the URL of your .pac file.16.7
16. To enable Single Sign-On (SSO), press the Enter key. Otherwise, type “no”.17. If SSO is not required, press the Enter key. Otherwise, type “yes”.18. Close the configuration by typing “no”.19. Type the URL of the Code42 CrashPlan server. For example: "https://master-server.example.com:4285".The installation script will download the client installer package from the Master Server and createthe custom installer package.When finished, the following file is added to the Code42CrashPlan Custom directory:Code42CrashPlan Mac.dmgThe Code42CrashPlan Mac.dmg file contains the Code42 CrashPlan App Installer InstallCode42 CrashPlan.pkg and a hidden .Custom directory that contains the custom installationsettings you just configured. These are the files you will use to deploy the Code42 CrashPlan app.For more information on how to create a custom installer package, see the Preparing The Code42CrashPlan App For Deployment Code42 support article.Building a Package of the Code42 CrashPlan CustomInstallation SettingsUse Composer to build a package of the Code42 CrashPlan custom installation settings so that youcan deploy them using the Casper Suite.The following steps need to be done on a system that does not have the CrashPlan app alreadyinstalled.Build a package of the Code42 CrashPlan Custom InstallationSettings:1. Mount the Code42CrashPlan Mac.dmg file in the Code42CrashPlan Custom directoryby double-clicking it.2. Create a new CrashPlan directory inside the root-level /Library/ApplicationSupport/ folder: sudo mkdir /Library/Application Support/CrashPlan3. Copy the hidden .Custom directory to /Library/Application Support/CrashPlan/ byexecuting the following command:sudo cp -r /Volumes/Code42CrashPlan/.Custom /Library/Application\Support/CrashPlan4. Open Composer and authenticate locally.5. Locate the CrashPlan directory in /Library/Application Support/ and drag it to thesidebar in Composer. The directory will appear under the Sources heading.8
5.6. Rename the CrashPlan package source to "CrashPlanCustomInstallation".7. Select the CrashPlanCustomInstallation package source in the sidebar and click Build as DMG.8. Choose a location to save the package and click Save.Adding the Installer and the Custom SettingsPackage to Casper AdminAdd the installer and the custom settings package to Casper Admin so you can deploy them using apolicy.Upload the Code42 CrashPlan App Installer and the CustomSettings Package1. Open Casper Admin and authenticate to the JSS.2. Drag the installer CrashPlanPROe.pkg and the custom settings packageCrashPlanCustomInstallation.dmg to the main repository in Casper Admin.The packages are displayed in blue text until you add them to a category.9
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 theinstaller is “10”.10
5.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.11
9. Click the Options tab and choose a priority to determine the order for installing the package. Therecommended priority for the custom settings package is “8”.10. Click OK.Deploying the Code42 CrashPlan Installer and theCustom Settings PackageDeploy the installer and the custom settings package using a policy.Deploy the Code42 CrashPlan Installer and the Custom SettingsPackage1. Log in to the JSS with a web browser.2. Click Computers at the top of the page.3. Click PoliciesOn 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 Code42 CrashPlan5.0”.12
5.6. Select “Login” as a trigger.7. Choose “Once Per Computer” from the Execution Frequency pop-up menu.8. Select the Packages payload, and then 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 edit the scope of the policy.15. Specify a distribution point for computers to download the package from.13
15.16. Click Save.Code42 CrashPlan is installed the next time the computers in scope check in with the JSS and meetall of the criteria. Once Code42 CrashPlan is installed, it automatically begins backing up users’ homedirectories.14
CrashPlan App Life CycleDeployment of App UpdatesUpdates and upgrades of the Code42 CrashPlan app do not need to be deployed via the CasperSuite. Instead, the updates are directly distributed from the Code42 CrashPlan Master Server. You willneed to choose the organizations that should be upgraded and the Code42 CrashPlan Master Serverwill do the rest automatically.For more information, see the Upgrading The CrashPlan App To Version 5.x Code42 support article.When to Update the Deployment PackageIn general, CrashPlan is able to take care of client upgrades on its own. It is best practice to create anew deployment package with the next major release.15
Reporting on Code42 CrashPlan AppUsageAfter deploying Code42 CrashPlan, you can create and save an advanced computer search to reporton computers that have Code42 CrashPlan 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 “Code42 CrashPlan“ in the Value field.16
11. Click Save.The results of a saved search are updated each time computers check in with the JSS and meet or failto meet the specialized search criteria. To view the search results, click View.17
Code42 CrashPlan.pkg and a hidden .Custom directory that contains the custom installation settings you just configured. These are the files you will use to deploy the Code42 CrashPlan app. For more information on how to create a custom installer package, see the Preparing The Code42 CrashPlan App For Deployment Code42 support article.
