Application Note 2011: Quick Installation guide for the OpenLM license management system v1.8

The OpenLM Floating license monitoring and Usage optimization tool interfaces an ever growing variety of license managers, such as Flexera FlexLM (Flexnet publisher), Beta LM, IBM LUM, DSLS, Sentinel HASP, Sentinel RMS, Reprise RLM, MathLM, LM-X and Easycopy.

Step 1: Installation

The OpenLM System components are available for download on the OpenLM site. After filling in your name and email, you would be directed to the download section. Select the OpenLM Version 1.8 section:


And start by downloading the server:

When downloading is complete, double click the downloaded *.msi file and follow the standard installation instructions.

Step 2: Configuring License Servers

When the installation is complete, click:

Windows’ Start → All Programs → OpenLM → Server → OpenLM Server Configuration

The OpenLM Server configuration window opens.

1. Add in your license servers:

  • Click the ‘Add’ button,

  • Type in the License server’s host name or IP (e.g. lm10) and Port number (e.g. 27000)

  • Select the new License server’s type (e.g. FlexLM)

  • Type in an informative name (e.g. “lm10 – ArcGis server”)

  • Select the license server’s time zone (e.g. UTC+1)

The image below demonstrates this configuration:

 

2. Select a license server and click the check button in order to ensure that OpenLM can retrieve information from that license server. This information is the input received from the License manager.

3. Repeat steps 1 & 2 for all license servers.

4. Click ‘Apply’, and “Restart now”.

Step 3: The OpenLM EasyAdmin Interface

The EasyAdmin web application is the main OpenLM Administrative and user interface.

You can find it on:

Windows’ Start → All Programs → OpenLM → OpenLM EasyAdmin2.

The OpenLM EasyAdmin opens. Click the EasyAdmin start button to explore this application’s features.

The image above is an example of an EasyAdmin workspace. It features Administrative tools, License data, License usage data, Graphic usage representation, Roles and permissions’ assignment, and Active Agent capabilities.

For more information on the OpenLM EasyAdmin web interface, please refer to this document.

Congratulations!

You now have an up and running OpenLM system.

For further information regarding the installation and preliminary configuration of the OpenLM system components, please refer to the “Application Note 2010: OpenLM license management system Complete Installation guide v1.8” document.

Revision table

Revision

Author

Date

Remarks

0.1

Orik

Apr 23,  2013

Preliminary

Siemens PLM license analysis and license monitoring

OpenLM supports license monitoring of a wide, and ever growing variety of license managers. Among those are Flexera FlexLM (Flexnet publisher), IBM LUM, DSLS, Sentinel HASP, Sentinel RMS, Reprise RLM, and LM-X.

This group of license management utilities encompass a great variety of licensed products. One group of such licensed products is the Siemens PLM (formerly UGS) 3D & 2D Product Lifecycle Management (PLM) group.

The OpenLM tool provides high level of application usage management and optimization for PLM licenses, providing clear and valuable usage information for Managers, License Administrators and End Users.

Siemens PLM Common Licensing

Siemens PLM employs the “Siemens PLM Software Common Licensing” tool in order to deliver a consistent licensing implementation to all PLM products. It is based on the Flexera FlexNet license management tool, and has incorporated some unique characteristics:

  • The PLM Common Licensing toolkit has adopted the Siemens PLM Software-wide licensing vendor daemon ugslmd. Consequently, all Siemens PLM products gain access to common licenses utilize this same daemon.
  • The PLM Common Licensing toolkit employs a unified license file for all PLM products.
  • The default port for the PLM ugslmd vendor daemon is 28000. That was decided in order to avoid conflicts with other applications, using the default FlexLM port 27000.
  • Composite ID (CID): This is a 12 digit hexadecimal unique machine identifier that is used as part of Siemens PLM Software licensing to lock a license file to a machine. The CID is distinguished from a FLEXnet hostid by the keyword “COMPOSITE=”.
  • NX bundles and Suite Packages: These are packages that Siemens PLM Software has predefined to meet the general needs of customers at a lower cost than purchasing individual floating licenses.

