IMD Command Parameter details




Overview
The following table describes the parameters used during IMD followed by examples.
Parameter type | Name | Use | Value |
---|---|---|---|
Mass deployment token |
TOKENV5 (for Windows) |
Mandatory |
The mass deployment token generated for IMD. |
inSync server IP address and port number |
SERVERLIST (for Windows) |
Mandatory |
The IP address and the backup/sync port of the inSync Server. |
Use of system proxy settings
|
SYSTEM_PROXY (for Windows)
|
Optional |
1, if system proxy settings must be used. |
Static proxy server details |
PROXY_SERVER (for Windows) |
Optional |
PROXY_SERVER contains the IP address and port number of the static proxy server. Example: 192.168.54.100:1080 |
WPAD URL details |
WPAD_URL (for Windows) |
Optional |
Based on the value provided for the WPAD_URL parameter, inSync fetches the proxy PAC file. Based on your requirement, specify one of the following values for WPAD_URL parameter: - If you want inSync client to use a specific, company internal URL to fetch the PAC file, specify WPAD_URL= http://<internalserver-company>.com/wpad.dat, - If you want inSync Client to automatically detect URL of the WPAD location using the DNS, specify WPAD_URL="WPAD_DNS" - If you want inSync Client to automatically detect the URL of the WPAD location using DHCP (252 option), specify WPAD_URL="WPAD_DHCP" PROXY_TYPE parameter is mandatory when using WPAD_URL parameter and must be set to either http, socks4, or socks5. |
Forces inSync Client to use system's certificates |
FORCE_SYSTEM_CERTS (for Windows) |
Optional |
FORCE_SYSTEM_CERTS is a parameter that will direct inSync Client to use the system's certificates for validation of inSync server's validation. Default value of the parameter is NO. Set this parameter to YES if you have MITM proxy configured in your environment. |
inSync Share folder location |
USERSHAREHOME (for Windows) |
Optional |
The path to the folder where the inSync Share folder will be created. For Windows OS, if the path contains a space, you must use three double quotes around the path.
|
Replace the existing device of the user |
REPLACE_DEVICE (for Windows) |
Optional |
If this parameter is set to Yes, the device will replace the existing device of the user. |
Restore System, App settings |
RESTORE_SYSTEM_ |
Optional
|
If this parameter is set to Yes, the system settings from the existing device will be restored on the new device. If this parameter is set to No, the system settings from the existing device will not be restored on the new device.
|
Restore data from an existing device of the user
|
RESTORE_DATA (for Windows) |
Optional |
If this parameter is set to Yes, the data backed up from the existing device will be restored on the new device. This works only if the user has one device and the new device has the same OS as the existing one.
|
inSync CloudCache Server ID
|
CACHESERVERID (for Windows) |
Optional
|
The inSync CloudCache Server ID to which you want to map users.
|
inSync CloudCache Backup Settings
|
CACHEFULLBLOCK (for Windows) |
Optional |
If you want to back up data to inSync Cloud when inSync CloudCache Server runs out of disk space, set this parameter to no. If you do not want to back up data to inSync Cloud when the inSync CloudCache Server runs out of disk space, set this parameter to yes. If you set this parameter to yes and inSync CloudCache Server runs out of disk space, backup operations fail. |
Hide the inSync client shortcut from appearing on the Desktop and in the notification area |
HEADLESS (for Windows) |
Optional |
If you want to hide the inSync client shortcut from appearing on the Desktop and in the notification area, set this parameter to 1. |
Install the inSync Client in a specific language |
LANGUAGE (for Windows) |
Optional |
You can install the inSync Client in one of the following languages: |
Check inSync Client activation on user device |
ACTIVATION_CHECK (for Windows) |
Optional |
If this parameter is set to YES, a check is performed for successful activation of the inSync Client on the user device.
Note: |
Timeout interval for inSync Client activation |
ACTIVATION_TIMEOUT (for Windows) |
Optional |
This parameter specifies the timeout period, value in seconds, before which the inSync Client must be activated after its installation on a device.
|
Remove inSync Client configuration on user devices |
CLEAR_CLIENT_CONFIGURATION (for Windows) |
Optional |
This parameter specifies whether the inSync Client configuration should be removed from the user devices during the inSync Client uninstallation process. |
Restrict users from uninstalling inSync Client from their devices |
HIDE_ARP |
Optional |
You can restrict the users from uninstalling or removing the inSync Client from their Windows devices while installing it on the user devices. This feature utilizes the Windows OS property ARPNOREMOVE. If you want to restrict the users from uninstalling and removing the inSync Client from there devices, set both of these parameters to 1. |
Note: For more information on the RESTORE_DEVICE, RESTORE_SYSTEM_SETTINGS, and RESTORE_DATA options, see Persona backup and OS migration.
Examples
Install inSync Client 6.7.0 on Windows devices
You can save the sample 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>" TOKENV5='<mass deployment token>' SERVERLIST="<IP address of inSync Server>:<Backup/sync port>"
For example
msiexec /qn /i "\\sharelocation\inSync.msi" TOKENV5='11-123this0is0a0sample0token0123' 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" TOKENV5='11-123this0is0a0sample0token0123' 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>" TOKENV5='<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" TOKENV5='11-123this0is0a0sample0token0123' 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" TOKENV5='11-123this0is0a0sample0token0123' 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 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>" TOKENV5='<mass deployment token>' SERVERLIST="<IP address of inSync Server>:<Backup/sync port>" HEADLESS="1"
For example
msiexec /qn /i "\\sharelocation\inSync.msi" TOKENV5='11-123this0is0a0sample0token0123' 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" TOKENV5='11-123this0is0a0sample0token0123' 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), and Spanish (es).
You can run the following command by using an automated installation tool:
msiexec /qn /i "<path to inSync msi>" TOKENV5='<mass deployment token>' SERVERLIST="<IP address of inSync Server>:<Backup/sync port>" LANGUAGE="<fr, en, de, ja, es>"
For example
msiexec /qn /i "\\sharelocation\inSync.msi" TOKENV5='11-123this0is0a0sample0token0123' 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" TOKENV5='11-123this0is0a0sample0token0123' 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)
- Spanish (es)
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>" TOKENV5='<mass deployment token>' SERVERLIST="<IP address of inSync Server>:<Backup/sync port>"
For example
msiexec /qn /i "\\sharelocation\inSync.msi" TOKENV5='11-123this0is0a0sample0token0123' 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" TOKENV5='11-123this0is0a0sample0token0123' 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 6: You want to restrict the users from uninstalling the inSync client from their devices
This feature is available with inSync Client 6.2.0 and above.
You can run the following command using an automated installation tool in addition to the desired parameters mentioned earlier, to restrict the users from uninstalling the inSync Client from their devices.
Using this command will not list inSync Client in Control Panel > Programs > Programs and Features.
msiexec /qn /i "<path to inSync msi>" TOKENV5='<mass deployment token>' SERVERLIST="<IP address of inSync Server>:<Backup/sync port> HIDE_ARP="1" HIDE_UNINSTALL="1"
For example
msiexec /qn /i "\\sharelocation\inSync.msi" TOKENV5='11-123this0is0a0sample0token0123' SERVERLIST="cloud.druva.com:443" HIDE_ARP="1" HIDE_UNINSTALL="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.