Skip to main content

Who is this article for?

Code42 for Enterprise
CrashPlan for Small Business

Code42 for Enterprise, yes.

CrashPlan for Small Business, no.

This article applies to on-premises authority servers.

Other available versions:

CloudLink: What version am I on?

HOME
GETTING STARTED
RELEASE NOTES
FAQS
SYSTEM STATUS
Code42 Support

Pre-stage the Code42 app upgrade

Who is this article for?

Code42 for Enterprise
CrashPlan for Small Business

Code42 for Enterprise, yes.

CrashPlan for Small Business, no.

This article applies to on-premises authority servers.

Other available versions:

CloudLink: What version am I on?

Overview

By default, upgrading devices involves sending files from the authority server to each user device when the device connects to the authority server. Depending on your environment, this process can consume enough network bandwidth that it results in slower network speeds during your employees' working hours. To alleviate this problem, you can optionally pre-stage the Code42 app upgrade files on each device during off-peak hours using a client management tool like SCCM or JAMF.

Considerations

Perform this procedure before enabling the Auto-upgrade devices setting on your Code42 server.

Steps

  1. Navigate to the /upgrade5 directory on your authority server:
  • Linux: /opt/proserver/installs/<OS folder>/upgrade5
  • Windows: C:\Program Files\CrashPlan PROe Server\installs\<OS folder>\upgrade5
  1. Copy the .jar files from the OS folders. The .jar files have an underscore and build number at the end of the file name (for example, "1466571600600_333.jar").
  1. Push the .jar files using your preferred file management application and place them in the following Code42 app directory on user devices:
  • Linux: /usr/local/crashplan/upgrade
  • Mac: /Library/Application Support/CrashPlan/upgrade
  • Windows: C:\Program Files\CrashPlan\upgrade

What's next

After pre-staging the upgrade files, you can upgrade the Code42 apps on devices in your environment.