0% found this document useful (0 votes)

254 views105 pages

Foundry Licensing Tools User Guide

Uploaded by

Wilmer Monsalvo

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

254 views105 pages

Foundry Licensing Tools User Guide

Uploaded by

Wilmer Monsalvo

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 105

Foundry Licensing Tools

User Guide
VERSION 7.1v1
FLT 7.1v1 User Guide. Copyright © 2016 The Foundry Visionmongers Ltd. All Rights Reserved. Use of this User Guide and the software is
subject to an End User License Agreement (the "EULA"), the terms of which are incorporated herein by reference. This User Guide and
software may be used or copied only in accordance with the terms of the EULA. This User Guide, the software and all intellectual
property rights relating thereto are and shall remain the sole property of The Foundry Visionmongers Ltd. ("The Foundry") and/or The
Foundry's licensors.

The EULA can be read in the Appendices.

The Foundry assumes no responsibility or liability for any errors or inaccuracies that may appear in this User Guide and this User Guide
is subject to change without notice. The content of this User Guide is furnished for informational use only. No part of this manual may
be reproduced, stored in a retrieval system, or transmitted in any form without the prior written permission of The Foundry.

In addition to those names set forth on this page, the names of other actual companies and products mentioned in this User Guide
(including, but not limited to, those set forth below) may be the trademarks or service marks, or registered trademarks or service marks,
of their respective owners in the United States and/or other countries. No association with any company or product is intended or
inferred by the mention of its name in this User Guide.

Linux ® is a registered trademark of Linus Torvalds.

Windows ® is the registered trademark of Microsoft Corporation.

Mac, Mac OS X, Snow Leopard, Lion, Mountain Lion, Mavericks, Shake, Final Cut Pro and QuickTime are trademarks of Apple, Inc.,
registered in the U.S. and other countries.

The Foundry
5 Golden Square
London
W1F 9HT
UK

Rev: Wednesday, July 13, 2016

Contents
Quick Start
About Licenses 6

Free Trial Licenses 7

Activation Keys 7
Purchasing an Activation Key 7
How to Use Your Activation Key 8

Node Locked and Floating Licenses 9

Windows 9
Mac OS X 12
Linux 14

More Information 16

Licensing on a Single Machine

About Licenses 17

Activation Keys 18
Purchasing an Activation Key 18
How to Use Your Activation Key 19

Node Locked Licenses 21

Purchasing a Node Locked License 21
Installing a Node Locked License 23

License Administration 27
Where are the License Keys and Log Files? 27
Moving the License Keys and Log Files 28
Appending to an Existing License 28

More Information 29

Licensing over a Network

Notation 30

About Floating Licenses 30

Purchasing a Floating License 31

Displaying Your System ID 31

Installing a Floating License 33

Windows 33
Mac OS X 38
Linux 42

License Administration 45
Where are the FLEXlm and RLM Files? 46
Moving the FLEXlm and RLM Files 46
When is a License Taken or Dropped? 49
Capping Licenses 52
Appending to an Existing License 53
The <server_name> Variable 55
Replace Licenses 55
Which RLM Port? 56

Managing the License Server 56

Starting the License Server 56
Stopping the License Server 57
Viewing the License Server Log 57
RLM Web Server 58
Useful Commands for System Administrators 60

Removing FLT 61
On Windows 61
On Mac OS X 62
On Linux 62

More Information 62

Troubleshooting Licenses
Firewalls 63
Windows 63
Mac OS X 70

Windows Hidden Files 72

FLU Reporting More Than One System ID 72

Node Locked and Client Licenses 73

Accessing the RLM Web Server on Mac OS X 73

Contacting Support 73
Using the Diagnostics Tool in GUI Mode 74
Using the Diagnostics Tool in Command Line Mode 74

Appendix A: Release Notes

FLT 7.1v1 75

FLT 7.0v5 77

FLT 7.0v4 78

FLT 7.0v3 78
FLT 7.0v2 79

FLT 7.0v1 81

FLT 6.0v4 82

FLT 6.0v3 83

FLT 6.0v2 84

FLT 6.0v1 84

Appendix B: License Syntax

Node Locked License Syntax 86
FLEXlm 86
RLM 87

Floating License Syntax 87

FLEXlm 87
RLM 88

Client License Syntax 89

FLEXlm 89
RLM 89

Appendix C: FLT Variables

Environment Variables FLT Recognizes 90

Setting Environment Variables 91

Windows 91
Mac OS X 92
Linux 93

Appendix D: EULA
End User License Agreement (EULA) 94
Quick Start
In a hurry? No time to read the whole user guide? We understand. Read this section—it'll tell you how
to use your activation key or install your license.

The Foundry Licensing Tools’ default settings do not support RLM licensing on virtual machines (VMs). If you have
any questions regarding licensing on VMs, please visit supportportal.thefoundry.co.uk for assistance.

Alternatively, if you want to know more about licensing, see Licensing on a Single Machine or Licensing over a
Network.

About Licenses
All The Foundry products built between October 2005 and October 2010 were licensed using FLEXlm. The Foundry is
currently migrating its products to activation key-based licensing and has chosen to use RLM for the back end
licensing.

To find out whether your product uses FLEXlm or RLM licensing, please refer to the product’s documentation.

To license one of our products, you need one of the following:

• Free trial license. This enables one of our products to work on one particular machine for 15 days. See Free Trial
Licenses.
• An activation key. An activation key can be used as an automated path to a node locked license, allowing you to
use The Foundry products on a single machine. They look something like this:
mari-0101-77d3-99bd-a977-93e9-8035
See Activation Keys.
• A node locked license. This enables one of our products to work on one particular machine. It is locked to a
unique number on that machine.
• A floating license. This enables one of our products to work on any networked client machine. The floating
license should be put on the server and is locked to a unique number on that server.
See Node Locked and Floating Licenses.

If you want to know what a license looks like, have a look at Appendix B: License Syntax for a description of the file
syntax.

6
QUICK START | FREE TRIAL LICENSES

Free Trial Licenses

If you simply want to obtain a free trial license for 15 days, you can:
• launch your product and, if a Licensing dialog appears, click the Try... button, or

• if your product doesn’t have a Licensing dialog, you may be able to obtain a trial license from our website at
www.thefoundry.co.uk. On the product page, click Free 15 day trial and follow the instructions.

You can only install a trial license once for each product on a single machine.

Activation Keys
This section tells you how to use an activation key with your product.

Purchasing an Activation Key

If you've been supplied with something that looks similar to this:
mari-0101-3733-eeda-8376-df83-7235

you have an activation key and you can activate your product.

7
QUICK START | ACTIVATION KEYS

If your product uses activation key-based licensing but you don’t yet have an activation key, you can purchase one
by:
• using the Buy... button on the Licensing dialog when you first launch your product,

• going to our web site at www.thefoundry.co.uk,

• e-mailing us at sales@thefoundry.co.uk,
• phoning our London office at +44 20 7479 4350 or our Los Angeles office at +1 (310) 399 4555.

Once you have an activation key, proceed to How to Use Your Activation Key.

How to Use Your Activation Key

If you are using a product that has a Licensing dialog (such as Mari or Hiero) and currently have no license, or are
running a temporary license, your product prompts you at start-up to enter your activation key into the Licensing
dialog. This step is skipped if:
• you’ve already activated a permanent license, or
• you’re trying to activate a product that doesn’t have a Licensing dialog (for example, a set of plug-ins). If this is the
case, go to http://www.thefoundry.co.uk/support/licensing/activate-product/, enter your activation key into the
field provided, and follow the instructions on screen.
If you’re trying to activate a product using the Licensing dialog, do the following:
1. Launch your product.
The Licensing dialog displays.

8
QUICK START | NODE LOCKED AND FLOATING LICENSES

2. Click Install License.

3. Click Activation Key / License Text.
4. Enter your activation key and click Install.
Your product connects to our activation server, retrieves the correct license key for your system, and installs it.
Your product launches when the download and installation are complete.

Node Locked and Floating Licenses

This section tells you how to obtain and install node locked and floating licenses for your product.

The instructions for installing node locked and floating licenses depend on your operating system, so before you do
anything else choose one of the following:
• To install a license on Windows, see Windows.
• To install a license on Mac OS X, see Mac OS X.
• To install a license on Linux, see Linux.

Windows
This section tells you how to get your license working on Windows.

Purchasing a License
You can purchase license keys by:
• going to our web site at www.thefoundry.co.uk,
• e-mailing us at sales@thefoundry.co.uk,
• phoning our London office at +44 20 7479 4350 or our Los Angeles office at +1 (310) 399 4555.

To generate a license key, we need to know your System ID. The System ID returns a unique number for your
computer. We lock our license keys to the System ID.

For floating licenses, we need to know the System ID of the machine that serves the licenses across the network.

To display your System ID, download the Foundry License Utility (FLU) from
www.thefoundry.co.uk/support/licensing/ and run it. The System ID is displayed at the bottom of the window, as
highlighted.

9
QUICK START | NODE LOCKED AND FLOATING LICENSES

NOTE: In most cases, our licensing tools find the RLM System ID, check that FLEXlm accepts the same ID,
and then display that ID. However, on rare occasions, you can have two System IDs reported. If this is the
case, both System IDs are displayed, like this:

R00ffb79aefc9:X00ffb79aefa9

When purchasing a license, you should send us the entire string with both IDs.

Installing a License Key

Once a license has been generated for you, we e-mail you a zip file containing the license key and instructions on how
to obtain the correct version of the Foundry License Utility (FLU). To check and install the license key, install the
Windows FLU and drag the license file onto the FLU application.

If you installed a node locked license key, you’re done.

When you install a floating license key, the license server address is displayed on screen:
<number>@<license server name>

10
QUICK START | NODE LOCKED AND FLOATING LICENSES

You should make a note of the address, as you’ll need it to activate the client machines. Then, proceed to Installing
the Foundry Licensing Tools (FLT) on the License Server.

Installing the Foundry Licensing Tools (FLT) on the License Server

Having installed a floating license, you need to install some additional software (FLT) to manage the licenses on your
network. Then you need to tell the client machines where to find the licenses.
1. Download FLT_7.1v1_win-x86-release-64.exe from our web site (www.thefoundry.co.uk/support/licensing/)
and install it on the Windows computer that you want to serve the licenses across the network.
The license server starts automatically after installation (and whenever you restart the machine).
2. To check the server status, click Start > All Programs > The Foundry > FLT 7.1v1 > Foundry License Utility,
view the FLEXlm Server or RLM Server tab, and click Refresh Log.
3. If the license server fails to start, navigate to Control Panel > Systems and Security > Administrative Tools
> Services. Then, select the appropriate service:
• For FLEXlm: Foundry FLEXlm Server
• For RLM: Foundry License Server
Click Start and check the server status again.

NOTE: If you have a firewall on your license server, this blocks all requests for licenses from your clients.
So all that good work you’ve done in setting up your Foundry License Server will be for nothing unless you
fix this. See Firewalls.

4. Proceed to Telling the Client Machines Where to Find the Licenses.

Telling the Client Machines Where to Find the Licenses

To point your product at the license server, do one of the following:
• If your product displays a Licensing dialog when you launch it, click Install License and then Use Server. Type
<number>@<server name> (for example, 4101@red) and click Install. Your client retrieves a license from the
License Server and launches.
• Download the Foundry License Utility (FLU) from our website (www.thefoundry.co.uk/support/licensing/) and
launch it. Make sure you are viewing the License Install tab and copy and paste in an RLM server line:
HOST <server name> any <port>
For example: HOST red any 4101
This creates and installs both a FLEXlm and RLM client license.

Repeat this process for each machine you wish to have access to licenses on the server.

11
QUICK START | NODE LOCKED AND FLOATING LICENSES

Mac OS X
This section tells you how to get your license working on Mac OS X.

To generate a license key, we need to know your System ID. The System ID returns a unique number for your
computer. We lock our license keys to the System ID.

For floating licenses, we need to know the System ID of the machine that serves the licenses across the network.

To display your System ID, download the Foundry License Utility (FLU) from
www.thefoundry.co.uk/support/licensing/ and run it. The System ID is displayed at the bottom of the window, as
highlighted.

R00ffb79aefc9:X00ffb79aefa9

When purchasing a license, you should send us the entire string with both IDs.

12
QUICK START | NODE LOCKED AND FLOATING LICENSES

Installing a License Key

Once a license has been generated for you, we e-mail you a zip file containing the license key and instructions on how
to obtain the correct version of the Foundry License Utility (FLU). To check and install the license key, install the Mac
OS X FLU and drag the license file onto the FLU application.

If you installed a node locked license key, you’re done.

When you install a floating license key, the license server address is displayed on screen:
<number>@<license server name>

You should make a note of the address, as you’ll need it to activate the client machines. Then, proceed to Installing
the Foundry Licensing Tools (FLT) on the License Server.

Installing the Foundry Licensing Tools (FLT) on the License Server

Telling the Client Machines Where to Find the Licenses

To point your product at the license server, do one of the following:

13
QUICK START | NODE LOCKED AND FLOATING LICENSES

• If your product displays a Licensing dialog when you launch it, click Install License and then Use Server. Type
<number>@<server name> (for example, 4101@red) and click Install. Your client retrieves a license from the
License Server and launches.
• Download the Foundry License Utility (FLU) from our website (www.thefoundry.co.uk/support/licensing/) and
launch it. Make sure you are viewing the License Install tab and copy and paste in an RLM server line:
HOST <server name> any <port>
For example: HOST red any 4101
This creates and installs both a FLEXlm and RLM client license.

Repeat this process for each machine you wish to have access to licenses on the server.

Linux
This section tells you how to get your license working on Linux.

To generate a license key, we need to know your System ID. The System ID returns a unique number for your
computer. We lock our license keys to the System ID.

For floating licenses, we need to know the System ID of the machine that serves the licenses across the network.

To display your System ID, download the Foundry License Utility (FLU) from
www.thefoundry.co.uk/support/licensing/ and run it from the command line:
<download location>/FoundryLicenseUtility -i

NOTE: The <download location> refers to the location where you saved the Foundry Licensing Utility.

R00ffb79aefc9:X00ffb79aefa9

When purchasing a license, you should send us the entire string with both IDs.

14
QUICK START | NODE LOCKED AND FLOATING LICENSES

Installing a License Key

1. Once a license has been generated for you, we e-mail you a .tgz file containing the license key and instructions
on how to obtain the correct version of the Foundry License Utility (FLU). Gunzip or untar the file and save the
FLU and your license key to a folder of your choice.
2. Navigate to the location of the FLU_7.1v1_linux-x86-release-64.tgz file.
3. Type the following commands to extract and install the FLU. Note that you need to replace [my license] with
the location of your license key.
tar xvzf FLU_7.1v1_linux-x86-release-64.tgz
cd FLU_7.1v1_linux-x86-release-64
./FoundryLicenseUtility -l [my license]
For example, if you saved your license key to /tmp/foundry.lic, the last line should be:
./FoundryLicenseUtility -l /tmp/foundry.lic
This checks the license key and copies it to the correct directory.
4. If you installed a node locked license key, you’re done.
If you installed a floating license key, the license server address is displayed on screen:
<number>@<license server name>
You should make a note of the address, as you’ll need it to activate the client machines. Then, proceed to
Installing the Foundry Licensing Tools (FLT) on the License Server.

Installing the Foundry Licensing Tools (FLT) on the License Server

Having installed a floating license, you need to install some additional software (FLT) to manage the licenses on your
network. Then you need to tell the client machines where to find the licenses.
1. Download FLT_7.1v1_linux-x86-release-64.tgz from our web site (www.thefoundry.co.uk/support/licensing/) on
the Linux machine that you want to serve these licenses across the network and save it to /tmp.
2. Open a shell and, using root or admin permissions, type these commands to extract and install the Foundry
Licensing Tools 7.1v1.
cd /tmp
tar xvzf FLT_7.1v1_linux-x86-release-64.tgz
cd FLT_7.1v1_linux-x86-release-64
./install.sh
The license server starts automatically after installation (and whenever you restart the machine).
3. To check the server status, navigate to /usr/local/foundry/LicensingTools7.1 and enter:
./FoundryLicenseUtility -s status
This reports the status of both FLEXlm and RLM servers. If you only want to view one or the other, use one of
the following commands instead:
./FoundryLicenseUtility -s status -t FLEXlm
./FoundryLicenseUtility -s status -t RLM

15
QUICK START | MORE INFORMATION

4. Proceed to Telling the Client Machines Where to Find the Licenses.

Telling the Client Machines Where to Find the Licenses

To point your product at the license server, do one of the following:
• If your product displays a Licensing dialog when you launch it, click Install License and then Use Server. Type
<number>@<server name> (for example, 4101@red) and click Install. Your client retrieves a license from the
License Server and launches.
• Download the Foundry License Utility (FLU) from our website (www.thefoundry.co.uk/support/licensing/). Gunzip
or untar the file and save the FLU to a folder of your choice. Then, launch a shell and navigate to the location of the
FLU_7.1v1_linux-x86-release-64.tgz file. Type the following commands:
tar xvzf FLU_7.1v1_linux-x86-release-64.tgz
cd FLU_7.1v1_linux-x86-release-64
./FoundryLicenseUtility -c <port>@<server name>
For example, the last line might be:
./FoundryLicenseUtility -c 4101@red
This creates and installs both a FLEXlm and RLM client license.

Repeat this process for each machine you wish to have access to licenses on the server.

More Information
For a complete explanation of licenses, license syntax, alternative license directories, useful server commands, and
much more, please read Licensing on a Single Machine or Licensing over a Network.

To troubleshoot licenses, refer to Troubleshooting Licenses.

16
Licensing on a Single Machine
This chapter tells you how to license your product on a single machine. If you want to license one of
our products over a network instead, please read Licensing over a Network.

NOTE: The Foundry Licensing Tools’ default settings do not support RLM licensing on virtual machines
(VMs). If you have any questions regarding licensing on VMs, please visit supportportal.thefoundry.co.uk
for assistance.

To find out whether your product uses FLEXlm or RLM licensing, please refer to the product’s documentation.

To license one of our products on a single machine, you need either:

• An activation key. An activation key can be used as an automated path to a node locked license. It is a string of
characters that represents your entitlement to a product license. You can use activation keys over the internet to
create automatically installed full license keys, on a machine of your choice, using our activation server.
Activation keys are a flexible approach to selling licenses, requiring no System ID at the point of purchase, though
activation can only occur once per activation key.
They look something like this:
mari-0101-77d3-99bd-a977-93e9-8035
For information on how to license one of our products using an activation key, see Activation Keys.
• A node locked license. This is sometimes called an uncounted license. It enables one of our products to work on
one particular machine. It is locked to a unique number on that machine. This license key does not work on a
different machine and if you need it to, you’ll have to transfer your license. Like activation keys, node locked
licenses do not require additional licensing software to be installed.
Node locked FLEXlm licenses look like this:
INCREMENT furnace_ofx_i foundry 4.0 05-jul-2011 \
uncounted HOSTID=000ea641d7a1 ISSUED=8-feb-2011 \
SIGN="03C7 5A34 BDE8 D421 6C2B 8111 8151 972A \
14E2 C143 4C00 741F 730D\ 784A D392 B1D9 9C3F \

17
LICENSING ON A SINGLE MACHINE | ACTIVATION KEYS

03FC DB2A E432 5EA7"

Node locked RLM licenses look like this:
LICENSE foundry mari_i 2011.1231 permanent uncounted share=h start=3-oct-2011
issued=3-oct-2011 _ck=fa062a5e5a
sig="60P0451P8JTKNGTUC2TR605Y300BQ63CKYJNYTG22GXS0AVA0DSFGSUJ8P8HJ1C5MX86UNS54M"
For further information about the structure of the license key, see Node Locked License Syntax.
For information on how to license one of our products using a node locked license, see Node Locked Licenses.

