Configuring the iManage Auto Updates installation

iManage Work introduces the capability to configure the installation of iManage and related third-party applications such that the latest product updates are seamlessly installed with minimal user intervention. iManage Work Agent notifies users whenever product updates are available. Users can install the updates when notified, or check for updates manually anytime later and then install them.

This new capability makes it easier for users to keep their desktops up-to-date with the latest features, enhancements, and bug fixes offered by iManage and its partners. In addition, this capability empowers IT administrators to easily deploy latest updates to selected users' desktops, and eventually across the entire organization. IT administrators have the option to specify the following:

  • Server location where updates are hosted. IT administrators have the choice to point users to the public location where latest updates are posted by iManage or to an alternate location, for example, an internal shared drive.

  • Update channels that define the release stage of updates, for example, Beta or Release.

  • Product(s) that should be deployed for each channel. IT administrators can use the Auto Updates feature to not only deploy iManage applications but also third-party applications that complement iManage products.

From version 10.6.0 onwards, Auto Updates are implemented with the functionality to run pre-lua scripts to handle installer dependencies. With this implementation, pre-Work Desktop for Windows.lua scripts are available for both 64-bit and 32-bit versions of iManage Work Desktop for Windows that run before the application installation to handle Microsoft WebView2 installation. These scripts are signed and checked for authenticity before running. You can modify these scripts to handle any future pre-requisites if you have up your own update server.


  • The file name has to match the product ID name that appears in the update.ini file that is the pre_iManage Work Desktop for Windows x64.lua script.

  • You cannot modify the scripts if you are using iManage Work update server.

  • You can add your own .lua scripts to handle installer dependencies. Ensure that these files are signed. You can add two .lua scripts for each product in the channel as each product available in the channel supports both pre_ and post_ .lua files).
    For every .lua script you add, a companion file similar to sign.txt file or update.ini file is required. The ConfigFileSigner.exe creates the right file in the working directory when you provided the file name.

This section covers the following topics: