Glossary

  • A code provided to the customer (typically after purchase) and entered into Thermo Scientific License Manager (LM), License Manager for Server (SLM), or the LM Portal to activate a license, either online or offline. It is often pasted as a text block enclosed by BEGIN and END tags.
  • The field label in Thermo Scientific License Manager (LM) and License Manager for Server (SLM) that displays the identifier associated with an activated license record.
  • The Thermo Scientific FlexNet vendor daemon name used by newer license generations (for example, Amira and Avizo versions later than 2020.3).
  • A floating license option that lets a user temporarily check out a license from a network license server for offline use. Borrowing enables the software to run while the user is disconnected from the local network. During the borrow period, the borrowed capacity is unavailable to other users until it is returned or expires.
  • A licensing model in which license rights are delivered in a digitally signed license certificate (license file). The digital signature(s) protects the license contents from tampering and is validated by FlexNet licensing. This approach differs from trusted storage–based licensing, where license rights are stored as encrypted fulfillment records.
  • The act of a client application requesting and obtaining permission (a seat, token, or feature) from the license server for use during a session.
  • The purchased right to use a product or option under specific terms (such as counts, expiration date, maintenance window, etc.). Activation binds an entitlement to a specific machine or license server.
  • The Flexera licensing technology used for Thermo Scientific floating licensing. It includes server components (lmadmin or lmgrd together with a vendor daemon) and client-side license checkout mechanisms.
  • A type of license that allows a defined number of users to access software simultaneously across multiple machines. It is managed by a license server and is commonly implemented through a token-based system. Also called a concurrent license or server license.
  • A unique identifier used to track the activation and management of a software license. It is used by some tools (particularly legacy server tools) to list, update, or reactivate installed licenses.
  • A machine identifier used to bind a license to a workstation (local license) or a server (server license). A Host ID may be derived from a MAC address or another platform-specific identifier, depending on the product or licensing policy.
  • A Human-readable network name for a computer or server (often DNS-resolved). It can be changed and is not inherently guaranteed to be globally unique.
  • A text-based license file that contains license rights, such as the license type, the number of permitted users, the expiration date (if applicable), and enabled features. Its integrity is protected by the publisher's digital signature, which is authenticated by FlexNet components. In Thermo Fisher workflows, this file is typically generated by the Thermo Scientific License Manager Portal as a text file with a .dat extension.
  • A unique identifier used to identify and manage a customer license in Thermo Fisher order processing and license management systems, such as a FlexNet activation ID or order line number.
  • A server running FlexNet components (lmadmin or lmgrd together with a vendor daemon) that reads license files and grants or denies client license checkout requests, enforcing counts, expiration dates, and policy.
  • A FlexNet web-based license server administration service used to configure the server, manage vendor daemons, import license files, and monitor license usage.
  • Legacy/original FlexNet command-line license server manager that starts vendor daemons and routes checkout requests. Its configuration is set at startup and is not persistent; lmadmin is preferred for new installations where supported.
  • A license activated for use on a single machine. License rights and state are stored locally (typically in trusted storage or a license file) and bound to a machine identity (for example, UMN or hardware-derived identifiers).
  • The Thermo Scientific FlexNet vendor daemon name used by older license generations (for example, Amira and Avizo versions earlier than 2020.3 and Open Inventor).
  • A network adapter. In licensing contexts, the NIC’s MAC address is often used as one of the identifiers in the Host ID calculation.
  • A licensing mode that supports offline use of floating licenses by borrowing (checking out) a license for a defined period.
  • A purchase or order identifier used in licensing tools and portal views to reference a specific order line associated with a license entitlement.
  • A license that grants the right to use a specific version indefinitely (with no built‑in expiration) following a one-time purchase. Access to updates, upgrades, and support depends on the applicable maintenance or support terms.
  • A network intermediary that may need to be configured to allow licensing tools to connect to online activation services or the LM Portal from restricted networks.
  • A licensing operation that updates the installed license state to reflect renewed entitlements, such as an updated expiration date.
  • A commercial or licensing action that extends the validity period of a time-limited entitlement. A renewal may require reactivation to update the installed license state or server license file.
  • A licensing lifecycle operation that deactivates a license on a workstation or license server and returns the license rights to the licensing system, allowing the license to be reactivated or reassigned according to the applicable entitlement rules.
  • The return of a checked‑out floating license to the license server, making it available to other users.
  • A client-side application installed on the computer where Thermo Scientific software runs. For local (node-locked) licenses, LM is used to view license status and perform operations such as activation, deactivation, upgrade, or transfer, where applicable. For floating (server) licenses, LM is used on the client machine to specify the license server used by the software and to display the status of the floating licenses available from that server.
  • A server-side application installed on the license server to support floating licensing. SLM installs and works together with lmadmin, the FlexNet web-based license server manager, to configure and manage the Thermo Scientific FlexNet license server. It is used to import or update server licenses, manage vendor daemons, and display the status of the floating licenses served by that server.
  • A Thermo Scientific web portal used to perform licensing operations outside the local LM or SLM applications. For local (node-locked) licensing, the LM Portal supports offline workflows where requests, response files, or activation data are exchanged manually. For floating licensing, the LM Portal is used to generate or update server license files for use with SLM and lmadmin.
  • A license that is valid only for a defined period, as specified by the customer’s contract. After the expiration date, the software or licensed features are no longer available unless the license is renewed and reactivated in accordance with the applicable contract terms. This licensing model contrasts with a perpetual license, which grants indefinite use.
  • Units of license capacity used by a floating license server to control concurrent use. A product or feature may consume a defined number of tokens while it is running. The total number of available tokens determines how many licensed products or features can be used simultaneously.
  • The process of moving a machine-bound license from one machine or server identity to another through an authorized return and transfer workflow, rather than by copying license files.
  • A secure, encrypted storage location used by FlexNet Publisher to store license rights. Trusted storage is bound to the machine on which it is created and can be accessed only by FlexNet licensing components. It is maintained through licensing lifecycle operations such as activation, deactivation, repair, and upgrade.
  • A machine identity value derived from system hardware or VM/hypervisor-controlled data, used to validate local activations and other machine-bound licensing operations for licenses stored in trusted storage. The UMN may change if the underlying system identity changes.
  • A publisher-specific FlexNet server component responsible for serving licenses for a particular software vendor or product family. In a Thermo Scientific floating licensing environment, lmadmin starts and manages the vendor daemon on the license server. When a client application requests a license, the appropriate vendor daemon processes the request by checking the available license rights, tracking license usage, and granting or denying the license checkout. Thermo Scientific vendor daemons include asglmd and mcslmd.