TIP: We also provide free 15-day trial licenses. See Free Trial Licenses.

Activation Keys
This section tells you how to use an activation key with your product.

Purchasing an Activation Key

If you've been supplied with something that looks similar to this:
mari-0101-3733-eeda-8376-df83-7235

you have an activation key and you can activate your product.

18
LICENSING ON A SINGLE MACHINE | ACTIVATION KEYS

• going to our web site at www.thefoundry.co.uk,

• e-mailing us at sales@thefoundry.co.uk,
• phoning our London office at +44 20 7479 4350 or our Los Angeles office at +1 (310) 399 4555.

Once you have an activation key, proceed to How to Use Your Activation Key.

How to Use Your Activation Key

If you currently have no license, or are running a temporary license, your product prompts you at launch to enter
your activation key into a Licensing dialog. This step is skipped if:
• you’ve already activated a permanent license, or
• you’re trying to activate a product that doesn’t have a Licensing dialog (for example, a set of plug-ins). If this is the
case, go to http://www.thefoundry.co.uk/support/licensing/activate-product/, enter your activation key into the
field provided, and follow the instructions on screen.

If you’re trying to activate a product that does have a Licensing dialog, such as Nuke, do the following:
1. Launch your product.
The Licensing dialog displays.

19
LICENSING ON A SINGLE MACHINE | ACTIVATION KEYS

2. Click Install License to display the available license installation options.

3. Click Activation Key / License Text and then either:
• Enter the Activation Key string in place of Insert Activation Key Here. A license key typically looks
something like this:
nuke-0101-77d3-99bd-a977-93e9-8035
OR
• Copy the license text and paste it over the Copy/Paste license text here string. License text typically looks
something like this:
INCREMENT nuke_i foundry 2013.0929 29-sep-2014 uncounted \
HOSTID=000a957bfde5 ISSUED=29-sep-2012 \
SIGN="00DA 99A9 E744 217E 8AD3 E7AF E289 C0C6 \
6B23 2891 AC01 0F50 E64D 8847 8B22 3A40 2BE9 \
A268 B7C2 4BC0 36AF"
4. Click Install.
Your product connects to our activation server, retrieves the correct license key for your system, and installs it.
Your product launches when the download and installation are complete.

NOTE: If you access the internet through a proxy server, you may be prompted to enter the server name,
port number, username, and password before the product can obtain a license.

20
LICENSING ON A SINGLE MACHINE | NODE LOCKED LICENSES

Node Locked Licenses

This section tells you how to obtain and install node locked licenses for your product.

Purchasing a Node Locked License

You can purchase node locked license keys by:
• going to our web site at www.thefoundry.co.uk,
• e-mailing us at sales@thefoundry.co.uk,
• phoning our London office at +44 20 7479 4350 or our Los Angeles office at +1 (310) 399 4555.

To generate a license key, we need to know your System ID. The System ID (sometimes called Host ID, lmhostid, or
rlmhostid) returns a unique number for your computer. We lock our license keys to the System ID. Just so you know
what a System ID number looks like, here’s an example:
000ea641d7a1

There are a number of ways to display your System ID, depending on your operating system.

R00ffb79aefc9:X00ffb79aefa9

When purchasing a license, you should send us the entire string with both IDs.

On Windows
• Download the Foundry License Utility (FLU) from our website (www.thefoundry.co.uk/support/licensing/) and run
it.
The System ID is displayed at the bottom of the window, as highlighted.

21
LICENSING ON A SINGLE MACHINE | NODE LOCKED LICENSES

• Alternatively, you can run the following from a command prompt:

<download location>/FLU_7.1v1_win-x86-release-64.exe -i

NOTE: The <download location> refers to the location where you saved the Foundry Licensing Utility.

NOTE: If you use the FLU from a command prompt and don’t pass it any arguments (such as -i in the
above example), it launches in GUI mode.

On Mac
• Download the Foundry License Utility (FLU) from our website (www.thefoundry.co.uk/support/licensing/) and run
it.
The System ID is displayed at the bottom of the window, as highlighted.

• Alternatively, you can run the following from the Terminal:

<download location>/FoundryLicenseUtility.app/Contents/MacOS/FoundryLicenseUtility -i

NOTE: The <download location> refers to the location where you saved the Foundry Licensing Utility.

22
LICENSING ON A SINGLE MACHINE | NODE LOCKED LICENSES

On Linux
Download the Foundry License Utility (FLU) from our website (www.thefoundry.co.uk/support/licensing/) and run it
from the command line:
<download location>/FoundryLicenseUtility -i

NOTE: The <download location> refers to the location where you saved the Foundry Licensing Utility.

Installing a Node Locked License

Once you have a node locked license, you can install it using two methods:
• The automated method (recommended). The easiest way to install a node locked license is to use The Foundry
License Utility (FLU).
On Windows and Mac OS X, the FLU can be used both in graphical user interface (GUI) mode and from the
command line.
On Linux, the FLU is a command line tool only.
For more information, see one of the following:
• The Automated Method on Windows
• The Automated Method on Mac OS X
• The Automated Method on Linux
• The manual method. We do not recommend this, but you can install a node locked license key by hand. You just
need the license key in a text file and your product. No other software is required. For more information, see The
Manual Method: Windows, Mac OS X, and Linux.

The Automated Method on Windows

Once a license has been generated for you, we e-mail you a zip file containing the license key and instructions on how
to obtain the correct version of the Foundry License Utility (FLU). To check and install the license key, install the
Windows version of the FLU and do one of the following:
• Drag the license file onto the FLU application;

23
LICENSING ON A SINGLE MACHINE | NODE LOCKED LICENSES

• Or cut and paste the license key text directly into the License Install tab in the FLU application;
• Or if you double-click on the FLU application, it installs any file with a .lic file extension that it finds in the same
directory as the application.

NOTE: If there is an error with any part of the license installation, this is reported in the FLU. You should
also see a Generate Report button, which you can click to write the errors out to a file and then visit
supportportal.thefoundry.co.uk for assistance.
If you are installing several licenses at the same time and only some of them fail validation, you can also
click Continue to complete the installation of the valid licenses.

The above methods are the easiest way to install a license. However, if you prefer, you can also install a license from
a command prompt. To do so:
1. Save the FLU and your license key to a folder of your choice. Note that the license file can be the original .lic file
or the license in a plain text file (as long as the file has a .lic extension).
2. Click Start, type cmd and press Return.
This launches a command prompt.
3. Navigate to the location of the FLU_7.1v1_win-x86-release-64.exe file.
4. Type the following command to install the FLU and the license. Note that you need to replace [my license] with
the location of your license key.
FLU_7.1v1_win-x86-release-64.exe -l[my license]
For example, if you saved your license key to D:\Temp\foundry.lic, the command should be:
FLU_7.1v1_win-x86-release-64.exe -l D:\Temp\foundry.lic
This checks the license key and copies it to the correct directory. You’re done.

NOTE: If you use the FLU from a command prompt and don’t pass it any arguments (such as -l in the
above example), it launches in GUI mode.

24
LICENSING ON A SINGLE MACHINE | NODE LOCKED LICENSES

The Automated Method on Mac OS X

Once a license has been generated for you, we e-mail you a zip file containing the license key and instructions on how
to obtain the correct version of the Foundry License Utility (FLU). To check and install the license key, install the Mac
OS X version of the FLU and do one of the following:
• Drag the license file onto the FLU application;

• Or cut and paste the license key text directly into the License Install tab in the FLU application;
• Or if you double click on the FLU application, it installs any file with a .lic file extension that it finds in the same
directory as the application.

The above methods are the easiest way to install a license. However, if you prefer, you can also install a license from
the command line. To do so:
1. Save the FLU and your license key to a folder of your choice. Note that the license file can be the original .lic file
or the license in a plain text file.
2. Launch Terminal and navigate to the location of the FLU_7.1v1_mac-x86-release-64.zip file.
3. Type the following commands to extract and install the FLU and the license. Note that you need to replace [my
license] with the location of your license key.
unzip FLU_7.1v1_mac-x86-release-64.zip
cd FoundryLicenseUtility.app/Contents/MacOS
./FoundryLicenseUtility -l [my license]
For example, if you saved your license key to /tmp/foundry.lic, the last line should be:
./FoundryLicenseUtility -l /tmp/foundry.lic
This checks the license key and copies it to the correct directory. You’re done.

25
LICENSING ON A SINGLE MACHINE | NODE LOCKED LICENSES

The Automated Method on Linux

Once a license has been generated for you, we e-mail you a .tgz file containing the license key and instructions on
how to obtain the correct version of the Foundry License Utility (FLU).
1. Gunzip or untar the file and save the FLU and your license key to a folder of your choice. Note that the license
file can be the original .lic file or the license in a plain text file.
2. Launch a command line and navigate to the location of the FLU_7.1v1_linux-x86-release-64.tgz file.
3. Type the following commands to extract the FLU and install the license. Note that you need to replace [my
license] with the location of your license key.
tar xvzf FLU_7.1v1_linux-x86-release-64.tgz
cd FLU_7.1v1_linux-x86-release-64
./FoundryLicenseUtility -l [my license]
For example, if you saved your license key to /tmp/foundry.lic, the last line should be:
./FoundryLicenseUtility -l /tmp/foundry.lic
This checks the license key and copies it to the correct directory. You’re done.

NOTE: If there is an error with any part of the license installation, this is reported on the command line.
You should also see a Generate Report button, which you can click to write the errors out to a file and
then visit supportportal.thefoundry.co.uk for assistance.
If you are installing several licenses at the same time and only some of them fail validation, you can
continue to complete the installation of the valid licenses.

The Manual Method: Windows, Mac OS X, and Linux

If you wish, you can install a node locked license key by hand. The license key goes in any plain text file with a .lic file
extension in a specific directory. The name of the file can be anything, but we recommend the following:
foundry.lic

Make sure you don’t save the key in a rich text (.rtf) file as it won’t work. You should also avoid using Word or other
word processing programs to create license files, as these add invisible control characters that trip up the licensing
and make it hard for us to diagnose the fault.

The recommended location for the license file varies depending on the operating system you are using, and is as
follows:

NOTE: There are other directories that can be searched for license files. See Moving the License Keys and
Log Files.

On Windows 7
• If your product uses FLEXlm licensing:

26
LICENSING ON A SINGLE MACHINE | LICENSE ADMINISTRATION

C:\ProgramData\The Foundry\FLEXlm\
• If your product uses RLM licensing:
C:\ProgramData\The Foundry\RLM\

NOTE: The ProgramData folder may be hidden. You can make it visible using the Folder Options in the
Control Panel. See Windows Hidden Files.

On Mac OS X:
• If your product uses FLEXlm licensing:
/Library/Application Support/TheFoundry/FLEXlm/
• If your product uses RLM licensing:
/Library/Application Support/TheFoundry/RLM/

On Linux:
• If your product uses FLEXlm licensing:
/usr/local/foundry/FLEXlm/
• If your product uses RLM licensing:
/usr/local/foundry/RLM/

License Administration
The following section contains details on license management and administration, including license behavior, file
location, and updating licenses.

Where are the License Keys and Log Files?

You can move the FLEXlm and RLM license keys and log files anywhere, but by default they are installed to the
following directories. We’ll refer to these locations as the <data path>.

<data path> on Windows:

C:\ProgramData\The Foundry\FLEXlm\
C:\ProgramData\The Foundry\RLM\

NOTE: The ProgramData folder may be hidden. You can make it visible using the Folder Options in the
Control Panel. See Windows Hidden Files.

<data path> on Mac OS X:

/Library/Application Support/TheFoundry/FLEXlm/
/Library/Application Support/TheFoundry/RLM/

<data path> on Linux:

27
LICENSING ON A SINGLE MACHINE | LICENSE ADMINISTRATION

/usr/local/foundry/FLEXlm/
/usr/local/foundry/RLM/

Moving the License Keys and Log Files

Moving the License File

If you move your node locked license key, you have to set an environment variable to point to the new location.
1. Move your node locked license key to a new location, for example:
/home/licenses/mylicense.lic
2. Now set the appropriate environment variable to point to the new location:
• For FLEXlm licenses, the environment variable is FOUNDRY_LICENSE_FILE.
• For RLM licenses, it is foundry_LICENSE.
For more information on setting environment variables, see Setting Environment Variables.

Moving the Log File

By default, problems with licenses are written to:
<data path>/license.log

You can change the location by setting the appropriate environment variable to the directory of your choice, for
example:
/home/fred/problems.log

For FLEXlm licenses, the environment variable is FOUNDRY_LICENSE_LOG and for RLM licenses, the variable is
foundry_LICENSE_LOG.

For more information on setting environment variables, see Setting Environment Variables.

TIP: A good command to use on very large log files to display the last 30 entries is:

tail -n 30 foundry.log

Note, however, that if you want to send the log file to the Support team, it should be the complete log file
created using the diagnostics tool in the Foundry License Utility (FLU). See Contacting Support.

Appending to an Existing License

You can add a new license to an existing key using two methods:
• Drop the license file onto the Foundry License Utility (FLU). This is the recommended method.

28
LICENSING ON A SINGLE MACHINE | MORE INFORMATION

• Use the command line. This is not recommended for most users. However, you can add a new license key by
editing the foundry.lic text file. Simply copy and paste the license to the end of your existing license file.

More Information
This user guide should cover all the information you need to use FLEXlm or RLM licenses for The Foundry products.
However, it is not meant to be an exhaustive exploration of all the features available with FLEXlm or RLM licensing.
For that, you should:
• see the FLEXnet Licensing End User Guide included in the Foundry Licensing Tools download or go to
www.flexerasoftware.com.
• see the RLM Licensing End User Guide included in the Foundry Licensing Tools download or go to
www.reprisesoftware.com.

Please be aware that advanced RLM features not discussed in this user guide are not supported with RLM licenses
from The Foundry.

29
Licensing over a Network
This chapter tells you how to license your product over a network. If you want to license one of our
products on a single machine instead, please read Licensing on a Single Machine.

Notation
Throughout this chapter, we refer to machines that serve licenses as servers and machines that ask for licenses as
clients.

About Floating Licenses

A floating license running on a server enables one of our products to work on any networked client machine. Floating
licenses are sometimes called counted licenses.

The floating license should be put on the server and is locked to a unique number on that server (see Displaying Your
System ID). Floating licenses on a server require additional software to be installed. This software manages those
licenses on the server, giving licenses out to client stations that want them. The software you need to manage these
licenses is called the Foundry Licensing Tools (FLT), which can be freely downloaded from our web site.

Floating licenses often declare a port number. This is required if you have an internet firewall on your license server
so that you can permit license communication while blocking others. See Firewalls.

A floating FLEXlm license looks like this:

SERVER <server_name> 000EA641D7A1
VENDOR foundry
INCREMENT nuke_i foundry 3.0 05-jul-2012 5 \
ISSUED=8-feb-2006 SIGN="00FF 6A1B 735B A476 2069 0A10 6894 4903 \
E2CF A238 7A01 1A15 1808 7BCF 346C F59E 8899 F53C 2B13 E204 C7FD"

A floating RLM license looks like this:

HOST <server_name> d49a20b9be26 4101
ISV foundry

30
LICENSING OVER A NETWORK | PURCHASING A FLOATING LICENSE

LICENSE foundry mari_i 2012.1231 permanent 20 share=h start=4 oct-2010 issued=4-oct-

2010 _ck=fa072c6a5a
sig="60P0453JHKQBGTB1HH7E3HNW843UJ627TSF4CXR22H7KNMYHG1B99WBSNHS1UE7FCN2W3AY8KV"

For further information about the structure of the license key, see Floating License Syntax.

For information on how to license one of our products using a floating license, see Purchasing a Floating License and
Installing a Floating License.

Purchasing a Floating License

You can purchase a floating license by:
• going to our web site at www.thefoundry.co.uk,
• e-mailing us at sales@thefoundry.co.uk,
• phoning our London office at +44 20 7479 4350 or our Los Angeles office at +1 (310) 399 4555.

To generate a license key, we need to know the System ID of the machine that acts as the server (not one of the
clients). The System ID (sometimes called Host ID, lmhostid, or rlmhostid) returns a unique number for that
computer. Just so you know what a System ID number looks like, here’s an example:
000ea641d7a1.

To display your server machine’s System ID, see Displaying Your System ID.

Once you have provided us with your server machine’s System ID number and a license key has been generated for
you, you receive the license key in an e-mail or internet download. The license key is contained in a text file called
foundry.lic. For information on what to do with the foundry.lic file, see Installing a Floating License.

Displaying Your System ID

There are a number of ways to display your server machine’s System ID, depending on your operating system.

R00ffb79aefc9:X00ffb79aefa9

When purchasing a license, you should send us the entire string with both IDs.

31
LICENSING OVER A NETWORK | PURCHASING A FLOATING LICENSE

On Windows
• Download the Foundry License Utility (FLU) from our website (www.thefoundry.co.uk/support/licensing/) and run
it on the machine that acts as the server.
The System ID is displayed at the bottom of the window, as highlighted.

• Alternatively, you can run the following from a command prompt:

<download location>/FLU_7.1v1_win-x86-release-64.exe -i

NOTE: The <download location> refers to the location where you saved the Foundry Licensing Utility.

NOTE: If you use the FLU from a command line and don’t pass it any arguments (such as -i in the above
example), it launches in GUI mode.

On Mac
• Download the Foundry License Utility (FLU) from our website (www.thefoundry.co.uk/support/licensing/) and run
it on the machine that acts as the server.
The System ID is displayed at the bottom of the window, as highlighted.

32
LICENSING OVER A NETWORK | INSTALLING A FLOATING LICENSE

• Alternatively, you can run the following from the command line:
<download location>/FoundryLicenseUtility.app/Contents/MacOS/FoundryLicenseUtility -i

NOTE: The <download location> refers to the location where you saved the Foundry Licensing Utility.

On Linux
On the machine that acts as the server, download the Foundry License Utility (FLU) from our website
(www.thefoundry.co.uk/support/licensing/) and run it from the command line:
<download location>/FoundryLicenseUtility -i

NOTE: The <download location> refers to the location where you saved the Foundry Licensing Utility.

Installing a Floating License

The Foundry Licensing Tools are supplied for Windows, Mac OS X, and Linux. To manage floating licenses across a
network, you have to install the Foundry Licensing Tools on a license server together with your floating license key(s).
Then you have to tell your client machines where to look for their license. How to do all this depends on your
operating system:
• If you’re on Windows, see Windows.
• If you’re on Mac OS X, see Mac OS X.
• If you’re on Linux, see Linux.

Windows
This section tells you how to get your floating license working on Windows.

Installing a Floating License on the License Server

1. Once a license has been generated for you, we e-mail you a zip file containing the license key and instructions on
how to obtain the correct version of the Foundry License Utility (FLU). To check and install the license key, install
the Windows version of the FLU and do one of the following:
• Drag the license file onto the FLU application, or

33
LICENSING OVER A NETWORK | INSTALLING A FLOATING LICENSE

• Cut and paste the license key text directly into the License Install tab in the FLU application, or
• If you double-click on the FLU application, it installs any file with a .lic file extension that it finds in the same
directory as the application.
2. The license server address is displayed on screen:
<number>@<license server name>
You should make a note of the address as you’ll need it to activate the client machines.
3. Proceed to Installing Foundry Licensing Tools (FLT) on the License Server.

If you are installing several licenses at the same time and only some of them fail validation, you can also
click Continue to complete the installation of the valid licenses.

You may also get a message saying that the license is not yet valid but may be valid in the future. This
means the license has been installed successfully and will automatically become live on the license start
date. You do not need to do anything further, but if you like, you can check that the server is up and the
server log reports the same message (see Viewing the License Server Log).

Alternative Methods of Installing the License