For more information on Siemens PLM Software Common Licensing, please refer to this PDF.

The OpenLM advantage

The OpenLM license monitoring tool incorporates many advantages in PLM software maintenance for members of all positions in an organization. In a nutshell:

  • Managers get a clear picture of their Software assets.
  • System Administrators are freed from managing licenses.
  • End users enjoy improved PLM license availability.

Additionally, OpenLM v 1.8 Automatically sorts NX suites, to clearly display Siemens PLM application usage measuring in its true context.

Troubleshoot Form: OpenLM Server Item 003 (Unable to connect to FLEXlm license server error: -96,7:11004 “Comm. error”)

Title Unable to connect to FLEXlm license server
Category OpenLM Configuration Form
Date Oct 24, 2012
Handled by
Relevant Links
Applies to license managers FLEXlm, FLEXera FLEXnet,
Applies to license model Floating licenses, Network licenses, Concurrent licenses
Symptoms No activity reported on EasyAdmin for a specific FlexLM license server
Observed during investigation Clicking the “Check” button for one of the FlexLM license servers on the OpenLM Configuration Form resulted in an error
Trouble shoot process Check License server connectivity configuration.
Solution Found (Found/Pending/Known Issue)
Other steps for troubleshooting

Symptom

The customer complained that he “Couldn’t connect to the FLEXlm license server”. Attempting to connect to the license server resulted in the following message box appearing on his screen:

lmgrd is not running: License server machine is down or not responding. (-96,7:11004 “Comm. error”)

Troubleshoot process

1. Make sure the license manager machine is up and that you could check out licenses from it.

2. Make sure that the hostname , Port number, License Manager type and timezone are configured correctly in the OpenLM server configuration tool. Also, please review this Troubleshoot guide.

3. Check the connectivity between the OpenLM server machine and the license server (using ping or telnet).

4.  Make sure that any security components (Firewall) are not blocking communication on both ends. The OpenLM server uses ports 7012, 7014, 7016, 7017 and 7019. The OpenLM server’s communication with the License server relies on port 7014.

Make sure that the port is open:

 

  • Try disabling the firewall temporarily.
  • Enter “Control Panel”→“System and Security”→“Windows Firewall”→ Advanced settings”.
  • If the port isn’t defined under the “‘Inbound Rules” open the port by adding a New Rule using the “New Rule” button located on the lower right side of the screen as depicted below:

5. The OpenLM Broker may bypass such communication issues. Install the OpenLM Broker on the license server machine. See this application note for more information: Application Note 1004: OpenLM Broker quick start guide

Application Note 1001_b: Configuring OpenLM to interface the Sentinel RMS license manager

Scope:

OpenLM supports the monitoring of a wide variety of license managers such as Flexera FlexLM ( Flexnet ), Beta LM, IBM LUM, DSLS, Sentinel HASP, Sentinel RMS, RLM, and LM-X. This application note elaborates the steps required to configure OpenLM to interface the Sentinel RMS License Manager, and obtain reliable license reports and usage statistics.

Enabling the OpenLM server to work with RMS

In order to configure OpenLM to work with  Sentinel RMS, please follow this procedure:
1. Download lsmon.exe and lsapiw32.dll . These files aren’t included in the OpenLM installation package. For information on how to obtain these files, please contact OpenLM on support@openlm.com.
2. Copy these files to “C:\Program Files\OpenLM\OpenLM Server\LM”
3. Enter the OpenLM Server Configuration Form. Select the LM Tools tab → RMS.
4. Type in the full path of the executable file, i.e.:  “C:\Program Files\OpenLM\OpenLM Server\LM\lsmon.exe” in the “RMS executable file” text box.

See the following image for further clarification:

Introducing a new Sentinel RMS server

