# 9 Install or deploy Origin to the user's computers or a file server

This page provides Origin deployment documentation for both the Concurrent Network and the Multi-seat Node Locked packages.

## Things to consider before getting started

Methods for distributing Origin

There are two ways you can build an Origin installation package for distribution:

• Pre-configuring installation settings by config.ini: In this case you can pre-set the serial number, install folder, license management, the User Files Folder and other properties in the config.ini file and then prepare an Origin package for distribution. Installer (InstallShield setup or MSI installers) will read from config.ini and install Origin silently. If you have a Multi-seat Node-Locked license package, it is the way we recommend to deploy your package.
• Preparing an MSI Installer: In this approach, you can use an MSI transform to pre-set the license management, the User Files Folder, and other properties. You can include a batch file to run the MSI and the transform. If you have a concurrent license package, you may want to use the MSI installer to install them.

## Prepare your customized settings with the installer

### Customize Installation Settings with Config.ini

Config.ini file is available from Origin 2019.

#### What is Config.ini and what can it do

Config.ini file is a configuration file to preset/customize installation settings. It is shipped with Origin setup file. Note: If you download the self extracting exe installer (exe format) from our website, it doesn't have Config.ini file. Please choose zip format instead.

##### What's in Config.ini?

It is optional to configure the following settings in Config.ini file. You can open it in a notepad editor to view and modify it. Detailed comments are included to help you understand each setting.

###### Installation Settings

Preset all installation data in [Setup] section:

- preset Serial Number, User Name and Company information, installation path, whether to install embedded Python and SPSS import module.
- determine whether to install Origin silently

Note: If you set QuietMode = 1 to install Origin in silent mode, you must preset the following items.

AcceptOriginLabLicenceAgreement=1
SN=
Company=

Other items will use the following default values if not specified

InstallPath=C:\Program Files\OriginLab\Origin####
EmbeddedPython=1
SPSSImport=0
AllUsers=1
ProgramFolder=C:\ProgramData\Microsoft\Windows\Start Menu\Programs\OriginLab Origin ####
###### Origin Folder Path
• User Files Folder
- preset User Files Folder in [Locations] section
- determine whether to show the User Files folder dialog with preset path when launching Origin the first time
• AutoSave, Backup and Unsaved Project Folders
- preset the root folder for AutoSave, Backup and Unsaved project folders in [Locations] section
• Apps
- preset Apps folder in [Apps] section

Note: If Config.ini has preset folder paths (for example User Files or AutoSave folder), they will be used instead of inheriting the old settings from previous version.

If a Concurrent Network package, preset the FLEXnet server's host name or IP address in [License] section. If Origin has been installed before, you can also decide whether to update the current server information or not.

#### Distribute your Origin installation package in silent mode

To use InstallShield's setup program to install Origin silently on computers in your organization, follow steps below:

1. Copy the Origin Setup files into a folder on computer "A". Note:
• Computer "A" must be on a network to which all potential Origin users can connect.
• Make sure Config.ini is included as long as other Origin Setup files in the folder.
2. Modify Config.ini file with all desired configuration preset.
3. If needed, preset license management as follow:
• If a Concurrent Network package, you can preset the FLEXnet server's host name or IP address in [License] section of Config.ini file. Otherwise the user must enter them in the License Information dialog when first start Origin.
• If a Multi-seat Node-Locked package, use the pk.txt file to preset product key. Origin will activate automatically at first start. Otherwise the user must activate a license from the OriginLab website, using the License Activation dialog.
Note: If you upgrade from Origin 2017 or later to a higher version, Origin will be activated automatically. You don't need to consider the license management in your distribution package.
4. Make sure this modified Config.ini and pk.txt files (if have) in the Origin Setup folder on \\A where setup.exe is located.
6. Email to all users to ask them to run the setup.exe file. Users must be logged into their computers with a log in account that has administrative privileges and they must be on the network and they must be able to access to \\A\<Origin Setup folder>.

Note:

• This silent installation method only installs Origin onto the target computers.
• For Concurrent Network packages, registration is optional. If user wants to register Origin, he/she can select menu Help: Register on-line to open the Registration dialog to register himself/herself.

## Post Installation Updates by Group Folder

The group folder is an optional feature Origin provides to distribute files. It can be used by any site/organization that has multiple Origin users managed by any license type. Even though the group leader and group members have different license types, sharing files between them by using Group Folder is available.

The Group Folder feature involves setting up one or more group leaders. For example, group leaders could be established at the department level of an organization. All or any number of Origin and OriginPro users in the organization can share the same group leader or leaders. Leader(s) can serve as a source for distributing files to members of the group.

You can set up a group leader which can serve as a source for distributing custom Origin files and patches to members of the group. Then once you have done this, you can set up the Origin in your organization so that it is predefined to receive updates from the group leader.

### Set up Group Leader(s) and Group Members

The first step is to set the Group Folder for the group leader machine.

Next, you can set the Group Folder for the member machines.

### Use the Group Folder Manager to Publish Files

Group leader uses the Group Folder Manager to add, remove files to group folder and then publish them to members of the group. Please refer to the Group Folder Manager document for detailed steps of how to use this tool.

After the group member specifies the group folder, and upon subsequent Origin start-ups, if newer files exist in the group folder, the group member will see a message telling them that files are updated (only for support files, not patches), or an update is now available and a re-start of Origin is required to receive the updates (for patches).

The support files from the shared group folder are copied to the group member's \GroupShared\ folder located in their User Files Folder.

The files then become available in various Origin dialogs such as Theme Organizer, Fitting Function Organizer etc. The files will have a prepend tag of (Group) to identify them as originating from the group folder.

#### Types of Files that can be Published

• Supported Origin files, such as project, templates and fitting functions.
Note: if you have some pre-defined system variables and want to share them via opx file, you will need to move the opx out of \GroupShared\ folder under the User Files folder. Otherwise the opx file will not be auto installed.
• Publish Origin Service Releases.
Within a version, OriginLab typically releases one or more service releases to fix problems found in the release version. Typically, the service release is provided as a patch.
1. You must first patch the group leader machine. Once done, re-start the group leader.
2. Use Group Folder Manager to publish the patch file that you applied to the group leader.
3. Now when the Origin group member starts their Origin, they will see a message that a patch is available from the group leader. They can choose to apply the patch, close their Origin, and the patch program will start running.
• Move the FLEXnet Server and updating members of the new location (Concurrent Network packages)>br? If a FLEXnet service is moved to a different machine, the Group Folder feature can be used to update the members of the Concurrent Network package with this new location.
1. After you set up the replacement FLEXnet server and have the service running successfully, you can edit the USE_SERVER.lic file located in the group leader's hidden License folder. Located:
C:\ProgramData\OriginLab\License
This file will typically have the following text, assuming the FLEXnet server is <FLEXnet server>
SERVER <FLEXnet server> ANY
USE_SERVER

A 3-Server Redundant FLEXnet server is also supported, for example if we have three servers <one>, <two>, <three>, and ports 12345, 23456, 34567, the USE_SERVER.lic file looks like:

SERVER <one> ANY 12345
SERVER <two> ANY 23456
SERVER <three> ANY 34567
USE_SERVER
2. Once this change is made and the Origin group leader is restarted, this file will be automatically published to the Group Folder, and the Origin group members will be notified of the change of FLEXnet server with a message "Concurrent license server settings are updated. Click OK to restart".