Skip to main content

 

Druva Documentation

Install inSync on Windows devices

inSync Cloud Editions: File:/tick.png Elite Plus File:/tick.png Elite File:/cross.png Enterprise File:/cross.png Business

Overview

You can save the script as a .bat file. You can deploy these scripts by using a third-party tool. You do not need to use all parameters simultaneously. Use only the parameters that you need.

Scenario 1: You can access inSync client executable on a shared network

The inSync client executable is located on a shared network. You can run the following command by using an automated installation tool:

msiexec /qn /i "<path to inSync msi>" TOKENV2='<mass deployment token>' SERVERLIST="<IP address of inSync Server>:<Backup/sync port>"

For example

msiexec /qn /i "\\sharelocation\inSync.msi" TOKENV2='33-bb0af8c55da3f9dd32e6ce6ad23e97b5d9951ae6fcf37ee062754ceabc76cf69' SERVERLIST="cloud.druva.com:443" 

Note: The token value used in the example is for presentation purpose only. A token is unique and you must generate your own before the installation.

You can define a secondary port in the command. If the inSync client is unable to use the primary port, the inSync client uses the secondary port to connect to the inSync Master.

For example

msiexec /qn /i "\\sharelocation\inSync.msi" TOKENV2='33-bb0af8c55da3f9dd32e6ce6ad23e97b5d9951ae6fcf37ee062754ceabc76cf69' SERVERLIST="cloud.druva.com:443,cloud.druva.com:6061,cloud.druva.com:80"

