Skip to main content

 

Druva Documentation

Mass deploying inSync client

Overview

This topic explains the process of mass deploying inSync client on user laptops and desktops.

The mass deployment process

If your organization uses Active Directory (AD) to authenticate user login, you can install inSync client on all user computers using the mass deployment process. This will save the time required to install inSync client individually on each computer.

When a user logs on to his computer after inSync client is installed, the inSync client sends the user's credentials to the inSync server. The inSync server verifies the credentials and activates inSync client on the computer. Once activated, backups from the user's computer starts. 

Prerequisites

To mass deploy inSync client, make sure that:

  • Your organization uses AD to authenticate user login.
  • Users in your organization use Windows or Mac computers. 
Note: inSync client cannot be mass deployed on Linux computers. You cannot mass deploy inSync Companion App.

Types of mass deployment

You can select two types of mass deployment:

  • Activate only the first device of a user: When you select this option, inSync client is activated only on the first device on which users log on. For subsequent devices, users must activate inSync client by providing AD credentials. 
  • Activate all devices of a user: When you select this option, inSync client is activated on all devices on which users log on. 

Mass deploying inSync client

Step 1: Configure user profiles

You must configure the profiles that you will assign to the users to accept AD password for authenticating user access. If you do not select the use of AD to authenticate user's inSync access, users cannot:

  • Activate inSync client on any other computer except the first
  • Log on to inSync Companion App
  • Log on to inSync Web

For instructions, see Allowing users to log on to inSync using their Active Directory credentials.

Step 2: Select the type of mass deployment you want to implement

To select the type of mass deployment

  1. On the menu bar, select Manage > Settings.
  2. Click the AD Accounts tab.
  3. Under Mass Deployment for AD, click Edit. The Edit window appears.
    massdeploy1.png

     

  4. Select the type of mass deployment you want to implement:
    • To activate inSync client on the first computer that the user logs on, select Activate first device only during deployment.
    • To activate inSync client on all devices on which the user logs on, click to clear Activate first device only during deployment.
  5. Click Ok.

Step 3: Create AD Mappings

When you create an AD mapping, inSync server selects a set of users from an AD to which a specific profile and storage can be assigned. Each AD mapping corresponds to a particular set of users. For instructions, see Creating AD Mapping.

Note: If you want to mass deploy inSync client for multiple sets of users, you must create multiple AD mappings. For example, you want to mass deploy inSync client for the Finance and the Development teams in your organization. But members of both teams are assigned to two different profiles. You must therefore create two separate AD mappings - one to create inSync users for the Finance team, other to create inSync users from the Development team. 

Step 4: Generate a mass deployment token

To generate the mass deployment token:

  1. On the menu bar, click Manage > AD Mappings.
  2. Click Mass Deployment Token. The Mass Deployment Token window appears.

  3. To set an expiry date for the token, select Enable Expiry Date and specify the date.
  4. Click Create New Token.

The mass deployment token is displayed. Copy the token to a text file. You will need this token when mass-installing inSync client on user computers.

Step 5: Mass-install inSync client

You can use any automated installation tools to install inSync client on all user computers in your organization. For example, to install inSync client on Windows computers, use System Center Configuration Manager (SCCM). Similarly, to install inSync client on all Mac computers, use LANDesk management solution.

Mass installing inSync client on Windows

To mass-install inSync client on Windows

  • Using an automated installation tool install inSync client on Windows computers, use the following command:
msiexec /qn /i <path to inSync msi> TOKENV2='<mass deployment token>' SERVERLIST="<IP address of inSync Server>:<Backup/sync port>" WPAD_URL="<URL of PAC file>" PROXY_TYPE="<type of proxy used>" PROXY_SERVER="<IP address of proxy server>:<port number>" SYSTEM_PROXY="1"

In the above code, the parameters WPAD_URL, PROXY_TYPE, PROXY_SERVER, and SYSTEM_PROXY are used if inSync client has to access inSync server through a proxy. Not all parameters are required simultaneously:

  • If proxy server details are published on a PAC file on a WPAD URL, the parameters WPAD_URL and PROXY_TYPE are required. PROXY_TYPE can either be http, socks4, or socks5.
  • If proxy server IP is constant, the parameters PROXY_SERVER and PROXY_TYPE are required.
  • If inSync client must use the system proxy settings, the parameter SYSTEM_PROXY is required and its value must be 1.

For example, if inSync client must access inSync server through a fixed proxy server:

msiexec /qn /i inSync.msi TOKENV2='33-bb0af8c55da3f9dd32e6ce6ad23e97b5d9951ae6fcf37ee062754ceabc76cf69' SERVERLIST="192.168.53.123:6061" PROXY_SERVER="192.168.54.100:1080" PROXY_TYPE="socks5"

Mass installing inSync client on Mac

Before you begin:

  • Make sure that the Mac computers on which you are installing inSync client are added to your organization's domain.
  • Add the following lines of code to a text file and save it as inSyncConfig.ini.
ADDRESS = "<IP address of inSync Server>:<Backup/sync port>"
TOKEN = '<mass deployment token>'
WPAD_URL= "<URL of PAC file>" 
PROXY_TYPE= "<type of proxy used>" 
PROXY_SERVER= "<IP address of proxy server>:<port number>" 
SYSTEM_PROXY= "1" 

In the above code, the parameters WPAD_URL, PROXY_TYPE, PROXY_SERVER, and SYSTEM_PROXY are used if inSync client has to access inSync server through a proxy. Not all parameters are required simultaneously:

  • If proxy server details are published on a PAC file on a WPAD URL, the parameters WPAD_URL and PROXY_TYPE are required. PROXY_TYPE can either be http, socks4, or socks5.
  • If proxy server IP is constant, the parameters PROXY_SERVER and PROXY_TYPE are required.
  • If inSync client must use the system proxy settings, the parameter SYSTEM_PROXY is required and its value must be 1.

 

To mass-install inSync client on a Mac

  1. Using an automated installation tool, install inSync Client on Mac computers.
  2. Copy the inSyncConfig.ini file to the /Library/Application Support/inSync folder of the Mac computers.

Note:

  • Contact Druva Support if you want to move or edit the inSyncConfig.ini file on the user devices.
  • The inSyncConfig.ini file must be copied to the System Library of the Mac computers.

Step 6: Importing user details from AD (only for non automatic import)

This step is required only if you did not Auto create/update users while creating the AD mapping. For instructions, see Importing user details from AD. Repeat this step every time you add a new user. 

  • Was this article helpful?