Delcam switches from FLEXlm (Flexera FLEXnet) licensing to SafeNet Sentinel RMS – OpenLM can make the switch easier

Delcam is a UK based software vendor that produces CAD/CAM solutions for manufacturing industry. Delcam provides software that helps companies to take a complex-shaped products from concept to reality.

On September 2010 Delcam announced that FLEXlm licensing won’t be supported in all Delcam’s 2011 series products: “FLEXlm network licensing is no longer supported by Delcam so all 2011 series products will now use Sentinel RMS network licensing. If you are a FLEXlm licence customer, please contact your local Delcam Sales Partner to request your new Sentinel RMS license before downloading FeatureCAM 2011.”

Delcam also explains that the new “RMS Network” can emulate FLEXlm environment and this helps to reduce the implementation costs. OpenLM Utilizer software version 1.6 and higher supports FLEXlm and Sentinel RMS alongside with other license managers like: IBM LUM, RLM and more. Users of OpenLM Software can switch between the license managers easily while preserving all the functionality related to license management:

  • Same management tools for system administrators.
  • Same end user interface.
  • Same reporting and charting interface (FLEXlm, FLEXnet, Sentinel RMS)
  • Same support level for license usage billing between cost centers.
  • Etc…

For more information about OpenLM Software please see: –

For more information on the Sentinel RMS Network Licence see:-

Problems and solutions for the management of Flexnet Floating license server

Many software packages use Macrovision Flexnet floating license manager in order to protect their products. The protection helps the software maker to reduce piracy rate but in most cases, it is also causing troubles to users by making the software less friendly.  In this brief guide, we are discussing some of the most common problems encountered while using Macrovision floating license manager, and we are offering “first aid” commands to resolve some of these common problems. In addition, you also have the option of using OpenLM as an overall solution so you will never need to bother with these commands again.

Users can manage the license manager by using UI or the command line. In our solution we prefer the use of the command line interface, since it is more comprehensive and easier for use (at least for ex UNIX users).  As of lately, many organizations abandoned UNIX workstations for Windows XP and the majority of the license servers that run on Windows 2003, are employing a hardware key. The hardware key on the Windows workstation replaces the unique CPU ID that was originally used at the time of the good old UNIX…

Following are a few common problems and their offered solutions for Flexlm manager:

Problem: Running a License Server is usually done by using windows service that was created as part of the installation process, some problems occur as part of the general use of the system requiring administrator’s intervention.

Solution: When problems arise the license server can be activated manually by using the command: lmgrd -c “license file name”
This command is allowing us to check the problems that prevent the license from working properly.

Problem: Verifying who is currently using the licenses.

Solution: Checking for used licenses can be accomplished by accessing the server Command Prompt or any other station that has the software installed.

On the server machine:  lmutil lmstat -a  Will list all license and users.
lmutil lmstat -A  Will list only Active users.
On a remote machine:   lmutil lmstat -a -c <port-number@license-server>

Problem: User exited the application however the license manager is still reporting him as being in use.

Solution: There are two possible Command Syntax for this problem, one that is absolutely difficult and a second which is relatively simple to use.

lmstat output for the sample:

Users of SOFT:  (total of 2 license available)

“some software” v4.0, vendor: ABC Soft

floating license

username SERVERNAME 6BLf”L{>j0)n0ecs~ (v9.0) (lic_server/27004 104), started Fri 6/11 10:30

The ugly: lmutil lmremove <feature> <user> <host> <display>

or with the values: lmutil lmremove “some softwar” username SERVERNAME 6BLf”L{>j0)n0ecs~

The problem is that the characters of the display string may cause problems.

The good: lmutil lmremove -h FEATURENAME server_host PORT handle

And with values:
lmutil lmremove -h SOFT SERVERNAME 27004@lic_server 104

Problem: One user is showing as having registered as using two licenses on the very same workstation.

Try to kill both of the licenses, even if we manage to kill both, the software will usually reconnect to the license server after 5 retries. If this will not help, restart the license manager service. If it is still not helping – there may be a process still running at the workstation, check and kill all your protected software processes.

