Skip to main content
Code42 Support

Code42 Platform Version 5.1.2 Release Notes (From 4.2.3.1)

Applies to:
  • Code42 CrashPlan (previously CrashPlan PROe)

Overview

Upgrading from version 4.2.3.1 to 5.1.2 of the Code42 platform introduces many new features, fixes, and enhancements. Highlights include:

  • Important security updates
  • Improved server and client upgrade processes
  • Refreshed, modern Code42 CrashPlan app user interface that no longer requires a Java Virtual Machine (JVM)
  • Performance and time-saving features such as:
    • A Legal Hold web app
    • New CrashPlan device migration wizard and support for Microsoft's User State Migration Tool (USMT)
    • Significant performance improvements to LDAP sync
    • Ability to define device backup bandwidth based on time of day (on- and off-peak business hours)
    • A new Code42 server command to export a sanitized version of the database, which removes all sensitive information
  • New tools to monitor and manage user devices:
  • The CrashPlan app can now be installed separately for each user account on a single computer.
  • Support for dual-stack IPv4/IPv6 and all-IPv6 network configurations.

Security Updates

  • Improves server-to-server and server-to-client messaging security.
  • Resolves Java security issue.
  • Improves clickjacking protection.
  • Updates Groovy library for latest security fixes.
  • Improves password security.
  • Security improvements to the Code42 API.
  • Improves cross-site scripting protection.
  • Improves SQL injection protection.
  • Corrects a server issue in which a deactivated CrashPlan Android device could still access backed up files under certain circumstances.
Code42 environments connecting to the Code42 cloud must upgrade to 4.3.4.1 before 3/1/2016
Due to a security update to the Code42 cloud, you must upgrade your Code42 environment to version 4.3.4.1 or later before March 1, 2016 if your on-premises authority server connects to the Code42 cloud. Beginning March 1, 2016, the Code42 cloud will not accept connections from versions 4.3.2 and earlier. This means backups and restores to the Code42 cloud will stop working.

For more information on this required upgrade, review the Code42 Public Cloud Version Policy.

New Features

Refreshed, Modern CrashPlan User Interface

Version 5.x of the Code42 CrashPlan app simplifies life for administrators and users with an overhauled user interface that makes it even easier to manage and use CrashPlan for backup and recovery. The new CrashPlan app also uses a natively precompiled Java service, which eliminates the need for a Java Virtual Machine (JVM) on each device. See Changes To The Code42 CrashPlan App In Version 5.x for complete details.

Improved Server And Client Upgrade Processes

The upgrade to version 5.1.2 is now possible in fewer steps than ever before. And, once your Code42 environment is on version 5.1.2, all future Code42 server upgrades will be much simpler.

In addition, the upgrade process for the CrashPlan app on Windows devices is greatly simplified and less error-prone than in the past. Previous CrashPlan app upgrades involved modifying the existing install. With 5.1.2, the upgrade process does a clean install, yet still retains all user settings.

LDAP Performance Improvements

Code42 environments using LDAP sync benefit from substantial performance improvements. In some cases, LDAP sync now completes in minutes instead of hours.

Windows User Profile Backup

The Code42 platform now supports user profile backup and integration with Microsoft's User State Migration Tool (USMT). User profile backup makes it easy to use CrashPlan to migrate system settings and application data to a new or upgraded user device.

CrashPlan App Replace Device Wizard

The CrashPlan app's new replace device wizard makes it even easier for users to transfer files and update settings from a previous device. When paired with our USMT feature, this greatly simplifies and speeds up device migration and refreshes.

Legal Hold

The Code42 Legal Hold web app allows legal teams to easily create and manage legal holds, place users (custodians) in your Code42 environment under a legal hold, and collect data from legal holds. For complete details, see Configuring A Legal Hold.

Schedule-Based Bandwidth Management

New scheduled sending limits allow administrators to specify different data transfer rates for peak and off-peak business hours. This helps ensure device backup activity does not slow down your network during the work day.

Enhanced Indexing And File Search

New indexing capabilities and an accompanying File Search web app allow administrators to search a user's backed up files based on file name, file content, and file metadata. This helps administrators and the security and legal teams determine if an employee accessed sensitive or confidential information.

Endpoint Monitoring

Endpoint monitoring leverages the CrashPlan app to monitor user devices for potential security problems or data leaks resulting from removable media, third-party cloud storage apps, unusual restore activity, and more. Administrators can view these events in real-time using the new Security web app.

Code42 Reporting Web App

The Code42 platform now features a Reporting web app, which enables administrators to easily search and view the backup status of users and devices. 