After configuring the OpenLM configuration tool to work with Sentinel RMS as elaborated above, the user may introduce an new  Sentinel RMS server under the License Servers tab:
1. Select the “License Servers” tab.
2. Select the RMS type from the “Type” dropdown list.
3. Type in a meaningful description in the “Description” text box.
4. Type in the appropriate “Hostname” and “Port” numbers. The Sentinel RMS default port is 5093.
5. Check the “Enabled” check box.
6. Click the “Apply” button. The  Sentinel RMS server is now ready to interface the OpenLM.

OpenLM Broker configuration for RMS

The OpenLM Broker is an optional though highly recommended component, that should be installed and configured on the RMS license manager machine. It provides accurate license statistics, and facilitates communication between the OpenLM Server and the License manager.

First, download and install the latest OpenLM Broker version. Follow the installation and configuration instructions on the OpenLM Broker configuration Application Note.

In the License server port dialog, select the RMS license manager type from the ‘Type’ dropdown list.
In the port’s Commands list make sure the ‘status’ command is
lsmon <License Server Name>

Document Revision Table

Version Author Date Changes
0.1 Orik May1, 2012 Preliminary
1.0 Orik Jun3, 2012 Revised.
1.1 Orik Jun6, 2012 Added Broker

 

Setting FlexLM port numbers statically

Flexnet / FlexLM ports numbers may be set statically by declarations made in the FlexLM license file. When remain undeclared, these ports would be set randomly every time the license manager is started.

1. In order to set the port connecting the license manager with the installed applications:

On the server side, on the license file (<license>.lic), add a port number to the end of the SERVER line, e.g.:

SERVER <ServerName> <HostId> <PortNumber>

On the client side, on the <license>.dat file add the same number to the end of the SERVER line, e.g.:

SERVER <ServerName> ANY <PortNumber>

2. In order to set the license manager to interface the Vendor over a predefined static port number, add this number in the end of the VENDOR line, in the license file on the license server machine, e.g.:

VENDOR <VendorName> PORT=<VendorPortNumber>

In order for these changes to take affect, you would need to reread the license file. You may do that by clicking the “Reread License file” button, under the “Start/Stop/Reread” tab in Flexera’s LMTOOLS application.

The OpenLM license monitoring tool interfaces these ports in order to extract license statistics, and reliable license usage reports.

For any further information about license management, please visit the new OpenLM site, or address us directly on support@openlm.com.

How do I know the FlexLM license manager port number ?

OpenLM employs the Flexnet / FlexLM reporting mechanism to monitor and optimize concurrent license usage, and obtain license statistics. The FlexLM license manager interfaces licensed applications via predefined ports. You can verify that a port number is set correctly by:

1. Using Flexera’s LMTOOL utility: Select the “Server Status” tab, and click the “Perform Status inquiry” button. the port number would appear on the line that begins with “License server status:” e.g.:

License server status: 27000@My_server

2. You can also find the server name and port number (If defined as static) directly in the license file, in the SERVER line e.g.:

SERVER <ServerName> <hostId> <PortNumber>

USE SERVER

The path and name of the license file is set in the LMTOOLS, under the “Config Services” tab.

FlexNet vulnerability: lmgrd Remote Code Execution

Zero Day has reported that a security vulnerability has been discovered in FlexNet License Server Manager installations. This vulnerability enables attackers to execute arbitrary code on remote FlexNet License Server managers. Authentication is not required to exploit this vulnerability. The flaw was reported by Luigi Auriemma and Alexander Gavrun.

The specific flaw exists within lmgrd license server manager. lmgrd listens by default on TCP port 27000. A specially crafted packet sent to the server will cause a stack overflow allowing for remote code execution under the context of the server.

Flexera Software has issued an update to correct this vulnerability and also provided license administrators best practices for mitigating risk exposure.

More details can be found at:

http://www.flexerasoftware.com/pl/13057.htm

Automatically Release “Orphan” ArcGIS and Autodesk licenses

