On a supported Windows system, use the following steps:1.In the Services window, locate SentinelRMS Development Kit License Manager and double-click it.2.Stop the License Manager (service, if running already).3.Set the parameter(s)in Start Parameters. For example,-s mylicensefile -l myusage.log -f mytrace.log -tr 7 will have the followingresult:While starting a service manually, you can also include additional startup parameters.To do so:Select the relevant service from the list of services.Right-click and select the Properties sub-option from the pop-up menu that appears.Type the parameters in Start parameters.Click Start.However, these settings are not persistent; Windows uses them once, and then restores the default settings on next automatic service startup.mylicensefile will besearched by the application for the license code. Any new licenses addedto the RMS License Manager will be added to this license file.myusage.log will be createdcontaining all the License Manager usage information (such as, the licenseserver start, shutdown, license request, and license release).mytrace.log will be createdcontaining the License Manager trace logs. Level 7 enables the functions,keys, and errors trace logs.NOTEThe WindowsService Controller ignores the double quotes (“ ”). So, do not use doublequotes while setting options, else these will be ignored.
For example,if you specify -f aa'aa, then it will be interpreted as -faaaa.4.Start the License Manager after providing the settings.See the screen-shot below for an example. The following options are provided for lservnt: OptionDescription-H or -hDisplay list of lservntoptions. Displays the help for lservnt.-X removeRemove the License Managerservice.-X installInstall the License Managerservice.-X startStart the License Managerservice.-X stopStop the License Managerservice.-X statusGet License Manager status.-X commlineStarts the License Managerservice and sets the options defined in.The Sentinel RMS License Manager Windows service ( lservnt.exe)does not read startup options if specified as::Program FilesCommonFilesArchestrAlservnt.exe-l c:SafeNet.log.Instead, specify the optionpreceding -X commline. Forexample, the following command will start the License Manager plus setthe usage log in C drive by the name SafeNet.log::Program FilesCommonFilesArchestrAlservnt.exe-X commline -lc:SafeNet.logSee Also.
Activated Licensing Improvements 2017 Update 1 & 2 and SE Licensing v3.4This document covers license updates in 2017 Update 1 and Update 2 (released May 25, 2017) andSE Licensing v3.4 (released July 20, 2018, available for download from GCS).Updated September 18, 2018IntroductionWith 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 activationA 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.License useOnce 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 outagesWhen 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 licenseOff-line activationWhen 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 failIf 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).License ImprovementsAfter 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.
Wonderware License Server
Following is a list of these enhancements.IMPROVED LICENSE MANAGEMENT: ALLOWS THE RELEASE OF A LICENSE VIA THE LICENSE MANAGERQ: 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?A: Yes.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 RENAMINGQ: Changing the Host Name of a License Server with activated licenses will orphan licenses.
Archestra License Manager Software Free
Has this been addressed?A: Yes.Starting with 2017 Update 2, it is possible to rename a License Server containing Activated Licenses without losing licenses.