Skip to main content

 

Druva Documentation

Installing inSync client for IMD

Parameters required during installation

When you are installing inSync client for IMD, you must include certain parameters that help inSync clients send activation requests to the inSync server. The purpose of each of these parameters are as follows:

  • Mass deployment token: This is used to authenticate the requests sent by the inSync client to the inSync server.
  • inSync server IP address and port number: These are required so that inSync client knows where to connect with the inSync server.
  • Proxy server details: These are required only if the inSync client has to connect to the inSync server through a proxy server. inSync supports the following methods of locating the proxy server:
    • It can use the system proxy settings, that is the proxy details included in the laptop's browser.
    • It can connect to a static proxy server. In such cases, the IP address and port number of the proxy server, and the proxy type is required.
    • It can connect to a proxy server whose details are published on a PAC file on a WPAD URL. In such cases, the WPAD URL and the proxy type is required.

Parameter details

The following table describes the parameters used during IMD.

Parameter type Name Use Value
Mass deployment token

TOKENV2 (for Windows)

TOKEN (for Mac)

Mandatory The mass deployment token generated for IMD.
inSync server IP address and port number

SERVERLIST (for Windows)

ADDRESS (for Mac)

Mandatory

The IP address and the backup/sync port of the inSync server.

Example: 192.168.50.236:6061 

Use of system proxy settings SYSTEM_PROXY Optional 1, if system proxy settings must be used.
Static proxy server details

PROXY_SERVER

PROXY_TYPE

Optional

PROXY_SERVER will contain the IP address and port number of the static proxy server. Example: 192.168.54.100:1080

PROXY_TYPE can either be http, socks4, or socks5.

WPAD URL details

WPAD_URL

PROXY_TYPE

Optional

WPAD_URL will contain the URL of the WPAD location. 

PROXY_TYPE can either be http, socks4, or socks5

Installing inSync clients on Windows laptops

Use an automated installation tool and run 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"

As described earlier, not all parameters are required. For example, if the inSync client executable is located on a shared network \\sharelocation\inSync.msi, and the inSync server can be accessed through a fixed proxy server of type socks5, the following command must be used:

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

Installing inSync clients on Macs

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"

As described earlier, not all parameters are required simultaneously. Use only those that you need.

Now, use an automated installation tool to:

  1. Install inSync Client on Mac laptops.
  2. Copy the inSyncConfig.ini file to the /Library/Application Support/inSync folder of the Mac laptops.
Note: The inSyncConfig.ini file must be copied to the System Library of the Mac laptops. Make sure that the .ini file is in the folder before the inSync client is launched for the first time.
  • Was this article helpful?