Users of network licensed ESRI ArcGIS and Autodesk (AutoCAD) applications report cases in which licensed application were closed, but the licenses remained “hanging”, and were not returned to the license pool. Here is an example for such a condition.

This condition may be caused by broken communication between the FlexLM license server and the workstation on which the application is running, or any other “glitch” for that matter. The answer given by the vendors to this condition is that the system administrator should manually release the checked-out license via the license administrator tool or Flexera’s LMTOOLS UI.

But this is wrong.

This problem does not manifest in any apparent error message or visible notification, so this condition may persist indefinitely. Because of that:

  • There is no way for manually and routinely tracking down and fixing this condition. This condition is only captured when there is an obvious “leak” in the amount of available licenses.
  • On top of not being able to utilize the full extent of the acquired software licenses, this condition may also cause exaggerated billing for users.

An automatic solution for the identifying and fixing this condition is therefore required, and is supplied by OpenLM. On the OpenLM EasyAdmin web application, there is a check box which is configured to do just that. It configures the OpenLM system to track down ArcGIS and Autodesk applications’ licenses which are checked out but not used, and retrieve them.

This option is set active by default. The configuration check box is found as follows:

  • Click the OpenLM ‘Start’ button, and select ‘Administration’. The ‘Administration’ window opens.
  • Select the “Active Agent” icon. The “Active Agent” window opens.
  • Select the “Extension dedicated” tab, and check the “Solve license manager errors” box.

That’s it. You wouldn’t have to worry about hanging “Orphaned” licenses for ArcGIS and Autodesk applications any more.

Note:
Support of this feature in ArcGIS 10 is subject to the stated in this paper.

FAQ: Flexera lmgrd log file is very big


The lmgrd log file collects all license check out / check in activity. This log would continue to increase in size and as long as the licensed service is running.

The log is cleared when the licensed service is restarted.
This can be done via Flexera’s LMTOOLS UI.

On The “Services/License File” tab choose the licensed service. e.g.: Autocad.

On the “Config Services” tab – you can view the log (e.g: Autocad.log) and its path.

On the “Start/Stop/Reread” tab, use the marked buttons. This would clear the service log file (Autocad.log) and restart logging.

One of the advantages of the OpenLM system is that the accumulation of large amounts of data in this log file is made redundant. The OpenLM Broker is a component in OpenLM’s system which reads the licensed log file, and reports its content to the OpenLM server. There this information is processed and exhibited in a clear and negotiable manner.

 

 

Application Note 1007: Configuring FLEXlm FLEXnet Option File Using OpenLM Easy Admin

Application Note 1007: Configuring FLEXlm FLEXnet Option File Using OpenLM Easy Admin

General:

FLEXLM ( FlexNet publisher ) option files grant license administrators close control over various operating parameters within the constraints of the license model. Licensed features can be dedicated, denied or reserved to users or groups of users, according to the option file’s setting.

Employing FlexLM option files, the license administrator can:

1. For concurrent (floating) licenses:

  • Allow the use of features

  • Deny the use of features

  • Reserve licenses

 

Concurrent licenses can be held either in license files or in fulfillment records within trusted storage.

2. For all license types:

  • Restrict the number of licenses available

  • Control the amount of information logged about license usage

  • Enable a report log file

  • Control the automatic rereading of licenses

 

FLEXlm Option files are implemented as text files, located on the license server. Although  this method fits the licensing requirements well, the process of creating and maintaining option files is error-prone and difficult to maintain.

The OpenLM solution incorporates synchronization of License administration tools with the organization’s LDAP (Active Directory), keeping the FLEXlm option file up-to-date as users leave or join the organization, or move between groups.

 

Creating an Option File

1. The Option file should be placed under the same directory as the vendor daemon file, in order to enable FlexLM to read it automatically. Locating the Option file in a different folder is possible, but this requires FlexLM to be configured to search for it in that location.