Note: You must follow the exact usage of single (') and double quotation marks (") as provided in the example.

Scenario 2: You can access the inSync Master through a fixed proxy server

The inSync client executable is located on a shared network. You can run the following command by using an automated installation tool:

msiexec /qn /i "<path to inSync msi>" TOKENV2='<mass deployment token>' CACHESERVERID=<ID> CACHEFULLBLOCK=<yes or no> SERVERLIST="<IP address of inSync Server>:<Backup/sync port>" PROXY_TYPE="<type of proxy used>" PROXY_SERVER="<IP address of proxy server>:<port number>" SYSTEM_PROXY="1" USERSHAREHOME="<new_location>"

For example

msiexec /qn /i "\\sharelocation\inSync.msi" TOKENV2='33-bb0af8c55da3f9dd32e6ce6ad23e97b5d9951ae6fcf37ee062754ceabc76cf69' CACHESERVERID=16 CACHEFULLBLOCK=no SERVERLIST="cloud.druva.com:443" PROXY_SERVER="192.168.54.100:1080" PROXY_TYPE="socks5" USERSHAREHOME="E:\"

Note: The token value used in the example is for presentation purpose only. A token is unique and you must generate your own before the installation.

You can define a secondary port in the command. If the inSync client is unable to use the primary port, the inSync client uses the secondary port to connect to the inSync Master.

For example

msiexec /qn /i "\\sharelocation\inSync.msi" TOKENV2='33-bb0af8c55da3f9dd32e6ce6ad23e97b5d9951ae6fcf37ee062754ceabc76cf69' CACHESERVERID=16 CACHEFULLBLOCK=no SERVERLIST="cloud.druva.com:443,cloud.druva.com:6061,cloud.druva.com:80" PROXY_SERVER="192.168.54.100:1080" PROXY_TYPE="socks5" USERSHAREHOME="E:\"

Note: You must follow the exact usage of single (') and double quotation marks (") as provided in the example.

Scenario 3: You want to hide the inSync client shortcut from appearing on the Desktop and in the notification area

You can use the HEADLESS parameter. You can run the following command by using an automated installation tool:

Note: If you have disabled Show icon inSync icon in the notification area for the selected profile, ensure that you use HEADLESS parameter in the script. If you do not use this parameter, inSync client icon continues to appear in the notification area for the user devices until the inSync client installation completes. For more information, see Enable inSync notifications.

msiexec /qn /i "<path to inSync msi>" TOKENV2='<mass deployment token>' SERVERLIST="<IP address of inSync Server>:<Backup/sync port>" HEADLESS="1"

For example

msiexec /qn /i "\\sharelocation\inSync.msi" TOKENV2='33-bb0af8c55da3f9dd32e6ce6ad23e97b5d9951ae6fcf37ee062754ceabc76cf69' SERVERLIST="cloud.druva.com:443" HEADLESS="1"

Note: The token value used in the example is for presentation purpose only. A token is unique and you must generate your own before the installation.

You can define a secondary port in the command. If the inSync client is unable to use the primary port, the inSync client uses the secondary port to connect to the inSync Master.

For example

msiexec /qn /i "\\sharelocation\inSync.msi" TOKENV2='33-bb0af8c55da3f9dd32e6ce6ad23e97b5d9951ae6fcf37ee062754ceabc76cf69' SERVERLIST="cloud.druva.com:443,cloud.druva.com:6061,cloud.druva.com:80" HEADLESS="1"

Note: You must follow the exact usage of single (') and double quotation marks (") as provided in the example.

Scenario 4: You want to install the inSync Client in a specific language

You can install the inSync client in one of the following languages:

French (fr), German (de), English (en), Japanese (ja).

Note: inSync client 5.4.2 or later supports the Japanese language. If you want to install the inSync client in the Japanese language, you must upgrade to inSync client 5.4.2. For more information on how you can upgrade the inSync client, see Upgrade inSync on a user laptop.

You can run the following command by using an automated installation tool:

msiexec /qn /i "<path to inSync msi>" TOKENV2='<mass deployment token>' SERVERLIST="<IP address of inSync Server>:<Backup/sync port>" LANGUAGE="<fr, en, de, ja>"

For example

msiexec /qn /i "\\sharelocation\inSync.msi" TOKENV2='33-bb0af8c55da3f9dd32e6ce6ad23e97b5d9951ae6fcf37ee062754ceabc76cf69' SERVERLIST="cloud.druva.com:443" LANGUAGE="en" 

Note: The token value used in the example is for presentation purpose only. A token is unique and you must generate your own before the installation.

You can define a secondary port in the command. If the inSync client is unable to use the primary port, the inSync client uses the secondary port to connect to the inSync Master.

For example

msiexec /qn /i "\\sharelocation\inSync.msi" TOKENV2='33-bb0af8c55da3f9dd32e6ce6ad23e97b5d9951ae6fcf37ee062754ceabc76cf69' SERVERLIST="cloud.druva.com:443,cloud.druva.com:6061,cloud.druva.com:80" LANGUAGE="en"

Note: You must follow the exact usage of single (') and double quotation marks (") as provided in the example.

Scenario 5: You want to install the inSync client in the user locale of the user device

The inSync client installer supports the following languages:

  • English (en)
  • French (fr)
  • German (de)
  • Japanese (ja)

If you do not specify a language parameter (scenario 4), the user locale of the user device determines the language in which the inSync client is installed. However, if the user locale is in a language other than the languages that the inSync client supports, the inSync client is installed in English. 

You can run the following command by using an automated installation tool:

msiexec /qn /i "<path to inSync msi>" TOKENV2='<mass deployment token>' SERVERLIST="<IP address of inSync Server>:<Backup/sync port>" 

For example

msiexec /qn /i "\\sharelocation\inSync.msi" TOKENV2='33-bb0af8c55da3f9dd32e6ce6ad23e97b5d9951ae6fcf37ee062754ceabc76cf69' SERVERLIST="cloud.druva.com:443" 

Note: The token value used in the example is for presentation purpose only. A token is unique and you must generate your own before the installation.

You can define a secondary port in the command. If the inSync client is unable to use the primary port, the inSync client uses the secondary port to connect to the inSync Master.

For example

msiexec /qn /i "\\sharelocation\inSync.msi" TOKENV2='33-bb0af8c55da3f9dd32e6ce6ad23e97b5d9951ae6fcf37ee062754ceabc76cf69' SERVERLIST="cloud.druva.com:443,cloud.druva.com:6061,cloud.druva.com:80"

Note: You must follow the exact usage of single (') and double quotation marks (") as provided in the example.

 

  • Was this article helpful?