Skip to main content
Code42 Support

Upgrade the Code42 app from version 4.x to version 6.x

Available in:

  • CrashPlan PRO
    • Standard
    • Premium
    • Enterprise
Applies to:

Overview

Version 6.x of the Code42 app differs significantly from version 4.x. In particular, users see a much different interface in 6.x than in 4.x. For that reason, when you upgrade an on-premises authority server to 6.x, version 4.x Code42 apps do not upgrade to 6.x until you specifically configure them to do so. This article describes how to configure a 6.x authority server to upgrade Code42 apps from 4.x to 6.x.

The Code42 app version 6.x user interface:

CrashPlan app version 6.x

Considerations

  • This article applies to on-premises authority servers only.
  • Devices must meet the system requirements for version 6.x to be eligible for upgrade.
  • After upgrading from version 4.x to 6.x of the Code42 app, user backups continue without interruption. However, users will need to sign in upon opening the new Code42 app for the the first time.
  • The 6.x Code42 app does not display custom text or images deployed with the 4.x Code42 app. To preserve customizations, you must re-apply them to your 6.x Code42 apps before deploying the apps.
  • The 6.x Code42 app does not support backing up to other account devices (computer-to-computer backup).
    • Device destinations cannot be configured or managed from version 6.x Code42 apps.
    • After upgrading devices, use the administration console to disable device destinations and remove the associated archives.
  • Users cannot manage version and frequency settings from the Code42 app in version 6.x. Users can adjust these settings from the administration console.
  • Version 6.x of the Code42 app does not support installation per user and for everyone on the same device. If you have devices with version 4.x of the Code42 app installed per user and for everyone, prevent upgrades to version 6.x for those devices.

Upgrade devices to version 6.x

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

Your devices must use version 4.4 or later of the Code42 app before upgrading to version 6.x. If devices in your Code42 environment use Code42 apps older than 4.4, upgrade your devices before proceeding with the steps below.

Step 2: Identify your organizations' orgIDs

Obtain the orgID, a numeric identifier, for each of your organizations.

  1. Sign in to the administration console on your authority 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 6.x upgrades for selected organizations

To enable upgrades to version 6.x of the Code42 app, enter an organization's orgID into the administration console command-line interface (CLI):

  1. Sign in to the administration console on your authority server as a user with SYSADMIN permissions.
  2. Double-click the Code42 logo in the upper-left to open the administration console CLI.
  3. Enter the following command:
    Replace <orgID> with the appropriate value from the exported CSV.
    native.client.upgrade <orgID> true
    The CLI responds with Upgrades enabled=true
  4. Repeat the command for each organization whose devices you want to upgrade to version 6.x of the Code42 app.

Step 4: (Optional) Prevent 6.x upgrades for selected organizations

To force devices to remain at version 4.x of the Code42 app, enter an organization's orgID into the administration console command-line interface (CLI):

  1. Sign in to the administration console on your authority server as a user with SYSADMIN permissions.
  2. Double-click the Code42 logo in the upper-left to open the administration console CLI.
  3. Enter the following command.
    Replace <orgID> with the appropriate value from the exported CSV.
    native.client.upgrade <orgID> false
    The CLI responds with Upgrades enabled=false
  4. Repeat the command for each organization whose devices you want to remain at version 4.x of the Code42 app.
View an organization's current upgrade setting
To show the upgrade setting for an organization, enter this command in the administration console CLI:
native.client.upgrade <orgID>
  • The CLI responds Current setting=falseif upgrades are disabled.
  • The CLI responds Current setting=trueif upgrades are enabled.
  • The CLI responds Current setting=inheritif upgrade behavior is inherited* from the parent organization.
If you have a large number of organizations and don't want to manually check each one, contact Code42 for Enterprise support for assistance.
*Inheriting organizations
If your Code42 deployment started with Code42 server 5.x or later, child organizations inherit the upgrade settings of their parents, until you specify otherwise.

Step 5: Begin upgrades

  1. Add the 6.x Code42 app to your authority server.
  2. Enable upgrades for single devices or for all devices:
    • For all devices in your Code42 environment: From Settings > Server, select Auto-upgrade devices.
    • For single devices: From Devices, select a device and then choose Upgrade from the action menu. (The Upgrade option appears only if Auto-upgrade devices is deselected in Settings > Server.)

The selected devices automatically upgrade over the next 24 hours as they connect with the authority server. Optionally, you can force devices to immediately connect with the authority server by restarting your authority server.

  • Was this article helpful?