You can now install iManage Drive in non-persistent Virtual Desktop Infrastructure (VDI) environments. 

IMPORTANT: To install iManage Drive in a non-persistent VDI environment, you must turn off iManage Auto Updates in iManage Work Agent. 

Prerequisites 

  • iManage Auto Updates in iManage Work Agent must be turned off. For information about how to turn off iManage Auto Updates, refer to the Turning off Auto Updates section in iManage Work Desktop for Windows Installation Guide

  • Microsoft Windows Server 2016

    • Microsoft Window Server 2016 version 1607 (OS build 14393.5066) or later

    • iManage Drive 10.8.0 or later

  • Microsoft Windows Server 2019

    • iManage Drive 10.8.0 or later

  • To make sure the modified date in Windows Explorer is correct, set enable_windows_set_ctime_mtime_file_link to true in the admin_settings.yaml file.

Compatibility

 iManage Drive was tested successfully when installed in the following environments:

  • VDI environment with FSLogix as the profile manager

  • Microsoft Windows Server 2019

Installing iManage Drive in non-persistent VDI environments

Installing iManage Drive in non-persistent VDI environments is similar to installing iManage Drive on your Microsoft Windows device. For details, refer to Installing iManage Drive manually.

To download iManage Drive full installation package, refer to iManage Help Center and select iManage Drive for Windows installation package without Auto Updates

Installing iManage Drive Native in non-persistent VDI environments

You can't install iManage Drive Native using Microsoft App-V in non-persistent VDI environments. This is because iManage Drive native includes a drive that can't be part of Microsoft App-V. iManage Drive native should be included as part of the base image or installed manually in non-persistent VDI environments.

Additional setup required for non-persistent VDI environments

All iManage Drive data, like diagnostics and other information, is saved to %localappdata%\iManage\GoDrive. Therefore, a profile manager application must also save the information to the same location.

The working iManage Drive directory is mapped to M:\. Therefore, a profile manager application must also have the same mapping: 

M:=C:\Users\<username>\iManageDrive

For more information about the various iManage Drive directories, refer to iManage Drive directories and configuration file