Skip to main content
Code42 Support

Upgrade the CrashPlan app from version 4.x to 5.x

Applies to:
  • Code42 CrashPlan (previously CrashPlan PROe)

Overview

Version 5.x of the CrashPlan app is a major software release that includes a new user interface, revised system requirements, and modified features. To assist you in preparing your users and devices for this upgrade, devices upgrade to the most recent version of the 4.x CrashPlan app by default.

Optionally, you can configure each organization in your Code42 environment to upgrade to version 5.x of the CrashPlan app.

CrashPlan app version 5.0

Considerations

CrashPlan app version 5.x requires on-premises master server
In order to upgrade to version 5.x of the CrashPlan app, you must have an on-premises master server. If you use the Code42 cloud with hosted keys or CrashPlan for Small Business (previously CrashPlan PRO), then your CrashPlan apps will upgrade to the most recent version of 4.x instead.
  • Devices must meet the system requirements for version 5.x to be eligible for upgrade.
  • After upgrading from version 4.x to 5.x of the CrashPlan app, the user must manually sign in the first time the app is opened. Backups continue to occur even if users do not sign in after upgrade.
  • Any modifications to the CrashPlan app's text or images are lost when you upgrade from version 4.x to version 5.x of the CrashPlan app. You can create modified CrashPlan apps in version 5.2.x and later using a new process.
  • Versions 5.0.x and 5.1.x of the CrashPlan app supports only the standard archive encryption key setting.
    • Devices belonging to users with enhanced security settings will not upgrade to 5.0.x or 5.1.x of the CrashPlan app, even when upgrades are enabled.
    • Users with enhanced security who install version 5.0.x or 5.1.x of the CrashPlan app are prevented from backing up or using the application.
  • Backing up to account devices (computer-to-computer backup) is not supported in version 5.x of the CrashPlan app.
    • Device destinations cannot be configured or managed from version 5.x of the CrashPlan app.
    • If you upgrade to version 5.x of the CrashPlan app, you can use the administration console to disable these destinations and remove the associated archives.
  • Users cannot manage versions and frequency settings from the CrashPlan app in version 5.x. Users must adjust these settings from the administration console.
  • Version 5.x of the CrashPlan app does not support installation per user and for everyone on the same device. If you have devices with version 4.x of the CrashPlan app installed per user and for everyone, do not upgrade these devices to version 5.x.

Upgrade CrashPlan apps to version 5.x

Step 1: Ensure devices use CrashPlan app version 4.4 or later

(Code42 server version 5.3.x and earlier only.)

You must use version 4.4 or later of the CrashPlan app before upgrading CrashPlan apps to version 5.x.

  • If there are devices in your Code42 environment using CrashPlan app versions older than 4.4, follow these instructions to upgrade your devices to the most recent version of the 4.x CrashPlan app before proceeding with the steps below.
  • If the devices in your Code42 environment are already using version 4.4 or later, proceed to the next step.

Step 2: Identify each organization's orgid

Obtain the orgId, a numeric identifier, for each organization whose CrashPlan apps you want to upgrade to version 5.x.

  1. Sign in to the administration console on your master server.
  2. Go to Organizations.
  3. From the action menu, select Export All.
    Export All in the Organization Overview action menu
    If prompted, enter your administration console credentials.
  4. Open the exported CSV file.
  5. For each organization, note the contents of the first column, orgId.

Step 3: Enable 5.x upgrades for each organization

Enabling upgrades to version 5.x of the CrashPlan app requires entering each organization's orgID into the administration console command-line interface (CLI), as described below.

Upgrade starts automatically
If Auto-upgrade devices is enabled in Settings > Server, CrashPlan apps in the enabled organizations start to upgrade automatically after you complete these steps.
  1. Sign in to the administration console on your master server as a user with SYSADMIN permissions.
  2. Double-click the Code42 logo in the upper-left to open the administration console CLI.
  3. To enable 5.x CrashPlan app upgrades for:
    • A single organization, enter: native.client.upgrade <orgID> true. Replace <orgID> with the appropriate value from the exported CSV. Repeat this step to enable upgrades for multiple organizations.
    • All organizations in your Code42 environment, enter: native.client.upgrade root true.
      The CLI responds Upgrades enabled=true.
Child organizations inherit the upgrade settings
Enabling 5.x upgrades for an organization also applies to all child organizations, even if the child organizations do not inherit device backup settings from the parent organization. To prevent 5.x upgrades for a specific child organization, enter native.client.upgrade <orgID> false for that organization.

Note that once you specify a true or false value for a specific organization, that organization no longer inherits future changes to the 5.x upgrade value from the parent organization.

Step 4: Verify each organization

Optionally, you can verify whether an organization is configured to use the upgrade to version 5.x.

  1. Sign in to the administration console on your master server.
  2. Double-click the Code42 logo in the upper-left to open the administration console CLI.
  3. Enter the following command: native.client.upgrade <orgID>
    The CLI responds Current setting=true if the organization is configured to use the upgrade to version 5.x.
    • Replace <orgID> with the appropriate information from the exported CSV.
    • Repeat this step for each organization you want to verify.

Step 5: Begin the upgrade

  1. (Code42 server version 5.3 and later only) If you haven't already, follow the steps to add the 5.x CrashPlan app to your master server.
  2. If Auto-upgrade devices is not already enabled, enable it for single devices or for all devices:
    • For single devices: From Devices, select a device and then choose Upgrade from the action menu.
    • For all devices in your Code42 environment: From Settings > Server, select Auto-upgrade devices.

Once Auto-upgrade devices is enabled, or if it was already enabled, devices upgrade the CrashPlan app automatically over the next 24 hours as they connect with the master server. Optionally, you can force devices to immediately reconnect with the master server by restarting your master server.

Step 6: Verify the CrashPlan app upgrade

Export a list of devices in your Code42 environment and sort by version to view CrashPlan apps that have not upgraded:

  1. Sign in to the administration console.
  2. Navigate to Devices.
  3. From the action menu, select Export All.
  4. Save the CSV file to your computer.
  5. Open the CSV file in the spreadsheet application of your choice.
  6. Sort by the displayVersion column and look for any CrashPlan apps with an old version number.

See View device backup status with the Reporting web app for a more detailed view of device status.

Install version 5.x of the CrashPlan app on a new device

Install CrashPlan app version 5.3.x and later

  1. Sign in to your administration console.
  2. Go to App Downloads.
  3. Download a CrashPlan app installer under Available on your Code42 server.
    If no CrashPlan app installers are listed, see Add clients to your Code42 environment.
  4. Install the CrashPlan app on your device.

Install CrashPlan app version 5.2.x and earlier

  1. Download the CrashPlan app installer that matches your Code42 server version from Code42 server and app downloads version 5.x.
  2. Install the CrashPlan app on your device.
  • Was this article helpful?