Skip to main content
Code42 Support

Deploy Code42 with Windows SCCM

Available in:

StandardPremiumEnterprise
Small Business
Applies to:

Overview

The Windows System Center Configuration Manager (SCCM) provides an efficient way to install Code42 for Enterprise to all Windows devices in your network. This article describes how to use SCCM and Active Directory to deploy Code42 for Enterprise to users' devices.

Applies to

  • Code42 app version 4.x, 5.x, and 6.x
  • Code42 server version 6.x
  • User devices with operating systems Windows 7 and later
  • Tested with System Center 2012 Configuration Manager SP2 and Active Directory 6.3

Before you begin

This article focuses on details and processes unique to deploying Code42 for Enterprise. The article assumes:

  • You have a SCCM server and Active Directory working together.
  • Your intended Code42 for Enterprise users are defined in Active Directory.
  • Your users' devices include SCCM clients.
  • You are familiar with using SCCM to define install packages, distribution points, and device collections.

For more information about SCCM, consult Microsoft's Documentation Library for System Center 2012 Configuration Manager.

Non-Code42 products
​Information about products from other manufacturers is intended as a resource to help you get the most out of Code42 products. However, our Customer Champions cannot provide direct assistance for these products. For assistance with products not developed by Code42, contact the product's manufacturer.

Steps

Step 1: Configure your Code42 server for silent installs

A "silent" installation of Code42 for Enterprise automatically backs up devices without user intervention. You do not need to manually create user accounts in the Code42 administration console. Users do not need access to the Code42 for Enterprise user interface.

  1. Sign in to the Code42 administration console.
  2. Go to active Organizations. 
    (Version 6.5.x and later) Go to Organizations > Active.
    (Version 6.0.x and earlier) Go to Organizations. 
  3. Select an organization for the users you will deploy to. If the organization doesn't exist yet, add an organization.
    Deploying to multiple organizations requires a separate SCCM install package for each organization.
  4. From the action menu, select Device Backup Defaults.
  5. From General, deselect Use device defaults from parent.
  6. From Backup > Destinations, select a destination to which Code42 for Enterprise will automatically back up.
  7. Click Save.
  8. From the top of the organization details console, copy the Registration key.
    You will need that 19-character string at Step 2, below.

Step 2: Assemble the install folder

Create and populate the install folder, which will become the source for your SCCM deployment.

When finished, the install folder's file structure should be:

Code42CrashPlan_X.x.x_WinNN
   \Code42CrashPlan_*.msi
   \Code42CrashPlan_install.bat
   \custom
      \custom.properties
  1. Create an empty folder at some convenient location on your local file system.
    We suggest the name Code42CrashPlan_X.x.x_WinNN, to identify the Code42 version and the Windows operating system (32- or 64-bit) For example: Code42CrashPlan_6.0.0_Win64.
  2. Inside that folder, create another empty folder named custom.
  3. From the Code42 administration console, select App Downloads.
  4. Under Newer versions available, select a Windows system and Code42 for Enterprise version, and click the plus sign ( + ).
    The Code42 for Enterprise installer copies to your Code42 server.
  5. Under Available on your Code42 server > Download Apps, click the download icon for the appropriate system and version.
  6. Save the Code42 for Enterprise installer, Code42CrashPlan_*.msi to the install folder, Code42CrashPlan_X.x.x_WinNN.
  7. Navigate to one of the following URLs:
    Replace <server.example.com:4285> with the protocol, host, and port for your Code42 server.
    • For Code42 app version 5.x and 6.x:
      https://<server.example.com:4285>/download/Code42CrashPlan_Custom.zip
    • For Code42 app version 4.x:
      https://<server.example.com:4285>/download/CrashPlanPROe_Custom.zip
  8. Save the custom install template, *CrashPlan*_Custom.zip, to your local file system.
  9. Unzip *CrashPlan*_Custom.zip.
  10. Copy *CrashPlan*_Custom\custom.properties to your install folder:
    Code42CrashPlan_X.x.x_WinNN\custom\custom.properties.
  11. Create a text file in the install folder:
    Code42CrashPlan_X.x.x_WinNN\Code42CrashPlan_install.bat.
  12. Populate the install.bat text file with the script listed below.

The *.bat script runs on the user's device and invokes the Code42 for Enterprise install executable, *.msi.

