CrashPlan app version 11.0 changes to application and service names

Overview

As one of the final pieces of CrashPlan separating from Code42, the CrashPlan agent will undergo branding updates as part of the version 11.0 agent release, targeting early February 2023.

The 11.0 agent will be updated to remove mentions of Code42 Software across all platforms (Mac, Windows, and Linux). Items which will be updated include:

  • Application and service process names
  • Menu shortcuts and names
  • Code signing certificates
  • Icons and logos

This article details the complete list of changes and highlights some affected areas that may require your IT or Security teams to make corresponding updates to your internal processes. 

Affects

If your CrashPlan environment uses any of the following, update your configurations to use the new names and directories listed below to ensure compatibility with CrashPlan app version 11.0 and later:

  • Firewall rules, if based on the Code42Service name. (Firewall rules based on IP addresses are not affected.)
  • Application monitoring with device management tools like SCCM or Jamf to ensure the CrashPlan process is always running.
  • CrashPlan exceptions for antivirus, malware, or other security monitoring tools.
  • Automated or scripted deployment and installation processes that include the filename of the  .msi, .dmg, or .tgz CrashPlan installer.

CrashPlan app download URLs were changed prior to the 11.0 release, but it's important to ensure your organization is using the correct links to the latest version of the application listed below. Any attempts to use older Code42 links will result in a timeout.

Changes

If you have any scripts, monitoring, exceptions, or other processes that specifically reference any item in the Code42 app version 10.4.1 column, you must update those references to use the new value in the CrashPlan app version 11.0.0 column.

Many items – including the macOS bundle ID and file locations for logs, app data, and caches – remain the same. Only the items listed below changed in CrashPlan app 11.0.0. 

Windows

Item CrashPlan app version 11.0.0 Code42 app version 10.4.1
Application / Start menu names
  • CrashPlan
  • CrashPlan Tray
  • Code42
  • Code42 Tray
Application location

Default install

C:\Program Files\CrashPlan\

Per user install

C:\Users\<username>\AppData\<Local or Roaming>\Programs\CrashPlan\

Default install

C:\Program Files\Code42\

Per user install

C:\Users\<username>\AppData\<Local or Roaming>\Programs\Code42\

Service name CrashPlanService Code42Service
Process names
  • CrashPlanService
  • CrashPlanDesktop
  • Code42Service
  • Code42Desktop
Installer file name
  • CrashPlan_11.0.0_Win64.msi
  • CrashPlan_11.0.0_Win32.msi
  • Code42_10.4.0_Win64.msi
  • Code42_10.4.0_Win32.msi
Upgrade location

Default install
C:\Program Files\CrashPlan\upgrade\

Per user install

C:\Users\<username>\AppData\Local\Programs\CrashPlan\upgrade\

Default install
C:\Program Files\Code42\upgrade\

Per user install

C:\Users\<username>\AppData\<Local or Roaming>\Programs\Code42\upgrade\

Mac

Item CrashPlan app version 11.0.0 Code42 app version 10.4.1
Application / Finder name CrashPlan Code42
Application location

Default install

/Applications/CrashPlan.app/

Per user install

 ~/Applications/CrashPlan.app/

Default install

/Applications/Code42.app/

Per user install

~/Applications/Code42.app/

Activity monitor names
  • CrashPlan Service
  • CrashPlan
  • Code42 Service
  • Code42
Installer file name CrashPlan_11.0.0_Mac.dmg Code42_10.4.0_Mac.dmg
Launch script com.crashplan.service.plist com.code42.service.plist

Linux

Item CrashPlan app version 11.0.0 Code42 app version 10.4.1
Application menu name CrashPlan Code42
Installer file name CrashPlan_11.0.0_Linux.tgz

Code42_10.4.0_Linux.tgz

Other considerations

  • Install and Uninstall scripts will need to be updated to reflect the new app paths and names.
  • Review any internal documentation and update content such as steps, screenshots, etc. to reflect the new paths and names.
Was this article helpful?
0 out of 1 found this helpful

Articles in this section

See more