In general, restarting the license manager service looks like a dangerous action but our long experience demonstrates that it solves the problem in most of the cases and if the license is properly configured, it will reconnect with all the clients shortly there after.

OpenLM license manager can help the License Manager administrator solve all of the problems we described automatically. OpenLM monitors Macrovision’s License Server and fixes any problem in real time, significantly increasing the availability of licenses for the organization users. OpenLM will leverage your investment in expensive software licenses and will allow you to save money on maintenance. Use our Contact Form to get in touch with us and we will show you how to save money and unnecessary headache

How Does OpenLM TIMEOUT for ESRI ArcGIS works


OpenLM for ESRI ArcGIS implements a TIMEOUT feature for ESRI ArcGIS software that uses FLEXlm software for licensing. The activity of the TIMEOUT feature is based on two parameters, maximum idle time and threshold.

Maximum idle time (minutes) – Set the maximum time that ESRI ArcGIS software will not be closed, even if the software is not in use (idle). The software may be closed after that time, if the usage is above a set level (threshold).

Threshold (percent) – The usage level that above it OpenLM will start to release ESRI ArcGIS FLEXlm licenses.

How does it works?

OpenLM monitors the usage level of each FLEXlm feature and once the usage level is above the set threshold, OpenLM will gracefully close sessions, starting with the ones that are idling longer. Once the usage level drops below the set threshold, OpenLM Server will not close more idling sessions.

From the end user’s point of view, his ESRI ArcGIS project will be saved and then closed. A pop-up message will announce that the project was closed and will allow the user to reopen the project in a single click. The user can also click OpenLM Agent located on the end user desktop and get the list of all recently closed projects.


The combination of the threshold/maximum idle time is a simple system that assures that licenses will be available for users that need licenses while trying to minimize the number of closed sessions.

Since the act of closing idle sessions of ArcGIS Desktop can cause some inconvenience, OpenLM, is trying to minimize the number of closed sessions. If demand for Desktop ArcGIS licenses is low then users can keep idle session. When there is a demand for licenses OpenLM Server must assure that a sufficient number of licenses are available for new users that may try to access the software.

For example:
ESRI ArcView Licenses – 100
ESRI ArcInfo Licenses – 10
ESRI ArcGIS Spatial Analyst – 3

The default OpenLM Values are:

Threshold – 80%
Maximum idle time – 20 Minutes

Starting with the ArcView licenses, OpenLM will try to keep 20 licenses free for new users. Since 400 or more users can use a pool of 100 ESRI ArcGIS concurrent licenses. Keeping an amount of 20 free licenses available for new users makes sense.

With a total of 10 licenses available, OpenLM will try to keep two free licenses of ESRI ArcInfo ready for new users. Assuming that 8 licenses were already consumed, if more then two users try to access the ESRI ArcInfo licenses at the same time, some will get a FLEXlm denial. If two or less users request an ArcInfo license at the same time, their request will be fulfilled and then OpenLM will try to release idle sessions for more new users.

Because of the low number of Spatial Analyst licenses, OpenLM will only keep one floating license free for new users. This is because when two licenses are in use the usage rate is only 66% (less than 80%). Only when the third floating license is consumed the usage rate will be 100% and OpenLM will try to release one license for new users.

As shown above, the threshold mechanism works well for both high and low numbers of ESRI ArcGIS concurrent licenses.

Is there any benefit in applying different timeout values for different features?

We will try to address this issue by an example. Let us assume we have two FLEXlm features with different groups of users for each group: editing users that use ESRI ArcInfo and viewers the use ESRI ArcView.

Feature Licenses Users
ArcView         10        40
ArcInfo          10        20

With a threshold of 80% OpenLM will try to keep two (2) free licenses for each FLEXlm feature (ArcView and ArcInfo). Since there are less users that are sharing the ArcInfo FLEXlm feature (10 licenses for 20 users), there are more chances that less then 8 licenses will be concurrently in use. When the usage is bellow the set threshold, no sessions will be closed by OpenLM and by that, we actually extend the maximum idle time parameter.