34
LICENSING OVER A NETWORK | INSTALLING A FLOATING LICENSE

4. Type the following command to install the FLU and the license. Note that you need to replace [my license] with
the location of your license key.
FLU_7.1v1_win-x86-release-64.exe -l[my license]
For example, if you saved your license key to D:\Temp\foundry.lic, the command should be:
FLU_7.1v1_win-x86-release-64.exe -l D:\Temp\foundry.lic
This checks the license key and copies it to the correct directory.
5. The license server address is displayed on screen:
<number>@<license server name>
You should make a note of the address as you’ll need it to activate the client machines.
6. Proceed to Installing Foundry Licensing Tools (FLT) on the License Server.

NOTE: If you use the FLU from a command prompt and don’t pass it any arguments (such as -l in the
example), it launches in GUI mode.

Alternatively, if you wish, you can install the license key by hand, though this is not recommended for most users. To
do so:
1. Launch a text editor and create a plain text file. Avoid using Word or other word processing programs to create
the file, as these add invisible control characters that trip up the licensing and make it hard for us to diagnose the
fault.
2. Copy the license key and paste it into the plain text file.
3. Save the file with a .lic extension (not .txt or .rtf) in the following directory. The name of the file can be
anything, but we recommend calling it foundry.lic.
• FLEXlm licenses:
C:\ProgramData\The Foundry\FLEXlm\
• RLM licenses:
C:\ProgramData\The Foundry\RLM\

NOTE: The ProgramData folder may be hidden. You can make it visible using the Folder Options in the
Control Panel. See Windows Hidden Files.

NOTE: There are other directories that can be searched for license files. See Moving the FLEXlm and RLM
Files.

4. If you installed an RLM license, create an options file and set a TIMEOUT or TIMEOUTALL period. This ensures
that licenses are returned to the server if the server and client machines lose contact with each other (due to a
network error, a crash, or some other failure). For more information, see Setting a TIMEOUT or TIMEOUTALL
Period.
If you installed a FLEXlm license, you can skip this step. FLEXlm licenses have a default timeout period of 7200
seconds (two hours).
5. Proceed to Installing Foundry Licensing Tools (FLT) on the License Server.

35
LICENSING OVER A NETWORK | INSTALLING A FLOATING LICENSE

Installing Foundry Licensing Tools (FLT) on the License Server

1. Download FLT_7.1v1_win-x86-release-64.exe from our web site (www.thefoundry.co.uk/support/licensing/)
and install it on the Windows computer that you want to serve the licenses across the network.
The license server starts automatically after installation (and whenever you restart the machine).
2. To check the server status, click Start > All Programs > The Foundry > FLT 7.1v1 > Foundry License Utility,
view the FLEXlm Server or RLM Server tab, and click Refresh Log.
To check RLM server status, you can also direct a web browser to the http://<server_name>:4102 server page
and click Status on the right.

3. If the license server fails to start, navigate to Control Panel > Administrative Tools > Services. Then, select
the appropriate service:
• For FLEXlm: Foundry FLEXlm Server
• For RLM: Foundry License Server
Click Start and check the server status again.

4. Proceed to Telling the Client Machines Where to Find the Licenses.

Telling the Client Machines Where to Find the Licenses

When you installed the floating license key on your server, you were provided with a <port>@<server name>. You
need this to license clients.

There are several ways to license clients. Choose one of the following and repeat it for each machine you wish to
have access to licenses on the server:

36
LICENSING OVER A NETWORK | INSTALLING A FLOATING LICENSE

• If your product displays a Licensing dialog when you launch it, click Install License and then Use Server. Type
<number>@<server name> (for example, 4101@red) and click Install. Your client retrieves a license from the
License Server and launches.
• Click Start > All Programs > The Foundry > FLT 7.1v1 > Foundry License Utility to launch the FLU. Make sure
you are viewing the License Install tab and copy and paste in an RLM server line:
HOST <server name> any <port>
For example: HOST red any 4101
This creates and installs both a FLEXlm and RLM client license.
• Launch a command prompt. Navigate to the location of the FoundryLicenseUtility.exe file, by default:
C:\Program Files\The Foundry\LicensingTools7.1
Then, type the following command:
FoundryLicenseUtility.exe -c <port>@<server name>
For example:
FoundryLicenseUtility.exe -c 4101@red
This creates and installs both a FLEXlm and RLM client license.
• Set an environment variable on your client as follows:
• If your product uses FLEXlm licensing, set the FOUNDRY_LICENSE_FILE environment variable on your client to
point to the license server (for example, @red). If you have more than one server, you could use:
@red:@green.
If you have specified a particular server port number (30001) in the foundry.lic file on the server, you should
set the environment variable to 30001@red.
• If your product uses RLM licensing, set the foundry_LICENSE environment variable on your client to point to
the license server (for example, 4101@red). If you have more than one server, you could use:
4101@red:4101@green
If you are using a port other than 4101, replace 4101 with the port selected.
For more information on setting environment variables, see Setting Environment Variables.
• Although not recommended, you can manually create a client license.
• If your product uses FLEXlm licensing, copy the foundry.lic file from the server to:
C:\ProgramData\The Foundry\FLEXlm
Rename the file and call it foundry_client.lic. Edit the file so it looks like this:
SERVER snowball 000a957bade9
VENDOR foundry
USE_SERVER
or if you had your own server port number set:
SERVER snowball 000a957bade9 30001
VENDOR foundry
USE_SERVER
• If your product uses RLM licensing, copy the foundry.lic file from the server to:
C:\ProgramData\The Foundry\RLM

37
LICENSING OVER A NETWORK | INSTALLING A FLOATING LICENSE

Rename the file and call it foundry_client.lic. Edit the file so it looks like this:
HOST red 000a957bade9 4101
or if you had your own server port number set:
HOST red 000a957bade9 30001

Mac OS X
This section tells you how to get your floating license working on Mac OS X.

Installing a Floating License on the License Server

1. Once a license has been generated for you, we e-mail you a zip file containing the license key and instructions on
how to obtain the correct version of the Foundry License Utility (FLU). To check and install the license key, install
the Mac OS X version of the FLU and do one of the following:
• Drag the license file onto the FLU application, or

• Drag the license file onto the Foundry License Utility, or

38
LICENSING OVER A NETWORK | INSTALLING A FLOATING LICENSE

If you are installing several licenses at the same time and only some of them fail validation, you can also
click Continue to complete the installation of the valid licenses.

Alternative Methods of Installing the License

The above methods are the easiest ways to install a license. However, if you prefer, you can also install a license from
the command line. To do so:
1. Save the FLU and your license key to a folder of your choice. Note that the license file can be the original .lic file
or the license in a plain text file (as long as the file has a .lic extension).
2. Launch a Terminal and navigate to the location of the FLU_7.1v1_mac-x86-release-64.zip file.
3. Type the following commands to extract and install the FLU and the license. Note that you need to replace [my
license] with the location of your license key.
unzip FLU_7.1v1_mac-x86-release-64.zip
cd FoundryLicenseUtility.app/Contents/MacOS/
./FoundryLicenseUtility -l [my license]
For example, if you saved your license key to /tmp/foundry.lic, the last line should be:
./FoundryLicenseUtility -l /tmp/foundry.lic
This checks the license key and copies it to the correct directory.
4. The license server address is displayed on screen:
<number>@<license server name>
You should make a note of the address as you’ll need it to activate the client machines.
5. Proceed to Installing Foundry Licensing Tools (FLT) on the License Server.

39
LICENSING OVER A NETWORK | INSTALLING A FLOATING LICENSE

FLEXlm licenses: /Library/Application Support/TheFoundry/FLEXlm/

RLM licenses: /Library/Application Support/TheFoundry/RLM/

NOTE: There are other directories that can be searched for license files. See Moving the FLEXlm and RLM
Files.

Installing Foundry Licensing Tools (FLT) on the License Server

1. Download FLT_7.1v1_mac-x86-release-64.dmg from our web site (www.thefoundry.co.uk/support/licensing/)
and install it on the Mac that you want to serve the licenses across the network.
The license server starts automatically after installation (and whenever you restart the machine).
2. To check the server status, navigate to /Applications/TheFoundry/LicensingTools7.1, double-click on
Foundry License Utility, view the FLEXlm Server or RLM Server tab, and click Refresh Log.
To check RLM server status, you can also direct a web browser to the http://<server_name>.local:4102 server
page and click Status on the right.

3. Proceed to Telling the Client Machines Where to Find the Licenses.

Telling the Client Machines Where to Find the Licenses

When you installed the floating license key on your server, you were provided with a <port>@<server name>. You
need this to license clients.

40
LICENSING OVER A NETWORK | INSTALLING A FLOATING LICENSE

There are several ways to license clients. Choose one of the following and repeat it for each machine you wish to
have access to licenses on the server:
• If your product displays a Licensing dialog when you launch it, click Install License and then Use Server. Type
<number>@<server name> (for example, 4101@red) and click Install. Your client retrieves a license from the
License Server and launches.
• Navigate to /Applications/TheFoundry/LicensingTools7.1/ and double-click on FoundryLicenseUtility to
launch the FLU. Make sure you are viewing the License Install tab and copy and paste in an RLM server line:
HOST <server name> any <port>
For example: HOST red any 4101
This creates and installs both a FLEXlm and RLM client license.
• Launch a Terminal and navigate to:
/Applications/TheFoundry/LicensingTools7.1/
Then, type the following commands:
cd FoundryLicenseUtility.app/Contents/MacOS/
./FoundryLicenseUtility -c <port>@<server name>
For example:
cd FoundryLicenseUtility.app/Contents/MacOS/
./FoundryLicenseUtility -c 4101@red
This creates and installs both a FLEXlm and RLM client license.
• Set an environment variable on your client as follows:
• If your product uses FLEXlm licensing, set the FOUNDRY_LICENSE_FILE environment variable on your client to
point to the license server (for example, @red). If you have more than one server, you could use
@red:@green.
If you have specified a particular server port number (30001) in the foundry.lic file on the server, you should
set the environment variable to 30001@red.
• If your product uses RLM licensing, set the foundry_LICENSE environment variable on your client to point to
the license server (for example, 4101@red). If you have more than one server, you could use
4101@red:4101@green.
If you are using a port other than 4101, replace 4101 with the port selected.
For more information on setting environment variables, see Appendix C: FLT Variables.
• Although not recommended, you can manually create a client license.
• If your product uses FLEXlm licensing, copy the foundry.lic file from the server to:
/Library/Application Support/TheFoundry/FLEXlm/
Rename the file and call it foundry_client.lic. Edit the file so it looks like this:
SERVER snowball 000a957bade9
VENDOR foundry
USE_SERVER
or if you had your own server port number set:
SERVER snowball 000a957bade9 30001

41
LICENSING OVER A NETWORK | INSTALLING A FLOATING LICENSE

VENDOR foundry
USE_SERVER
• If your product uses RLM licensing, copy the foundry.lic file from the server to:
/Library/Application Support/TheFoundry/RLM/
Rename the file and call it foundry_client.lic. Edit the file so it looks like this:
HOST red 000a957bade9 4101
or if you had your own server port number set:
HOST red 000a957bade9 30001

Linux
This section tells you how to get your floating license working on Linux.

Installing a Floating License on the License Server

1. Once a license has been generated for you, we e-mail you a .tgz file containing the license key and instructions
on how to obtain the correct version of the Foundry License Utility (FLU). On the machine that acts as the license
server, gunzip or untar the file and save the FLU and your license key to a folder of your choice, for example
/tmp. Note that the license file can be the original .lic file or the license in a plain .txt file (as long as the file has a
.lic extension).
2. Navigate to the location of the FLU_7.1v1_linux-x86-release-64.tgz file.
3. Type the following commands to extract and install the FLU and the license. Note that you need to replace [my
license] with the location of your license key.
tar xvzf FLU_7.1v1_linux-x86-release-64.tgz
cd FLU_7.1v1_linux-x86-release-64
./FoundryLicenseUtility -l [my license]
For example, if you saved your license key to /tmp/Foundry.lic, the last line should be:
./FoundryLicenseUtility -l /tmp/Foundry.lic
This checks the license key and copies it to the correct directory.
4. The license server address is displayed on screen:
<number>@<license server name>
You should make a note of the address as you’ll need it to activate the client machines.
5. Proceed to Installing Foundry Licensing Tools (FLT) on the License Server.

42
LICENSING OVER A NETWORK | INSTALLING A FLOATING LICENSE

If you are installing several licenses at the same time and only some of them fail validation, you can
continue to complete the installation of the valid licenses.

Alternatively, if you wish, you can install the license key by hand, though this is not recommended for most users. To
do so:
1. Launch a text editor and create a plain text file. Avoid using Word or other word processing programs to create
the file, as these add invisible control characters that trip up the licensing and make it hard for us to diagnose the
fault.
2. Copy the license key and paste it into the plain text file.
3. Save the file with a .lic extension (not .txt or .rtf) in the following directory. The name of the file can be
anything, but we recommend calling it foundry.lic.
FLEXlm licenses: /usr/local/foundry/FLEXlm/
RLM licenses: /usr/local/foundry/RLM/

NOTE: There are other directories that can be searched for license files. See Moving the FLEXlm and RLM
Files.

Installing Foundry Licensing Tools (FLT) on the License Server

1. Download FLT_7.1v1_linux-x86-release-64.tgz from our web site (www.thefoundry.co.uk/support/licensing/)
on the Linux machine that you want to serve these licenses across the network and save it to /tmp.
2. Open a shell and, using root or admin permissions, type these commands to extract and install the Foundry
Licensing Tools 7.1.
cd /tmp
tar xvzf FLT_7.1v1_linux-x86-release-64.tgz

43
LICENSING OVER A NETWORK | INSTALLING A FLOATING LICENSE

cd FLT_7.1v1_linux-x86-release-64
./install.sh
The license server starts automatically after installation (and whenever you restart the machine).
3. To check the server status, navigate to /usr/local/foundry/LicensingTools7.1 and enter:
./FoundryLicenseUtility -s status
This reports the status of both FLEXlm and RLM servers. If you only want to view one or the other, use one of
the following commands instead:
./FoundryLicenseUtility -s status -t FLEXlm
./FoundryLicenseUtility -s status -t RLM
To check RLM server status, you can also direct a web browser to the http://<server_name>:4102 server page
and click Status on the right.

4. Proceed to Telling the Client Machines Where to find the Licenses below.

Telling the Client Machines Where to find the Licenses

When you installed the floating license key on your server, you were provided with a <port>@<server name>. You
need this to license clients.

44
LICENSING OVER A NETWORK | LICENSE ADMINISTRATION

This creates and installs both a FLEXlm and RLM client license.
• Set an environment variable on your client as follows:
• If your product uses FLEXlm licensing, set the FOUNDRY_LICENSE_FILE environment variable on your client to
point to the license server (for example, @red).
If you have more than one server, you could use @red:@green.
If you have specified a particular server port number (30001) in the foundry.lic file on the server, you should
set the environment variable to 30001@red.
• If your product uses RLM licensing, set the foundry_LICENSE environment variable on your client to point to
the license server (for example, 4101@red).
If you have more than one server, you could use 4101@red:4101@green.
If you are using a port other than 4101, replace 4101 with the port selected.
For more information on setting environment variables, see Appendix C: FLT Variables.
• Although not recommended, you can manually create a client license.
• If your product uses FLEXlm licensing, copy the foundry.lic file from the server to:
/usr/local/foundry/FLEXlm/
Rename the file and call it foundry_client.lic. Edit the file so it looks like this:
SERVER snowball 000a957bade9
VENDOR foundry
USE_SERVER
or if you had your own server port number set:
SERVER snowball 000a957bade9 30001
VENDOR foundry
USE_SERVER
• If your product uses RLM licensing, copy the foundry.lic file from the server to:
/usr/local/foundry/RLM/
Rename the file and call it foundry_client.lic. Edit the file so it looks like this:
HOST red 000a957bade9 4101
or if you had your own server port number set:
HOST red 000a957bade9 30001

License Administration
The following section contains details on license management and administration, including file location and
updating licenses.

45
LICENSING OVER A NETWORK | LICENSE ADMINISTRATION

Where are the FLEXlm and RLM Files?

You can move the FLEXlm and RLM files anywhere, but by default they are installed to the following directories. We
refer to this directory throughout this guide and assume all the FLEXlm and RLM components we ship are here.

Application Files
These are files included in the Foundry License Installer. We’ll refer to this location as the <app path>.

<app path> on Windows:

C:\Program Files\The Foundry\LicensingTools7.1\bin\

<app path> on Mac OS X:

/Applications/TheFoundry/LicensingTools7.1/bin/

<app path> on Linux:

/usr/local/foundry/LicensingTools7.1/bin/

Data Files
These include the license keys and log files. We’ll refer to these locations as the <data path>.

<data path> on Windows:

C:\ProgramData\The Foundry\FLEXlm\
C:\ProgramData\The Foundry\RLM\

NOTE: The ProgramData folder may be hidden. You can make it visible using the Folder Options in the
Control Panel. See Windows Hidden Files.

<data path> on Mac OS X:

/Library/Application Support/TheFoundry/FLEXlm/
/Library/Application Support/TheFoundry/RLM/

<data path> on Linux:

/usr/local/foundry/FLEXlm/
/usr/local/foundry/RLM/

Moving the FLEXlm and RLM Files

If you want to move a floating license key to another directory then, if you have a license server already running, you
need to shut it down. You’ll need to edit the startup scripts to look in the new location. Then restart the license

46
LICENSING OVER A NETWORK | LICENSE ADMINISTRATION

server.

On Windows
If your product uses FLEXlm licensing:
1. First, stop the license server if it’s running. Navigate to Start > Control Panel > Systems and Security >
Administrative Tools > Services. Select Foundry FLEXlm Server and click Stop.
2. Click Start, type regedit, and then press Return on your keyboard.
3. Open the hierarchical structure HKEY_LOCAL_MACHINE > SOFTWARE > FLEXlm License Manager > Foundry
FLEXlm Server:

4. Select License and append the new license location to the current one using a ; (semicolon) between them:
C:\Program Files\The Foundry\FLEXlm;C:\tmp
5. Quit regedit.
6. Restart the license server. Navigate to Start > Control Panel > Systems and Security > Administrative
Tools > Services. Select Foundry FLEXlm Server and click Start.

TIP: You can also stop and start the license server using the Foundry License Utility (FLU). See Managing
the License Server.

If your product uses RLM licensing:

1. First, stop the license server if it’s running. Do one of the following:
• Navigate to Start > Control Panel > Systems and Security > Administrative Tools > Services. Select
Foundry License Server and click Stop.
• Use a web browser to go to the http://<server_name>:4102 server page. Click Status > Stop.
2. Click Start, type regedit, and then press Return on your keyboard.
3. Open the hierarchical structure HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > Foundry
License Server:

47
LICENSING OVER A NETWORK | LICENSE ADMINISTRATION

4. Move down the Registry as shown and select ImagePath.

5. Assuming your licenses are in C:\tmp, insert this into the path as shown:
"C:\Program Files\The Foundry\\LicensingTools7.1\bin\rlm.foundry.exe" "-c"
"C:\ProgramData\The Foundry\RLM;C\tmp" "-ws" "4102" "-dlog"
"C:\ProgramData\The Foundry\RLM\\log\foundry.log" -service

NOTE: Semi colons are used to separate license directories on Windows.

6. Quit regedit.
7. Restart the license server by doing one of the following:
• Navigate to Start > Control Panel > Systems and Security > Administrative Tools > Services. Select
Foundry License Server and click Start.

TIP: You can also stop and start the license server using the Foundry License Utility (FLU). See Managing
the License Server.

