Client Management Updates reference guide (CrashPlan)
Who is this article for?
Instructor, no.
Incydr Professional, Enterprise, Gov F2, and Horizon, no.
Incydr Basic, Advanced, and Gov F1, no.
CrashPlan Cloud, yes.
Retired product plans, yes.
CrashPlan for Small Business, no.
Overview
This reference guide explains the Client Updates settings in the Code42 console, which enable administrators to define Code42 app upgrade schedules by organization. Configuring these settings to specify when new versions of the Code42 app are released to user devices enables you to:
- Test new Code42 app versions on a small group of users before updating all users in your Code42 environment.
- Schedule Code42 app upgrades to better align with your change management process.
- Create a staggered rollout schedule based on organization. Upgrading the Code42 app over several days or weeks can help you better manage network resources.
New Code42 app release dates are announced in advance in the Code42 community. To automatically receive email notifications about upcoming releases, subscribe to announcements for your product plan.
Considerations
Client Updates
To view or modify Code42 app upgrade schedules:
- Sign in to the Code42 console.
- Select Administration > Client Management > Updates.
| Item | Description | |
|---|---|---|
| a | Delays | Displays options for setting a global delay or organization specific delays. |
| b | Version Blocking |
Displays options to block Code42 app upgrades to a specific version.
Version Blocking is not visible by default. To enable Version Blocking, contact our Customer Champions for support. |
| c | Global Delay |
Defines the number of days after the release date that organizations in your Code42 environment receive the updated Code42 app, with the exception of any organizations listed in the Organization Specific Delays section below. The maximum delay is 60 days.
See the Code42 community for Code42 app release dates. |
| c | Organization Specific Delays |
Lists organizations configured to use a different delay setting than the Global Delay. |
| e | Add Delay | Click to add a delay for an organization that differs from the Global Delay. Choose a Recurring or One-time delay. |
| f |
Organization |
The organization to which the delay applies. Includes all child organizations, unless a child organization has its own delay. |
| g | Delay Type |
|
| h | Scheduled Update |
Date the Code42 app is updated on user devices. Upgrades begin at midnight Coordinated Universal Time (UTC) on the selected date.
For Recurring delays, this date is calculated by adding the Delay number of days for this organization to the original Code42 app release date. Recurring delays do not specify a Scheduled Update date because the date changes for each version and each release, but it is always the same number of days after the Code42 app release date. |
| i | Delay |
The number of days after the release date this organization receives Code42 app updates. The maximum delay is 60 days. Only applies to Recurring Delays.
See the Code42 community for Code42 app release dates. |
| j | New Version | The Code42 app version number to which the delay applies. |
| k | Actions |
Click to view options for managing this delay:
|
During the delay period, you always have the option to manually update clients before the Scheduled Update date.
For all devices in an organization:
- Select Administration > Environment > Organizations.
- Select an organization.
- From the action menu in the upper-right, select Upgrade Clients.
- From the navigation menu on the left, select Administration > Environment > Devices.
- Select a device.
- From the action menu in the upper-right, select Upgrade.