If the usage rate of the FLEXlm ArcInfo feature is higher then the set threshold, 80%, a higher time out will not allow OpenLM to release idle licenses. The result is that we allowed idle users to hold licenses that are required by other users, and by that, avoided them from doing their work.

The conclusion is that timeout should be kept minimal and uniform to all features and user groups.


The timeout mechanism provided by OpenLM for ESRI ArcGIS is based on two parameters, “maximum idle time” and threshold. The combination of these two parameters provides a good solution for floating licenses (FLEXlm features) with both high and small number of licenses. The timeout value should be kept minimal (15-20 minutes) for all FLEXlm features and user groups.

OpenLM EasyAdmin – Supported browsers

EasyAdmin interface is OpenLM Management and reporting application for system administrators, managers and even users (using the new role based security system).OpenLM supports most popular browsers such as Microsoft Internet Explorer, Mozilla FireFox and Google Chrome. Other browsers such as Opera were reported as supported by users but are not officially supported by us. The full list of supported browsers and versions can be found in our software compatibility list.

We usually test the latest version of each version of a browser. This approach is good since new versions are more secure and provide better support for advanced functionality.

The economical factor is also critical, supporting older versions of browser is a very expensive task for software companies. The required resources in hardware, software and human resources are huge.

The demand for newer versions of software sometimes causes problems because of these reasons (but not limited to…):
Conservative Software Upgrade Policy – Organizations tend to be very conservative on their software upgrade policy. In some organizations it can take more than a year to get a newer version of an application implemented.
Many applications from different vendors – Most workstations are required to support many different applications from different software vendors. Some applications may require older versions of a browser and other – newer versions. For example, Pro/E WF3 from PTC requires IE version 6 while OpenLM EasyAdmin requires IE version 7 or higher.
Old applications – Upgrading to newer versions of application requires a significant investments from IT departments. This is why organizations tend to preserve older version. The use of older version of application dictates a requirement for older version of browsers.
Server policy – The limitations system managers impose on server environment are much higher than the ones imposed on workstations. System administrators tend to keep the original browser version provided with the operating system. For example, Windows Server 2003 is provided with IE 6. IE 6 is an outdated software that impose security risk on the server.

How to solve compatibility problems?

Always access EasyAdmin from a workstation, not from the server itself. OpenLM runs on a browser and is designed for remote access. Workstation’s browsers tend to be more updated then the ones running on servers.

When accessing the organization network remotely from outside the network, system managers has sometimes limited access . In such a case, try to upgrade IE on the server and if possible, also install another browser.

When the upgrade of IE on a workstation is not allowed we suggest to install of an alternative browser such as Mozilla FireFox.

OpenLM – Streching Your Licenses to Their Limit
FLEXlm, FLEXnet, IBM LUM, SafeNet HASP, SafeNet RMS, RLM, LMX license management
OpenLM for ESRI ArcGIS, OpenLM for Autodesk and OpenLM Utilizer

ArcGIS Version 9.3 and Windows 7

Installing ESRI ArcGIS Version 9.3 on Windows 7 can be a frustrating task because of problem with the registry size limit.

We faced the problem after trying to install Autodesk Map 3D on a Windows 7 machine already running ArcGIS 9.3 and another with Microsoft Visual Studio and ArcGIS 9.3.

The Autodesk Autocad (With concurrent network license using FLEXlm) installation failed at the same point on both computers. Searching the Internet for this problem suggested that the problem is related to the registry size. A helpful thread that contains this information is located at

The symptoms of a full registry are:

  • Software installations on the machine fails without a clear error message (In our case it was: “Micro​soft Visual C++ 2005 Redistributable Failed Installation aborted, Result=1603” when we tried to install Autocad Map 3D 2011)).
  • Windows components appears empty at the “Turn Windows on or off” window.

The weird fact is that the installation of ESRI ArcGIS 9.3 is adding the registry limit.
After running the installation of ESRI ArcGIS the registry key is added to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\RegistrySizeLimit with a limited value.

