Skip to main content

Who is this article for?

Code42 for EnterpriseSee product plans and features
CrashPlan for Small Business 

CrashPlan for Small Business, no.

Code42 for Enterprise, yes.

Link: Product plans and features.

This article applies to Cloud.

Other available versions:

Version 6 and laterLink: What version am I on?

Code42 Support

Upgrade client deployment to version 6.5 or later

Overview

Co-branding and deployment of Code42 apps changed significantly with version 6.5. The new process is simpler, more secure, and allows for changes to Code42 apps after they are distributed and installed. This article describes how to duplicate existing configurations in the new processes that took effect with version 6.5.

New deployments of Versions 6.5 and later must use the new process
The new deployment process has no effect on already-installed Code42 apps that you upgrade to version 6.5. But to deploy new Code42 apps version 6.5 and later, you must use the new version 6.5 deployment process.

Considerations

These instructions apply to the Code42 cloud. If you work in an on-premises Code42 environment, see Manage app installations in your Code42 environment.

To use these deployment tools, you need to sign in to your administration console as a user with the role:

Duplicate existing configuration in the new administration console tools

Co-branding and customizing version 6.4 and earlier Code42 apps meant downloading and editing a set of configuration files.
version 6.4 and earlier configuration files

To duplicate your existing co-branding and custom deployment, use your administration console version 6.5 or later:

As you proceed, duplicate your existing customization in the administration console, as described below.

Co-branding and deployment are separate now
Co-branding and deployment are separate operations in versions 6.5 and later, and you can change co-branding at any time after deployment.

Deployment policies

Copy co-branding images

If you co-branded your Code42 apps version 6.4 and earlier, copy two of your custom images to the new co-branding tool in your administration console, version 6.5 and later.

  • Code42CrashPlan_Custom/skin/co-branding/about.png
  • Code42CrashPlan_Custom/skin/co-branding/login.png

See the article Client customizations

Duplicate deployment configuration

Duplicate custom.properties

The custom.properties file guided old-style deployments to all devices. Duplicate its parameters in a 6.5 and later deployment as follows:

Property name Description

address

secondaryAddress

hideAddress

lockedAddress

Do nothing. Your authority server's address is automatically written to your deployment policy and hidden in the Code42 app UI. You do not need to provide it. Users cannot change it.

registrationKey

Do nothing. The registration key is automatically written to your deployment policy when you select the Code42 organization that new Code42 apps register into.

username

In the administration console's deployment policy tool, either select the default user-detection script or provide a custom script.

password The new deployment process either auto-generates passwords or gets them from your SSO or LDAP system.

proxy.enable

proxy.pacUrl

Configure proxies as a part of configuring the organization that your newly deployed Code42 apps sign into during installation.

ssoAuth.enabled

ssoAuth.required

Configure the authentication method as a part of configuring the organization that your newly deployed Code42 apps sign into during installation.

Duplicate userinfo.sh for Mac

The userinfo.sh script guided old-style deployments to Mac devices. Duplicate its parameters in a 6.5 and later deployment as follows:

Variable Description
startDesktop

In the administration console's deployment policy tool, select:

Launch desktop app after initial install? Yes or No.

CP_USER_HOME

user

userGroup

CP_USER_NAME

In the administration console's deployment policy tool, either select the default user-detection script or provide a custom script.

When a newly deployed Code42 app installs, it downloads and runs that script. The script examines the device and determines the username and home directory for the new Code42 app.

Duplicate your install command for Mac

The install command for version 6.5 Code42 apps on Mac has slight changes.

Copy the -target argument from your existing install command:

Argument Description
- target LocalSystem Installs the client for all users of a device.
- target CurrentUserHomeDirectory Installs the client for the currently signed-in user only.

Duplicate your install script for Windows

For old-style deployments to Windows devices, you provided a custom install script, *.bat. Duplicate its parameters in a 6.5 and later deployment as follows:

Variable Description
CP_SILENT

In the administration console's deployment policy tool, select

Launch desktop app after initial install? Yes or No.

CP_USER_HOME

CP_USER_NAME

In the administration console's deployment policy tool, either select the default user-detection script or provide a custom script.

When a newly deployed Code42 app installs, it downloads and runs that script. The script examines the device and determines the username and home directory for the new Code42 app.

CP_REG_KEY Do nothing. The registration key is automatically written to your deployment policy when you select the Code42 organization that new Code42 apps register into.
ALLUSERS=2
MSIINSTALLPERUSER=1
INSTALL_PER_USER=1

In a Code42 app install command, these three arguments cause installation for a single user of each device, not all users.

You can add the same arguments to the installation properties that you copy from your deployment policy to your software management tool or deployment scripts.