Database Sanitization

The Code42 server contains a new command to export a sanitized version of the database, which removes all sensitive information. This enables administrators to quickly and easily provide Code42 Customer Champions data for troubleshooting, without exposing any sensitive or personally-identifiable information. 

Improved Code42 App For Splunk

The Code42 app for Splunk version 2.1 introduces:

  • Support for new features in the Code42 server version 5.1, including file content pattern matching, file upload detection and other endpoint detection events
  • Other enhancements for security and stability
CrashPlan Per-User Installation

The CrashPlan app can now be installed separately for each user account on Windows and OS X computers. When installed per user, each installation behaves as a separate device with its own settings, license, and backup archive.

Full IPv6 Support

The Code42 platform now supports dual-stack IPv4/IPv6 and all-IPv6 network configurations. For more information about implementing IPv6, see Using IPv4 & IPv6 In Your Code42 Environment.

External Reference Fields

New reference fields allow administrators to add descriptive information to devices, users, and organizations. This information can be used to integrate with external systems, and also to add additional context to items in the administration console.

Unified Web Login

All Code42 web apps—such as the administration console and Legal Hold web app—now share the same login screen, which allows users to sign in once and switch between apps using a new streamlined header.

Fixes And Enhancements

Upgrading from version 4.2.3.1 to 5.1.2 also includes numerous other fixes and enhancements to the Code42 platform, administration console, CrashPlan app, and Code42 API.

Code42 Platform

  • Critical security updates.
  • Performance and stability improvements.
  • CN-760 Significantly improves LDAP sync performance.
  • The minimum required Java version for the Code42 server is now 1.8.
  • Java is now bundled with the OS X Code42 server installer.
  • Corrects an issue in which the enterprise server could become unresponsive while balancing archives between store points on the same server.
  • Corrects an issue introduced in version 4.3.4.1 in which the transaction recovery log could fail to properly recover enterprise server activity.
  • Corrects an issue in which enterprise server logs could be truncated during a server shutdown.
  • Improvements to server-to-server sync and balancing processes.
  • Email notifications about user licenses nearing expiration now direct administrators to view licensing details in the administration console.
  • Code42 servers that only have IPv6 addresses can now communicate with other Code42 servers that have hostnames with both IPv4 and IPv6 DNS records.
  • LDAP environments that also require the account password to access the CrashPlan app no longer generate a new login token every time the password is entered.
  • Corrects an issue that could cause balancing archives from a Windows storage server to a master server in the same destination to fail.
  • Improvements to server-to-server sync processes.
  • Corrects LinkedIn link in the footer of emails sent from the Code42 server.
  • In Code42 environments with more than one destination, devices can now back up normally to other destinations if the master server is offered as a destination but has no store points.
  • Improved options for syslog configuration, which now also persist through enterprise server upgrades.
  • Corrects an issue introduced in version 4.1.7: administrators can now restore a user's backup archive to a device not owned by that user.
  • Previously deactivated CrashPlan devices can now resume backups and restore from provider storage destinations without administrator intervention or waiting for a node sync to occur.
  • Corrects an issue introduced in version 4.2.0: administrators can now reactivate a user that belongs to a previously deactivated organization.
  • Adds global exclusion for Windows devices to not back up files or folders ending with .tmp.
  • Administrator backup alert emails now include the computer name.
  • Users now receive both a warning email (after 3 days by default) and a second critical alert email (after 7 days by default) if a device is not backing up. (This corrects an issue introduced in version 4.1.6 in which some users only received the first email.)
  • In a provider storage environment, adds the ability to unblock a child organization of a blocked parent organization.
  • The server history log now correctly captures the source organization when moving a user to a different organization.
  • Improvements to server upgrade logging.
  • Improves logging when purging archives from cold storage.
  • Removes entries from the recovery log not relevant to recovery.
  • The enterprise server build number is now included in the app.log.
  • Improves stability if a node.sync is started while a previously started node.sync is still in process.
  • Adds support for SSO AD FS environments with more than one certificate.
  • Corrects issue which prevented some customers from being able to execute a full directory LDAP sync.
  • Corrects issue introduced in 4.2.0 in which the daily.services job logged unnecessary storage server system alerts.
  • Corrects an issue that could prevent an administrator from configuring a custom certificate for SSO with the Code42 API.
  • When configuring SSO, administrators can now access the master server’s service provider metadata file without adding an identity provider first.
  • Improvements to server-to-server sync processes.
  • Corrects an issue introduced in version 4.2.0 in which some administrators applying a server upgrade were prompted to sign in a second time, which resulted in the upgrade file uploading to the server a second time.
  • Corrects an issue introduced in version 4.2 for environments with multiple LDAP servers in which some users had trouble signing in.
  • The web restore quota is no longer incorrectly applied to push restores for users without web restore permissions.