On Mac OS X
• If your product uses FLEXlm licensing, edit:
/Library/LaunchDaemons/uk.co.thefoundry.lmgrd
changing this line:
<string>/Library/Application
Support/TheFoundry/FLEXlm/:/usr/local/foundry/FLEXlm/</string>
to this, assuming your license is in /home/licenses
<string>/Library/Application
Support/TheFoundry/FLEXlm/:/usr/local/foundry/FLEXlm/:/home/licenses</string>
• If your product uses RLM licensing, edit:
/Library/LaunchDaemons/uk.co.thefoundry.rlm.plist

48
LICENSING OVER A NETWORK | LICENSE ADMINISTRATION

changing these lines:

<string>-c</string>
<string>/Library/Application Support/TheFoundry/RLM/</string>
to this, assuming your license is in /home/licenses:
string>-c</string>
<string>/Library/Application Support/TheFoundry/RLM/:/home/licenses</string>

On Linux
• If your product uses FLEXlm licensing, edit:
/etc/init.d/foundryflexlmserver
changing this line:
FnLicDir=/usr/local/foundry/FLEXlm
to this, assuming your license is in /home/licenses
FnLicDir=/usr/local/foundry/FLEXlm:/home/licenses
• If your product uses RLM licensing, edit:
/etc/init.d/foundryrlmserver
changing this line:
FnLicDir=/usr/local/foundry/RLM
to this, assuming your license is in /home/licenses
FnLicDir=/usr/local/foundry/RLM:/home/licenses

When is a License Taken or Dropped?

Product licenses are checked out from the server when the product is first used on the client. Plug-in products
generally take a license when the first plug-in of the set is used.

When a license is returned to the server depends on a number of things. Let’s consider the following scenarios:
• The Product Exits or is Deleted/Unloaded from the Client
• The Product Doesn’t Exit but is not Used for a While
• The Server and Client Machine Lose Contact with Each Other

The Product Exits or is Deleted/Unloaded from the Client

If the product exits or is deleted/unloaded from the client, the license is given back to the server.

Plug-in products generally return the license when the last plug-in of the set is removed from the effects tree or layer
stack. The exact point at which a license is returned by a plug-in product is host-specific, and can be unpredictable.

49
LICENSING OVER A NETWORK | LICENSE ADMINISTRATION

The Product Doesn’t Exit but is not Used for a While

If you take a license from the server and then go to lunch for an hour, your license will still be there when you get
back.

If you want your license to go back to the server if you don’t use it for a while, you need to change the default
behavior by disabling the heartbeat.

NOTE: The heartbeat ensures the communication between the server and client persists in a stable
fashion and therefore should be disabled with caution, otherwise users may find their licenses being
withdrawn unexpectedly.

To disable the heartbeat:

1. Do one of the following:
• If your product uses FLEXlm licensing, set the FOUNDRY_HEARTBEAT_DISABLE environment variable to true
on the client.
• If your product uses RLM licensing, set the foundry_HEARTBEAT_DISABLE environment variable to true on
the client.
For more information on setting environment variables, see Appendix C: FLT Variables.
2. Next, you must make sure a TIMEOUT or TIMEOUTALL value is set in the options file (foundry.opt). This value
dictates how long the server should wait for communication to resume with the client before deciding that the
client has exited. After the TIMEOUT period, the server deems the license released and makes it available on the
network again. If no TIMEOUT period is set, however, the server may never release the license in some
circumstances.
See Setting a TIMEOUT or TIMEOUTALL Period.

NOTE: When installing RLM licenses using the Foundry License Utility (FLU), the FLU automatically creates
the options file and sets the TIMEOUTALL value to 3600 seconds (one hour).

The Server and Client Machine Lose Contact with Each Other
Should the server and client machines lose contact with each other (due to a network error, a crash, or some other
failure), licenses are returned to the server according to the TIMEOUT or TIMEOUTALL flag set in the options file
(foundry.opt):
• FLEXlm licenses
• By default, the TIMEOUT value is set to 7200, which means the server waits for 7200 seconds (two hours)
before deciding that the client has crashed or failed in some other way, then deems the license released, and
makes it available on the network again. If you want to change the default timeout period, you need to edit
the options file. For instructions on how to do this, see Setting a TIMEOUT or TIMEOUTALL Period.
• RLM licenses

50
LICENSING OVER A NETWORK | LICENSE ADMINISTRATION

• If you installed an RLM license using The Foundry License Utility (FLU), the options file was created
automatically, with the TIMEOUTALL flag set to 3600 seconds (in other words, one hour). This means the
server waits for one hour before deciding that the client has crashed or failed in some other way, then deems
the license released, and makes it available on the network again. If you want to change the default timeout
period, you need to edit the options file. For instructions on how to do this, see Setting a TIMEOUT or
TIMEOUTALL Period.
• If you installed an RLM license manually, you must create the options file and set a TIMEOUTALL or TIMEOUT
period yourself. If you don’t, the server does not have a default timeout period and may never release the
license in some circumstances. For more instructions, see Setting a TIMEOUT or TIMEOUTALL Period.

Setting a TIMEOUT or TIMEOUTALL Period

1. Create the options file if one doesn’t already exist. It should be a plain text file called foundry.opt placed in the
same directory as the license (unless a different options file location is specified in the license file itself, either on
the VENDOR or ISV line).
2. In the options file, you can set the TIMEOUT on a per-product basis, for example:
TIMEOUT mari_i 3600
TIMEOUT katana_r 600
The lines above tell the server that if it has not had communication with a mari_i client for an hour, it should
consider the license released. However, for the katana_r client, it should wait only 10 minutes before deciding
the license is free to be served again.
You can also use:
TIMEOUTALL 3600
This tells the server that all features, except those with their own TIMEOUT flags, should time out after one hour.

NOTE: For RLM licenses, the options file TIMEOUT can only be set to a minimum of 3600 seconds (1 hour),
unless your license contains a min_timeout=<secs> flag.

3. Once you have edited your options file, you need to stop and start the license server:
• On Windows and Mac, launch the Foundry License Utility (FLU), go to one of the Server tabs and click Stop
Server, followed by Start Server.
• On Linux, launch a shell, navigate to where you saved the Foundry License Utility (FLU), and enter one of the
following commands:
./FoundryLicenseUtility -s stop -t FLEXlm
./FoundryLicenseUtility -s stop -t RLM
Then, enter either:
./FoundryLicenseUtility -s start -t FLEXlm
./FoundryLicenseUtility -s start -t RLM

TIP: You can also use the FLU from a Terminal on Mac OS X or a command prompt on Windows.

51
LICENSING OVER A NETWORK | LICENSE ADMINISTRATION

TIP: To find out what the timeout period is set to, you can run the Foundry License Utility’s Diagnostics
tool (see Using the Diagnostics Tool in GUI Mode). This prints the contents of the options file if one is
found.

Capping Licenses
Have you ever needed a license only to find they have all been checked out by your colleagues? Just needed a
command to stop someone’s license so you can grab it? Then these are the commands for you!

The lmremove (for FLEXlm) and rlmremove (for RLM) utilities allow you to remove a single user’s license for a
specified feature. As ever, let’s consider some examples.

First, who’s got the licenses?

• Using the lmutil command (FLEXlm licenses):
<app path>/lmutil lmstat -c <data path> -a
• Using the rlmutil command (RLM licenses):
<app path>/rlmutil rlmstat -c <data path> -a

NOTE: See Application Files and Data Files for the correct <app path> and <data path>.

The above FLEXlm command might produce this output:

Users of keylight_ofx_i: (Total of 1 licenses issued; Total of 1 license in use)
"keylight_ofx_i" v2.1, vendor: foundry
floating license
jack red /dev/ttys001 (v2.1) (blue/30003 14094), start Tue 8/26 14:56

where the user is jack, the user’s computer is red, the display is /dev/ttys001, the server computer is blue, the
TCP/IP port is 30003 and the license handle is 14094.

Similarly, the RLM command might produce this output:

foundry license usage status on licserv (port 38565)
mari_i v2015.1231: jack@red 1/0 at 10/07 14:40 (handle: 8a)
mari_i v2015.1231: mike@green 1/0 at 10/07 14:41 (handle: 67)

where the user is jack, the user’s computer is red, and the license handle is 8a.

To remove Jack’s license, use this command:

• FLEXlm:
<app path>lmutil lmremove keylight_ofx_i jack red dev/tts001
or
<app path>lmutil lmremove -h keylight_ofx_i blue 30003 14094
• RLM:

52
LICENSING OVER A NETWORK | LICENSE ADMINISTRATION

<app path>/rlmutil rlmremove licserv 38565 foundry 8a

Since it’s a bit rude to cap someone’s license, systems administrators can disable this functionality by:
• starting the lmgrd with a flag, -x lmremove.
• starting the rlm.foundry with a flag, -x rlmremove.

Appending to an Existing License

You can add a new license to an existing key using two methods:
• On Windows and Mac OS X, drop the license file onto the Foundry License Utility. On Linux, run the FLU from the
command line using
./FoundryLicenseUtility -l [license path]. This is the recommended method.
• Edit the license file manually from the command line. This is not recommended for most users.
If your product uses FLEXlm licensing, see Manual Method (FLEXlm).
If your product uses RLM licensing, see Manual Method (RLM).

Manual Method (FLEXlm)

You can add a new license key by editing the foundry.lic text file and then using lmutil to re-read this file.

Here is an example floating license key for a machine called red with System ID 000EA641D7A1 that serves 2
floating Nuke licenses onto the network.
SERVER red 000EA641D7A1
VENDOR foundry
INCREMENT nuke_i foundry 2012.0930 permanent 2 \
ISSUED=8-feb-2012 SIGN="00FF 6A1B 735B 0A10 6894 4903 E2CF \
A238 7A01 1A15 1808 7BCF 346C F59E 8899 F53C 2B13 E204"

If you are then sent a Furnace for Nuke license key for the same machine, just add the INCREMENT lines to your
existing file, ignoring any SERVER lines, so that it would look like this:
SERVER red 000EA641D7A1
VENDOR foundry
INCREMENT nuke_i foundry 2012.0930 permanent 2 \
ISSUED=8-feb-2012 SIGN="00FF 6A1B 735B A476 6894 \
4903 E2CF A238 7A01 1A15 1808 7BCF 346C F59E 8899 \
F53C 2B13 E204"
INCREMENT nuke_r foundry 2012.0930 permanent 2 \
ISSUED=8-feb-2012 SIGN="0269 8747 2EA4 1D42 A5F5 \
56B9 7A26 6802 2A09 E931 F14B 09D5 B8E8 051E 606B \
07D5 64F3 7152"
INCREMENT furnace_ofx_i foundry 3.0 permanent 4

53
LICENSING OVER A NETWORK | LICENSE ADMINISTRATION

ISSUED=20-feb-2012 SIGN="0048 8492 6890 DC3F 23E8 \

4F29 83D7 9302 3F9E 79B1 54F8 D6EF 341D 5D09 C630 \
C75C 384C 1B89"
INCREMENT furnace_ofx_r foundry 3.0 permanent 4
ISSUED=20-feb-2012 SIGN="0309 431F 8D69 9499 340C \
0E25 366A 3900 5296 990B 079D 7F83 B5C8 C085 DD7A \
8437 9552 DE14"

Now re-read the license file with this command:

<app path>/lmutil lmreread -c <data path>

Manual Method (RLM)

You can add a new license key by editing the foundry.lic text file and then using rlmutil to re-read this file.

Here is an example floating license key for a machine called red with System ID 000EA641D7A1 that serves 2
floating Mari licenses onto the network:
HOST red 000EA641D7A1 4101
ISV foundry
LICENSE foundry mari_i 2010.1231 permanent 2 share=h start=6-oct-2010 issued=6-oct-2010
_ck=fad7306732
sig="60Q04580SBD4AEEY4C93A1K0H718JRY9DWGP1HWR08AG1CY16HPHCKKQ44FDKGYQKE0BXKGRJ3WBT"

If you are then sent an Ocula license key for the same machine, just add the LICENSE lines to your existing file,
ignoring any HOST or ISV lines, so that it would look like this:
HOST red 000EA641D7A1 4101
ISV foundry
LICENSE foundry mari_i 2010.1231 permanent 2 share=h start=6-oct-2010 issued=6-oct-2010
_ck=fad7306732
sig="60Q04580SBD4AEEY4C93A1K0H718JRY9DWGP1HWR08AG1CY16HPHCKKQ44FDKGYQKE0BXKGRJ3WBT"
LICENSE foundry ocula_nuke_i 3.0 permanent 2 share=h start=6-oct-2010 issued=6-oct-2010
_ck=72d73079d7
sig="60PG4512DMXC338XEG3F0XBNPFREB6SHHD0QXA822M09MNJUB3E9VQUXKJP69DJ5CYR27AUYFRS0"

Now re-read the license file with this command:

<app path>/rlmutil rlmreread -c <data path>

Using a web browser, go to http://red:4102 and click Status > Reread.

54
LICENSING OVER A NETWORK | LICENSE ADMINISTRATION

The <server_name> Variable

If you requested a floating license key but didn’t tell us the hostname of your license server, then we will have given
you a license key with <server_name> in the first line. You need to replace the text <server_name> with the name
of your license server (if you use the Foundry License Utility, it does this for you).

Replace Licenses
You may see the word SUPERSEDE in your FLEXlm license file or replace in your RLM license file. These flags are
used in conjunction with the ISSUED (FLEXlm) and issued (RLM) flags to roll together multiple licenses.

For example, let’s consider this FLEXlm license for Nuke:

SERVER red 2c4138a7d9ba
VENDOR foundry
INCREMENT nuke_i foundry 2013.1231 31-jan-2014 2 SUPERSEDE \
ISSUED=29-feb-2012 START=29-feb-2012 TS_OK SIGN="001E AA6A \
8780 5A12 7811 15B9 F441 8F7F 186D 2B74 3303 B6AD 2072 079C \
440D 7F36 F09C 1A2B FF4A 274F 6C67"

Here, the SUPERSEDE flag forces FLEXlm to ignore any nuke_i licenses with an ISSUED date older than 29th February
2012.

Similarly, in the following RLM license for Mari, the replace flag forces RLM to ignore any mari_i licenses with an
issued date older than 1st December 2013.
HOST red 2c4138a7d9ba 4101
ISV foundry
LICENSE foundry mari_i 2013.1231 permanent 2 share=h min_timeout=30
start=1-dec-2013 issued=1-dec-2013 replace
_ck=07d7a84d33

55
LICENSING OVER A NETWORK | MANAGING THE LICENSE SERVER

sig="60PG4580SR8RRKV7XM5E8J1XPV0BEV00PSASH0UV08A4MHS
EMWMKW520H34RNCGKM0XUVT229BT0"

Which RLM Port?

Although the default port used by RLM is 5053, The Foundry has opted to use port 4101 for all its licenses to ensure
there are no conflicts with any other RLM license servers that may be running on the server.

If, however, no port is specified on the HOST line of a license, or in the foundry_LICENSE environment variable, the
port defaults to 5053. For example, the following entry:
HOST red 000EA641D7A1
behaves in the same way as:
HOST red 000EA641D7A1 5053

Licenses sent to you by The Foundry appear as follows:

HOST red 000EA641D7A1 4101
If you wish to change this port number, ensure that you modify all your client licenses in the same way.

Managing the License Server

Starting the License Server

The License Server starts automatically when you reboot your machine, but you can start it manually:
• On Windows and Mac OS X, launch the Foundry License Utility (FLU), go to the FLEXlm Server or RLM Server tab,
and click Start Server.

TIP: You can also use the FLU from a command prompt on Windows or a Terminal on Mac OS X.

• On Linux, launch a shell, navigate to where you saved the Foundry License Utility (FLU), and enter one of the
following commands:
./FoundryLicenseUtility -s start -t FLEXlm
./FoundryLicenseUtility -s start -t RLM
• On all platforms, if your product uses RLM licensing, you can also use a web browser to navigate to the
http://<server_name>:4102 server page. For example, http://red:4102. Click the Status button, and click Start
on the Foundry License Server.

56
LICENSING OVER A NETWORK | MANAGING THE LICENSE SERVER

NOTE: On Mac OS X, if you’re browsing from the License Server itself, you must add .local in the browser
address: http://<server_name>.local:4102.

Stopping the License Server

To stop the license server:
• On Windows and Mac OS X, launch the Foundry License Utility (FLU), go to the FLEXlm Server or RLM Server tab,
and click Stop Server.

TIP: You can also use the FLU from a command prompt on Windows or a Terminal on Mac OS X.

• On Linux, launch a shell, navigate to where you saved the Foundry License Utility (FLU), and enter one of the
following commands:
./FoundryLicenseUtility -s stop -t FLEXlm
./FoundryLicenseUtility -s stop -t RLM
• On all platforms, if your product uses RLM licensing, you can also use a web browser to navigate to the
http://<server_name>:4102 server page and click Stop.

NOTE: On Mac OS X, if you’re browsing from the License Server itself, you must add .local in the browser
address: http://<server_name>.local:4102.

Viewing the License Server Log

You can view the license server log even if you don’t have administrator privileges. To do so:
• On Windows and Mac OS X, launch the Foundry License Utility (FLU), go to the FLEXlm Server or RLM Server tab,
and click Refresh Log.

TIP: You can also use the FLU from a command prompt on Windows or a Terminal on Mac OS X.

• On Linux, launch a shell, navigate to where you saved the Foundry License Utility (FLU), and enter:
./FoundryLicenseUtility -s status
This reports the status of both FLEXlm and RLM servers. If you only want to view one or the other, use one of the
following commands instead:
./FoundryLicenseUtility -s status -t FLEXlm
./FoundryLicenseUtility -s status -t RLM
• On all platforms, if your product uses RLM licensing, you can also use a web browser to navigate to the
http://<server_name>:4102 server page and click the Status button.

57
LICENSING OVER A NETWORK | MANAGING THE LICENSE SERVER

NOTE: On Mac OS X, if you’re browsing from the License Server itself, you must add .local in the browser
address: http://<server_name>.local:4102.

RLM Web Server

The RLM web server also allows you to:
• retrieve server and license status (similar to rlmstat)
• cause the servers to re-read the license files (rlmreread)
• switch debug (rlmswitch) or report log (rlmswitchr) files
• move the current report log file to a new name (rlmnewlog)
• shutdown and startup the license servers (rlmdown/rlmreread).

Using this web-based interface, you can administer the license server from any platform, and you do not need to
install the RLM utilities - you only need a web browser.
• Main Status - if you select Status from the menu on the left, the main status screen is displayed in the view area
as shown below.

• Server Status - click on an ISV button in the Server Status column to display a detailed status display for an
individual ISV server in the view area. This displays some server statistics in a table at the top, followed by a table of
all the licenses served by this ISV server.

58
LICENSING OVER A NETWORK | MANAGING THE LICENSE SERVER

• License Status - if you click on the usage... button in the Show License Usage column above, you see the
license status screen, as shown.

• Reread/Restart/Shutdown - click Reread/Restart Servers from the menu on the left (or from the REREAD
column in the ISV server status display) to display the Reread/Restart Servers screen in the view area. Enter an
ISV name and click REREAD/RESTART. This restarts the server if it is not running, or sends it a reread command if it
is running.
You can also type all to refresh or restart all discovered servers.

59
LICENSING OVER A NETWORK | MANAGING THE LICENSE SERVER

Useful Commands for System Administrators

Type all these commands from the The Foundry FLEXlm or RLM applications directory on the server.

See Application Files for a description of the <app path> variable, and Data Files for a description of <data path>.

Is the License Server Up and Running?

<app path>/lmutil lmstat -c <data path>
<app path>/rlmutil rlmstat -c <data path>

I’m Using The Foundry Software on Machine "blue". Which Licenses is the License Server
"red" Offering?
<app path>/lmutil lmstat -c <port>@red -a
<app path>/rlmutil rlmstat -c <port>@red -a

What is My System ID Number?

