- Code42 for Enterprise
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 appropriate .jar file. There are two .jar files in this location: one with an underscore and build number at the end of the file name (for example, "1466571600600_333.jar"), and one without the build number. The client you're upgrading from determines which .jar to use:
- Upgrading from clients older than 4.4.x: Copy the .jar file without a build number at the end of the file name.
- Upgrading from clients 4.4.x and newer: Copy the .jar file with a build number at the end of the file name.
- Push the appropriate .jar file using your preferred file management application and place it in the following Code42 app directory on user devices:
- Linux: /usr/local/crashplan/upgrade
- Code42 app 4.x: /Applications/CrashPlan.app/Contents/Resources/Java/upgrade/
- Code42 app 5.0 to 6.7.1: /Applications/CrashPlan.app/Contents/Resources/Code42/upgrade
- Code42 app 6.7.2 and later: /Library/Application Support/CrashPlan/upgrade
- Windows: C:\Program Files\CrashPlan\upgrade
After pre-staging the upgrade files, you can upgrade the Code42 apps on devices in your environment.