Activated Licensing Improvements 2017 Update 1 & 2 and SE Licensing v3.4
This document covers license updates in 2017 Update 1 and Update 2 (released May 25, 2017) and
SE Licensing v3.4 (released July 20, 2018, available for download from GCS).
Updated September 18, 2018
With the launch of System Platform and InTouch 2017, a new licensing system was introduced to allow centralized license management, remove the need for dongles, and increase license security by use of Activated licenses. Since the original release, several field scenarios were brought to our attention that required changes in the licensing system. The below improvements affect licensing for InTouch, InTouch Web Client, Application Server, Historian Server, Historian Clients, OI Server, Alarm Adviser, and Recipe Manager Plus.
This document provides a summary of the licensing process to help you form a good understanding of the recent license improvements in 2017 Update 1, Update 2 and SE Licensing v3.4. After the summary of the licensing process, the license improvements are described.
License creation and activation
A license is created and delivered as an XML file. The XML file contains one to many Activation IDs, one ID for each license purchased. Distributors forward the XML file to the customer who activates the XML file by connecting their local License Server to the FNO in the Cloud by using the License Manager application installed on their local License Server. The License is locked to the License Server when the activation process takes place. During this Activation process, the local License Server is typically connected to the Internet, however, after Activation is complete, connection of License Server to the FNO in the Cloud is no longer necessary.
Please note that should the local License Server not have access to the Internet, there is an offline process to activate licenses. See the Licensing Guide for details.
The License Manager application allows management of the licenses across the network.
Once activated and using the License Manager application, licenses can be ‘reserved’ to a particular node or left unreserved (floating) to be acquired by a software product on the network. A License Server can be located on the SCADA network as a centralized License Server serving and managing all licenses across the network or the License Server can be the same node running the product software.
Once a license is acquired by product software, the license cannot be used by another product until the license is released back to the License Server. The release of the license occurs when the product goes through a proper shutdown or when the License Server Administrator manually releases the license.
License system handles network outages
When a license is acquired, a ‘borrowed time’ counter starts counting down. This ‘borrowed time’ is periodically reset by contacting the License Server.
For most company SCADA networks, the licensed nodes will be in permanent contact with the License Server over the SCADA network. The node running the software and the centralized License Server are in ‘heart beat’ communication.
However, sometimes the network may be down/disconnected for a period of time.
The system was originally designed so that when a disconnect occurs, the product software that acquired the license would stop running after the borrowed time was exceeded. (Note: this behavior has been modified, see below stated enhancements). Additionally, when the borrowed time is exceeded, the acquired license is then automatically released by the License Server making it available for use. If a node has successfully acquired a license and is running, it will continue to run even if connection to the License Server is not available. However, if the product software continues to be disconnected from the License Server and is stopped and restarted, it will not be able to acquire a license
When a License Server is not directly connected to the Internet, an off-line license activation process is available. Please see the License Manager Help or the SE Licensing Guide for details.
When machines fail
If the software is not gracefully shut down or the device fails, then the license is not released back to the License Server. Therefor, the license is not available for another node or the same node.
So, the product software will not be able to start again until a license is available and acquired. The License Administrator has two choices: Either wait for the borrowed time to end, thus releasing the license, or manually release the license from the License Server (one of the enhancements described below).
After the release of 2017, several field scenarios were brought to our attention that required changes in the licensing system. Multiple improvements have been made to address them. Following is a list of these enhancements.
IMPROVED LICENSE MANAGEMENT: ALLOWS THE RELEASE OF A LICENSE VIA THE LICENSE MANAGER
Q: One of my computers was physically damaged while various components of the Wonderware System Platform software were running. Licenses had been acquired by the product software. My understanding is that the licenses are released automatically at the end of “borrowed time” which in some cases is 20 minutes and in others 14 days but I cannot wait that long. Is there a way I can force the release of a license using the License Manager?
Previously, the release of an acquired license involved a multi-step process that included a call to our Global Customer Service (GCS) team.
The primary solution for this issue is to start up a device with the same name to recover the license. If the primary solution is not an option, starting with 2017 Update 2, the License Administrator can release a license by simply selecting it in the License Manager, deactivating and reactivating it. This requires fewer steps and eliminates the need to contact GCS.
Note: If your system has no connection to the Internet, you need to do the deactivation /reactivation using the offline procedure.
IMPROVED LICENSE SERVER: LICENSE SERVER RENAMING
Q: Changing the Host Name of a License Server with activated licenses will orphan licenses. Has this been addressed?
Starting with 2017 Update 2, it is possible to rename a License Server containing Activated Licenses without losing licenses. Recovery is possible without contacting GCS.
SOFTWARE PERSISTENCE: PRODUCTS CONTINUE TO RUN, EVEN IF THEY LOSE CONNECTION TO THE LICENSE SERVER
Q: While the product is running, if it loses connection to the License Server will it continue to run even after the original time limit (aka: Borrowed Time)?
A: Yes, starting with 2017 Update 1, products are no longer shut down at the end of the time limit if the connection to the License Server is lost.
Note: If the Borrowed Time has elapsed and the product is restarted, it will require a connection to the License Server to acquire a valid license.
IMPROVED LICENSE RELEASE: AWARENESS OF OS SHUTDOWN EVENTS
Q: There are many customers using InTouch in an RDS environment who configure the Microsoft RDS Server to automatically end disconnected sessions after a preconfigured timeout period. We noticed this would not give InTouch the opportunity to do a graceful shutdown and therefore would not release the license back to the License Server and the licenses then could not be used by other nodes requesting a license. Has this been addressed?
In Update 2, InTouch WindowViewer is now aware of OS Shutdown events. When it detects the OS initiating a shutdown it immediately releases the license to the License Server, and then continues to perform its other internal shutdown sequences that can be safely interrupted by the OS if needed.
CONSISTENCY FROM PREVIOUS VERSIONS: FAILOVER LICENSES REINTRODUCED
Q: How many licenses do I need for failover functionality? I thought with the new activated licensing system failover did not require a second set.
A: FLB (Failover/Load Balance) licenses are required.
Customer feedback on their typical product usage in scenarios involving Remote Desktop Services turned out to be different than we anticipated. Further testing for many of those scenarios determined that Failover / Load Balance (FLB) licenses are still needed for common implementations in the field. Hence, FLB licenses have been reintroduced to provide the most robust, consistent licensing experience for our customers.
IMPROVED RDS SESSION HANDLING: HANDLING OF MULTIPLE REMOTE DESKTOP SESSIONS FROM A SINGLE CLIENT
Q: In an architecture where multiple InTouch RDS client sessions were launched from a single client node and successfully acquired licenses, if the primary RDS server failed and an attempt was made to connect the same client node to a secondary RDS server and launch the same number of InTouch RD client sessions, sessions beyond the first one could not run. Has this been addressed?
With Update 2, the ID structure has been improved, addressing this issue.
IMPROVED LICENSE RESERVATION: SUPERVISORY CLIENT AND INTOUCH WEB CLIENT LICENSE RESERVATIONS
Q: InTouch stand-alone licenses can be reserved to a device. However, there are issues reserving Supervisory Client (OMI and InTouch View) licenses and InTouch Web Client licenses to a node. Has this been addressed?
The licenses on the FNO Activation Server have been corrected in June 2018 to address this issue. Supervisory Client and InTouch Web Client licenses can now be reserved to a specific machine. Licenses that have not been activated are fine. For licenses that were already activated, the customers just need to Sync their License Server with the FNO Activation Server.
Note: The License Manager pull down list displays an option to reserve a license to a User. This functionality is not implemented. For more details, see Tech Alert 297 (on GCS).
REMOVAL OF LICENSE SERVER REDUNDANCY TIME LIMIT
Q: A redundant License Server had a 3 day operational limit. Has this been addressed?
A: Yes. The limit was removed in SE Licensing v3.4 (available for download from GCS). There is no longer a limit to how long a backup license server can serve licenses.
For details on the issue, please refer to Tech Alert TA358.
LICENSE SERVER SUPPORT FOR WORKGROUPS.
Q: Are License Servers supported in a Workgroup environment?
A: Yes. The new licensing system was enhanced in Update 2 to support Workgroups.
NEW LICENSING WORKGROUP CONFIGURATION UTILITY
Q: Even after Update 1, configuring licenses within a Workgroup environment was complicated. Has this been addressed?
Licensing Workgroup Configuration Utility configures licensing nodes that are in workgroup environment, so that node-to-node communication can be established between licensing components (License server and License Manger).
The Licensing Workgroup Configuration Utility allows you to add a License Server to a remote license manager in work group environment.
The Workgroup Utility is part of SE Licensing v3.4 install. More information about the Workgroup Configuration Utility in a document located here: C:\Program Files\Common Files\ArchestrA\Licensing Framework\Licensing Utilities
LICENSE SERVER NO LONGER GOES INTO GRACE PERIOD WITHOUT EXPLANATION
Q: My customer experienced the License Server going into its Grace Period without explanation. Has this been addressed?
Grace Period is a condition that occurs when the licensing software believes that the License Server has been cloned. SE Licensing v3.4 includes a fix so that Grace Period is not triggered erroneously.
REDUNDANT LICENSE SERVER NO LONGER UNPAIRS WITHOUT EXPLANATION
Q: My customer experienced the redundant License Server unpairing from the primary License Server without explanation. Has this been addressed?
SE Licensing v3.4 includes a fix so this does not happen.
FOR ADDITIONAL INFORMATION ABOUT LICENSING, PLEASE SEE THE TECH NOTES AND TECH ALERTS
TN2907 – Schneider Electric Licensing – Best Practices
TN2908 – Resolving Historian Server Unable to Return License to the License Server
TA271 – Installing 2017 Software or License Server on the Same Computer on which a 2014 License Server …
TA274 – Communication failure between Wonderware products and a License Server can result in product…
TA280 – Improper Shutdown of InTouch from within an InTouch RDS/TSE Session May Result in the License …
TA281 – Do NOT Rename the License Server Computer when Licenses are Activated
TA297 – Issue with 2017 Licensing – Reserve License Capability For Supervisory Client and InTouch Web Client
TA358 – The Backup License Server fails to serve licenses when the Primary License Server is down…
TN2907 – Schneider Electric Licensing – Best Practices
OPEN ISSUES WE’RE WORKING ON
As documented in the SE Licensing Installation guide, upgrading any prior version to version 3.4 on a Hyper-V or Azure VM will put a License Server containing Activated Licenses into Grace Period.
As documented in the SE Licensing Installation guide, upgrade version 3.0 to version 3.4 on any platform will put a License Server containing Activated Licenses into Grace Period.
In an environment with a redundant License Server configuration, when one of the License Servers fails, there are known issues when trying to pair a replacement License Server. Currently, we require a backup of the original computer / VM in order to reestablish a pairing.
TA367 – License Server Limitation on Number of Product Activation IDs