Things to Consider Before you Start

From OriginLab Wiki

Jump to: navigation, search

Go back to Multi-user Site Deployment

There are a number of methods you can use to deploy Origin on the machines of your potential Origin users. The method you select may depend on:

  • the number of users in your multi-user package,
  • how much you want these users to be involved in the Origin installation process,
  • how much you want these users to be involved in the Origin start up process,
  • whether you want to deploy an Origin that includes customizations,
  • whether you want to use the Group Leader / Group Folder feature, and deploy an Origin that is pre-set to point to a Group Leader. The Group Leader can publish Origin Service Releases (patches) to the Group members, as well as customized Origin files.

Before you decide how to deploy Origin, please consider this information:


[edit] Origin Installation

To install Origin, you must be logged into the computer with an Administrator log in account. The following information is entered or selected during an Origin installation:

  1. User name
  2. Company name
  3. Origin serial number
  4. Origin destination program folder
  5. Whether to install Origin Help documentation
  6. Whether to install pre-compiled Origin files
  7. Whether to install data import filters
  8. Whether to allow this Origin to be available for all Windows log in users on the machine, or just the current Windows log in user
  9. Program folder for the Origin program icons

[edit] Starting Origin after Installation

The following steps are performed when starting Origin for the first time. Administrator log in permissions are required for licensing Origin:

a. User Files Folder
The User Files Folder is log in user specific. It is the default location when opening and saving Origin supported files. The default selection is the Application Data Folder, which is:
<<Drive>>:\Documents and Settings\<<WinLogInUser>>\My Documents\Origin User Files\

b. License Management
When you purchased your multi-user Origin package, you purchased the package with a specific type of license management. For multi-user packages, this is usually:

- Concurrent Network Packages
Origin is managed by a FLEXnet license server

- Group Packages
Node-locked managed Group Package: Origin is managed by a license file that is based on a Computer ID that Origin generates for the computer. The license file is obtained from the OriginLab website.

c. Registration
For Group Packages that are node-locked, Registration occurs automatically when a user obtains a node-locked license file from the OriginLab website.
For the Concurrent Network package, registration is optional - but is required for OriginLab Technical Support.
OriginLab provides a dialog box for Registration.

d. Specifying an Origin Group Leader (optional setting)
You can define one Origin to serve as a Group Leader for all the other Origins. This Origin Group Leader can publish customized Origin supported files for all members of the group. This can include templates, fitting functions, import filters, and other files.
Also, the Origin Group Leader can publish an Origin patch, so that all members of the group will receive the patch.
Furthermore, if the FLEXnet server (Concurrent Network) is moved to a different machine, the Origin Group Leader can publish the new FLEXnet server location, thus avoiding having to tell all users the new FLEXnet server machine, or avoiding having to push out a file with the updated information.
The Group Leader feature is discussed in detail here:
Sharing Custom Origin Files

[edit] How to Select a Deployment Method?

Please review and consider the information provided above, and then review the following deployment methods. Links are provided for more information on each method.

Origin users must have Windows log in accounts with administrative privileges. You must tell the users the Origin serial number. Also, if the Origin is part of an Origin Concurrent package, you must tell users the FLEXnet server host name or IP address to enter in the licensing dialog box at first Origin start up.

In this case you will record an Origin installation. Thus your users will not need to know the Origin serial number. You will need to make the recording available to the users. When running the silent setup on their machines, the users must be logged in with a Windows log in account with administrative privileges. Also, if the Origin is part of an Origin Concurrent package, you must tell the users the FLEXnet server host name or IP address to enter in the licensing dialog box at first Origin start up.

There are two ways you can build an Origin installation package for distribution:
MSI File: An MSI installation file is provided on the Origin 8.5 DVD. You can also download the MSI Installer.
Template Installation: You can install Origin on a "template" machine and then prepare an Origin package for distribution.
For the Concurrent Network package, distributing Origin in these ways is most useful because you can pre-set the license management. Thus, your potential Origin users do not need to be aware of - or have log in permissions for - details related to installation or license management. In both cases, you can then use a software distribution environment / software such as NetInstall or SMS to distribute the MSI package or the template installation you prepared.

This is only supported if you own the Concurrent Network package. In this case you will install Origin on a remote access server. After installing Origin, you can pre-set the FLEXnet server host name or IP address. Also, you can pre-register the Origin (optional). If you pre-set the FLEXnet server and registration, then the clients that run this Origin will not be asked to do this.