Deployment strategies

The steps outlined here can be used when deploying identically configured Workbenches onto multiple machines, decreasing the time needed to configure each Workbench:

  1. On a single computer that has the same OS as the other computers the Workbench will be installed on, complete a full Workbench installation.
  2. Launch the newly installed Workbench and complete the initial Workbench setup by doing the following:
    • Set up the licensing. See Licenses for details.
    • Install any desired plugins. Plugins can be downloaded via the Workbench Plugin Manager if the Workbench can connect to the external network. Alternatively, plugin files can be downloaded on a machine with external network access from, and then copied to the machine with the Workbench, and installed using the "Install from File" functionality of the Workbench Plugin Manager.
    • If you have any modules (commercial plugins) you plan to use for analysis work, the licensing can be set up for these now if you wish, but this step can also be done later1.1.
      • For a network license setup, the relevant module licenses should be made available from your CLC License Server.
      • For static licenses, a license file for the relevant products needs to be present on each machine where analyses will be carried out.

      For further information about plugin installation and licensing, please refer to the individual plugin manuals, available from

  3. Configure the settings to be applied to all Workbench users via properties files. See Per-computer Workbench information data for a list of property files and links to the relevant chapters describing them.
  4. Run the Workbench installer in silent mode (-q) on each of the other computers to install the Workbench on them. See Installation modes - console and silent for details.
  5. Copy the following files from the initial Workbench installation to the corresponding location on the other computers.
    • All files under the settings folder of the installation directory.
    • The plugins folder and its contents from under the initial Workbench's installation area.

Another option for deployment is to create an image, which is then copied to all the target computers. With this option, though, there are a few routines performed by the Workbench installer that need to be taken into account, such as the creation of short cuts and file associations, and the setting of memory limits, which is described in Memory allocation.


... later1.1
For CLC Genomics Workbench 10.x, CLC Main Workbench 7.x, and Biomedical Genomics Workbench 4.x and as well as earlier versions of these products, you must install relevant module licenses at this point, even if you do not plan to use the initial installation for analysis work.