2. The recommended name for the Option file is vendor.opt, where vendor is the vendor daemon name. Note that the name should not contain white spaces ( e.g.: Arcgis vendor: arcgis.opt,  Adsflex vendor: adsflex.opt ) “Vendor name.opt” is illegal.

FLEXlm option file editing

When configuring the option file using OpenLM, the configuration data is presented to the OpenLM Server, and forward by it to the OpenLM Broker, located on the license server machine. The OpenLM Broker updates the option file.

OPENLM SERVER CONFIGURATION

Check the “Enable OpenLM option file management” box

 

It is necessary to install the OpenLM Broker on the license server machine in order to edit the option file using the OpenLM EasyAdmin web application.

OPENLM BROKER INSTALLATION

  • Information about the OpenLM Broker and its installation process is available in Application Note #1004.

  • The latest OpenLM Broker version  is available for download for version 1.8. If you need a previous version please contact Support@openlm.com.

OPENLM BROKER CONFIGURATION

The next step after creating an option file on the license server machine, is to configure the OpenLM Broker to work with it.

 

1. Open the “OpenLM Broker configuration tool” installed on the license server machine

(“Start” → “Programs” → “OpenLM” → “Broker” → “Broker Configuration Tool”). The Broker Configuration Tool window appears.

 

2. On the Broker Configuration Tool window, Click the (+) button near the License server name in the configuration window.

 

 

3. Click the (+) button near “Vendors” (1).

 

4. Click the “Edit” button.

 

5. Check the “Watch Option File” box (2)

 

6. Type in the path to the Option file previously created. (3)

 

7. Restart the OpenLM Broker.

Editing Option Files

OPTION FILE TARGETS: USERS, USER GROUPS, HOSTS, HOST GROUPS AND IPS

Option Files apply license permission limitations to certain target categories; namely Users, User groups, Hosts, Host groups and IPs. Setting up and introducing these targets is beyond the scope of this article, but a short explanation on each of these target categories is attached at the end:

In order to edit option files, select a specific option file, and then apply changes to it.

OPTION FILE SELECTION

1. Open the OpenLM EasyAdmin web application.

2. Click Start → Opt. File Admin. The “Option File” dialog window appears.

3. Select the specific Option file to be edited (e.g.: Autocad Option File) and click “Set”.

 

GLOBAL SETTINGS OF THE VENDOR DAEMON

On the EasyAdmin web application click Start →  Option Files → Policy.

The “Policy of Option File” window appears.

This window comprises of several text boxes:

GROUPCASEINSENSITIVE (OFF / ON)

ON: User names and host names specified with the Options File GROUP and HOST_GROUP keywords respectively, are treated as case insensitive.

OFF (Default): User names and host names are treated as case sensitive.

NOLOG { IN | OUT | DENIED | QUEUED }

Suppresses logging of the selected type of event in the debug log file.  License administrators may use this option to reduce the size of the debug log file, however it can reduce the usefulness of the debug log when debugging license server problems.

  • IN / OUT: Turns off logging of license check-ins and check-outs respectively.

  • DENIED: Turns off logging of license check-out denials.

  • QUEUED: Turns off logging of queued license requests.

REPORTLOG

Specifies the report log file for this vendor daemon. It is recommended to precede the report_log_path with a ‘+’ character to append logging entries; otherwise the file is overwritten each time the daemon is started.

TIMEOUTALL

Specify the idle timeout for all features, after which an inactive license is reclaimed. The software publisher sets a minimum value. If a smaller value is set – it is ignored, and the publisher’s minimum value is used.

DEBUGLOG

Writes debug log information for this vendor daemon to the specified file.

Note that this affects output from only the vendor daemon associated with this options file. The debug log output of lmadmin or lmgrd and any other vendor daemons in the same license file is not captured in this file.

Click the ‘Save’ button in order to save the edited configuration.

FEATURE SETTINGS

On the EasyAdmin web application window click ‘Start’ →  ‘Option Files’ → ‘Features’.