<app path>/lmutil lmhostid
<app path>/rlmutil rlmhostid

What’s My <server_name>?
<app path>/lmutil lmhostid -hostname
<app path>/rlmutil rlmhostid host

Show Me All My Licenses and Who has Checked Them Out.

<app path>/lmutil lmstat -c <data path> -a
<app path>/rlmutil rlmstat -c <data path> -a

60
LICENSING OVER A NETWORK | REMOVING FLT

If your product uses RLM licensing, you can also use a web browser to go to http://<server name>:4102 and click
Status > Server Status to view license usage.

NOTE: On Mac OS X, if you’re browsing from the License Server itself, you must add .local in the browser
address: http://<server_name>.local:4102.

Who Has Checked Out a Particular License?

<app path>/lmutil lmstat -c <data path> -f furnace_ofx_r
<app path>/rlmutil rlmstat -c <data path> -p mari_r

I’ve been given a new floating license key, which I’ve edited into my license file, but it has not
been picked up by the server. What do I do?
• On Windows and Mac OS X, launch the Foundry License Utility, go to one of the Server tabs, and use the Reread
Server button.
• Alternatively, use one of the following commands:
<app path>/lmutil lmreread -c <data path>
<app path>/lmutil rlmreread -c <data path>
• If your product uses RLM licensing, you can also use a web browser to go to http://<server name>:4102 and click
Reread/Restart Servers. Enter the server name you want to reread and click Reread/Restart.

NOTE: On Mac OS X, If you’re browsing from the License Server itself, you must add .local in the browser
address: http://<server_name>.local:4102.

My Default Debug Log File (foundry.log) is Too Big. How do I Start a New One Called
october.log Without Interrupting the lmgrd or rlm.foundry Daemon?
<app path>/lmutil lmswitch -c <data path> foundry october.log
<app path>/rlmutil rlmswitch foundry october.log

Removing FLT

On Windows
To stop the Foundry License Server and remove FLT from your machine, from the Start menu go to All Programs >
The Foundry > FLT 7.1v1 > Uninstall FLT 7.1v1.

61
LICENSING OVER A NETWORK | MORE INFORMATION

On Mac OS X
To stop the Foundry License Server and remove FLT from your machine, run the FLT Uninstaller script from a
terminal with root or sudo permissions:
/Applications/TheFoundry/LicensingTools7.1/uninstall.sh

On Linux
To stop the Foundry License Server and remove FLT from your machine, run the script:
/usr/local/foundry/LicensingTools7.1/uninstall.sh

Please be aware that advanced RLM features not discussed in this user guide are not supported with RLM licenses
from The Foundry.

62
Troubleshooting Licenses
There are many reasons why your license key may fail to work. This section is here to guide you
through some common problems and how to fix them.

Firewalls

The Problem
You have set up a floating license, but client machines are not able to get a license from the server. Everything seems
to be set up correctly. The server is running and is floating licenses. The client is correctly pointing to the server using
a client.lic file or an environment variable. So what’s wrong?

The Solution
This could be any number of things, but if everything is set up correctly, it could be the firewall on the server blocking
perfectly legitimate requests from the client. In order to fix this, you need to specify ports for your servers and allow
these to be open.
• If you’re on Windows, see Windows.
• If you’re on Mac OS X, see Mac OS X.
• If you’re on Linux, consult your system administrator.

Windows
Two firewall exception methods are available to enable client machines to checkout licenses and connect to the web
service in the License Server: programs and port numbers.

63
TROUBLESHOOTING LICENSES |

Windows Program Exceptions

1. From the Windows Start menu, click Control Panel > System and Security > Windows Firewall and then
click on the Advanced settings link.

2. Select Inbound Rules in the left-hand panel and click New Rule as shown below.

3. Select Program and then click Next.

4. Select This program path and then browse to the location of the following programs, dependent on the license
server you’re using:
• If your product uses FLEXlm licensing, browse to:
C:\Program Files\The Foundry\LicensingTools7.1\bin\FLEXlm
Add lmgrd.foundry.exe and then repeat the process to add an input exception for foundry.exe.
• If your product uses RLM licensing, browse to:
C:\Program Files\The Foundry\LicensingTools7.1\bin\RLM
Add rlm.foundry.exe.
5. Click Allow the connection and then click Next.

64
TROUBLESHOOTING LICENSES |

6. Select all the checkboxes that apply to the rule. Domain, Private, and Public in the example below.

7. Click Next and enter a meaningful name for the rule, such as FLEX_SERVER or RLM_HOST.
8. Click Finish to complete the process.
9. Stop and Start the license server as described in Managing the License Server.

Windows Port Exceptions

Port exceptions are set up slightly differently depending on whether you’re using a FLEXlm or RLM license server.

FLEXlm Port Exceptions

First, you need to change the license files on the server and any clients to include port numbers. See Where are the
FLEXlm and RLM Files? for the license file locations. These port numbers must be different. For example, you might
edit a FLEXlm license to look like this:
SERVER red 000EA641D7A1 30001
VENDOR foundry PORT=1001

And a client license like this:

SERVER red ANY 30001
VENDOR foundry PORT=1001
USE_SERVER

NOTE: You may want to check with your system administrator that the port number you choose is not
already in use by another program.

Next, on the license server, go to your firewall settings and add Inbound Rules for TCP ports with the port numbers
in the SERVER and VENDOR lines.

65
TROUBLESHOOTING LICENSES |

1. From the Windows Start menu, click Control Panel > System and Security > Windows Firewall and then
click on the Advanced settings link.

2. Select Inbound Rules in the left-hand panel and click New Rule as shown below.

3. Select the Port radio button and then click Next.

4. Select TCP and Specific local ports and enter the port number in the field provided, 30001 in the example.
5. Click Next.
6. Select Allow the connection and click Next.
7. Select when the new rule should be applied using the checkboxes. In the example, the rule is applied at all times,
but you can modify this as required.

66
TROUBLESHOOTING LICENSES |

8. Click Next and enter a meaningful name for the new rule, for example FLEXlm_SERVER, and write a description,
if required.
9. Click Finish.
10. Select the new rule from the Inbound Rules list and click Properties.
11. Click the Programs and Services tab, select This program, and browse to <app path>/lmgrd.foundry.exe as
shown.

12. Click Open to return to the Properties dialog.

13. Click Apply, and close the dialog.
14. Repeat steps 2 through 14 for the VENDOR port, replacing the port number, and the program with <app
path>/foundry.exe.
15. Stop and start the license server as described in Managing the License Server.

67
TROUBLESHOOTING LICENSES |

RLM Port Exceptions

As with FLEXlm, you need to change your license file to include two different port numbers. Unlike FLEXlm, RLM also
requires an options file entry.

If you installed an RLM license using the FLU, the options file was created automatically in the same directory as your
license. If, however, you installed your license manually, create a plain text file called foundry.opt in the same
directory as the license. See Where are the FLEXlm and RLM Files? for the license file location.

A typical RLM licence including port numbers and an options file might look like this:
HOST red 000ea641d7a1 4101
ISV foundry OPTIONS=foundry.opt PORT=12345

NOTE: You may want to check with your system administrator that the port number you choose is not
already in use by another program.

A foundry.opt file for Mari should contain the following line:

TIMEOUT mari_i 3600

Or, for all RLM licensed products:

TIMEOUTALL 3600

After editing the license and options file, stop and start the license server as described in Managing the License
Server. In the license server interface, click Status and check that the ports specified are listed and that the server is
running.

Next, go to your firewall settings and add Inbound Rules for TCP ports with the port numbers in the HOST and ISV
lines.
1. From the Windows Start menu, click Control Panel > System and Security > Windows Firewall and then
click on the Advanced settings link.

68
TROUBLESHOOTING LICENSES |

2. Select Inbound Rules in the left-hand panel and click New Rule as shown below.

3. Select the Port radio button and then click Next.

4. Select TCP and Specific local ports and enter the port number in the field provided (4101 in the example).
5. Click Next.
6. Select Allow the connection and click Next.
7. Select when the new rule should be applied using the checkboxes. In the example, the rule is applied at all times,
but you can modify this as required.

8. Click Next.
9. Enter a meaningful name for the new rule, for example RLM_HOST, and write a description, if required.
10. Click Finish.
11. Select the new rule from the Inbound Rules list and click Properties.
12. Click the Programs and Services tab, select This program, and browse to <app path>/rlm.foundry.exe as
shown.

69
TROUBLESHOOTING LICENSES |

13. Click Open to return to the Properties dialog.

14. Click Apply, and close the dialog.
15. Repeat the process for the ISV port, replacing the port number and rule name.
16. Click the Programs and Services tab, select All programs that meet the specified conditions.
17. Click OK to close the dialog.

Mac OS X
You need to adjust your firewall settings. How to do this depends on your firewall and the version of Mac OS X you
are running, but here’s how to do it on Mac OS X 10.6 (Snow Leopard):
1. Launch System Preferences.
2. Click on Security & Privacy and go to the Firewall tab.
3. Click the Firewall Options button.

NOTE: You may need to click the lock icon at the bottom-left to enable changes.

70
TROUBLESHOOTING LICENSES |

4. Under the list of incoming connections, click on the + button.

5. If your product uses FLEXlm licensing:

• Navigate to /Applications/TheFoundry/LicensingTools7.1/bin/FLEXlm
• Select both foundry and lmgrd.foundry and click Add.
If your product uses RLM licensing:
• Navigate to /Applications/TheFoundry/LicensingTools7.1/bin/RLM
• Select rlm.foundry and click Add.

71
TROUBLESHOOTING LICENSES | WINDOWS HIDDEN FILES

Windows Hidden Files

On Windows, the C:\ProgramData directory may be hidden. You can make it visible by navigating to Control Panel
> Appearance and Personalization > Folder Options > View tab and then selecting Show hidden files,
folders, and drives.

Enable Show hidden files, folders,

and drives.

FLU Reporting More Than One System ID

For most machines the FLEXlm System ID and RLM System ID are the same, so the FLU displays a single System ID.
However, on rare occasions, two System IDs are reported (one for FLEXlm and one for RLM). If this is the case, both
System IDs are displayed, like this:
R00ffb79aefc9:X00ffb79aefa9
If the FLU returns two System IDs for your machine, the one that you need to use depends on which software you
are running:
• For FLEXlm licensed software you need to use the second System ID minus the X, 00ffb79aefa9 in the example.
• For RLM licensed software you need to use the first System ID minus the R, 00ffb79aefc9 in the example.

For a full list of The Foundry products and which licensing software they use, go to the Licensing FAQ here, and open
What are RLM and FLEXIm licenses?

72
TROUBLESHOOTING LICENSES | NODE LOCKED AND CLIENT LICENSES

Node Locked and Client Licenses

If you have a node locked license in a client license file that is pointing to the server for its licenses, the node locked
license won’t work. Use separate files for the node locked license (foundry.lic) and client license (foundry_client.lic).
For example, this Mari RLM license won’t work in this file that is looking on “red” for its licenses.
HOST red 000EA641D7A1 4101
ISV foundry
LICENSE foundry mari_i 2011.1006 permanent uncounted hostid=000ea641d7a1 share=h
start=6-oct-2010 issued=6-oct-2010 _ck=fbf430af8c
sig="60PG4515BFTJCYAXSYJ6GTUJ3B9NRRGF3VUUKD022M0BXU48SSESUGSAFJ8BAD5BN883526ETKQ0"

Accessing the RLM Web Server on Mac OS X

The Problem
On Mac OS X, you’re browsing to http://<server_name>:4102, on the License Server itself, looking for the RLM Web
Server page, but you can’t connect.

The Solution
Due to Mac OS X system architecture, you must add .local to the URL address when you’re browsing from the
License Server itself:
http://<server_name>.local:4102

NOTE: You can use this address on other platforms, but it’s not necessary.

Contacting Support
If you have flicked through this user guide and haven’t found the answer to your question, then please:
1. See the frequently asked questions at www.thefoundry.co.uk/support/faqs/.
2. Run the Foundry License Utility’s diagnostics tool in GUI mode (Windows and Mac) or from the command line
(Windows, Mac, and Linux). This gives you a text file that you can send to support for assistance. See Using the
Diagnostics Tool in GUI Mode or Using the Diagnostics Tool in Command Line Mode.
3. Visit supportportal.thefoundry.co.uk for assistance.

73
TROUBLESHOOTING LICENSES | CONTACTING SUPPORT

Using the Diagnostics Tool in GUI Mode

1. Launch the Foundry License Utility (FLU).
2. Go to the Diagnostics tab, and click Run Diagnostics.
This gathers lots of information on your machine that helps us diagnose the problem. No personal information
is gathered.
3. Click Save to write out a text file we can use to assist you when you visit supportportal.thefoundry.co.uk.

Using the Diagnostics Tool in Command Line Mode

1. Launch a command prompt (Windows), a Terminal (Mac), or a shell (Linux).
2. Navigate to the directory where you have saved the Foundry License Utility (FLU).
3. Enter one of the following commands.
Windows
FLU_7.1v1_win-x86-release-64.exe -d
Mac OS X
./FoundryLicenseUtility.app/Contents/MacOS/FoundryLicenseUtility -d
Linux
./FoundryLicenseUtility -d
This gathers lots of information on your machine that helps us diagnose the problem. No personal information
is gathered.
4. The tool prompts you to save a text file we can use to assist you when you visit supportportal.thefoundry.co.uk.
To do so, enter Y.

TIP: By default, the file is saved to your home directory and given an automated file name. If you’d like to
specify a different directory and name, use -f <path> instead. For example, on Windows:

FLU_7.1v1_win-x86-release-64.exe -f C:\temp\log.txt

74
Appendix A: Release Notes
This section describes the requirements, new features, improvements, fixed bugs, and known bugs
and workarounds for each release of the Foundry Licensing Tools (FLT).

FLT 7.1v1
This is a major new release of FLT, with new features, enhancements, and bug fixes.

Release Date
March 2015

System Requirements
• Mac OS X 10.6 (Snow Leopard), 10.7 (Lion), or 10.8 (Mountain Lion), 64-bit only
• Linux RHEL 5.4 or RHEL 6, 64-bit
• Windows 7 or Windows 8, 64-bit

NOTE: These are the operating systems FLT has been tested on. Other operating systems are likely to
work.

New Features
• The FLU and FLT are now only supported on 64-bit machines.
• The FLU now checks more licensing directories when you click Run Diagnostics.

Feature Enhancements
A new command line flag, --name or -n, has been added to the FLU to show the local machine name.

Fixed Bugs
• Mac OS X: The default file descriptor limit has been increased to 10240 in the foundryrlmserver start up script.

75
APPENDIX A: RELEASE NOTES |

• BUG ID 47116 - Windows 7 only: The default license and log file paths were incorrect.

Known Issues and Workarounds

There are no known issues in this release.

76
APPENDIX A: RELEASE NOTES | FLT 7.0V5

FLT 7.0v5
This is a maintenance release of FLT.

Release Date
October 2013

System Requirements
• Mac OS X 10.6 (Snow Leopard), 10.7 (Lion), or 10.8 (Mountain Lion), 64-bit only
• Linux RHEL 5.4 or RHEL 6, 32-bit or 64-bit
• Windows XP, Windows 7, or Windows 8, 32-bit or 64-bit

NOTE: These are the operating systems FLT has been tested on. Other operating systems are likely to
work.

New Features
There are no new features in this release.

Feature Enhancements
There are no feature enhancements in this release.

Fixed Bugs
• On rare occasions, the Foundry License Utility (FLU) reported the System ID as "np".
• BUG ID 36568 - The Foundry License Utility (FLU) did not run correctly on Mac OS X 10.9 (Mavericks).

Known Issues and Workarounds

There are no known issues in this release.

77
APPENDIX A: RELEASE NOTES | FLT 7.0V4

FLT 7.0v4
This is a maintenance release of FLT.

Release Date
April 2013

System Requirements
• Mac OS X 10.6 (Snow Leopard) and 10.7 (Lion), 64-bit only
• Linux RHEL 5.4, 32-bit or 64-bit
• Windows XP or Windows 7, 32-bit or 64-bit

NOTE: Other operating systems are likely to work.

New Features
There are no new features in this release.

Feature Enhancements
There are no feature enhancements in this release.

Fixed Bugs
BUG ID 35235 - The Foundry License Utility (FLU) was reporting the port number incorrectly for FLEXlm floating
license installations.

Known Issues and Workarounds

There are no known issues in this release.

FLT 7.0v3
This is a maintenance release of FLT.

78
APPENDIX A: RELEASE NOTES | FLT 7.0V2

Release Date
April 2013

System Requirements
• Mac OS X 10.6 (Snow Leopard) and 10.7 (Lion), 64-bit only
• Linux RHEL 5.4, 32-bit or 64-bit
• Windows XP or Windows 7, 32-bit or 64-bit

NOTE: Other operating systems are likely to work.

New Features
There are no new features in this release.

Feature Enhancements
There are no feature enhancements in this release.

Fixed Bugs
BUG ID 35191 - When Windows machines were connected to a RAID array, the server failed to start due to system
ID conflicts. This was a bug in RLM 9.4 BL3 and earlier. FLT has been updated to use RLM 9.4 BL4, which fixes the
problem.

Known Issues and Workarounds

There are no known issues in this release.

FLT 7.0v2
This is a maintenance release of FLT, with feature enhancements and several bug fixes.

79
APPENDIX A: RELEASE NOTES | FLT 7.0V2

Release Date
October 2012

System Requirements
• Mac OS X 10.6 (Snow Leopard) and 10.7 (Lion), 64-bit only
• Linux RHEL 5.4, 32-bit or 64-bit
• Windows XP or Windows 7, 32-bit or 64-bit

NOTE: Other operating systems are likely to work.

New Features
There are no new features in this release.

Feature Enhancements
• Linux 64-bit only: The RLM server limit on client connections has been increased to 32,000.
• BUG ID 26534 - Generated log output from failed license installs has been improved to help diagnose issues.
• BUG ID 26911 - The FLT installer now lists any files that exist on a target machine that are blocking installation,
such as previous FLT versions.
• BUG ID 30524 - If a license with an invalid ID is supplied, the FLU now reports the expected ID in the error report.
• BUG ID 30527 - The FLU now displays details of how to proceed if more than one System ID is found.

Fixed Bugs
• BUG ID 26331/26920 - It was not possible to copy, cut, or paste from the FLU installation window using keyboard
shortcuts or the right-click menu.
• BUG ID 29154 - Windows 7 only: The port exception instructions were incorrect in the FLT documentation.

Known Issues and Workarounds

There are no known issues in this release.

80
APPENDIX A: RELEASE NOTES | FLT 7.0V1

FLT 7.0v1
This is a major new release of FLT, with several new features and feature enhancements.

Release Date
May 2012

System Requirements
• Mac OS X 10.6 (Snow Leopard) and 10.7 (Lion), 64-bit only
• Linux RHEL 5.4, 32-bit or 64-bit
• Windows XP or Windows 7, 32-bit or 64-bit

NOTE: Other operating systems are likely to work.

New Features
• All functionality previously split between FLT 6.0 and FFT 5.0 is now included in FLT 7.0.
• The Foundry License Utility (FLU) merges all previous utility applications into one. The FLU is fully backwards
compatible, and you can use it to manage existing license servers.
• Both FLEXlm and RLM servers are now installed as one.

Feature Enhancements
• Enhanced license installation reporting.
• Improved diagnostics reporting.
• There is now a command line interface for all operating systems.
• The server log is displayed in the FLU interface and on the command line.

Fixed Bugs
There are no fixed bugs in this release.

Known Issues and Workarounds

There are no known issues in this release.

81
APPENDIX A: RELEASE NOTES | FLT 6.0V4

FLT 6.0v4
This is the fourth release of the Foundry Licensing Tools (FLT) addressing issues that arose during previous builds.

Release Date
October 2011