@ECHO OFF
REM Script grabs currently logged in user and user home; installs silently. Compatible with running the installer as administrator or another user.

REM Determine which user lauched explorer.exe, presumes that this is a domain account user
for /f "TOKENS=1,2,*" %%a in ('%systemroot%\system32\tasklist.exe /FI "IMAGENAME eq explorer.exe" /FI "STATUS eq running" /FO LIST /V') do if /i "%%a %%b"=="User Name:" set _currdomain_user=%%c
REM in the case of no domain account, change "currdomain_user" to "curruser", otherwise you need the line, below, to trim out the domain and wind up with "curruser"
for /f "TOKENS=1,2 DELIMS=\" %%a in ("%_currdomain_user%") do set _currdomain=%%a & set _curruser=%%b

SET CP_USER_NAME=%_curruser%
ECHO UserName: %CP_USER_NAME%
REM The users home directory (Windows Vista and newer), used in backup selection path variables.
SET CP_USER_HOME=C:\Users\%_curruser%

ECHO UserHome: %CP_USER_HOME%
REM Tells the installer not to run CrashPlan client interface following the installation.
SET CP_SILENT=true
ECHO Silent: %CP_SILENT%
SET CP_ARGS="CP_USER_NAME=%CP_USER_NAME%&CP_USER_HOME=%CP_USER_HOME%"
ECHO Arguments: %CP_ARGS%

REM 64-bit Windows installer. You can use any of the msiexec command-line options.
ECHO Installing CrashPlan...
"%~dp0Code42CrashPlan_6.0.0_Win64.msi" /qn /l* install.log CP_ARGS=%CP_ARGS% CP_SILENT=%CP_SILENT%

Step 3: Edit the install configuration

  1. In the final line of Code42CrashPlan_install.bat, change the *.msi file name to match your installer file.
"%~dp0Code42CrashPlan_6.0.0_Win64.msi" /qn /l* install.log CP_ARGS=%CP_ARGS% CP_SILENT=%CP_SILENT%
  1. In the custom.properties file, set options as follows:
Property=Value Description
address=<server.example.com>:4282
secondaryAddress=<server.example.com>:4282

Provide addresses for Code42 client-server communications.

 

In the Code42 administration console:

  1. Go to Settings > Server > General.
  2. Note the values for:
    Primary network address
    Secondary network address.
registrationKey=<19-character-key...>

The key is the identifier for the Code42 organization you defined in Step 1 above.

 

In the Code42 administration console:

  1. Versions 6.5 and later: Go to Organizations > Active.
    Versions 6.0.x: Select Organizations from the navigation menu.
  2. Select your users' organization.
  3. At the top of the organization's details, copy the Registration key.
username=${username} When Code42CrashPlan_install.bat runs on a Windows device, it populates ${username} with the value of "CP_USER_NAME", which is the user name of the currently logged-on Windows user.
password=${deferred} When the installer runs on Windows, the Code42 for Enterprise acquires the password from Active Directory.

Step 4: Deploy Code42 for Enterprise with SCCM

  1. Copy your install folder to a location accessible to your SCCM control panel.
  2. Create a new SCCM package. For its source files, select your install folder.
  3. For that package, specify a standard program, and select your script file: Code42CrashPlan_install.bat.
  4. Specify that the program can run only when a user is logged on.
  5. Specify that the program will run with administrative rights to the user devices.
  6. Check Allow users to view and interact with the program installation.

Create package and program wizard

  1. Select or create an SCCM distribution point for your package.
  2. Create a new SCCM device collection (or use an existing collection) that includes the devices to which you will deploy Code42 for Enterprise.
  3. Deploy your Code42 for Enterprise package to the distribution point and device collection.
    When prompted, select the following options:
    • Purpose: Required
    • Deployment options: Download content from distribution point and run locally.

 

Step 5: Verify that deployment succeeded

After allowing time for SCCM to complete the deployment process, verify that Code42 for Enterprise is installed and successfully backing up user devices:

  1. Sign in to the Code42 administration console.
  2. Navigate to the Reporting web app.
    • (Version 6.5.x and later) Choose Reporting in the left menu.
    • (Version 6.0.x and earlier) From the application selector in the upper right, choose Reporting.
  3. Select the Device Status report.
  4. In the Organization field, enter the name of the organization you defined in Step 1 above.
  5. Click Run Report.
    The results display details about the devices backing up in this organization.
  • Was this article helpful?