...

1. Obtain a Permanent Floating License:  Provide Intercax with details of your license deployment (ie: count, server name, ports, etc.) to obtain license file(s) for the server
2. License Server Setup:  Install and setup a floating license server with a floating license file on a single machine
3. Client License File Creation:  Create and distribute to all client machines a client license file that points to the floating license server

...

Pre-

...

Reqs

Floating License Requirements

A single floating license file will be issued for each product (e.g. Syndeia). This license file will be located on the license server. The following information is required from you (end user organization) for us to generate a floating license file (* = required).  

1. Helpdesk Account*:  If you are a new customer, have your Technical Point of Contact (PoC) for the license request create a new account here.  If you already have an account, login.  

Once an account is created, create a Helpdesk License Request ticket with the below information in the relevant fields and we will process the request accordingly.  

1. Technical Point-of-Contact (PoC) Name*, Email* (and phone #, if available):  Technical Point-of-Contact (PoC) Name, Email (and phone #, if available), ex:  John Doe, johndoe-model@mega.org, 555-123-4567
2. Organization Name* & Group (if you are a large organization):  Name of your organization + group name (if you are a large organization), ex:  MegaOrg, Modeling-Division (specify this in the Organization field)
3. Contract Id (if you are an existing customer with a paid/permanent license AND wish to update/augment that license)*:  if you are an existing customer with a paid/permanent license and you wish to update/augment that license, specify your contract id in the Description field, ex:  MEGAORG-MODELING-20191118.  If you are an existing customer and do not wish to replace/augment your existing license(s), ie: have it be separate or for a different project, please specify that instead (a new contract_id will be generated for this).  
4. Features or other options*: The license will give access to the features and other options requested here, ie: one or more of CREO, DOORS, JAMA, JIRA, GitHub, MySQL, NX, SIMULINK, TC, WC, etc. (note, license quantities for a given license currently can only be per product VS per feature, ex:  12 x (CREO, DOORS, JAMA) VS 1 CREO, 12 DOORS, 4 JAMA).  If you are an existing customer please also specify whether this license request will replace/augment your existing license(s) or be separate from it/for a different project.  
5. Server MAC Address*:  Physical Ethernet MAC address of the machine where the server will run. The license server and accompanying license will be available (locked) only to this machine.
6. Total # of Floating Licenses*:  Number of floating licenses needed. The number of license available for use at a given time.
7. Server Platform*:  Platform where the license server will run (Win 32, Win 64, Linux 64, or Mac 64). This will determine which platform of the license server software to make available.
8. Max # Offline Licenses (optional, default = total # of licenses):  Maximum number of licenses allowed to be borrowed (roam) – must be less than or equal to the number of floating licenses. This allows users to have access to the license when not connected to the license server network. If a license is borrowed, it remains checked out from the licenser server until it is returned.
9. Offline License Lease Length (optional, default = 30 days):  Maximum number of days allowed to borrow (roam) a license.

Provide all the information above in a Helpdesk License Request ticket and we will process the request accordingly.  

...

License Server Setup Requirements

The following are required to setup a floating license server & the client (pointer) license file (* = required):  

...