Who is this article for?
CrashPlan for Small Business, yes.
Code42 for Enterprise, yes.
Link: Product plans and features.
This article applies to Cloud.
Other available versions:
A system image that you deploy to new devices can include installer files for the Code42 app—but only the installer files. Do not run the installer. Do not install the app on the system image until after you deploy the image to a user device. The sequence is critical:
- Get and customize installer files for Code42 apps.
- Copy your installer files to your system image.
- Deploy your system image to your devices.
- Run the Code42 app installers on your devices.
Do not install a Code42 app on a system image, then duplicate that system image on multiple devices. The result will be multiple devices with same Code42 identity, using the same Code42 backup archive. That means you will lose almost all of your backed-up data.
- System images and devices must meet Code42 app system requirements.
- Code42 Customer Champions can assist you with customization and scripts for Code42 app installers.
- Our Customer Champion team cannot assist you with building and deploying system images, and with software management tools such as Jamf Pro, OS X Disk Utility, SCCM, or Microsoft Deployment Toolkit.
Information about products from other manufacturers is intended as a resource to help you get the most out of Code42 products. However, our Customer Champions cannot provide direct assistance for these products. For assistance with products not developed by Code42, contact the product's manufacturer.
Step 1: Get and customize installer files for Code42 apps
There are multiple ways to install Code42 apps, depending on how you wish to authenticate users and devices when the app installs and connects to a Code42 authority server.
The article Manage app installations in your Code42 environment describes three options.
Select one option, and follow the linked instructions until you are told to run an install command or installer executable.
- Do not run any install command or installer executable.
- Instead, proceed to Step 2: Copy your installer files to your system image.
Option 1: Deploy Code42 apps silently with SSO
For a Code42 environment that uses SSO authentication, customize Code42 installers
to connect and authenticate automatically. No user intervention is necessary.
Option 2: Deploy Code42 apps for manual sign on
Customize Code42 installers to open an interface on user desktops.
- The app automatically connects to the Code42 authority server.
- The app takes its username from the device and operating system.
- The user defines the app's Code42 password.
Option 3: Install the default Code42 app
Use the default Code42 installer executable, with no customization. The app opens a desktop interface and prompts the user for:
- Username and password
- Registration key (the identifier for for your Code42 organization)
- Server address (the domain and port number for the Code42 authority server)
Step 2: Copy your installer files to your system image
How you copy your Code42 installer files onto your system image depends on your software management tool.
How many and which files you copy also depends on your situation:
- Installer executables are *.msi, *.dmg, or *.tgz files, depending on the image's operating system.
- Mac installations include a plain-text configuration file, deploy.properties.
- Installers are typically invoked with scripts that provide your custom command arguments.
Step 3: Deploy your system image to your devices
How you deploy a system image to devices is outside the scope of this article. However, you must deploy the image before invoking the installer for the Code42 app.
Step 4: Run the Code42 app installers on your devices
Use a software management tool or the device operating system to launch a script or task that runs the Code42 app installer.
For SSO and manual sign on (options 1 and 2 above), the installer needs to run after a user logs in to the device, because the most recently logged in username becomes the Code42 app's username.