Skip to content

Update clients

SmartUpdate

SmartUpdate automatically updates clients at startup if the installed Octoplant version is older than the version available on the assigned server.

Prerequisites for SmartUpdate

  • The registered user account must have the following permissions:

    • Full access to the client archive
    • Write access to the installation directory of the Octoplant client applications

    • Write access to the Windows Registry (HKLM section for MSI registration)

    • SmartUpdate might run without administrator rights if the signed-in Windows user has sufficient permissions to write to:

      • The Windows Registry (HKLM)
      • The program installation directory (Program Files (x86))
      • The existing client archive directory

      You can configure Group Policy for authorized users without administrator rights.

      If your organization uses additional client security software, explicitly approve installation of the MSI packages for the Octoplant client and BackupClient on the relevant computers.

    • If the BackupClient is also installed, SmartUpdate and general operation of the BackupClient require administrator rights.

    Tip

    If SmartUpdate is not available for the logged-in user without administrator privileges due to insufficient permissions, restart the Octoplant client application and run it as an administrator.

  • In the AdminClient > Global settings module > Clients tab, enable the Automatically update clients to new version on login checkbox.

— Speeding up SmartUpdate

SmartUpdate may take a considerable amount of time.

If you do not use the BackupClient, you can speed up SmartUpdate by removing the BackupClient installer from the server archive. This reduces the SmartUpdate download size by nearly 500 MB.

  1. Navigate to the server archive.
  2. Remove the octoplantBackupClient.msi file from the {server archive}\vdog client setup\bin\common\ directory.

We recommend storing the file in a different location in case you need it later.

If you require the BackupClient at a later time, copy the octoplantBackupClient.msi file back into {server archive}\vdog client setup\bin\common\ directory before installing the BackupClient on a client computer.

Deactivate SmartUpdate

You can deactivate SmartUpdate if, for example, you use an MSI package or want to distribute the updates via an internal software management.

Go to AdminClient > Global settings module > Clients tab and deactivate the Automatically update clients to new version on login checkbox.

Installation requirements for mounted drives

We recommend that you do not install the client archive on a mounted drive. Should you have to, please be aware of the following:

  1. If the client archive will be installed in a directory that requires elevated rights (write rights) and the setup is run as administrator, the mounted drive on which the client archive will be located must be mounted for the user and for the administrator account.
  2. When carrying out a Smartupdate, the setup must be run as administrator if the installation directory requires elevated rights (write rights). The client archive must also be mounted for the administrator if it is mounted for a standard user.

Update clients manually

Alternatively, you can manually download the octoplantClient_Setup.exe (or octoplantBackupClient_Setup.exe) from the shared vdog client setup folder on the Octoplant server to update the clients using a setup wizard. With this method, you can customize the installation paths as needed using the wizard’s Advanced option.

The Advanced option also allows users without administrator rights to select the Just for me (per-user) installation, which requires fewer permissions than the installation for all users (per-computer) performed during a SmartUpdate.

In this case, the installer writes only to the HKCU registry (of the current user) and to the user’s Windows Home directory for the software installation, rather than to the Program Files (x86) folder.

This option is not available for the BackupClient, which is always installed for all users and not per user.

Tip

Windows permissions can be complex. Involve your IT department early to configure Group Policy settings for authorized non-administrators to install MSIs, or to provide credentials for Run as Administrator.


Related topics