The Vector License Client is the tool Vector provides to “easily manage all licenses for Vector tools”. Almost all actions can also be run from a command line, which is how they are performed on Linux.[1] The EULA allows Vector to “use technical measures to enforce the provisions that permit and/or restrict the Customer’s use”, to require activation, and to require regular re-activation, which is free of charge. Vector supplies the utilities needed for activation, re-activation and de-activation.[12] For a software asset manager, the License Client is the main inventory source for Vector entitlements actually deployed. It is not proof of compliance, because the EULA separates activation from the right to use.[12] Catalog proof: Activation is a prerequisite, not a grant of rights.
Editions
The License Client distinguishes local licences, activated by a user or administrator on a license carrier, from network licences, which “are located on a license server and are managed by your administrator”.[1]
| Licence | License type | Bound to | Possible carriers |
|---|---|---|---|
| Local | Device License | A specific license carrier | Windows: computer, Keyman, Vector network interface. Linux: computer, Keyman |
| Local | Named User License | A specific user or license carrier | As Device, plus a virtual machine |
| Network | Named User | A specific user | License server |
| Network | CI Agent Count, CI Team | A scope such as a team or project, not a user | License server |
Source: Vector License Client help.[1] Catalog proof: Local licences (Device, Named User) versus network licences (Named User, CI Agent Count, CI Team).
The Vector Keyman (article number 07214) is “a small USB-Dongle that manages licenses and activation of the Vector software tools”; Vector supports it only on Windows computers or Vector devices running Vector software.[13] Under the EULA, dongles and hardware interfaces supplied by Vector are Devices.[12] Catalog proof: The Keyman dongle is a license carrier for Vector tools.
Activation keys: ELA and EULA licences
Licences are delivered as activation keys. The help names two kinds of agreement. Under an “ELA License (Enterprise License Agreement/Company License)” the customer’s administrator “creates the activation keys for the license in the Vector Portal”. Under a “EULA License (End User License Agreement/User License)” the key “is provided by Vector”.[1] License requests are checked against the Vector Activation Server.[1] When the key is loaded, the client lists all licences it contains before they are activated on the chosen carrier.[5] See the Enterprise License Agreement program row.
Metrics
For every licence the client displays attributes that map directly to the EULA. Useful columns for an entitlement record include:[2]
| Column | Meaning |
|---|---|
| License Type, License Model, License Restriction | For example Device or Named User; perpetual; evaluation |
| Material Number, Vector License ID | Vector’s product number and the licence’s identifier |
| Maximum Version | “You may use all the versions of this product up to this version.” |
| License Quantity | How many users or computers can use the licence in parallel; always 1 for local licences |
| Reactivation Due on, Reactivation Period | When the licence must next be reactivated to stay usable |
| Expiration Date | For subscriptions, the date after which the product can neither be used nor reactivated |
| Is Activatable in VM, Is Country Specific, Is Reactivatable | Technical limits of the licence |
| No. of Committer, Scope | For CI Team and CI Agent Count licences |
| Volume Method, Volume Quota, Remaining Volume Quota | For volume licences: data, time or operations |
For a network Named User licence, quantity and user list go together. A licence “with quantity 10 is activated on a license server and a list of authorized 10 users is stored. These 10 users can use this license in parallel.”[2] Catalog proof: Network Named User quantity equals parallel users on the user list; Perpetual licences are version-specific.
License servers
An administrator turns a computer into an on-premise license server by enabling “Share Licenses in Local Network”, activates the licences on it, manages user assignments for Named User licences and gives users the server’s IP address or DNS name.[3] License servers communicate on TCP and UDP ports 22350 to 22352.[3] Users enter one or more servers in a server search list, whose order sets the search order, without administrator rights. If a server cannot be reached, the help suggests checking whether “the CodeMeter service is running on the server machine”.[4]
User assignments can be managed in the graphical client or on the command line, but the two are not synchronised, so Vector advises using only one. It recommends the client for about 20 licences and 20 users and the command line above that, and suggests separate license servers for licences with and without user lists.[6]
Counting / floors
Borrowing. Users can borrow network licences onto a license carrier for offline use. No activation key or Internet connection is needed, but the servers must be reachable. “Borrowing is not possible for all network licenses and not on all license carriers”, a maximum loan period applies, and “A license cannot be borrowed more than once at the same time on the same license carrier.” A borrowed licence is usable until midnight of the chosen day and then “falls back and is available again on the license server”; it may be returned earlier.[2] Until then the borrowed licence is not available to other users of the server. Catalog proof: Borrowed network licences return to the server at midnight of the chosen day.
Moving licences. To move a licence to another carrier, deactivate it, after which it is available again in the activation key, and activate it on the new carrier. “However, ELA licenses are still assigned to the license carrier on which they were previously activated” until the local administrator changes the assignment.[9] Each move is also a re-assignment under the EULA, limited to four per year outside the listed exceptions.[12] Catalog proof: ELA licences stay assigned to the old carrier after deactivation; Re-Assignment at most four times per year.
Updates. After a maintenance renewal or upgrade, licences are updated online or offline. “You can only update all licenses associated with a license carrier”, and “Once updated, you can not undo the update again.”[8] Catalog proof: Licence updates apply to all licences on a carrier and cannot be undone.
Migration of old license bits. Hardware-based “license bits” from older Vector products can be migrated to new Vector licences, but only with the graphical client. “The migration process cannot be undone because the license bits are deleted from the license bit carrier.” License bits from a Keyman can no longer be migrated, and Vector Sales must be contacted.[7] Catalog proof: Migrating hardware license bits deletes them; Keyman bits can no longer be migrated.
Offline and remote activation
Activation, deactivation, reactivation and updates can be done for computers without Internet access. The client writes a context file (*.vlc) on the offline computer. An online computer running the same client version, or the browser-based Vector Offline Licensing app, turns it into an update file (*.vlu). Applying that file on the offline computer produces a receipt file (*.vlr).[10] On Windows, online actions can also be run on a remote license carrier, including Vector Tool Platform devices such as the RT Rack and VT6000 series, through a remote connection. Both sides need the same client version.[11]
Virtualization & partitioning
“Not all licenses can be activated in a virtual machine”; the “Is Activatable in VM” attribute shows which can.[6] “License activation in a Docker Container is not supported.” Containers instead list a computer enabled as a license server in their server search list.[5] A license server can itself be a virtual machine. Before changing that VM, for example its CPU cores or memory, the administrator must deactivate the licences and activate them again afterwards: “If you do not follow this sequence, then the licenses will lost.”[3] Whether virtual use is permitted is still decided by the license type in the EULA, not by the client. Catalog proof: Not every licence can be activated in a virtual machine or a Docker container; License server on a VM: deactivate before changing the VM; Device License: no remote connection and no Virtual Desktop.
Programs
The client shows but does not create commercial programs. The ELA affects who issues activation keys and how assignments are changed. Subscription licences carry an Expiration Date, while perpetual licences carry a Maximum Version that rises only through maintenance updates.[2]
Out of scope
- The Vector Portal and Vector Offline Licensing app themselves, and Vector Support knowledge base articles, which require a login.
- Earlier licence management tools and older client versions.
- Embedded software delivery and its tooling, which are governed by the separate Terms and Conditions for Embedded Software.