Our guess is that it was probably added to enlarge the defaults for older windows versions. As far as we know this key was removed in the new versions (see here:

The solution is (running as administrator):

  • Open the Windows 7 Registry using the command: regedit
  • Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control and locate the key: RegistrySizeLimit. Change its value to ffffffff (no limit) and then reboot the machine.
  • Run the command ” SFC /SCANNOW” on command line (with administrator rights)

This may solve many other Windows 7 problems as well.

OpenLM DNS Resolving service


OpenLM Software reports all aspects of license usage such as license inventory, used licenses, users, workstations and more. An important information for system administrator is to know the IP address of the workstation that pulls the license.

Some floating license manager do not report the IP addresses of the workstations that pull the licenses. The IP address is mostly important for international companies. In such companies  the system administrator can recognize the location of the use according to the IP address.

OpenLM Server is able resolve the IP address of workstations using network services and by that, provide this important information.

DNS resolving configuration

DNS configuration is executed as a background process in OpenLM Server. The configuration is done in OpenLM Server Configuration form->Advanced TAB

The settings are:

1. DNS resolving (true/false)
2. Resolve time

If DNS resolving is set to true (checked), then the process will take place every 24 hours at the set time.

For example, at The screenshot below, DNS resolving is set to take place every night at midnight.

Before the first occurrence of the process, no IP addresses will be shown. Between occurrences of the resolving process some workstation may be shown without IP address.

IP Addresses in OpenLM Interface

IP address shows in every tab or report that lists workstation names. For example, in the workstations TAB:

The user can configure his EasyAdmin interface to show or hide the any column, including this field using OpenLM interface.

About OpenLM

OpenLM is a license management system that supports all popular license managers including: FLEXlm, FLEXnet, IBM LUM, SafeNet HASP, SafeNet RMS, RLM and more.
OpenLM Also provides dedicated solutions for popular systems such as Autodesk software or ESRI ArcGIS. The software OpenLM for ESRI ArcGIS and OpenLM for Autodesk provides a unique solution for organizations that allows them to get more usage out of their existing licenses.

Monitoring an IBM LUM License server using OpenLM Software

OpenLM Version 1.6 Supports the IBM LUM license server. IBM LUM licenses are used by different software vendors, the main vendor is probably Dassault Systems (Catia software).


In order for OpenLM to support the LUM License server it has to be able to access the LUM License server remotely or locally. Different configuration options are supported by OpenLM that allows system managers to configure license servers located on LAN and WAN networks.

Configurations Options

OpenLM Supports flexible configurations that support LAN or WAN networks. This section lists the different configurations. Most of the information in this section is also relevant to other license servers such as SafeNet RMS, SafeNet HASP, FLEXlm, FLEXnet, RLM and others.

IBM LUM and OpenLM on the same machine

This is the most simple configuration but not a very realistic one. Most companies have more than one license server and because of that, they install OpenLM on a separate machine.

When OpenLM server is installed on the same machine as the IBM LUM License server, there is no additional configuration steps, just add the server name and port to the configuration.

IBM LUM and OpenLM on separate machines

In this scenario OpenLM Server is installed on one machine and the license server is installed on another. The problem we have to solve is how to allow OpenLM Server to access the LUM License Server. There are two possible solutions:

  • Use OpenLM Broker to send IBM LUM usage to OpenLM Server.
  • Configure OpenLM Server machine to be able to query usage on the IBM LUM License server.
Configure OpenLM Broker to push usage information to OpenLM Server

This is the most simple solution but it requires access to the license server machine for installation. OpenLM Broker software is reading the license usage locally and pushing the information to OpenLM Server.

The installation of OpenLM Broker requires only Java JRE. It can run on any operating system supported by Java and by that OpenLM supports Linux, Windows and UNIX license servers.

Configure OpenLM Server machine to be able to query usage on the IBM LUM License server.

IBM LUM Server allows other machines to query license usage and perform other actions from a remote machine. For a full install procedure please consult IBM LUM documentation, we will provide short overview of the requirements.

  1. Install Java JRE on the OpenLM Server machine.
  2. Make sure that you have IIS installed and configured on the OpenLM Server Machine.
  3. Install LUM software on the OpenLM Server machine, there is no need to configure your licenses.
  4. Add reference to OpenLM Server on the IBM LUM License server

Adding an IBM LUM license server in OpenLM

Like the configuration of FLEXlm and SafeNet RMS Services the configuration of an IBM LUM is simple and straight forward.
Using OpenLM Server Configuration->License Servers tab, Add the new license server and port. In the license server type the LUM type needs to be selected.

IBM LUM Support Level

Most of the functionality provided by OpenLM is also supported for IBM LUM licenses. We also support unique features of IBM LUM such as features versions.

OpenLM support for IMB LUM includes:

  • License inventory reporting.
  • License expiration alerts.
  • Current license usage.
  • Usage reports and charts.
  • License billing for groups or projects.
  • More…


IBM LUM (License Use Management) is the IBM product for technical software license management (similarly, the Flexera product is  FLEXnet). OpenLM Software fully supports the IBM LUM software and provides a flexible architecture that supports complex configurations.

The support for IBM LUM licenses if full, OpenLM supports unique features of IBM LUM such as versions for features. The advanced functionality of OpenLM such as License Usage Billing, Usage Reports, Usage Charts and more  is also supported for IBM LUM.

Collecting project information for usage using OpenLM Software


OpenLM Software allows organizations to collect usage data for billing and management purposes. OpenLM supports different policies, by groups or by project. Collecting information by groups is most common, the organization is using OpenLM in order to collect information according to any sub-division: subsidiaries, divisions, departments, etc.. The information is then used in order to implement the billing policy selected by the organization: charge by the hour, distribute maintenance costs between cost centers, or other.

Billing usage time by the active project is mainly used by project oriented companies. It helps such companies to calculate a more accurate cost of the project by collecting the usage time for each project.

Supported Software Systems

The process of collecting project information for software usage is supported for software systems that are using license managers such as FLEXlm (FLEXnet), SafeNet RMS, SafeNet HASP, IBM LUM, LMX and more.

These types of license managers are used by high-end software systems such us: ESRI ArcGIS, AutoDesk Autocad, Pro Engineer, PTC, Catia, Matlab and more.

Setting project support settings

OpenLM interfaces that allow the system administrator to perform the following actions:

  • Create new projects.
  • Set project state (Active, Not Active).
  • Assign users to projects (or remove).

Version 1.5 of OpenLM provides these interface by using OpenLM Users Management Module. From version 1.6 and on, we integrated these interfaces into OpenLM EasyAdmin.

The project collecting capability needs to be activated from OpenLM Server Configuration form. This can be done by navigating to the Projects tab. The following options are available:

Activating projects capability (“Log Project Information”).
Minimal Usage Duration – User can set a short period of usage that won’t be considered as actual usage.
Agent’s Behavior – Allows the system administrator to select one of two policies, by using OpenLM Agent functionality or by Environment Variables. The use of OpenLM Agent functionality is more user friendly and provides a more accurate results.

Environment Variables – The use of an environment variable is simple, set the name of the environment variable and OpenLM will automatically collect the information based on the environment variable settings. Using these option may also require the use of “Add unknown projects”, OpenLM server will automatically create unknown project names reported by users.

OpenLM Agent functionality – OpenLM actively collects project information for usage sessions. OpenLM Agent provides the following functionality:

  • Active Project prompt popps up automatically from OpenLM Agent when the user is activating the licensed software.
  • Active project prompt to pop-up every few minutes, in case the user switched to another project.
  • Active project prompt can be set to disappear automatically when the user ignores it.
  • The user can also activate the active project prompt from OpenLM Agent icon at any time.

Generating Reports

OpenLM EasyAdmin->Reports Tab provides reports based on active project. The user can generate usage reports at any time and limit the query by almost any argument.

Individual sessions can be reported by using OpenLM EasyAdmin->License activity tab.

Synchronization with external systems and sharing information

OpenLM allows organization to synchronize project assignment information automatically with external systems like the organization project management system.

OpenLM supports the update of the project list and and assignment of users to project through OpenLM API.

External systems can also access the project information and totals by using OpenLM API.


OpenLM System provides a complete infrastructure that allows organizations to implement a billing policy for licensed software usage. The system supports billing policy based on groups or users, projects or both together.

OpenLM Supports automatic synchronization of project information with external system like project management systems.