System Requirements
• Mac OS X (10.5 (Leopard) and 10.6 (Snow Leopard))
• Linux Centos 4.5 (32-bit or 64-bit)
• Windows XP or Windows 7

NOTE: Other operating systems are likely to work.

New Features
There are no new features in this release.

Feature Enhancements
There are no feature enhancements in this release.

Fixed Bugs
• The installer failed to install the RLM License Server on Mac OS 10.7 (Lion). While this bug has been resolved, Mac
OS 10.7 (Lion) is not yet fully supported.
• Linux 64-bit: The license server was unable to cope with more than 1000 simultaneous license checkouts.
• Linux: The default file descriptor limit has been increased to 10240 in the foundryrlmserver start up script.

Known Issues and Workarounds

• BUG ID 23186 - Mac only: RLM License Server is limited to approximately 247 checkouts.

82
APPENDIX A: RELEASE NOTES | FLT 6.0V3

FLT 6.0v3
This is the third release of the Foundry Licensing Tools (FLT) addressing issues that arose during previous builds.

Release Date
November 2010

System Requirements
• Mac OS X (10.5 (Leopard) and 10.6 (Snow Leopard))
• Linux Centos 4.5 (32-bit or 64-bit)
• Windows XP or Windows 7.

NOTE: Other operating systems are likely to work.

New Features
There are no new features in this release.

Feature Enhancements
There are no feature enhancements in this release.

Fixed Bugs
• The default RLM Web Server (5054) and Foundry License Server (5053) ports could cause issues at startup with
other servers present on the network.
To avoid conflicts with other servers that may be present:
• The default RLM Web Server port has changed to 4102.
• The default Foundry License Server port has changed to 4101.
• Setting the foundry_LICENSE_LOG environment variable was being ignored.
• The Foundry License Diagnostic Tool was not correctly determining the status of the server on Linux.
• The Foundry License Diagnostic Tool was not correctly diagnosing client license file issues.

83
APPENDIX A: RELEASE NOTES | FLT 6.0V2

FLT 6.0v2
This was an internal build of the Foundry Licensing Tools (FLT).

Release Date
November 2010

System Requirements
• Mac OS X (10.5 (Leopard) and 10.6 (Snow Leopard))
• Linux Centos 4.5 (32-bit or 64-bit)
• Windows XP or Windows 7.

NOTE: Other operating systems are likely to work.

New Features
There are no new features in this release.

Feature Enhancements
There are no feature enhancements in this release.

Fixed Bugs
This section will contain descriptions of fixed bugs in future releases.

FLT 6.0v1
This is the first release of the Foundry Licensing Tools (FLT).

Release Date
November 2010

84
APPENDIX A: RELEASE NOTES | FLT 6.0V1

System Requirements
• Mac OS X (10.5 (Leopard) and 10.6 (Snow Leopard))
• Linux Centos 4.5 (32-bit or 64-bit)
• Windows XP or Windows 7.

NOTE: Other operating systems are likely to work.

New Features
This section will contain descriptions of new features in future releases.

Feature Enhancements
This section will contain descriptions of feature enhancements in future releases.

Fixed Bugs
This section will contain descriptions of fixed bugs in future releases.

85
Appendix B: License Syntax
This section describes the various syntax requirements for the Foundry Licensing Tools (FLT).

Node Locked License Syntax

FLEXlm
A node locked or uncounted FLEXlm license looks like this:
INCREMENT furnace_ofx_i foundry 3.0 5-jul-2012 \
uncounted HOSTID=000ea641d7a1 ISSUED=5-jun-2012 \
SIGN="03C7 5A34 BDE8 D421 6C2B 8111 8151 972A \
14E2 C143 4C00 741F 730D 784A D392 B1D9 9C3F 03FC \
DB2A E432 5EA7"

Node locked FLEXlm licenses are broken down into nine parts:

INCREMENT - indicates the start of a FLEXlm license feature.

furnace_ofx_i - the product to be licensed. In this example, it is Furnace for Nuke interactive. A background render
license would be furnace_ofx_r.

foundry - the vendor name. All licenses from The Foundry must contain the vendor name foundry.

3.0 - the version number of the product to be licensed. This licenses all features with a version number equal to or
less than 3.0.

For maintenance-based products, such as Nuke, the version number is replaced by the maintenance date. All
releases built before this date will run until the license timeout. All releases built after this date will not run.

5-jul-2012 - the date when the license expires. If this says permanent, the license never expires.

uncounted - this is a node locked license. Floating licenses have a number in place of the uncounted tag.

HOSTID - also known as the System ID, this is the ethernet (mac) address of the machine to be licensed.

ISSUED=5-jun-2012 - the day the license was made, which may differ from the license start date.

86
APPENDIX B: LICENSE SYNTAX | FLOATING LICENSE SYNTAX

SIGN - the encrypted license key. It represents a unique hash of the information in the license and is used to validate
the license.

RLM
A node locked or uncounted RLM license looks like this:
LICENSE foundry katana_i 2012.1006 permanent uncounted hostid=000ea641d7a1 share=h
start=6-oct-2012 issued=6-oct-2012 _ck=fbf430af8c
sig="60PG4515BFTJCYAXSYJ6GTUJ3B9NRRGF3VUUKD022M0BXU48SSESUGSAFJ8BAD5BN883526ETKQ0"

Node locked RLM licenses are broken down into 11 parts:

LICENSE - indicates the start of an RLM license feature.

foundry - the vendor name. All licenses from The Foundry must contain the vendor name foundry.

katana_i - the product to be licensed. In this example, it’s a Katana interactive license. A background render license
would be katana_r.

2012.1006 - the maintenance date. All Katana releases built before this date will run until the license timeout. All
releases built after this date will not run.

For non-maintenance products, this is often just the version of the product, for example 3.0.

permanent - this is a permanent license. If this field were a date 5-jul-2012, it would be a temporary license with
that expiry date.

uncounted - this is a node locked license. Floating licenses have a number in place of the uncounted tag.

hostid - also known as the System ID, this is the ethernet (mac) address of the machine to be licensed.

share - this indicates how multiple checkouts from the same client machine are treated. share=h indicates licenses
are shared by the same host.

start=6-oct-2012 - the date when the license starts. This date may be in the future.

issued - the day the license was made, which may differ from the license start date.

ck and sig - the encrypted license key. It represents a unique hash of the information in the license and is used to
validate the license.

Floating License Syntax

FLEXlm
A floating or counted FLEXlm license looks like this:

87
APPENDIX B: LICENSE SYNTAX | FLOATING LICENSE SYNTAX

SERVER <server_name> <FLEXlm system ID> <server port>

VENDOR foundry OPTIONS=<file> PORT=<vendor port>
INCREMENT nuke_i foundry 2012.1006 5-jul-2012 5 \
START=5-jun-2012 SIGN="00FF 6A1B 735B A476 2069 0A10 6894 4903 \
E2CF A238 7A01 1A15 1808 7BCF 346C F59E 8899 F53C 2B13 E204 C7FD"

Floating licenses are broken down into a SERVER line, a VENDOR line, and one or more INCREMENT lines:

SERVER - the server line indicates which server may serve the floating licenses in this license file:
• <server name>, also known as the hostname, is the name of the license server, for example red.
• <FLEXlm system ID>, also known as lmhostid or the System ID, is a unique number for that machine.
• <server port> is the user-defined server port number over which requests from the client are made to the lmgrd
daemon.

VENDOR - The vendor line indicates which vendor made the license. The vendor line helps decode the license line for
The Foundry's specific licensing keys and identify the vendor licensing daemon.
• OPTIONS=<file> is the plain text file that controls the behavior of the server. Specifying an options file in the
license is optional.
• PORT=<vendor port> is the user-defined port over which the vendor daemon communicates to the client. If left
blank, a port number is picked for you.

NOTE: The server port number and the vendor port number MUST be different.

INCREMENT - license feature line. The only difference from a node locked license is that uncounted is replaced with
the number of available floating licenses.

The above license works on any five hosts simultaneously. It licenses versions of Nuke built before 6 October 2012.
It starts on 5 June 2012 and expires on 5 July 2012.

RLM
A floating or counted RLM license looks like this:
HOST <server_name> <server host id> <port>
ISV foundry <options file> <port>
LICENSE foundry mari_i 2012.1006 permanent 10 share=h start=6-oct-2012 issued=6-oct-
2012 _ck=fb063057fd
sig="60PG451E0VM5S81E5EWRYM8E82CMKYR6SSB93P822M0AT1UU7FWA85M9P34UKXK4HMD7ERG65YA0"

Floating licenses are broken down into a HOST line, an ISV line, and one or more LICENSE lines:

HOST - The host line indicates which server may provide the floating licenses in the license file.
• <server_name>, also known as the hostname, is the name of the license server, for example red.
• <server host id>, also known as the rlmhostid or System ID, is a unique number for that machine.

88
APPENDIX B: LICENSE SYNTAX | CLIENT LICENSE SYNTAX

• <port> is the user-defined server port number over which requests from the client are made to the RLM daemon.

ISV - The ISV line indicates which vendor made the license. The vendor line helps decode the license line for The
Foundry's specific licensing keys and identify the vendor licensing daemon.
• <options file> is the plain text file that controls the behavior of the server. Specifying an options file in the license is
optional.
• <port> is the user-defined port over which the vendor daemon communicates to the client. If left blank, the port
number is picked for you.

NOTE: The host port number and the ISV port number MUST be different, and remember to avoid port
4102, which is reserved for the web server.

LICENSE - license feature line. The only difference from a node locked license is that uncounted is replaced with the
number of available floating licenses and the hostid in omitted from the LICENSE block.

The above license works on any 10 hosts simultaneously. It licenses all Mari releases built before 6 October 2012 and
it begins 6 October 2012.

Client License Syntax

FLEXlm
Client FLEXlm licenses typically have just three lines, which may be:
SERVER <server name> <server host id> <port number>
VENDOR foundry
USE_SERVER

or
SERVER <server_name> any <port number>
VENDOR foundry
USE_SERVER

RLM
Client RLM licenses typically have just one line, which may be:
HOST <server name> <server host id> <port number>

or
HOST <server name> any <port number>

89
Appendix C: FLT Variables
This section describes the environment variables that the Foundry Licensing Tools (FLT) recognize.

Environment Variables FLT Recognizes

There are many occasions when you might need to set an environment variable to tailor the functionality of FLT. The
following table lists the environment variables FLT recognizes.

FLEXlm Environment RLM Environment Description

Variable Variable

FOUNDRY_LICENSE_ foundry_LICENSE Sets the location of the license file.

FILE
If you move your license file, you can set this to point to the
new location.

You can also use this to point client machines to a floating

license on a license server machine.

FOUNDRY_LICENSE_ foundry_LICENSE_ Sets the location of the log file that gets generated if there
LOG LOG are problems with licenses.

90
APPENDIX C: FLT VARIABLES | SETTING ENVIRONMENT VARIABLES

FLEXlm Environment RLM Environment Description

Variable Variable

FOUNDRY_HEARTBEAT_ foundry_HEARTBEAT _ By default, floating licenses are given back to the server only
DISABLE DISABLE if the product exits or is deleted/unloaded from the client. If
you want your license to go back to the server if you don’t
use it for a while, you can set this environment variable to
true.

If you disable the heartbeat, you must also set a TIMEOUT

value in the options file, so that licenses are returned to the
server correctly. See Setting a TIMEOUT or TIMEOUTALL
Period.

NOTE: The heartbeat ensures the communication

between the server and client persists in a stable
fashion and therefore should be disabled with
caution, otherwise users may find their licenses
being withdrawn unexpectedly.

Setting Environment Variables

Of course, how you set environment variables differs for each operating system. Here’s a brief guide if you can’t find
your systems administrator.

NOTE: In the following examples, we describe setting an environment variable for an RLM-based license.
This is done using the environment variable foundry_LICENSE; however, if your product uses FLEXlm
licensing, the environment variable you need to set is FOUNDRY_LICENSE_FILE. All other steps are exactly
the same.

Windows
1. Go to Start > Control Panel > System and Security > System.
2. Click Advanced system settings in the left-hand panel and then the Environment Variables button. You
can specify system-wide variables that all users will pick up or user variables to restrict the environment variable
to one particular user.
3. Click on New and enter the variable name and value.

91
APPENDIX C: FLT VARIABLES | SETTING ENVIRONMENT VARIABLES

Mac OS X
You can easily set an environment variable that is active in one terminal only:
1. The procedure for setting an environment variable depends on what your default shell is. To get the name of the
shell you are using, launch a terminal (Applications > Utilities > Terminal) and enter:
echo $SHELL.
2. Depending on the output of the previous step, do one of the following:
• If your shell is a csh or tcsh shell, enter:
setenv foundry_LICENSE /tmp/foundry.lic
• If your shell is a bash or ksh shell, enter:
export foundry_LICENSE=/tmp/foundry.lic

You then need to run the product from the same terminal that you used to set the environment variable. If you
open another terminal, this environment variable is not set in that terminal unless you type it in there too.

For a more permanent solution, you can set an environment variable for all processes launched by a specific user by
creating an environment file in the user’s home directory:
~/.MacOSX/environment.plist

NOTE: The tilde ( ~ ) represents the home directory of the target user, and the command is case sensitive,
so take care to copy the string exactly.