Critical LDAP Fix
Upgrading from 4.2.3.1 to 5.1.2 also corrects an issue introduced in version 4.2.0 that could lead to data loss: if your LDAP server is unavailable when your Code42 master server performs LDAP synchronization, users could be deactivated. When a user is deactivated, the user’s backup archives are placed in cold storage.

By default, the cold storage retention period is 365 days, with an additional 20-day grace period. However, if you changed these defaults for your Code42 environment to a shorter time period and you do not manually reactivate affected users before the retention period ends, the users' archives are permanently deleted.

See LDAP Sync Incorrectly Deactivates Users for complete details.

Administration Console

  • Corrects rare issue in which searching for a computer and selecting an item in the Plans section returned no results.
  • Corrects minor cosmetic display issue in Settings > Device Backup > Backup > Frequency And Versions: when scrolling down, the sliders no longer partially display on top of the page footer.
  • Improvements to administration console translations.
  • Introduces Korean as a new available locale.
  • The Device Overview, Users Overview, and Plans Overview now display correctly when accessing from the Safari browser in Private Mode.
  • Downloading the sample file to bulk add users no longer prompts to re-enter the username and password.
  • Improvements to page layout when viewing the Devices > action menu > Edit > Network screen in a small browser window.
  • Corrects rare issue in which changes made from Organizations > Action Menu > Device Backup Defaults may not save properly if changes were also made from Organizations > Action Menu > Edit.
  • Corrects issue introduced in version 4.3.0: the Logout link in the administration console of a storage server now properly logs the user out.
  • From the Organizations action menu, Show Deactivated is disabled if no organizations have been deactivated.
  • Improves accuracy of archive size reported in the Migrate Device Archives confirmation message.
  • The title of the Destinations > Balancing Activity screen displays correctly when there are no balancing activities listed.
  • Improved scrolling experience for organizations with many child organizations.
  • No longer able to select Local directory service when authentication method is LDAP.
  • Improved error messaging when attempting to move a store point to a new path before creating the directory.
  • Improved error messaging when an administrator attempts to perform a web restore from a provider destination.
  • From the Organizations Overview screen, clicking a value in the Backup Devices column now correctly only displays the devices in that organization.
  • Corrects issue introduced in version 4.3 in which attempting to sign in to a storage server’s administration console more than once could fail.
  • The CLI command test.email <user email> code42 no longer generates an unnecessary warning message.
  • Configuring backup inclusions in the administration console to include :allusers now correctly applies the backup file selection to new users.
  • Improved Korean translations.
  • Improved performance when exporting and downloading a CSV file with a large dataset from the administration console.
  • Removes the Sign up for an account option from the administration console sign in screen.
  • Corrects an issue in which some users were unable to reset passwords via the administration console sign in screen when using Internet Explorer 10 or 11.
  • Corrects an issue introduced in version 4.2 in which Use default archive encryption setting did not stay locked when an administrator locked the setting.
  • When an administrator locks backup set settings in the administration console, the File Selection for the backup set now correctly displays a lock icon.
  • Selecting Print from an action menu now correctly prints all items when the list is longer than one page.
  • Moving a child organization to a different parent organization now more clearly indicates that the child organization does not inherit the Device Backup Default settings from the new parent organization. 
  • Organizations with multiple LDAP servers can now manually add users to the Code42 environment if one LDAP server is offline.
  • In provider storage environments, web restores are now included in the Restore column count on the Device Details screen.
  • Enabling archive key password security is no longer allowed from the administration console for users in organizations that use SSO. Instead, users are instructed to enable archive key password from the CrashPlan app. This prevents a known issue that could lead to the archive becoming inaccessible.
  • Corrects an issue in which the the web-enabled licensing store could switch to the local licensing screen.
  • In Settings > Organization > Quotas, the web restore limit fields now more clearly specify to which users the values apply.
  • Clicking Days Left from the Licensing section of the dashboard correctly routes you to the enhanced enterprise licensing interface.
  • Improvements to page layout when viewing the Organization Settings screen in a small browser window.
  • In the Users detail view, blocked devices are now indicated by the same red icon used to indicate blocked devices in the Device Overview.
  • Improvements to administration console translations.
  • All languages in the languages list now appear in their locale.
  • Improved performance when adding hundreds or thousands of users at once via an uploaded text file.
  • Corrects an issue introduced in version 4.2.0: the Reconnect button correctly reconnects users who were disconnected from the administration console, without the need to sign in again or manually refresh the page.
  • Child organizations that Inherit destination settings from parent are only able to offer the same destinations offered by the parent organization.
  • Corrects issue introduced in version 4.2.0 in which pushing and locking file exclusions for all operating systems incorrectly replaced any existing customized exclusions for an individual operating system.
  • Alerts now expire and are removed from the Alerts page after 90 days.
  • Corrects issue introduced in version 4.2.0 which required some users to sign in to the administration console again after upgrading. 
  • Corrects rare issue in which the upgrade devices reminder at the top of the administration console remained visible even after device upgrades occurred.
  • Changing the enterprise server's primary or secondary network address now immediately updates the address on user devices.
  • Restores ability to sort archives in Cold Storage by organization name and store point name.
  • Corrects issue for provider storage environments introduced in version 4.2.0 in which clicking the Cold value from the Destination details incorrectly displayed the message “No cold storage." 

