Hexagon Geospatial
MENU

Licensing Knowledge Base

Easily license Hexagon Geospatial desktop products using the License Manager .
Showing results for 
Search instead for 
Do you mean 

How to install Geospatial Licensing Administrator 2018 and activate a concurrent 2018 license?

by jmorris on ‎08-09-2018 11:44 AM - edited 2 weeks ago by mvardovs (1,389 Views)

Question

How do I install Geospatial Licensing Administrator 2018 and activate a concurrent 2018 Activation ID license?

Answer

The Hexagon Geospatial version 2018 products use a new licensing methodology that no longer requires license (.lic) files.  The new licensing method uses an Activation ID that is claimed from the Licensing Portal for the application that you wish to license and then the license is activated (in the case of concurrent licenses) via the 'Geospatial License Administrator 2018' software on the concurrent license server machine.

 

To use version 2018 Activation ID based licenses you must be running a license service that was created using the 'Geospatial Licensing Administrator 2018' software. This is required because a license service created with previous versions of 'Geospatial Licensing Administrator' (prior to 2018) does not support Activation IDs.

 

Once you have created a license service using 'Geospatial Licensing Administrator 2018' and activated a 2018 license, that license service can then serve licenses for client systems running previous supported versions of the applications as well.  For example, a license service with a 2018 GeoMedia license can serve client machines running GeoMedia versions 2014, 2015, 2016 and 2018 (16.5).  Similarly, a license service with a 2018 IMAGINE license can serve client machines running IMAGINE versions back to 2013.

 

To use the version 2018 Activation ID that you claimed from the Licensing Portal you will need to perform the following steps to install or update the license service and activate the 2018 license.

 

Note that if you have a previous version of Geospatial Licensing Administrator installed on the machine and/or an existing Intergraph License Service running on the machine you do not need to remove the Hexagon Geospatial License Administrator software or stop the existing Intergraph License Service before performing these steps.  If there is an earlier version of the Geospatial License Administrator software installed and/or an existing Intergraph License Service running on the machine the installer for Geospatial Licensing Administrator 2018 will automatically uninstall the previous version of Geospatial Licensing Administrator and stop/remove the existing Intergraph License Service before creating/starting the new license service.

 

  1. If you have not already done so, download version 16.5.0.16 of the 'Geospatial License Administrator 2018' utility from this link...

https://download.hexagongeospatial.com/downloads/other/geospatial-license-administrator-2018

 

Note: If you have downloaded/installed the 'Geospatial License Administrator 2018' software previously, make sure that it is not a version prior to 16.5.0.16.  If you do have an earlier version installed, then you will want to make sure that you install version 16.5.0.16 since it contains several fixes to resolve problems in prior 'Geospatial License Administrator 2018' builds.

 

Once you have downloaded and unzipped the 'Geospatial License Administrator 2018' software, install it on the machine that you want to use as the concurrent license server by double-clicking the setup.vbs file from the root folder of the installation files.

 

Running 'setup.vbs' will automatically check for the required .NET Framework software and install it if it does not already exist on the machine.

 

  1. Run the 'Geospatial License Administrator 2018' utility.

 

  1. Select Licenses > Activate Licenses to open the Activate Licenses dialog.

 

  1. From this dialog click the Add button to open the 'Add Activation ID' dialog.

 

  1. Then copy the Activation ID that you obtained from the Licensing Portal into the field and click OK.

 

The Activation ID for a concurrent license will be prefixed with CC and will look something like the following ‘CC_cf32-f597-8a4d-4fc4-a034-161c-f7b7-2e51’.

 

If you have other products that you want to host on the same license server you can repeat this step for each product by clicking Add, copying the respective Activation ID from the License Portal and pasting the value into the Activation ID field, then clicking OK. *

 

  1. Once you have one or more Activation IDs showing in the grid (within the Activation ID’ column), click the Activate button at the bottom of the dialog to activate the licenses.

  

  1. Now click the Close button on the Activate Licenses dialog. The license service should now be active and the License Sources list should show the name of the license server for the concurrent license service required by the 2018 applications (with the list of licensed products that were activated shown below the server name).

 

  1. When each client application is started, and the dialog is displayed asking for the Concurrent License Server, enter the node name of the license server (that was created in step 6) into the Concurrent License Server field.

 

  • Note that there is also an option to Activate all 2018 licenses at once via the use of the Browse File option at the bottom of the Activate Licenses dialog.  To use the Browse File option, you must have first selected all desired 2018 licenses on the Licensing Portal by placing a check in the box to the left of each product and then selecting the Email option from the ‘wrench’ icon to the left of the Version field.  This will send a .xml file containing all selected 2018 licenses to you that you can then enter into the ‘Import Activation' field from the License Administrator when you click the Browse File option.

Details of this workflow can be found in the Knowledge Base article linked below with the title...

 

How to Activate concurrent 2018 Activation ID licenses using an ActivationIDs.xml file?

 

 

 

Comments
by LST
on ‎10-08-2018 11:32 PM

Hi team

 

How about failover architectures with three license servers? 

 

We have a customer with more than 100 licenses which are distributed on a failover system where two servers are running constantly. In case of a break-down of one of the first two servers the third server will serve as a backup. At the moment we got a .LIC file with the accoring informations: Three Server IP Adresses, which were also specifyed in the file "INGRTS_LICENSE_PATH" C:\ProgramData\Intergraph\Licensing\INGRTS_LICENSE_PATH.  Is thsi still possible with the version 16.5? If not, how should we proceed?

 

Thank you.

 

Regards,

Laura 

by jmorris
on ‎10-10-2018 02:28 PM

To use three server redundancy for your license service with version 16.5 you would need use an 'offline' license which is a traditional certificate based license (.lic) file.  You can file a Licensing Ticket to request conversion of your licenses to 'offline'.

by emarcano
on ‎10-11-2018 07:21 AM

is this new license manager compatible with Windows Server 2016?

 

Thanks

 

eugenio

by sbent
on ‎10-11-2018 09:34 AM

Hi Eugenio,

 

Yes, the Geospatial License Administrator 2018 is supported on Windows Server 2016.

 

Regards,

 

Stephen Bent

Hexagon Geospatial Support

by emarcano
on ‎10-18-2018 07:05 AM

I had a terrible time trying to get the license manager to work through a firewalled system.  I followed the instructions given elsewhere and opened the ports 27000-27009 but nothing work.

 

Our system is a Vmware virtual server behind a Palo Alto firewall.  The machine is now running Windows server 2016. 

 

We opened both, the Windows and the server farm's firewall ports and nothing worked, until we noticed that the workstations were pinging the server whenever we launched the ERDAS Imagine software in the workstation (without finding any license).  When we opened the ping port, now license manager in the workstation listed the server machine as "Online", but still it wouldn't license.

 

Then we noticed that the workstations were also sending signals to port 64706 to the license server, but those were being blocked by the firewall.  As soon as we opened that port, everything worked beautifully.

 

I don't know where/how to report these findings, but I think it should be included in your instructions about licensing and firewall. 

 

Hope this can help somebody.

 

Eugenio

 

Contributors