By default, any PC that can reach your Floating License Server can check out a license. If you need tighter control — letting only certain machines use licenses, or blocking specific ones — you can set that up using Named License Pools.
You define your rules in a small text file (a "model definition"), then upload it to the server. This guide covers what you can control, the two Materialise-specific details to get right, and how to upload your rules.
Before you begin
- You need admin access to the Floating License Server.
- Identify the machines you want to allow or block by their Host ID (see Host IDs below).
- Rules apply at the feature level, not the product level — this affects how you write them (see Rules apply per feature below).
How it works
- Write your rules in a model definition file and save it as a
.txtfile. The rule syntax (called the model definition grammar) is documented in Revenera's model definition components. - Upload the file to your server (see Upload your rules below).
- The server applies the rules immediately. For a block rule, affected users are disconnected as soon as the model is uploaded.
Materialise specifics
Two details differ from the generic Revenera examples. Getting these right is what makes the difference between a model that works and one the server rejects.
Identify machines by Host ID
Materialise uses a string-type Host ID, so you can list Host IDs without specifying a type. Write them like this:
on hostid (
"4BE23134-3FF0-3702-4DF9962901550A1DB5",
"4BE23134-3FF0-4302-4DF9962901550A1DB5",
"4BE23134-3FF0-3242-4DF9962901550A1DB5"
)
Do not add the /STRING suffix that appears in some generic examples:
on hostid (
"4BE23134-3FF0-3702-4DF9962901550A1DB5/STRING", ← don't do this
...
)
Rules apply per feature
Each Materialise product is made up of multiple features, and there's no option to write a rule at the product level. To control access to a product, list all of that product's features in the rule (partition).
The one exception is a full block of a machine, which can be done at the Host ID level (see the scenarios below).
Common scenarios
| What you want to do | How to set it up | Revenera example |
|---|---|---|
| Block a machine entirely (or disconnect a user from the server) | Simple block list, at the Host ID level | Simple Block List |
| Block a machine from specific products only | Block list, at the feature level (list the product's features) | Simple Block List |
| Allow only a fixed list of machines | Simple allow list, at the feature level | Simple Allow List |
| Reserve licenses for certain machines while leaving the rest available to others | Allow list with reservation, at the feature level | Simple Allow List |
For more combinations, see Revenera's use-case examples for Named License Pools.
Upload your rules
Once your .txt model file is ready, upload it to the server.
Via the License Server Manager (recommended)
Use the License Pools view in the FlexNet License Server Manager to upload your model file. See Revenera's License Pools view guide.
Don't have the Manager installed? See Install the ID-based Floating License Server.
Via the command line (advanced)
If you manage the server from the command line, upload the model file following Revenera's upload instructions.
Related guides
- Activate licenses on the Floating License Server — activate, review, and manage licenses.
- Full reference: Managing Named License Pools (Revenera).
Something not working?
- Still stuck — contact Materialise Support.
‹ Back to: Quick start guide