CrashPlan App​

Version 4.5.2

  • Security updates.
  • Performance and stability improvements.
  • The minimum required Java version for the CrashPlan app is now 1.7.
  • Corrects issue introduced in version 4.3 of the Windows CrashPlan app in which the the CrashPlan Tray app (the CrashPlan icon in the notification area) is dimmed and disabled when the CrashPlan app is installed in a folder other than the default location.
  • Improvements to the upgrade process in the OS X CrashPlan app when applying upgrades that span multiple versions.​
  • Improvements to OS X CrashPlan app customization process: customizing the default.service.xml file is now honored by the installer.
  • Corrects rare issue that could prevent a user with two different computers backing up to a provider storage destination from being able to restore files from one computer to the other.
  • Enables upgrades for OS X devices using CrashPlan app version 3.7 installed to "run as user”.
  • CrashPlan apps installed per user that also use LDAP deferred passwords now start backing up automatically, without requiring the user to sign in first.
  • Corrects an issue in which some 4.3.x CrashPlan apps installed per user do not upgrade correctly.
  • After adopting a computer, CrashPlan now automatically updates the backup file selection to include the default backup file selection of the user's Organization. This ensures the new computer is protected. Like earlier versions of the CrashPlan app, the previous computer's file selection is also transferred as part of the adoption.
  • Improvements to the CrashPlan app upgrade process.
  • Windows users now have the ability to choose to restore files with original or current user permissions.
  • The default backup set name now displays correctly in the CrashPlan app when the device name is locked in the administration console.
  • Improvements to logging.
  • Corrects an issue for per user CrashPlan app installations in which the backup progress never reached 100% under certain circumstances.
  • The CrashPlan app now displays fewer confirmation dialogs when installing per user on Windows devices.
  • Improves logging when restoring files backed up from an OS X device to a Windows device.
  • CrashPlan apps installed per user that also use LDAP deferred passwords now start backing up automatically, without requiring the user to sign in first. 
  • When the CrashPlan app is installed per user in a non-default location on a Windows device, the CrashPlan tray app now opens correctly.
  • Fixes a rare issue in which archive maintenance might not finish properly if a new version of a file was created with a timestamp older than the previous most recent version. This typically occurred if the device's time and date were manually changed to a time in the past.
  • Fewer confirmation messages appear when uninstalling the Windows CrashPlan app.
  • The CrashPlan app now uses dynamic port selection when connecting to the Code42 cloud and computer destinations. If necessary, you can review our tutorial to identify the ports used by the CrashPlan app.
  • Corrects an issue that prevented users from restoring a previous version of a file from the CrashPlan web app when the filename contained an apostrophe.
  • Corrects an issue that prevented users from using the CrashPlan web app on OS X and Linux to restore files in a folder with restricted permissions.
  • Adds a filename exclusion for Windows devices to not back up files or folders ending with .tmp.
  • Corrects an issue introduced in 4.1.6 in which the critical backup alert email for a computer not backing up (sent after 7 days by default) would not always send. The warning backup alert email for a computer not backing up (sent after 3 days by default) was not impacted.
  • In environments with multiple provider storage destinations, the CrashPlan app no longer presents the option to Start Backup to a destination that is no longer offered to users.
  • Resolves issue introduced in 4.2.0 in which upgrading to custom key security or changing the custom key caused the CrashPlan app to never finish synchronizing.
  • Corrects a rare issue introduced in version 4.2.0 in which the CrashPlan app installation could fail on a Windows device if Windows Firewall was disabled.​
  • For environments using customized CrashPlan app installers with a deferred password that also have enabled archive password security, adding additional devices for an existing user no longer prompts the user to create a new archive password.
  • In SSO environments, the CrashPlan app now correctly displays the SSO sign in page when Require account password to access CrashPlan app is enabled.
  • Improvements to the upgrade process in the OS X CrashPlan app when applying upgrades that span multiple versions.
  • Improves performance of the real-time file watcher on Windows devices when renaming large numbers of files.
  • Corrects an issue on OS X devices introduced in version 4.3.0 in which the CrashPlan uninstaller included in the .dmg could only uninstall CrashPlan one time. Now, the same uninstaller can be used more than once.