The “Features of Option File” window opens, according to the option file selected before. This window enables the configuration of each feature separately, applying changes either globally or to specific Users, User groups, Hosts, Host groups and IPs.

1. Select a feature. The ‘Permission’ column is filled

2. Select a user (shown in the screenshot below):

2a. Select the Users tab

2b. Click the ‘Add’ icon. The “Users search” window appears.

2c. Mark users from the “Users search” window, and click the ‘Select’ icon. The selected users are added

3. Select a specific permission, and set its value as explained here:

BORROW_LOWWATER:

Sets the minimal number of BORROW licenses that cannot be borrowed, i.e: the minimal number of licenses that need to remain as Network licenses. For example, if FEATURE has a count of 10, borrowing is enabled in the application, and BORROW_LOWWATER = 7 then only 3 licenses may be borrowed. This option is used for licenses held in license files.

LINGER:

A lingering license stays checked out for a specified period of time beyond its checkin or FlexEnabled application exit, whichever comes first. This configuration enables users to extend the linger time for a feature beyond its check in.

Note:

  • The software publisher sets a minimum linger value. If a value smaller than the minimum is configured, the minimum value is used.

  • The linger time may be configured by the software publisher in the FlexEnabled application. When this is the case, the longer linger time is applied.

MAX_BORROW_HOURS:

Change the maximum borrow period for a specific feature. The new configured period value must be less than that in the license file. This option is used for licenses held in license files.

MAX_OVERDRAFT:

The overdraft policy allows a software publisher to specify a number of additional licenses which users are allowed to use, in addition to the licenses they have purchased. This allows your users to not be denied service when in a “temporary overdraft” state. The MAX_OVERDRAFT parameter Limits the overdraft usage to less than the amount specified in the license file.

TIMEOUT:

Specify the idle timeout for a feature, after which an inactive license is reclaimed. The software publisher sets a minimum value. If a smaller value is set – it is ignored, and the publisher’s minimum value is used.

SETTING PERMISSIONS ON SPECIFIC FEATURES

Some Option permissions may be applied according to the following categories: Users, Groups, Hosts, Host Groups and IPs as shown below.

These configurations include

  • Reserved: Reserve licenses for a User / User group / Host / Host group of users/hosts.

  • Included: Allow a user to use a feature.

  • Excluded: Deny a user access to a feature.

  • Borrow Included: Allow a user to borrow licenses.

  • Borrow Excluded: Deny a user the ability to borrow licenses.

  • Max: Limit usage for a particular feature/group—prioritizes usage among users.

ALLOW OR DENY THE ENTIRE VENDOR’S FEATURE SET

It is possible to Allow or Deny a category of users (user\group\host\host group\IP) the entire set of features that a specific vendor daemon serves. In order to do that:

  1. On the EasyAdmin web application window click ‘Start’ →  ‘Option Files’ → “All Features”.  The “All Features …” window appears.

1. Add a Category of users (User \ Group \ Host \ Host Groups \ IP)

2. Check the “Include All” or “Exclude All” radio button;

  • Include All: Allow a user to use all features served by this vendor daemon.

  • Exclude All: Deny a user access to all features served by this vendor daemon.

3.Click ‘Save’.

SAVING THE OPTION FILE ON THE LICENSE SERVER

Saving the changes made to the Option file back to the License Server is done as follows:

1. On the EasyAdmin web application window click “Start” → “Opt. File Admin.”

2. Select the specific Option File, and click “Set”.

3. Select “Save back to server”.

The Option file update mechanism

  • The OpenLM Server writes this request to a table on OpenLM db and waits.

  • Every 10-15 seconds the OpenLM Server checks that table for any new messages for sending to the OpenLM Broker.

  • If such messages are available, the OpenLM Server sends the option file back to the broker.

  • The OpenLM Broker receives the new option file. It creates a copy of the old option file and replaces it with the new one.

  • After that, the broker issues a re-read command to the license manager. If the re-read was successful, the process is complete.

