HOWTO: Redirect the Ivanti Workspace Control Agent cache for non-persistent/pooled VDI

Version 5

    Question

    Redirect the Ivanti Workspace Control Agent cache for non-persistent/pooled VDI.

    The Ivanti Workspace Control Agent cache uses UpdateGUIDs to determine which parts of the cache need to be updated.
    Together with the Ivanti Workspace Control Policy settings, these UpdateGUIDs are stored in the registry.
    When the UpdateGUIDs in the registry are different from the UpdateGUIDs in the Datastore/Relay Server, the relevant items are updated.

    In VDI environments that use a non-persistent/pooled model, and where the Ivanti Workspace Control Agent cache is stored on a persistent disk, most likely the latest versions of the UpdateGUIDs and Ivanti Workspace Control policy settings are not in the registry of the golden image/template.

    Therefore, the cache will be updated with information from the Datastore or Relay Server, even though the most recent versions of the cache files are already present in the Ivanti Workspace Control cache on the persistent disk. The update causes I/O load and network traffic.

    With the new registry value LocalCacheOnDisk it is possible to make the cache independent of the Operating System`s (OS) registry.
    Setting this registry value will convert the UpdateGUIDs and policy settings automatically from the OS` registry to two new XML files in the Ivanti Workspace Control DBcache folder on the persistent disk: UpdateGUIDs.xml and Settings.xml.

     

    Answer

    To store the UpdateGUIDs and Ivanti Workspace Control policy settings in the Ivanti Workspace Control DBcache folder set the following registry values:

    Ivanti Workspace Control:
    1) Stop the Ivanti Workspace Control Agent.

     

    2) Edit or create the following registry keys:
    Key: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\RES\Workspace Manager
    Value: LocalCacheOnDisk 
    Type: REG_SZ
    Data: Yes

    Key: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\RES\Workspace Manager
    Value: LocalCachePath
    Type: REG_SZ
    Data: <drive>:\<folder>

     

    3) Start the Ivanti Workspace Control  Agent service.

     

    4) Browse to the cache location:
    Browse to the configured location in Step 2 and delete the file UpdateGuids.xml.

    5) Restart the Ivanti Workspace Control  Agent service.

     

    Notes:
    1. This key is available from RES Workspace Manager 2012 SR5 and RES Workspace Manager 2014 SR1 or higher.
    2. By removing the registry keys from the Agent, the cache will automatically convert UpdateGUIDs.xml and Settings.xml back into the OS' registry and the files will be deleted from the DBCache folder (after the Ivanti Workspace Control service is restarted). Changing the registry key data to "No" will not be sufficient as this still create symbolic link folders, which are needed in case of cache redirection.
    3. Setting this registry value will prevent unnecessary network traffic caused by the initial cache update, but may cause some additional disk I/O load on the Ivanti Workspace Control cache folder when processing changes in the Datastore throughout the day.
    4. By installing the Ivanti Workspace Control Agent on the system drive the NTFS security is set correctly by default for the Program Files folder and therefore the Ivanti folder is inheriting the correct permissions. Some folders in the DBCache folder are configured with additional protection in the user session through built-in protection. 
      If the local cache is redirected to a folder on another drive than the system drive, the NTFS security should be changed otherwise an end user is able to delete files in the local cache (DBCache) folder. By default, the Authenticated Users are having the Modify rights.
      Best practice for the redirected local cache folder is to remove inheritable permissions, convert the inherited permissions and remove Authenticated Users.