Version 5.1.2 (also includes all fixes listed above for version 4.5.2)

  • The CLI command restart now correctly restarts the CrashPlan app if the app is installed per user.
  • Corrects issue introduced in version 4.3.0 when installing per user in which the backup completion percentage never reached 100%.
  • Corrects an issue on OS X devices introduced in version 4.3.0 in which the CrashPlan uninstaller included in the .dmg could only uninstall CrashPlan one time. Now, the same uninstaller can be used more than once.
  • Improved error messaging if the localhost entries in a device's hosts file do not point to the default loopback IP addresses.
  • Corrects issue in which some customized CrashPlan app installers allowed the user to edit the server address field, even when lockedAddress was set to true.
  • Corrects an issue in which an unmounted Network File System (NFS) on an OS X device could be automatically re-mounted by CrashPlan.
  • The CrashPlan app for OS X now uses a natively precompiled Java service, which does not require the Java Virtual Machine (JVM) to run.
  • Improvements to the CrashPlan app upgrade process on Windows devices.
  • Removes the need for users to accept a confirmation dialog when installing or uninstalling the Windows CrashPlan app under certain circumstances.
  • The CrashPlan app for Windows now uses a natively precompiled Java service, which does not require the Java Virtual Machine (JVM) to run.
  • The CrashPlan app can no longer be administered from another device (sometimes referred to as "headless" operation). CrashPlan can only be controlled directly from the device running the CrashPlan app, or from the administration console.
  • Improves compatibility for IPv6 literal hostnames.

Code42 API​

New Reporting Capabilities

The new DeviceBackupReport resource provides options for powerful reporting on devices.

  • One API call provides all of the most commonly needed information on devices, users, and orgs.
  • More efficient than making multiple API calls to separate resources.
  • Greater visibility into resource usage by devices and users.

New Custom Metadata Fields

The following Code42 API resources now have custom metadata fields that can be used for external references and descriptive notes:

  • Computer
  • Org
  • User

Fixes And Enhancements

  • Security updates.
  • Performance and stability improvements.
  • The File resource now supports deleting a file.
  • The File resource now supports moving a file.
  • Default boolean input parameters now set correctly for the following resources:
    • Computer
    • User
    • PlanSummary
  • The ArchiveMetadata resource decrypts paths for backup archives located in provider storage.
  • The path input parameter for the FileVersions resource now correctly appears in the API Documentation Viewer as a path parameter, not a query parameter.
  • The SsoAuthSpMetadata resource returns the updated identity certificate after the certificate is changed through the administration console.
  • The documentation for the WebRestoreJob resource in the API Documentation Viewer has been corrected to reflect the fact that the resource does not support starting a push restore job.
  • The Archive resource now accepts the following query parameters, which had been removed in version 4.2.0:
    • targetComputerId
    • guid
  • The ColdStorage resource now accepts the following query parameters, and provides the following output values, which had been removed in version 4.2.0:
    • Query parameters:
      • values for the srtKey parameter
        • sourceUserName
        • sourceComputerName
    • Output values:
      • fcuId
      • sourceUserId
      • sourceUserFirstName
      • sourceUserLastName
      • sourceUserEmail
      • sourceComputerId
      • sourceComputerName
      • sourceComputerService
  • Users are no longer required to have administrator permissions to change their own archive password via the Code42 API.
  • The incAll input parameter of the Computer resource no longer produces an error when the search query returns multiple devices.
  • Administrators in hybrid storage environments can now use the ArchiveMetadata resource to access archive metadata in provider storage destinations.

API Documentation Viewer

  • The examples in the BalancingCommand resource now correctly specify archiveGuid (instead of guid).
  • The ArchivePassword resource more clearly explains under what circumstances the current password is required.
  • The WebRestoreJob resource now indicates that the resource does not support starting a push restore job.

Videos

The videos below summarize many of the new features introduced in versions 4.3, 5.0, and 5.1.