FAQ
  • 11 Feb 2025
  • 3 Minutes to read
  • PDF

FAQ

  • PDF

Article summary

FAQ


Q: Starting from version 1.21, it is possible to obtain an Unlicensed file. When is necessary to Unlicense a node?

A: Unlicensing a N3uron node is only necessary when transferring some or all licenses to another node. This includes the following scenarios:

  • Changing the hostname and/or UID of the node.

  • Moving one or more licenses from one node to another.

  • Releasing a license from a node back to the unused licenses pool.

In all other cases, unlicensing is not required.

Q: If an end-user with version 1.21 wants to change the type of a module (e.g., from OPC DA Client to OPC UA Client), is it necessary to unlicense and provide the unlicensing file for the change?

A: Unlicensing the N3uron node is not necessary since the conversion process does not involve migrating modules from one node to another. The following example demonstrates the procedure to convert a module type without the need to unlicense the node: EXAMPLE

Q: A node is running with a trial license and the client has purchased perpetual licenses. Is unlicensing necessary?

A: Unlicensing is not necessary. To add perpetual licenses to a node currently running with trial licenses, simply apply the perpetual licenses directly. Once you have confirmed that the perpetual licenses are functioning correctly, you can remove the trial license using the Unlicense option (right-click on the trial license).

Q: A node has perpetual licenses and the client has purchased additional perpetual licenses. Is unlicensing necessary to add more perpetual licenses?

A: Unlicensing is not necessary. To add additional perpetual licenses to a node that already has perpetual licenses, simply add the new licenses to the existing node. After that, apply the updated perpetual license file to the node. The previous perpetual license file will become invalid and can be safely deleted from the node.

Q: A client wants to migrate the perpetual licenses from one node to another, and some of the modules' licenses do not have active S&M. Is it possible?

A: Only licenses with active Support & Maintenance (S&M) can be migrated to another node. Licenses without active S&M will remain assigned to the original node.

Q: A client wants to convert 3 "Local Tags" licenses into a "Remote Tags" license and some of the "Local Tags" modules' licenses do not have active S&M. Is it possible?

A: Only licenses with active Support & Maintenance (S&M) can be converted. Therefore, to convert 3 'Local Tags access' licenses into a 'Remote Tags access' license, all 3 'Local Tags access' licenses must have active S&M. Licenses without active S&M cannot be included in the conversion.

Q: If 3 "Local Tags" licenses with different S&M end dates are converted into one "Remote Tags" license, what S&M end date will the "Remote Tags" license have?

A: When converting 3 'Local Tags' licenses with different Support & Maintenance (S&M) end dates into a single 'Remote Tags' license, the new 'Remote Tags' license will inherit the earliest S&M end date among the original licenses.

Q: If 3 "Local Tags" licenses with different S&M end dates are converted into one "Remote Tags" license, and later the "Remote Tags" license is converted back into 3 "Local Tags" licenses, what S&M end date will the final "Local Tags" licenses have?

A: When 3 'Local Tags Access' licenses with different Support & Maintenance (S&M) end dates are converted into a single 'Remote Tags Access' license, the new 'Remote Tags Access' license will inherit the earliest S&M end date among the original licenses.

If the 'Remote Tags Access' license is later converted back into 3 'Local Tags Access' licenses, each of the resulting 'Local Tags Access' licenses will retain their original S&M end dates from before the initial conversion to 'Remote Tags Access'.

Q: If S&M is updated, and we want to get the file with the updated S&M to update the software, what should we do?

A: To obtain the license file with the updated Support & Maintenance (S&M) information, you need to download the latest license file from the License Manager. Once downloaded, apply the updated license file to the corresponding node.

However, updating the license file is only necessary when you are updating the software version. If the software version remains unchanged, applying the updated license file is not required.


Was this article helpful?