Skip to main content

How can we help you?

Druva Documentation

Customize inSync Client for Mac devices

Overview

An administrator can customize the inSync Client installer to provide the users with an enhanced experience for activating inSync Client on their Mac devices. The following customization features are available with the inSync Client customization package.

  • Pre-define the cloud URL
  • inSync Client auto-launch after successful installation
  • Pre-configure proxy server details

As a result, the inSync users do not have to manually enter the details required for inSync Client activation and can quickly get started by just entering their Femail and password (if applicable).

 

  • Currently, the customization of inSync installer can be done for Mac devices only and is available for the first-time installation and not applicable to inSync Client upgrade. 
  • You may choose any or all of the listed customization features as per your requirements. The parameters for the features which you do not intend to customize must be left blank.

Customize inSync installer

Perform the following steps to customize the inSync installer. 

  1. Download the latest version of inSync Client for macOS here.
  2. Download the inSyncCustomizations.json and the inSyncCustom.sh files here.
  3. Save the files downloaded in Steps 1 and 2 in the desired folder. 
  4. Open the inSyncCustomizations.json file and set the parameters as applicable. The following code snippet provides an example of the parameters. 
    "_customizations" : {
    
                "cloudURL":{
                    "cloudURL"      :   "cloud.druva.com/govcloud/customURL"
                },
    
                "autoLaunchinSync": {
                    "options"       :   "true/false"
                },
    
                "proxyOptions" : {
                    "enableProxySettings"   :   "true",
                    "configureProxyUsing"   :   "proxyServerDetails"
                },
    
                "systemProxySettings": {},
    
                "proxyServerDetails" :{
                    "proxyServerIPAddress"   : "0.0.0.0",
                    "port"                   : "80",
                    "proxyType"              : "http/socks4/socks5"
                },
    
                "configurationFileURL" :{
                    "WPAD/PAC_FileURL" :   "",
                    "proxyType"        :   "socks4/socks5/http"
                },
    
                "AutomaticallyDetectSettings" :{
                    "detectUsingDHCP" :   "true/false"
                }
        }
    }

    The following table describes the parameters and its details: 

    Parameter Description
    cloudURL

    Preference to set the URL to which you want the user to log into. 

    SetcloudURLto login.druva.com to allow users to log into inSync Public cloud. 

    SetcloudURLto loginfederal.druva.com to allow users to log into inSync Data Governance cloud. 

    SetcloudURLto a custom URL to allow users to log into inSync Cloud. 

    autoLaunchinSync

    Preference to launch inSync automatically after inSync is successfully installed on the user device. 

    SetautoLaunchinSyncas "true" to allow inSync to auto-launch after installation. 

    proxyOptions

    Preference to enable proxy settings and configure proxy server details.

    SetenableProxySettingsto "true" to enable the proxy settings.

    SetproxyServerDetailsas follows:

    If you want to choose the System Proxy Settings method, provide the following details: 

    • proxyServerIPAddress
    • port
    • proxyType 

    If you want to choose the Configuration File URL method, provide the following details: 

    • WPAD/PAC_FileURL
    • proxyType

    If you want to choose the automatic proxy detection method, setdetectUsingDHCPas "true".

  5. Open the Mac Terminal and run the following command 
    sh inSyncCustom.sh -o mac. As a result,  inSyncCustomizations.json file gets copied into the inSync.DMG file.  
  6. Share the .DMG file created in Step 5 with the inSync users to install the customized inSync Client on their devices.
  • Was this article helpful?