./FoundryLicenseUtility -d
/opt/FoundryLicensingUtility/bin/FoundryLicenseUtility -d
47 Matching Annotations
- Jun 2019
-
help-stage.thefoundry.co.uk help-stage.thefoundry.co.uk
-
-
./FoundryLicenseUtility.app/Contents/MacOS/FoundryLicenseUtility -d
/Applications/FoundryLicensingUtility.app/Contents/bin/FoundryLicensesUtility -d
-
FoundryLicenseUtility.exe -d
We'll need to put in the fuller pather i.e.
cd C:\Program Files\FoundryLicensingUtility\bin FoundryLicenseUtility.exe -d
-
-
help-stage.thefoundry.co.uk help-stage.thefoundry.co.uk
-
Windows: FoundryLicensingUtility.exe -s status • Mac and Linux: ./FoundryLicenseUtility -s status
these paths will also need updating to use the bin paths in the above comments
-
navigate to the Foundry Licensing Utility (FLU) install directory, and enter one of the following commands: • Windows: FoundryLicensingUtility.exe -s start • Mac and Linux: ./FoundryLicenseUtility -s start
see comment below for updated info
-
• Windows: FoundryLicensingUtility.exe -s stop • Mac and Linux: ./FoundryLicenseUtility -s stop
These paths will need to be expanded as the path to the underlying commandline executable will be a bit different.
Mac: cd /Applications/FoundryLicensingUtility.app/Contents/bin ../FoundryLicenseUtility -s stop
Windows: cd C:\Program Files\FoundryLicensingUtility\bin FoundryLicensingUtility.exe -s stop
Linux: need to double check
-
-
help-stage.thefoundry.co.uk help-stage.thefoundry.co.uk
-
000a957bade9
you don't need to specify the SystemID instead it can use "any"
HOST red any 4101
-
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.
can this be the second recommended method, below the FLU method
-
To check the server status, direct a web browser to the http://<server_name>:4102 server page and click Status on the left.
You can check the server status via the RLM webserver. You can access this from the FLU by clicking on License Server > Control > License Server Dashboard or by going to http://serverName:4102 where serverName is the hostname of your server
-
-
help-stage.thefoundry.co.uk help-stage.thefoundry.co.uk
-
If you want to license one of our products on a single machine instead, please read Installing a License Key.
Should this bit say there are 3 stages to using floating lcienses
- installing the license on the server machine
- installing the server tools
- Telling the client machines where to get a license from
-
Foundry Licensing Tools (FLT), which can be freely downloaded from our web site.
We should say that with FLU 8.0 this can be installed (and uninstalled) directly from the FLU without requiring an additional download.
-
-
help-stage.thefoundry.co.uk help-stage.thefoundry.co.uk
-
If you’re trying to activate a product using the Licensing dialog, do the following:
Need to add a note that this won't work for Activation Keys for login based licenses, such as Mari Individual Subscription or Modo Maintenance. They should go to the page on the website
-
-
help-stage.thefoundry.co.uk help-stage.thefoundry.co.uk
-
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 Licensing Utility, it does this for you).
Can we please tweak this to make it a bit clearer that they only need to do this if manually installing a license
When you get a floating license key it will have <server_name> on the HOST line of the license. If you use the Foundry Licensing Utility to install the license this will automatically be replaced with the hostname of your server machine. If you manually install the license you will need to replace the <server_name> string (including the < > brackets) with the hostname of the server machine.
-
The name of the file can be anything, but we recommend the following: foundry.lic
Can this say we recommend foundry.lic for nodelocked licenses and foundry_float.lic for server/floating licenses
-
If you installed a server license key, the license server address is displayed on screen: <port number>@<license server name> Make a note of the address, as you’ll need it to activate the client machines. Then, proceed to Installing the Server Tools.
This bit is no longer true. The instructions should be something along the lines of
If you installed a server license key, the FLU will tell you if you need to install or restart the license server tools to make the license available from the server. Please follow the instructions to install or restart the server tools. Please note the information displayed on the License Server section of the FLU for how you can point other machines toward your license server.
-
, available from: https://www.foundry.com/licensing/tools
is this needed? Fine to stay in but seems a bit unnecessary
-
-
help-stage.thefoundry.co.uk help-stage.thefoundry.co.uk
-
_0.17.1
remove this version number once we know what the final build will be called.
@fernando.porter with the final build be called foundry-licensing-utility_8.0.1.AppImage
-
Move the AppImage to permanent file path, such as your home directory.
Should we give an example command?
mv ~/Downloads/foundry-licensing-utility.AppImage ~/
-
Run the installation file from the current directory. For example: ./FoundryLicensingUtility.dmg
You can't launch a dmg like this.
The commands would need to start like those in https://learn.foundry.com/nuke/content/getting_started/installation/installing_nuke_mac.html#Installing__from_the_command_line
i.e. Mount the dmg installer with hdiutil attach /path/to/FoundryLicensingUtility.dmg
Put the installer path in memory pushd /Volumes/FoundryLicensingUtility
copy the utility into the applications folder with cp -r FoundryLicensingUtility.app /Applications/
popd
hdiutil detach /Volumes/FoundryLicensingUtility
-
Installing on Mac
Can the headings for installing on Mac, Windows and Linux have anchor / linkable things please. e.g. so we can send someone a link to
learn.foundry.com/licensing/Content/User_Guide/Installing/flu_install.html#mac
-
www.foundry.com/licensing
/tools
-
www.foundry.com/licensing
/tools
-
www.foundry.com/licensing
The downloads will be on
-
an explorer or Finder
add "window"
an explorer or Finder window
-
Installing the Foundry Licensing Utility
Should all this info be out in a separate section? It seems odd to me that installing the tool is under the installing licenses section.
So the structure could be
- Installing the Foundry Licensing Utility
- Installing Licenses 2.1 About Foundry Licenses 2.2 Installing Licenses 2.2.1 Activation Keys
-
-
help-stage.thefoundry.co.uk help-stage.thefoundry.co.uk
-
unique number
the SystemID
-
unique number
should this mention SystemID?
It is locked to a unique number, the SystemID, on that machine.
-
Activation keys install the license for you.
Being picky this isn't strictly true. Its more that the activation key is a code that can be exchanged for a license.
-
- May 2019
-
help-stage.thefoundry.co.uk help-stage.thefoundry.co.uk
-
If you installed a floating license key, the license server address is displayed on screen: <number>@<license server name>
This bit is subject to change. Making a note so we can look at it when its fixed in the FLU
-
-
help-stage.thefoundry.co.uk help-stage.thefoundry.co.uk
-
Navigate to the directory where you saved the os-specific installation file using the cd command. For example, if you saved the installation file in C:\Users\jasmine\Downloads\ use the following command and press Enter: cd C:\Users\jasmine\Downloads\ 4. Run the installation file from the current directory. For example, on macOS: ./FoundryLicensingUtility.dmg
We need separate steps for Windows, OSX and Linux. Let me know if you need help with this and I can look at it later on.
-
Double-click the desktop icon to start the Foundry Licensing Utility when the installation is complete.
There's only a desktop shortcut on Windows, not on OSX or Linux
-
/opt/
I need to double check, but I believe its
/opt/FoundryLicensingUtility
-
/Applications/
/Applications/FoundryLicensingUtility
-
C:\Users\<username>\AppData\Local\Programs\flu-2\
This is if you install it for just your user, and the path is actually C:\Users\<username>\AppData\Local\Programs\FoundryLicensingUtility
If you choose to install it for all users then it goes in C:\Program Files\FoundryLicensingUtility
-
-
help-stage.thefoundry.co.uk help-stage.thefoundry.co.uk
-
also known as floating licenses
I'd suggest having this earlier in the description.
These licenses are still referred to as floating licenses in many places so we should put it earlier to avoid confusion.
-
-
s3.amazonaws.com s3.amazonaws.com
-
s3.amazonaws.com s3.amazonaws.com
-
Navigate to the directory where you saved the os-specific installation file using the cd command. For example, if you saved the installation file in C:\Users\jasmine\Downloads\ use the following command and press Enter: cd C:\Users\jasmine\Downloads\ 4. Run the installation file from the current directory. For example, on macOS: ./FoundryLicensingUtility.dmg
These installation instructions look incomplete and need updating
-
flu-2\
Is this flu-2 bit correct? If so that is a bug that needs fixing
-
Windows: C:\Users\<username>\AppData\Local\Programs\flu-2\
This differs depending on whether you choose to install it for just yourself or for all users.
Need to double check, but if you install it for all users the program goes in
C:\Program Files\Foundry Licensing Utility
-
-
s3.amazonaws.com s3.amazonaws.com
-
A server license - enables one of our products to work on any networked client machine. The server license should be put on the server and is locked to a unique number on that server. For guidance on installing licenses, see Installing Licenses. Server licenses are also known as floating licenses and are primarily used for multi-seat facilities where a server controls a pool of floating licenses automatically.
Should this section mention that in order to use the license they need to install the server tools, and link to that section?
-
An activation key
I'd put the activation key section after Server License part
-
I'd suggest putting the "also known as floating licenses" early on in the paragraph
-
an automated path to a node-locked license,
activation keys aren't just for node-locked licenses. They can be for floating/server licenses or for login based licenses
-
node locked
Should this be hyphenated or joined?
The following paragraph uses node-locked but checking RLM's own documentation they seem to use node-locked and nodelocked interchangeably. so it probably doesn't matter
-
-
s3.amazonaws.com s3.amazonaws.com
-
Installing Licenses
Should this heading be "Installing the Foundry Licensing Utility ?
Are these headings above the pictures needed? The following page doesn't have headings above the pages and it seems to have a similar layout https://learn.foundry.com/nuke/content/user_guide.html
-
Featured
Page layout differs from live versions of Nuke and other product help e.g. https://learn.foundry.com/nuke/content/learn_nuke.html
Will this be changed for release?
-
Download PDF
Both these links point to the Support Portal rather than downloads.
I'm sure this is known already, just checking
-