Who is this article for?
CrashPlan for Enterprise, yes.
Code42 for Enterprise, yes.
CrashPlan for Small Business, no.
This article applies to on-premises authority servers.
Other available versions:
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.
Perform this procedure before enabling the Auto-upgrade devices setting on your Code42 server.
- 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
- 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").
- 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
- Version 8.2 and later: C:\Program Files\Code42\upgrade
- Version 8.0 and earlier: C:\Program Files\CrashPlan\upgrade
After pre-staging the upgrade files, you can upgrade the Code42 apps on devices in your environment.