Deploy Code42 apps for manual sign on

Last updated
Save as PDF
Share
1. Share
2. Tweet

Who is this article for?

CrashPlan for Small Business

Incydr, yes.

CrashPlan for Enterprise, yes.

Code42 for Enterprise, yes.

CrashPlan for Small Business, no.

This article applies to Code42 cloud environments.

Other available versions:

On-premises

Error: missing value for parameter 'doc' (index 0) (click for details)

Callstack:
    at xml.select()
    at (Template:Code42/SiteMapThisPage), /content/body/pre, line 30, column 11
    at template()
    at (Administrator/Cloud/Planning_and_installing/Manage_app_installations_in_your_Code42_environment/Deploy_Code42_apps_for_manual_sign_on), /content/body/pre[1], line 6, column 9

Overview

This article describes how to configure deployment packages to open Code42 app interfaces automatically on users' desktops. Backups begin when users sign in to your Code42 environment.

Considerations

This article assumes you understand the introduction to deployment provided by the article Prepare to deploy Code42 client apps.

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 Code42 console as a user with the Customer Cloud Admin role.
In the Code42 federal environment, app installations must be deployed with a deployment policy to ensure the use of FIPS encryption in the Code42 app. Users cannot download the installation package from the Code42 console or an email message.

Step 1: Identify the deployment organization

In your Code42 console, create or identify an organization that has at least one destination where backups can auto-start.

Check configuration of the organization, as follows:

Sign in to the Code42 console.
Select Administration > Environment > Organizations.
Select an organization.
Note the organization name; you will need it later.
Select DEVICE BACKUP DEFAULTS > Backup.
- DESTINATIONS should list at least one destination name and Yes.
- The other possible value, DESTINATIONS ... Auto-start, means endpoint backups do not start until users manually select a destination. In the Code42 app interface, see Tools > Options > Destinations.
- To configure destinations, go to the organization's action menu. Select Device Backup Defaults > Backup > Destinations.

Select DEVICE BACKUP DEFAULTS > Network.
Note whether PROXY is enabled; you will need that information later.
If necessary, change organization configuration. In the action menu in the upper-right, select Edit.

Step 2: Create the deployment policy

Define the deployment policy for the organization you identified in Step 1.

In the Code42 console, select Administration > Client Management > Deployment.
Select Create New Deployment Policy or Create New Policy.
The prompt differs depending on whether you see the initial welcome screen or your list of existing policies.
Enter a Policy Name to describe this policy.
At How should new users register? select the organization you identified at Step 1, above.
If your organization's name is grayed out in the menu, that organization already has a policy.
You may edit or delete that existing policy.
At Do you want to automatically register users?, select No.
Organizations using local authentication have no choice: No is selected. Yes is greyed out.
At Which operating systems, select the systems you will deploy Code42 apps to.
For each operating system you select, select Add a custom batch/bash script.
Provide a script that identifies the username and home directory that the Code42 app will provide when it registers with your Code42 environment. The script must end by echoing the username and user home directory. The username must be an email address. For details, see the script reference.
```
echo C42_USERNAME=<value>
echo C42_USER_HOME=<value>
```
The Code42 cloud requires a custom script
Because user names in the Code42 cloud must be email addresses, deployments for connection to the Code42 cloud always require a customized user detection script.
At Do your clients need a proxy URL, select No or Yes, depending on what you determined at Step 1, above.
At Launch desktop app after initial install, select Yes.
The desktop interface opens so that users can create passwords and submit their credentials.
Click Save.
The Policy Saved dialog appears.
Click Done.
You do not need to save or download the installation properties now. You can easily reach them later, as you configure your deployment software.

Example username detection scripts for the Code42 cloud

Step 3: Deploy Code42 apps to user devices

Retrieve installation properties from your deployment policy as follows:

Sign in to the Code42 console.
Select Administration > Client Management > Deployment.
In the list of policies, click on the name of the policy you want to use.
Copy deployment properties from the policy:
- Windows or Linux: Copy the properties and paste them into your deployment software.
- Mac: Download the deploy.properties file and provide it to your deployment process.

Distribute installation properties and Code42 app installers to your target devices. Then run the installers.
Details for those two tasks depend on your device management tool and endpoint operating systems:

Consult the vendor's documentation for your device management tool.
For deployment to Mac devices, see details about placing the deploy.properties file.
For details about Code42 app install commands, see the Deployment script and command reference.

Step 4: Users sign in

On Windows and Mac devices, the Code42 app opens on the desktop automatically.
On Linux, users should run this command:/usr/local/crashplan/bin/CrashPlanDesktop

Instruct users to provide names and passwords as prompted by the Code42 app.

For details, direct users to Sign up with newly deployed Code42 app.

Troubleshooting

If a user opens the desktop UI for a newly deployed Code42 app, but the UI never progresses beyond the message Connecting... , then the deployment has probably failed.

Confirm the error as follows:

Find service.log.0 in one of these locations:
- Windows: C:\ProgramData\CrashPlan\log
  To view this hidden folder, open a file browser and paste the path in the address bar. If you installed per user, see the file and folder hierarchy.
- Mac: /Library/Logs/CrashPlan
  If you installed per user, see the file and folder hierarchy.
- Linux: /usr/local/crashplan/log
Open service.log.0 with a text editor.

Find deployment errors by searching for Deploy::, for example:

deploy:: Unable to make request

Deploy:: Unable to process deployment package, USERNAME_NOT_IN_OUTPUT

Step 5: Verify success

After users sign in, check that deployments succeed by reviewing the number of devices signed in to your organization and backing up data.

Sign in to the Code42 console.
Select Administration > Environment > Organizations.
Select the organization you deployed to.
At the top of the window, click the value under Devices.
The number of devices listed for your org should match the number of devices you deployed Code42 apps to.
The quantity of data stored for each device should be greater than zero.