You have to create the .MacOSX directory yourself using a terminal (by typing mkdir .MacOSX in your home
directory). You also have to create the environment file yourself. The environment file is actually in XML/plist format
(make sure to add the .plist extension to the end of the filename or this won't work). An example environment file is
shown below. The file can be created using /Developer/Applications/Utilities/PropertyListEditor.app or you
can use a text editor if you’re careful with the formatting. We can also send you one if you wish.
<?xml version="1.0" encoding="UTF-8"?>

92
APPENDIX C: FLT VARIABLES | SETTING ENVIRONMENT VARIABLES

<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN"

"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>foundry_LICENSE</key>
<string>/tmp/foundry.lic</string>
</dict>
</plist>

In this case we set the environment variable foundry_LICENSE to /tmp/foundry.lic. Note also that the environment
variable is only active once you’ve logged out and logged back in.

Linux
1. The procedure for setting an environment variable depends on what your default shell is. To get the name of the
shell you are using, launch a shell and enter:
echo $SHELL.
2. Depending on the output of the previous step, do one of the following:
• If your shell is a csh or tcsh shell, enter:
setenv foundry_LICENSE /tmp/foundry.lic
• If your shell is a bash or ksh shell, enter:
export foundry_LICENSE=/tmp/foundry.lic
3. You then need to run the product from the same terminal that you used to set the environment variable. If you
open another terminal, this environment variable is not set in that terminal unless you type it in there too.
4. To make this permanent for any shell launched, you can edit your .cshrc, .tcshrc, .bashrc, or .kshrc file in your
home directory.
5. If you want it to be system wide, then /etc/profile can be used (or /etc/environment on some flavors of
Linux).

93
Appendix D: EULA

End User License Agreement (EULA)

PLEASE READ THIS EULA CAREFULLY BEFORE ORDERING OR DOWNLOADING OR USING ANY SOFTWARE
PRODUCTS OF THE FOUNDRY. YOUR ATTENTION IS PARTICULARLY DRAWN TO CLAUSES 12 AND 13 WHERE WE
LIMIT OUR LIABILITY TO USERS OF OUR SOFTWARE PRODUCTS.

IMPORTANT NOTICE TO ALL USERS: BY DOWNLOADING AND/OR USING THIS SOFTWARE YOU ACKNOWLEDGE
THAT YOU HAVE READ THIS EULA, UNDERSTAND IT AND AGREE TO BE BOUND BY ITS TERMS AND CONDITIONS. IF
YOU DO NOT AGREE TO THE TERMS OF THIS EULA DO NOT DOWNLOAD, INSTALL, COPY OR USE THE SOFTWARE.

IMPORTANT NOTICE TO CONSUMERS WHO PURCHASE SOFTWARE PRODUCTS DIRECT FROM THE FOUNDRY: YOU
HAVE THE RIGHT TO WITHDRAW FROM YOUR TRANSACTION WITH THE FOUNDRY WITHOUT CHARGE AND
WITHOUT REASON AT ANY TIME BEFORE DOWNLOADING OUR SOFTWARE PRODUCT(S). HOWEVER YOU WILL LOSE
THIS RIGHT ONCE YOU BEGIN TO DOWNLOAD OUR SOFTWARE PRODUCT(S). THIS DOES NOT AFFECT YOUR
CONSUMER RIGHTS IN RELATION TO DEFECTIVE PRODUCTS OR SERVICES.

This END USER LICENSE AGREEMENT ("EULA") is, in cases where you purchase our product(s) direct from The
Foundry, incorporated into the agreement between The Foundry Visionmongers Limited, a company registered in
England and Wales, ("The Foundry"), and you, as either an individual or a single company or other legal entity
("Licensee") on the terms of which you will purchase the products and services of The Foundry (the “Agreement”).
In cases where you purchase our product(s) from one of our resellers, the use of the term “Agreement” in this EULA
refers to the arrangements between The Foundry and Licensee on which Licensee is permitted to use The Foundry’s
product(s), including this EULA.

The Foundry reserves the right to refuse to grant a License (as defined in clause 1.1) to any Licensee who has failed
to pay any sum due either to The Foundry or to a reseller of The Foundry either in connection with the Agreement or
in connection with any other software license to use any Software product(s) of The Foundry.

1. GRANT OF LICENSE

1.1 Subject to the limitations of clause 3 and all the other terms of the Agreement, The Foundry grants to Licensee a
limited, non-transferable (subject to clause 2.1(b) below) and non-exclusive license to download, install and use a
machine readable, object code version (subject to clauses 3 and 4 below) of the software program(s) purchased by

94
APPENDIX D: EULA |

Licensee (the "Software") and any accompanying user guide and other documentation (the "Documentation"),
solely for Licensee's own internal purposes (the "License"); provided, however, that Licensee's right to download,
install and use the Software and the Documentation is limited to those rights expressly set out in this EULA.

1.2 Some types of license models set out in clause 2.1 limit the installation and use of the Software to the country in
which Licensee is based at the date of purchase (the “Home Country”), unless otherwise agreed in writing.
Notwithstanding such limits, Licensee may still use the Software outside the Home Country if traveling or working
outside the Home Country on a temporary basis provided that such use does not exceed 70 days in aggregate in any
rolling twelve month period or, in the case of any license which lasts for less than twelve months, does not exceed
the number of days representing 20% of the term of the license.

1.3 Only to the extent that is proportionate to, and reasonably necessary to support, Licensee’s licensed use of the
Software in accordance with the Agreement, Licensee may (provided valid license keys have been obtained) install
the Software on more than one computer, provided always that Licensee’s concurrent use of different installations
of the Software does not exceed the number of valid Licenses that Licensee has paid for or licensed (as applicable).

2. LICENSE MODELS

2.1 For each Software product purchased from The Foundry, the License will be one of the following types of license,
and subject to the following terms and conditions. Please note that some licensing models set out below do not
apply to certain Software products of The Foundry. Whichever licensing model applies, Licensee shall not at any one
time use more copies of the Software than the total number of valid licenses purchased or licensed by Licensee (as
applicable).

(a) “Node Locked License”

If Licensee purchases a Node Locked License, Licensee will install and use only a single copy of the Software on only
one computer at a time, which may be located anywhere in the Home Country.

(b) “Individual License”

If Licensee purchases an Individual License, Licensee warrants and represents that Licensee is a natural person and
that only Licensee will use the Software. Licensee may transfer or assign (“transfer”) the Individual License to
another natural person (“Assignee”) subject to Licensee: (i) notifying The Foundry of such transfer and obtaining
The Foundry’s express written consent, (ii) paying an administrative fee with respect to such transfer as may be
required by The Foundry, and (iii) after transferring a single copy of the Software to the Assignee, deleting any copies
of the Software that Licensee may have in Licensee’s possession, custody or power. An Individual License entitles
Licensee to use the Software on only one computer at a time, which may be located anywhere and is not restricted
to the Home Country.

(c) “Floating License”

If Licensee purchases a Floating License, use of the Software may be at any site in the Home Country.

(d) “Login-Based License”

95
APPENDIX D: EULA |

If Licensee purchases a Login-Based License, Licensee warrants and represents that Licensee is a natural person and
that only Licensee shall use the Software. Licensee will be issued with log in details and may use the Software on any
number of computers (but not simultaneously).

2.2 Some of the Software may be made available at concessionary rates or free of charge (as applicable) as follows:

(a) “Educational License”

If Licensee has purchased the Software on the discounted terms of The Foundry’s Educational Policy published on its
website (the “Educational Policy”), Licensee warrants and represents to The Foundry as a condition of the
Educational License that: (i) (if Licensee is a natural person) he or she is a part-time or full-time student at the time of
purchase and will not use the Software for any commercial, professional or for-profit purposes; (ii) (if the Licensee is
not a natural person) it is an organization that will use the Software only for the purpose of training and instruction,
and for no other purpose, and (iii) Licensee will at all times comply with the Educational Policy (as such policy may be
amended from time to time). Unless the Educational License is a Floating License, Licensee shall use the Software on
only one computer at a time.

(b) “Non-Commercial License”

If the License is a Non-Commercial License, Licensee warrants and represents that Licensee is a natural person, that
they will only access and/or use one copy of a Non-Commercial License for personal, recreational and non-
commercial purposes and that only Licensee will use the Software. Under a Non-Commercial License, Licensee will
not use the Software: (a) in conjunction with any other copies or versions of the Software, under any type of License
model; (b) for any commercial, professional, for-profit and/or on-sale purpose or otherwise to provide any
commercial service(s) to a third party (whether or not for financial or other reward and including for education,
instruction of or demonstration to any third party for commercial purposes); (c) in the course of any employment or
business undertaking of Licensee; (d) on any commercial premises during business hours (except where use of the
Software is solely for a personal, recreational, educational or other non-commercial purpose); and/or (e) to create
any commercial tools or plug ins.

(c) “MODO Steam Edition”

A version of MODO with limited functionality as described in the Documentation is available to purchase on discount
terms through Valve Corporation’s Steam store. If Licensee has purchased such version, Licensee warrants and
represents to The Foundry as a condition of the Agreement that: (i) Licensee is a natural person; and (ii) Licensee will
use the Software strictly through Steam and only for personal, recreational and non-commercial use, except only
that if Licensee uses the Software to create assets and content Licensee may sell such assets and content through
Valve’s Steam Workshop.

(d) “MODO indie” and “MARI indie”

Variants of MODO and MARI with limited functionality as described in the Documentation are available to purchase
on discount terms through Valve Corporation’s Steam store. If Licensee has purchased such a variant, Licensee
warrants and represents to The Foundry as a condition of the Agreement that: (i) Licensee is a natural person; or (ii)
Licensee is an entity in the direct ownership of a single natural person; (iii) Licensee will only access and/or use one
copy of either variant; and (iv) only Licensee will use the Software.

96
APPENDIX D: EULA |

(e) “Trial License”

Licensee may register for a “Trial License” of the Software (not available for all products or in all regions or markets).
A Trial License lasts a limited specified period on the expiry of which the Software will automatically cease to
function. Licensee will use the Software on only one computer at a time.

(f) “Free License”

Licensee may register for a “Free License” of selected Software from The Foundry (not available for all Software
products or in all regions or markets). A Free License lasts for a limited specified period on the expiry of which the
Software will cease to function. Usually, a replacement License to cover a new, time limited, period will be issued by
The Foundry. Licensee will use the Software under a Free License on only one computer at a time.

(g) “Personal Learning Edition License”

If the Software is a Personal Learning Edition (“PLE”), it will not require a license key to be issued to Licensee and will
have limited functionality as described in the Documentation. Licensee may use it only for the purpose of personal
or internal training and instruction, and for no other purpose. PLE versions of the Software may not be used for
commercial, professional or for-profit purposes including, for the avoidance of doubt, the purpose of providing
training or instruction to third parties. Licensee shall use the Software on only one computer at a time.

2.3 If Licensee has purchased a License that permits “non-interactive” use of the Software (“Headless Rendering”),
Licensee is authorized to use a non-interactive version of the Software for rendering purposes only (i.e. without a
user, in a non-interactive capacity) and shall not use such Software on workstations or otherwise in a user-interactive
capacity. Headless Rendering is not available on all products. In all cases except MODO (in respect of which there is
no limit on the amount of Headless Rendering allowed), Headless Rendering licenses are limited to one computer
such that the number of computers on which Headless Rendering can be carried out is limited to the number of valid
Licenses that have been purchased.

3. RESTRICTIONS ON USE

Please note that in order to guard against unlicensed use of the Software, a license key is required to
access and enable the Software (other than Software which is licensed under the Personal Learning Edition
model – see clause 2.2 (g) above). Licensee is authorized to use the Software in machine readable, object code form
only (subject to clause 4), and Licensee shall not: (a) assign, sublicense, sell, distribute, transfer, pledge, lease, rent,
lend, share or export the Software, the Documentation or Licensee's rights under this EULA; (b) alter or circumvent
the license keys or other copy protection mechanisms in the Software or reverse engineer, decompile, disassemble or
otherwise attempt to discover the source code of the Software; (c) (subject to clause 4) modify, adapt, translate or
create derivative works based on the Software or Documentation; (d) use, or allow the use of, the Software or
Documentation on any project other than a project produced by Licensee (an "Authorized Project") or to provide a
service (whether or not any charge is made) to any third party; (e) allow or permit anyone (other than Licensee and
Licensee's authorized employees to the extent they are working on an Authorized Project) to use or have access to
the Software or Documentation; (f) copy or install the Software or Documentation other than as expressly provided
for in this EULA; or (g) take any action, or fail to take action, that could adversely affect the trademarks, service
marks, patents, trade secrets, copyrights or other intellectual property rights of The Foundry or any third party with

97
APPENDIX D: EULA |

intellectual property rights in the Software (each, a "Third Party Licensor"). For purposes of this clause 3, the term
"Software" shall include any derivatives of the Software.

Unless Licensee has purchased an Individual License or a Login-Based License, if the Software is moved from one
computer to another, the issuing of replacement or substituted license keys is subject to and strictly in accordance
with The Foundry’s License Transfer Policy, which is available on The Foundry’s website and which requires a fee to be
paid in certain circumstances. The Foundry may from time to time and at its sole discretion vary the terms and
conditions of the License Transfer Policy.

4. SOURCE CODE

Notwithstanding that clause 1 defines “Software” as an object code version and that clause 3 provides that Licensee
may use the Software in object code form only:

4.1 if The Foundry has agreed to license to Licensee (including by way of providing SDKs, upgrades, updates or
enhancements/customization) source code or elements of the source code of the Software, the intellectual property
rights in which belong either to The Foundry or to a Third Party Licensor (“Source Code”), Licensee shall be licensed
to use the Source Code as Software on the terms of this EULA and: (a) notwithstanding clause 3 (c), Licensee may use
the Source Code at its own risk in any reasonable way for the limited purpose of enhancing its use of the Software
solely for its own internal business purposes and in all respects in accordance with this EULA; (b) Licensee shall in
respect of the Source Code comply strictly with all other restrictions applying to its use of the Software under this
EULA as well as any other restriction or instruction that is communicated to it by The Foundry at any time during the
Agreement (whether imposed or requested by The Foundry or by any Third Party Licensor);

4.2 to the extent that the Software links to any open source software libraries (“OSS Libraries”) that are provided to
Licensee with the Software, nothing in the Agreement shall affect Licensee’s rights under the licenses on which the
relevant Third Party Licensor has licensed the OSS Libraries, as stated in the Documentation. To the extent that Third
Party Licensors have licensed OSS Libraries on the terms of v2.1 of the Lesser General Public License issued by the
Free Software Foundation (see http://www.gnu.org/licenses/lgpl-2.1.html) (the “LGPL”), those OSS Libraries are
licensed to Licensee on the terms of the LGPL and are referred to in this clause 4.2 as the LGPL Libraries. The
Foundry will at any time during the three year period starting on the date of the Agreement, at the request of
Licensee and subject to Licensee paying to The Foundry a charge that does not exceed The Foundry’s costs of doing
so, provide Licensee with the source code of the LGPL Libraries (the “LGPL Source”) in order that Licensee may
modify the LGPL Libraries in accordance with the LGPL, together with certain object code of the Software necessary
to enable Licensee to re-link any modified LGPL Library to the Software (the “Object”); and

4.3 notwithstanding any other term of the Agreement, The Foundry gives no express or implied warranty,
undertaking or indemnity whatsoever in respect of the Source Code, the OSS Libraries (including the LGPL Libraries),
the LGPL Source or the Object, all of which are licensed on an “as is” basis, or in respect of any modification of the
Source Code, the OSS Libraries (including the LGPL Libraries) or the LGPL Source made by Licensee (“Modification”).
Licensee may not use the Object for any purpose other than its use of the Software in accordance with this EULA.
Notwithstanding any other term of the Agreement, The Foundry shall have no obligation to provide support,
maintenance, upgrades or updates of or in respect of any of the Source Code, the OSS Libraries (including the LGPL
Libraries), the LGPL Source, the Object or any Modification. Licensee shall indemnify The Foundry against all liabilities

98
APPENDIX D: EULA |

and expenses (including reasonable legal costs) incurred by The Foundry in relation to any claim asserting that any
Modification infringes the intellectual property rights of any third party.

5. BACK-UP COPY

Licensee may store one copy of the Software and Documentation off-line and off-site in a secured location within
the Home Country that is owned or leased by Licensee in order to provide a back-up in the event of destruction by
fire, flood, acts of war, acts of nature, vandalism or other incident. In no event may Licensee use the back-up copy of
the Software or Documentation to circumvent the usage or other limitations set forth in this EULA.

6. OWNERSHIP

Licensee acknowledges that the Software (including, for the avoidance of doubt, any Source Code that is licensed to
Licensee) and Documentation and all related intellectual property rights and other proprietary rights are and shall
remain the sole property of The Foundry and the Third Party Licensors. Licensee shall not remove, or allow the
removal of, any copyright or other proprietary rights notice included in and on the Software or Documentation or
take any other action that could adversely affect the property rights of The Foundry or any Third Party Licensor. To
the extent that Licensee is authorized to make copies of the Software or Documentation under this EULA, Licensee
shall reproduce in and on all such copies any copyright and/or other proprietary rights notices provided in and on
the materials supplied by The Foundry hereunder. Nothing in the Agreement shall be deemed to give Licensee any
rights in the trademarks, service marks, patents, trade secrets, confidential information, copyrights or other
intellectual property rights of The Foundry or any Third Party Licensor, and Licensee shall be strictly prohibited from
using the name, trademarks or service marks of The Foundry or any Third Party Licensor in Licensee's promotion or
publicity without The Foundry's prior express written approval.

Subject to clause 4.3, The Foundry undertakes (the “Undertaking”) to defend Licensee or at The Foundry’s option
settle any claim brought against Licensee alleging that Licensee’s possession or use of the Software or
Documentation in accordance with the Agreement infringes the intellectual property rights of a third party in the
same country as Licensee (“Claim”) and shall reimburse all reasonable losses, damages, costs (including reasonable
legal fees) and expenses incurred by or awarded against Licensee in connection with any such Claim, provided that
the Undertaking shall not apply where the Claim in question is attributable to possession or use of the Software or
Documentation other than in accordance with the Agreement, or in combination with any hardware, software or
service not supplied or specified by The Foundry. The Undertaking is conditional on Licensee giving written notice of
the Claim to The Foundry as soon as reasonably possible, cooperating in the defence of the Claim and not making
any admission of liability or taking any step prejudicial to the defence of the Claim. If any Claim is made, or in The
Foundry's reasonable opinion is likely to be made, against Licensee, The Foundry may at its sole option and expense
(a) procure for Licensee the right to continue using the Software, (b) modify the Software so that it ceases to be
infringing, (c) replace the Software with non-infringing software, or (d) terminate the Agreement immediately by
notice in writing to Licensee and refund the License Fee (less a reasonable sum in respect of Licensee's use of the
Software to the date of termination) on return of the Software and all copies by Licensee. The Undertaking
constitutes Licensee's exclusive remedy and The Foundry's only liability in respect of any Claim.

99
APPENDIX D: EULA |

7. LICENSE FEE

7.1 Licensee acknowledges that (subject to clause 7.2) the rights granted to Licensee under this EULA are conditional
on Licensee's payment in full of the license fee payable in connection with the Agreement or, as the case may be,
payable to The Foundry’s reseller (the "License Fee").

7.2 In the cases of Non-Commercial NUKE, Trial Licenses and Free Licenses, for the avoidance of doubt, the fact that
no License Fee may be payable shall not be construed as a waiver by The Foundry of any right or remedy available to
it in relation to any breach by Licensee of this EULA or the Agreement, or of any other right or remedy arising under
applicable law, all of which are expressly reserved.

8. UPGRADES/ENHANCEMENTS

If the Licensee has paid an annually renewable fee for access to support, upgrades and updates for the Software
("Annual Upgrade and Support Programme"), this Agreement is subject to the terms and conditions for the
Annual Upgrade and Support Programme available on The Foundry's website. The Foundry may from time to time
and at its sole discretion vary the terms and conditions of the Annual Upgrade and Support Programme. The Annual
Upgrade and Support Programme is not available for all Software license types and variations.

9. TAXES AND DUTIES

Licensee agrees to pay, and indemnify The Foundry from claims for, any local, state or national tax (exclusive of taxes
based on net income), duty, tariff or other impost related to or arising from the transaction contemplated by the
Agreement.

10. LIMITED WARRANTY

10.1 Subject to clause 10.3, The Foundry warrants that, for a period of ninety (90) days after Licensee first
downloads the Software (“Warranty Period”): (a) the Software will, when properly used on an operating system for
which it was designed, perform substantially in accordance with the functions described in the Documentation; and
(b) that the Documentation correctly describes the operation of the Software in all material respects. If, within the
Warranty Period, Licensee notifies The Foundry in writing of any defect or fault in the Software as a result of which it
fails to perform substantially in accordance with the Documentation, The Foundry will, at its sole option, either repair
or replace the Software, provided that Licensee makes available all the information that may be necessary to
identify, recreate and remedy the defect or fault. This warranty will not apply to any defect or fault caused by
unauthorised use of or any amendment made to the Software by any person other than The Foundry. If Licensee is
a consumer, the warranty given in this clause is in addition to Licensee’s legal rights in relation to any Software or
Documentation that is faulty or not as described.

10.2 The Foundry does not warrant that the Software or Documentation will meet Licensee's requirements or that
Licensee's use of the Software will be uninterrupted or error free.

100
APPENDIX D: EULA |

10.3 If Licensee purchases a license of the Software that is of a fixed term duration, the Warranty Period in clause
10.1 shall apply only to Licensee’s first purchase of such license and not to any subsequent renewal(s) even if a
renewal involves another download.

11. INDEMNIFICATION

Licensee agrees to indemnify, hold harmless and defend The Foundry, the Third Party Licensors and The Foundry's
and each Third Party Licensor’s respective affiliates, officers, directors, shareholders, employees, authorized resellers,
agents and other representatives from all claims, defence costs (including, but not limited to, legal fees), judgments,
settlements and other expenses arising from or connected with any claim that any authorised or unauthorised
modification of the Software or Documentation by Licensee or any person connected with Licensee infringes the
intellectual property rights or other proprietary rights of any third party.

12. LIMITATION OF LIABILITY TO BUSINESS USERS

This clause applies where Licensee is a business user. Licensee acknowledges that the Software has not been
developed to meet its individual requirements, and that it is therefore Licensee’s responsibility to ensure that the
facilities and functions of the Software as described in the Documentation meet such requirements. The Software
and Documentation is supplied only for Licensee’s internal use for its business, and not for any re-sale purposes or
for the provision of the Software (whether directly or indirectly) to third parties. The Foundry shall not under any
circumstances whatever be liable to Licensee, its affiliates, officers, directors, shareholders, employees, agents or
other representatives, whether in contract, tort (including negligence), breach of statutory duty, or otherwise, arising
under or in connection with the Agreement for loss of profits, sales, business, or revenue, business interruption, loss
of anticipated savings, loss or corruption of data or information, loss of business opportunity, goodwill or reputation
or any indirect or consequential loss or damage. In respect of any other losses, The Foundry’s maximum aggregate
liability under or in connection with the Agreement whether in contract, tort (including negligence) or otherwise, shall
in all circumstances be limited to the greater of US$5,000 (five thousand USD) and a sum equal to the License Fee.
Nothing in the Agreement shall limit or exclude The Foundry’s liability for death or personal injury resulting from our
negligence, fraud or fraudulent misrepresentation or for any other liability that cannot be excluded or limited by
applicable law. This EULA sets out the full extent of our obligations and liabilities in respect of the supply of the
Software and Documentation. Except as expressly stated in this EULA, there are no conditions, warranties,
representations or other terms, express or implied, that are binding on The Foundry. Any condition, warranty,
representation or other term concerning the supply of the Software and Documentation which might otherwise be
implied into, or incorporated in, the Agreement, whether by statute, common law or otherwise, is excluded to the
fullest extent permitted by law.

13. LIMITATION OF LIABILITY TO CONSUMERS

This clause applies where Licensee is a consumer. Licensee acknowledges that the Software has not been developed
to meet Licensee’s individual requirements, and that it is therefore Licensee’s responsibility to ensure that the
facilities and functions of the Software as described in the Documentation meet such requirements. The Software
and Documentation are only supplied for Licensee’s domestic and private use. Licensee agrees not to use the
Software and Documentation for any commercial, business or re-sale purposes, and The Foundry has no liability to

101
APPENDIX D: EULA |

Licensee for any loss of profit, loss of business, business interruption, or loss of business opportunity. The Foundry
is only responsible for loss or damage suffered by Licensee that is a foreseeable result of The Foundry’s breach of the
Agreement or its negligence but The Foundry is not responsible for any loss or damage that is not foreseeable. Loss
or damage is foreseeable if they were an obvious consequence of a breach or if they were contemplated by Licensee
and The Foundry at the time of forming the Agreement. Our maximum aggregate liability under or in connection
with the Agreement, whether in contract, tort (including negligence) or otherwise, shall in all circumstances be limited
to a sum equal to the greater of US$5,000 (five thousand USD) and a sum equal to the License Fee. Nothing in the
Agreement shall limit or exclude The Foundry’s liability for death or personal injury resulting from our negligence,
fraud or fraudulent misrepresentation or for any other liability that cannot be excluded or limited by applicable law.

14. TERM; TERMINATION

14.1 The Agreement is effective upon Licensee's download of the Software, and the Agreement will remain in effect
until termination or expiry. Licensee may terminate the Agreement on written notice to The Foundry if The Foundry
is in breach of this Agreement and fails to cure the breach within 10 (ten) working days of receiving notice of such
breach. If Licensee breaches the Agreement, The Foundry may terminate the License immediately by notice to
Licensee.

14.2 If the Agreement expires or is terminated, the License will cease immediately and Licensee will immediately
cease use of any Software and Documentation and either return to The Foundry all copies of the Software and
Documentation in Licensee's possession, custody or power or, if The Foundry directs in writing, destroy all such
copies. In the latter case, if requested by The Foundry, Licensee shall provide The Foundry with a certificate
confirming that such destruction has been completed.

14.3 The Foundry reserves the right to terminate and/or suspend the License as it deems reasonable in its sole
discretion by notice to Licensee if it becomes aware that Licensee has failed to pay any sum due either to The
Foundry or to a reseller of The Foundry either in connection with the Agreement or in connection with any other
Software license to use any product(s) of The Foundry or the Licensee is otherwise in breach of or fails to comply
with any term of the Agreement.

14.4 The Foundry may also terminate this EULA if Licensee becomes subject to bankruptcy proceedings, becomes
insolvent, or makes an arrangement with Licensee’s creditors. This EULA will terminate automatically without further
notice or action by The Foundry if Licensee goes into liquidation.

15. CONFIDENTIALITY

Licensee agrees that the Software (including, for the avoidance of doubt, any Source Code that is licensed to
Licensee) and Documentation are proprietary to and the confidential information of The Foundry or, as the case
may be, the Third Party Licensors, and that all such information and any related communications (collectively,
"Confidential Information") are confidential and a fundamental and important trade secret of The Foundry and/or
the Third Party Licensors. If Licensee is a business user, Licensee shall disclose Confidential Information only to
Licensee's employees who are working on an Authorized Project and have a "need-to-know" such Confidential
Information, and shall advise any recipients of Confidential Information that it is to be used only as expressly
authorized in the Agreement. Licensee shall not disclose Confidential Information or otherwise make any

102
APPENDIX D: EULA |

Confidential Information available to any other of Licensee's employees or to any third parties without the express
written consent of The Foundry. Licensee agrees to segregate, to the extent it can be reasonably done, the
Confidential Information from the confidential information and materials of others in order to prevent commingling.
Licensee shall take reasonable security measures, which measures shall be at least as great as the measures Licensee
uses to keep Licensee's own confidential information secure (but in any case using no less than a reasonable degree
of care), to hold the Software, Documentation and any other Confidential Information in strict confidence and safe
custody. The Foundry may request, in which case Licensee agrees to comply with, certain reasonable security
measures as part of the use of the Software and Documentation. This clause shall not apply to any information that
is in or comes into the public domain, or was in Licensee’s lawful possession before receipt or which Licensee
develops independently and without breach of this clause. Licensee acknowledges that monetary damages may not
be a sufficient remedy for unauthorized disclosure of Confidential Information, and that The Foundry shall be
entitled, without waiving any other rights or remedies, to such injunctive or other equitable relief as may be deemed
proper by a court of competent jurisdiction.

16. INSPECTION AND INFORMATION

16.1 Unless Licensee is a consumer, Licensee shall advise The Foundry on demand of all locations where the
Software or Documentation is used or stored. Licensee shall permit The Foundry or its authorized agents to audit all
such locations during normal business hours and on reasonable advance notice.

16.2 The Software may include mechanisms to collect limited information from Licensee’s computer(s) and transmit
it to The Foundry. Such information (the “Information”) may include details of Licensee’s hardware, details of the
operating system(s) in use on such hardware and the profile and extent of Licensee’s use of the different elements of
the Software. The Foundry may use the Information to (a) model the profiles of usage, hardware and operating
systems in use collectively across its customer base in order to focus development and support, (b) to provide
targeted support to individual customers, (c) to ensure that the usage of the Software by Licensee is in accordance
with the Agreement and does not exceed any user number or other limits on its use, and (d) to advise Licensee about
service issues such as available upgrades and maintenance expiry dates. To the extent that any Information is
confidential to Licensee it shall be treated as such by The Foundry when so notified or identified by Licensee when
the Information is first provided to The Foundry (whether verbally or in written form). To the extent that any
Information constitutes personal data for the purposes of the Data Protection Act 1998 it shall be processed by The
Foundry in accordance with that Act and with The Foundry’s Privacy Policy (see
http://www.thefoundry.co.uk/privacy/). Licensee undertakes to make all of users of the Software aware of the uses
which The Foundry will make of the Information and of the terms of The Foundry’s Privacy Policy.

17. U.S. GOVERNMENT LICENSE RIGHTS

All Software, including all components thereof, and Documentation qualify as “commercial items,” as that term is
defined at Federal Acquisition Regulation (“FAR”) (48 C.F.R.) 2.101, consisting of “commercial computer software”
and “commercial computer software documentation” as such terms are used in FAR 12.212. Consistent with FAR
12.212 and DoD FAR Supp. 227.7202-1 through 227.7202-4, and notwithstanding any other FAR or other
contractual clause to the contrary in any agreement into which this Agreement may be incorporated, a government
end user will acquire the Software and Documentation with only those rights set forth in this Agreement. Use of
either the Software or Documentation or both constitutes agreement by the government that all Software and

103
APPENDIX D: EULA |

Documentation are “commercial computer software” and “commercial computer software documentation,” and
constitutes acceptance of the rights and restrictions herein. The Software is the subject of the following notices:

* Unpublished-rights reserved under the Copyright Laws of the United Kingdom.

18. SURVIVAL.

Clause 6 and clauses 9 to 20 inclusive shall survive any termination or expiration of the Agreement.

19. IMPORT/EXPORT CONTROLS

To the extent that any Software made available under the Agreement is subject to restrictions upon export and/or
re-export from the United States, Licensee agrees to comply with, and not act or fail to act in any way that would
violate, applicable international, national, state, regional or local laws and regulations, including, without limitation,
the U.S. Export Administration Act and the Export Administration Regulations, the regulations of the U.S.
Department of Treasury Office of Foreign Assets Control, and the International Traffic in Arms regulations
(collectively, “U.S. Export Laws”), and the United States Foreign Corrupt Practices Act, as those laws may be
amended or otherwise modified from time to time, and neither The Foundry nor Licensee shall be required under
the Agreement to act or fail to act in any way which it believes in good faith will violate any such laws or regulations.
Without limiting the foregoing, Licensee agrees that it will not export or re-export, directly or indirectly, The Foundry’s
Software or related products and services, or any commodity, technology, technical data, software or service that
incorporates, contains or is a direct product of The Foundry’s Software, products and/or services, (i) in violation of
the U.S. Export Laws; (ii) to any country for which an export license or other governmental approval is required at
the time of export, without first obtaining all necessary export licenses or other approvals; (iii) to any country, or
national or resident of a country, to which trade is embargoed by the United States; (iv) to any person or firm on any
government agency’s list of blocked, denied or barred persons or entities, including but not limited to the U.S.
Department of Commerce’s Denied Persons List and Entities List, and the U.S Treasury Department’s Specially
Designated Nationals List; or (v) for use in any nuclear, chemical or biological weapons, or missile technology end-use
unless authorized by the U.S. Government by regulation or specific license.

20. MISCELLANEOUS

Unless Licensee is a consumer, the Agreement is the exclusive agreement between the parties concerning its subject
matter and supersedes any and all prior oral or written agreements, negotiations, or other dealings between the
parties concerning such subject matter. Licensee acknowledges that Licensee has not relied upon any representation
or collateral warranty not recorded in the Agreement inducing it to enter into the Agreement. The Agreement may be
modified only in writing, by The Foundry, at any time. The failure of either party to enforce any rights granted under
the Agreement or to take action against the other party in the event of any such breach shall not be deemed a waiver
by that party as to subsequent enforcement of rights or subsequent actions in the event of future breaches. The
Agreement and any dispute or claim arising out of or in connection with it or its subject matter or formation
(including, unless Licensee is a consumer, non-contractual disputes or claims) shall be governed by, and construed in
accordance with English Law and the parties irrevocably submit to the non-exclusive jurisdiction of the English

104
APPENDIX D: EULA |

Courts, subject to any right that a consumer may have to bring proceedings or to have proceedings brought against
them in a different jurisdiction.

If The Foundry fails to insist that Licensee performs any obligation under the Agreement, or delays in doing so, that
will not mean that The Foundry has waived its rights.

Unless Licensee is a consumer, Licensee agrees that The Foundry may refer to Licensee as a client or a user of the
Software, may display its logo(s) for this purpose and may publish quotations and testimonials from Licensee, its
directors, partners, officers or employees. The Foundry agrees to promptly cease any such use on Licensee’s written
request.

The Foundry and Licensee intend that each Third Party Licensor may enforce against Licensee under the Contracts
(Rights of Third Parties) Act 1999 (the “Act") any obligation owed by Licensee to The Foundry under this EULA that is
capable of application to any proprietary or other right of that Third Party Licensor in or in relation to the Software.
The Foundry and Licensee reserve the right under section 2(3)(a) of the Act to rescind, terminate or vary this EULA
without the consent of any Third Party Licensor.

21. COMPLAINTS & ONLINE DISPUTE RESOLUTION PLATFORM

We hope that you are satisfied with any Software purchase made or service received from The Foundry, but if you
have a complaint, in the first instance, please contact us on info@thefoundry.co.uk or through our Support Portal:
https://supportportal.thefoundry.co.uk/hc/en-us (for technical support and bug reports), or you can request a call
back from the Sales team here: https://www.thefoundry.co.uk/about-us/contact-us/. We will do our best to resolve
the issue but if you are still not happy with our response, you may seek to resolve it using the Online Dispute
Resolution Platform at www.ec.europa.eu/consumers/odr/.

Last updated March 30, 2016.

105

Install Windows
0% (1)
Install Windows
2 pages
Sage 50cloud Pastel Accounting User Guide
No ratings yet
Sage 50cloud Pastel Accounting User Guide
292 pages
Troubleshooting Guide For Licensing Problems in FLOW-3D
No ratings yet
Troubleshooting Guide For Licensing Problems in FLOW-3D
6 pages
Orca 3D Guide Rhinoceros
100% (4)
Orca 3D Guide Rhinoceros
358 pages
Disha Computer Knowledge
No ratings yet
Disha Computer Knowledge
247 pages
User Guide
No ratings yet
User Guide
97 pages
Important Definitions of a- Level Compter Science (9618)
No ratings yet
Important Definitions of a- Level Compter Science (9618)
25 pages
Manual 60
No ratings yet
Manual 60
59 pages
HMI Seminar Report
67% (3)
HMI Seminar Report
30 pages
Computer: Deputy Collector Rank File
No ratings yet
Computer: Deputy Collector Rank File
7 pages
TEKLA Software Installation and Licensing Guide
No ratings yet
TEKLA Software Installation and Licensing Guide
26 pages
FOS License AdminGd v730
No ratings yet
FOS License AdminGd v730
58 pages
UB CFX-750 UserGuide 1A ESP NH
No ratings yet
UB CFX-750 UserGuide 1A ESP NH
132 pages
TSC Steam EULA FrogwaresIrelandLtd
No ratings yet
TSC Steam EULA FrogwaresIrelandLtd
5 pages
FLT 7.0v2 UserGuide
No ratings yet
FLT 7.0v2 UserGuide
97 pages
UC21NA D3AO110 60 Tips in 60 Mins For AVEVA Enterprise Licensing
No ratings yet
UC21NA D3AO110 60 Tips in 60 Mins For AVEVA Enterprise Licensing
58 pages
Tecnomatix License Mechanism: Installation Instructions
100% (1)
Tecnomatix License Mechanism: Installation Instructions
19 pages
Libero Installation Licensing Setup User Guide PDF
No ratings yet
Libero Installation Licensing Setup User Guide PDF
46 pages
Acronyms A4 Duplex PDF
No ratings yet
Acronyms A4 Duplex PDF
179 pages
OcNOS License Server UG
No ratings yet
OcNOS License Server UG
24 pages
Vmware Backup User Guide
No ratings yet
Vmware Backup User Guide
770 pages
MGC Licen
No ratings yet
MGC Licen
95 pages
Ensoft, Inc.: 3003 West Howard Lane Tel. 512-244-6464 Austin, Texas 78728 Fax 512-244-6067
No ratings yet
Ensoft, Inc.: 3003 West Howard Lane Tel. 512-244-6464 Austin, Texas 78728 Fax 512-244-6067
3 pages
LicensingUserGuide
No ratings yet
LicensingUserGuide
87 pages
Ranorex Studio System Details
No ratings yet
Ranorex Studio System Details
79 pages
Installation Guide For Fluent Products and License Software
No ratings yet
Installation Guide For Fluent Products and License Software
47 pages
Libero Installation Licensing Userguide
No ratings yet
Libero Installation Licensing Userguide
44 pages
Reformer Pro License
No ratings yet
Reformer Pro License
9 pages
MagicDraw FloatingLicense UserGuide
No ratings yet
MagicDraw FloatingLicense UserGuide
18 pages
Manage SW Ie3d
No ratings yet
Manage SW Ie3d
89 pages
FOS LicenseGuide v721
No ratings yet
FOS LicenseGuide v721
60 pages
Synplicity License Lin Ug
No ratings yet
Synplicity License Lin Ug
17 pages
Flexframe Ff4s-Sap Install
No ratings yet
Flexframe Ff4s-Sap Install
178 pages
Roadworthy ECertificate User Guide
No ratings yet
Roadworthy ECertificate User Guide
37 pages
What Is Computer System
No ratings yet
What Is Computer System
45 pages
Autocad 2012 Licensing Guide
No ratings yet
Autocad 2012 Licensing Guide
68 pages
Telelogic Licensing Guide 1.5 PDF
No ratings yet
Telelogic Licensing Guide 1.5 PDF
72 pages
Ii-Jcs1411 Os Lab Manual
No ratings yet
Ii-Jcs1411 Os Lab Manual
78 pages
SLM 71 Sys
No ratings yet
SLM 71 Sys
136 pages
Licensing Mentor Graphics Software: Software Version v2009 - 2 August 2009
No ratings yet
Licensing Mentor Graphics Software: Software Version v2009 - 2 August 2009
86 pages
Tecnomatix License Mechanism: Installation Instructions
No ratings yet
Tecnomatix License Mechanism: Installation Instructions
26 pages
Xygate Data Protection: Optimizing Voltage Security Tokenization and Encryption For HP Nonstop Environments
No ratings yet
Xygate Data Protection: Optimizing Voltage Security Tokenization and Encryption For HP Nonstop Environments
28 pages
FMX UserGuide 7A Cutdown POR For Signoff
No ratings yet
FMX UserGuide 7A Cutdown POR For Signoff
212 pages
Basic Notes
No ratings yet
Basic Notes
118 pages
How-To-Update-Server-for-New-Version
No ratings yet
How-To-Update-Server-for-New-Version
5 pages
Adsk Lic
No ratings yet
Adsk Lic
60 pages
License With Software Key From Internet PDF
No ratings yet
License With Software Key From Internet PDF
12 pages
Graduation Project Report - Turki Ali - Ahmed Eid
No ratings yet
Graduation Project Report - Turki Ali - Ahmed Eid
28 pages
Modelsim Se Install
No ratings yet
Modelsim Se Install
30 pages
End-User License Agreement
No ratings yet
End-User License Agreement
1 page
Satyanarayana Parakota
No ratings yet
Satyanarayana Parakota
8 pages
2017 Licensing For Infrastructure Products Using Reprise
No ratings yet
2017 Licensing For Infrastructure Products Using Reprise
18 pages
Intel VROC VMD Supported Configs 7 7
No ratings yet
Intel VROC VMD Supported Configs 7 7
16 pages
Most Recently Asked Interview Questions
No ratings yet
Most Recently Asked Interview Questions
24 pages
Readem
No ratings yet
Readem
2 pages
Thea Render, Plugins and Resources End User License Agreement
No ratings yet
Thea Render, Plugins and Resources End User License Agreement
4 pages
EULA, GraphN AB_Polygonflow
No ratings yet
EULA, GraphN AB_Polygonflow
8 pages
Idea Statica
No ratings yet
Idea Statica
18 pages
license
No ratings yet
license
2 pages
Autodesk Licensing Guide: Autocad 2013
No ratings yet
Autodesk Licensing Guide: Autocad 2013
68 pages
Types of License Key
No ratings yet
Types of License Key
1 page
60-256 System Programming: Introduction To Unix: by Dr. B. Boufama
No ratings yet
60-256 System Programming: Introduction To Unix: by Dr. B. Boufama
28 pages
Universal Temporary Licenses For Optional FOS Features For Use During 2018
No ratings yet
Universal Temporary Licenses For Optional FOS Features For Use During 2018
3 pages
Using The Standalonekey Utility For Managing Csi Standalone Licenses
No ratings yet
Using The Standalonekey Utility For Managing Csi Standalone Licenses
3 pages
Readme
No ratings yet
Readme
8 pages
Chapter 1 Introduction PDF
No ratings yet
Chapter 1 Introduction PDF
77 pages
License
No ratings yet
License
11 pages
Demonstrating Value With BMC Server Automation (Bladelogic)
No ratings yet
Demonstrating Value With BMC Server Automation (Bladelogic)
56 pages
CTS Copa 2017 PDF
No ratings yet
CTS Copa 2017 PDF
39 pages
(SFLM) Offline Guide
No ratings yet
(SFLM) Offline Guide
6 pages
List of Computing and IT Abbreviations
100% (1)
List of Computing and IT Abbreviations
22 pages
CSA 204 Use of Symbol and Certificates (v3 - 3)
No ratings yet
CSA 204 Use of Symbol and Certificates (v3 - 3)
12 pages
Eula
No ratings yet
Eula
3 pages
Mobile Cloud Computing
No ratings yet
Mobile Cloud Computing
5 pages
Benltey Systems - Term License FactSheet
No ratings yet
Benltey Systems - Term License FactSheet
2 pages
TEKnowlogy Solutions Basic LUM Installation
No ratings yet
TEKnowlogy Solutions Basic LUM Installation
3 pages
History of Computer
No ratings yet
History of Computer
3 pages
Unit - Ii: Communication and Invocation
No ratings yet
Unit - Ii: Communication and Invocation
16 pages
Lilijenemasarumi
No ratings yet
Lilijenemasarumi
3 pages
Emerson's Response To NERC Reliability Standard CIP 003-8 For Transient Cyber Asset(s)
No ratings yet
Emerson's Response To NERC Reliability Standard CIP 003-8 For Transient Cyber Asset(s)
2 pages
Lesson 1 - Windows Fundamentals
No ratings yet
Lesson 1 - Windows Fundamentals
12 pages
standalone_UpdateLicense
No ratings yet
standalone_UpdateLicense
1 page
Waukesha ONE: Distributed Power
No ratings yet
Waukesha ONE: Distributed Power
1 page
Notes For Nursing Tics
No ratings yet
Notes For Nursing Tics
6 pages
The Shellcoder's Handbook: Discovering and Exploiting Security Holes
From Everand
The Shellcoder's Handbook: Discovering and Exploiting Security Holes
Chris Anley
No ratings yet
Evaluation of Some Cloud Based Virtual Private Server (VPS) Providers
From Everand
Evaluation of Some Cloud Based Virtual Private Server (VPS) Providers
Dr. Hidaia Mamood Alassouli
No ratings yet
Set Up Your Own IPsec VPN, OpenVPN and WireGuard Server: Build Your Own VPN
From Everand
Set Up Your Own IPsec VPN, OpenVPN and WireGuard Server: Build Your Own VPN
Lin Song
5/5 (1)
LINUX SECURITY AND ADMINISTRATION: Safeguarding Your Linux System with Proactive Administration Practices (2024 Guide for Beginners)
From Everand
LINUX SECURITY AND ADMINISTRATION: Safeguarding Your Linux System with Proactive Administration Practices (2024 Guide for Beginners)
RANDALL BLAIR
No ratings yet
Mastering Unix Shell Scripting: Bash, Bourne, and Korn Shell Scripting for Programmers, System Administrators, and UNIX Gurus
From Everand
Mastering Unix Shell Scripting: Bash, Bourne, and Korn Shell Scripting for Programmers, System Administrators, and UNIX Gurus
Randal K. Michael
3.5/5 (2)
Evaluation of Some Cloud Based Virtual Private Server (VPS) Providers
From Everand
Evaluation of Some Cloud Based Virtual Private Server (VPS) Providers
Dr. Hidaia Mahmood Alassouli
No ratings yet

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.