Specifying the update server location

The update server is a location from which update.ini and updateinfo.json are downloaded. Any updates to iManageUpdater.exe are also downloaded and applied. Actual locations where software updates are hosted for download are specified inside update.ini. If required, you can set up your own update server and specify that server's path as the update server location for the Auto Updates feature.


Ensure that the update server includes the following files:

  • update.ini

  • updateinfo.json

  • imanageinstaller.ts1

  • imanageinstaller.ts2

  • imanageinstaller.ts3

  • ConfigFileSigner.exe

  • libcrypto-1_1.dll

  • libssl-1_1.dll

  • openssl.exe

  • pubkey.crt

  • pubkey.pem

  • sign.txt

You can download sample content for each of these files from https://updates.imanage.work/updates/work10.

For example, to view the update.ini file content, visit https://updates.imanage.work/updates/work10/update.ini. Similarly, you can view the content of other files.

To specify the update server location, u pload the update.ini file using iManage Control Center (iCC):

  1. Open iCC, and select SETTINGS > Office > Configuration.

  2. Select the Upload File button to upload the update.ini file .

The file is downloaded to %ProgramData%\iManage\AgentServices\CentralizedConfigs by iManage Work Desktop for Windows and, thereafter, iManage Updater reads all information from this update.ini file. If the update.ini file is not present, iManage Updater checks in the following location: %ProgramData%\iManage\AgentServices\Configs.


This option is applicable only when you are upgrading from iManage Work Desktop for Windows 10.1.x.

You can also specify the update server location using the following options, which are listed in the order of their precedence. End-users are directed to the specified update server when they install the applications and whenever the applications are updated.

  • Command line: You can run the installer from the command line with the following argument: UPDATESERVERPATH=server_name.com/myupdateserver.
    For example: iManageInstaller.exe server_name.com/myupdateserver

  • Registry setting: You can add the following registry setting:

    • Location: HKEY_LOCAL_MACHINE\Software\iManage\AgentServices\AutoUpdate


    • Type: String (REG_SZ)

    • Value: Path to the server; for example, \\shared-drive\work-updates\.

      The server path can be a file path (local or UNC style) or an HTTP/HTTPS web server. If you are using a web server, ensure that the following mime types are defined on the server:

      • application/octet-stream - ts3

      • application/zip - ts1 and ts2

  • Environment variable: You can add the UPDATESERVERPATH variable with the required server location to the environment path; installer will use that information for downloading the applications and their updates.


  • You can use the command line and environment variable options only during the installation of iManage Installer.

  • The registry setting is used during the installation and the update process.

  • If you do not set the update server location using any of the options listed in this section, iManage Updater downloads the software application and their updates from updates.imanage.work/updates/work10.

Workflow to identify the update server

After the initial installation, iManage Updater locates its assigned update server as follows:

  1. iManage Updater looks for the registry setting UPDATESERVERPATH at HKEY_LOCAL_MACHINE\Software\iManage\AgentServices\AutoUpdate .

  2. If the registry setting is missing and if the update.ini file is uploaded to iManage Control Center, the file is downloaded to %ProgramData%\iManage\AgentServices\configs by iManage Work Desktop for Windows.

  3. If update.ini is not present in this location, iManage Updater reads from its local copy of update.ini (located at %ProgramData%\iManage\AgentServices\CentralizedConfigs ). In this file, the update server location is set for the server property under the [General] section. Using this value, iManage Updater determines where to get its latest update.ini and updateinfo.json files.

  4. Updateinfo.json used on your custom update server needs to be pulled from another update server and not from the local machine. The local file is already processed and will cause auto update to not function properly. The version of updateinfo.json stored on update servers contain macros that are replaced at run time to allow the iManage Agent to properly determine the settings.

  5. iManage Updater then connects to the update server and downloads the latest update.ini and updateinfo.json files, and thereafter, reads all information from this update.ini file.