This procedure refers to user permissions. The same permissions are applicable to Groups( a groups of users ), Hosts, Host Groups (defines a group of hosts) and IPs.

 

Appendix A: Users and Groups

There are two methods of introducing new users and user groups to the OpenLM system. One is through the EasyAdmin web application, and the other is by synchronizing with a company’s Active directory. Both these methods are elaborated below.

SYNCHRONIZING USERS AND USER GROUPS WITH AN ACTIVE DIRECTORY (AD)

The best way to add users and groups is to synchronize them with the AD. OpenLM supports such synchronization:

1. Open “OpenLM Server Configuration” (Start →  Programs → OpenLM →  OpenLM server configuration )

2. Select the “Active Directory” tab.

3. Enter The following information in order to connect to the AD and synchronize users:

3a. Domain name: The Active Directory domain name is the full Domain Name System (DNS) name of the domain.

3b. Active directory user name and password, in the respective fields.

4. From the LDAP Server drop-down menu select “ActiveDirectory”.

5. Check the “Synchronize users” checkbox.

Another method for adding users and groups makes use of the EasyAdmin “Users & Permissions” menu:

INTRODUCING A NEW USER

On The EasyAdmin window, Click Start → Users&permissions → Users. The User details window appears.

Insert the required data, Check the ‘Enabled’ box,  and click the ‘Save’ button.

INTRODUCING A NEW USER GROUP

  • In The EasyAdmin web application, Click “Start” → “Users & Permissions” → “Groups”. The Groups window appears.

  • Click the green “Add Group” icon in order to create a new group. Enter the new group name (e.g.: my_new_group), and click “OK”.

 

  • On the “Groups” window, select the newly created group (e.g.: my_new_group), and click the “Members” icon to add new members to the group. The “Users in my_new_group” window appears.

  • Click the green ‘Add’ button. The “Users search” window appears. Mark and select users from the “Users search” window to add to my_new_group.

Appendix B: Adding an IP

What is an IP?

An Internet Protocol (IP) address is a numerical label assigned to each device (e.g., computer, printer) participating in a computer network that uses the Internet Protocol for communication. An IP address serves two principal functions: Host or Network interface identification and location addressing.

Controlling the license usage of a specific computer is made possible by the “IPs” tab on the “Features of Option File” window. It is also possible to control the license usage of an IP range of computers. For example, typing in the IP:  123.123.123.* causes the feature configurations done in the “Features of Option File” window to be implemented on all user IPs in the range of 123.123.123.0 through 123.123.123.255.


Adding a specific IP:

1. On the EasyAdmin web application window click ‘Start’ →  ‘Option Files’ → ‘IPs’

2. Click The green “Add” button. “Add Ip” window will pop.

3. In the text box enter the Ip address you want to add.

Add a range of IPs

1. On the EasyAdmin web application window click ‘Start’ →  ‘Option Files’ → ‘IPs’

2. Click The green “Add” button. “Add Ip” window will pop.

3. In the text box enter the Ip range you want to add (as explained above).

 

Appendix C: Adding a Host Group

About Host Groups

Custom groups of virtual machine hosts may also be created, for grouping of hosts and their virtual machines in meaningful ways. For example, you may create a host group for every branch office in your organization. You can also use host groups to set aside resources on hosts in the host group for the use of the host operating system.

1. On the EasyAdmin web application window click “Start” →  “Option Files” → “Host Groups”. The “Host Groups” window appears.

2. Click the green ‘+’ sign, and add a group (e.g.: my_host_group1).

3. Select the newly added group, and click the “Members” icon. The “Memebers of my_host_group1” window opens (see image).

4. Select the computers that are required for grouping, and click the green “Select” button. The new Host group is ready for use.

Revision

Revision 1.3 (Revised)

Authors: Mira, Orik, Chen

May 20, 2013.