Translate This Page

Release Blog CGPeers IRC Chat User CP FAQ Search Latest Posts User Tools Log Out

Welcome, flubous.
CGPersia Forums > Off Topic > CG General Discussion
You last visited: 02-23-2024 at 07:45:19 AM
Houdini licensing system for "dummies" Private Messages: Unread 0, Total 27.

CG General Discussion General discussion related to computer graphics and the CG industry

Thread Tools Search this Thread Rating:

01-30-2024, 03:58:56 PM #1

Houdini licensing system for "dummies"

timpriest
Original Poster
HOUDINI LICENSING SYSTEM FOR "DUMMIES"
Join Date: Apr 2013
Posts: 1,520
* This is an unfinished article!
Thanks (Given): 2732 I will add and improve this article after the release of "XFORCE Houdini Keygen/Patcher" for Houdini-20.0...
Thanks (Received): 5666
Let's define the minimum level of concepts and terminology.

Houdini can use two licensing systems:

The first licensing option: "Login Licensing".

"Login Licensing" uses remote SideFX servers as a license server.
This means you don't have to maintain your own local license server.
And when installing Houdini, you do not need to install the "Licensing server" additionally.
However, to log in (to your SideFX account) you need an active internet connection and you need version Houdini-18.5 or higher.
At the same time, your licenses are stored in your account on a remote SideFX server.
This is the only licensing option when using "Houdini Indie".

For obvious reasons, this option is of little interest to us. (Of course, you can sincerely sympathize with people who are forced to use "Houdini Indie").

Second licensing option: "Studio Licensing".

"Studio Licensing" differs from "Login Licensing" in that you do not allow SideFX to manage the license server for you.
This means that the license server must be installed on a dedicated server on your network or directly on your workstation.
In this case, you do not need an Internet connection.

Obviously, for such a licensing system there are: “Server Side” and “Client Side”.

***

SERVER SIDE:

The main component for Server Side is the "Houdini License Server".
To install Houdini License Server (sesinetd) on your computer, you must check option: "Licensing server" in the installer.
* For Windows and Mac you CANNOT INSTALL "Licensing server" (sesinetd) ONLY, you will have to install the full Houdini package.
* For Linux you have the option to install ONLY the "Licensing server" (sesinetd): sesinetd.install
Houdini License Server (sesinetd). This license server daemon/service. It always runs in the background, managing Houdini licenses to local or remote client machines.
The Houdini installer (with check option "Licensing server") registers this program with the operating system so that it will always run.
Must be in the running state for any Houdini-products to open, include Houdini Apprentice.
By default listen on TCP port 1715. This may be changed.
The client License Administrator (hkey) or non-graphical "sesictrl" will connect to "sesinetd" for license information and administration.

For example:

On Windows, Houdini License Server (sesinetd) is registered as a service that should always start when the OS starts:
For example, for Houdini License Server (sesinetd) version >= 19.0:
service: "HoudiniLicenseServer"
Link(s):
C:\Program Files\Side Effects Software\License Server\sesinetd.exe (-options)

Options file for Houdini License Server:

Link(s):
C:\Program Files\Side Effects Software\License Server\sesinetd.ini

(By default, this file is not created.)

For Houdini License Server (sesinetd) version < 19.0:

service: "HoudiniLicenseServer"
Link(s):
C:\Windows\System32\sesinetd.exe (-options)

Link(s):
C:\Windows\SysWOW64\sesinetd.exe (-options)

Options file for Houdini License Server:

Link(s):
C:\Windows\System32\sesinetd.options

Link(s):
C:\Windows\SysWOW64\sesinetd.options

(By default, this file is not created.)

start/stop service:
start/stop "HoudiniLicenseServer" in Control Panel -> Administrative Tools -> Services
In order to delete/create/stop/start the "HoudiniLicenseServer" service in Windows, you can use the "sc" command:
Run CMD as Administrator:
Link(s):
sc stop HoudiniLicenseServer
sc delete HoudiniLicenseServer
sc create HoudiniLicenseServer start= auto error= ignore tag= 0 binPath= "C:\Program Files\Side Effects Software\License Server\sesinetd.exe" obj= LocalSystem DisplayName= HoudiniLicenseServer
sc start HoudiniLicenseServer

On MacOS, the "sesinetd" file is located in the directory:

Link(s):
/Application/Houdini/Houdini[version]/Frameworks/Houdini.framework/Versions/[version]/Resources/houdini/sbin/sesinetd

Link(s):
/Application/Houdini/Houdini[version]/Frameworks/Houdini.framework/Versions/Current/Resources/houdini/sbin/sesinetd

Link(s):
/Library/Preferences/sesi/sesinetd

On MacOS, Houdini License Server (sesinetd) is registered as a Daemon, which should always start when the OS starts:

Link(s):
/Library/LaunchDaemons/com.sidefx.sesinetd.plist

Options file for Houdini License Server:

Link(s):
/Library/Preferences/sesi/sesinetd.ini

start/stop Houdini License Server:

In a terminal, use:

Link(s):
sudo launchctl load /Library/LaunchDaemons/com.sidefx.sesinetd.plist
sudo launchctl unload /Library/LaunchDaemons/com.sidefx.sesinetd.plist

On Linux, the "sesinetd" file is located in the directory:

Link(s):
/usr/lib/sesi/

On Linux, the installer creates an "init.d" script for the server.

Link(s):
/opt/hfs[version]/houdini/sbin/sesinetd

This will still be picked up on system distributions by the system's backward compatiblity layer.
Options file for Houdini License Server:
Link(s):
/usr/lib/sesi/sesinetd.ini

start/stop Houdini License Server:

Run the sesinetd startup scriptt located in "/etc/init.d". Use:
Link(s):
/etc/init.d/sesinetd {start|stop}

(You can change the type of service that Houdini License Server runs under (from init.d to systemd))

Houdini License Server (sesinetd) reads license keys for Houdini-products and license keys for License Servers from file: "licenses".

***

CLIENT SIDE:

The main component for the Client Side is the "Houdini Server".
Houdini Server (hserver): Houdini communicates through this proxy server with the licensing daemon/service "sesinetd" to obtain licenses.
Houdini Server (hserver) - This is a service running on the same computer that runs Houdini FX, Engine, Mantra, Karma and other Houdini-products SideFX.
Houdini Server acts as a proxy for the Houdini License Server (sesinetd) and ensures that multiple copies of the same Houdini product (even different versions) running (on the same machine) retrieve only one license of that type from the Houdini License Server (sesinetd ).
By default listen on TCP port 1714. This may be changed.

On Linux/OSX, hserver is launched "on demand", that is, the first time Houdini is launched in the current OS session.
The launched hserver continues to work until the OS is rebooted.
If hserver is already running, another version of hserver does not start (Even if this version is higher than the one already running).
Therefore, if you need to run different versions of Houdini on Linux/OSX, it is recommended to run hserver using the highest version of Houdini.
On Linux, the "hserver" file is located in the directory:
[code]
Link(s):
/opt/hfs[version]/bin/hserver

On MacOS, the "hserver" file is located in the directory:

Link(s):
/Application/Houdini/Houdini[version]/Frameworks/Houdini.framework/Versions/[version]/Resources/bin/hserver

Link(s):
/Application/Houdini/Houdini[version]/Frameworks/Houdini.framework/Versions/Current/Resources/bin/hserver

On Windows, Houdini Server (hserver) is registered as a service that should always start when the OS starts. For example:
For Houdini Server (hserver) version >= 19.0:
service: "HoudiniServer"
Link(s):
C:\Program Files\Side Effects Software\Houdini Server\hserver.exe (-options)

For Houdini Server (hserver) version < 19.0:

service: "HoudiniServer"

Link(s):
C:\Windows\System32\hserver.exe (-options)

As of Houdini-19, you can choose not to create (or stop/start/delete/) the "HoudiniServer" service on Windows.
In this case, Administrator rights are not required to launch and use hserver.
In this case, "Houdini Server" will behave the same as in Linux/OSX. That is, it will be launched the first time Houdini is started from the “bin” folder in the Houdini installation:

Link(s):
C:\Program Files\Side Effects Software\Houdini [version]\bin\hserver.exe

Keep in mind that although the Houdini-18.5 installation contains "bin\hserver.exe", this will not work automatically by default.
Houdini versions prior to 18.5 do not contain "hserver.exe" in the "bin" directory.
In order to delete/create/stop/start "HoudiniServer" in Windows, you can use the "sc" command:

Run cmd as Administrator:

Link(s):
sc stop HoudiniServer
sc delete HoudiniServer
sc create HoudiniServer start= auto error= ignore tag= 0 binPath= "C:\Program Files\Side Effects Software\Houdini Server\hserver.exe" obj= LocalSystem DisplayName= HoudiniServer
sc start HoudiniServer

start/stop "HoudiniServer":
start/stop "HoudiniServer" in Control Panel -> Administrative Tools -> Services

For "hserver" full control is available not only using the configuration options file. "hserver" has full command line control. This is true for starting "hserver" and for managing an already running "hserver".

!!! In Houdini-19, the licensing system has been conceptually updated and is fundamentally different from the previous licensing system!
All environment variables have been changed! Backwards compatibility is not supported!
Licensing Houdini-19 uses HTTP(S) exclusively!
Hserver can run using both licensing systems at the same time, but upgrading/downgrading will be disabled because hserver can't decide what to do since the older systems don't provide all the information needed!

***

Licensing system service utilities.

In the Houdini licensing system, the main service utilities are the following standalone utilities:
"Houdini License Administrator" (hkey) and "Non-Graphical Houdini License Administrator" (sesictrl).

"Houdini License Administrator" (hkey) - This is a stand-alone GUI utility (Also known as "License Administrator") designed to manage licenses and server parameters.

!!! For full operation of the utility, administrative privileges are required (To interact with system services)!

Using the "Houdini License Administrator" interface you can:

- Show all license servers and view all licenses installed on them.
- Install/Reinstall/Import licenses and redeem entitlements.
- Manage Houdini license servers and configure settings for license servers.
- Activate Apprentice
- Interact with the remote SideFX license server, manage login/logout to/from your account (For example, for Indi & Education users)*.
- View a list of users for selected licenses.
- View and save diagnostic information.
- Start and stop "Houdini Server" and "Houdini License Server".

*For Login Licensing support additional settings must be made.

* In this case, there must be an active Internet connection and "hserver" must be running.

On Windows, "hkey" is located in the "bin" directory of the Houdini installation. For example:
Link(s):
C:\Program Files\Side Effects Software\Houdini [version]\bin\hkey.exe

On MacOS, the "Houdini License Administrator" (hkey) is located in the Houdini installation directory, in the "Administrative Tools" folder, as License Administrator [version].

Link(s):
/Application/Houdini/Houdini[version]/Frameworks/Houdini.framework/Versions/Current/Resources/bin

On Linux, the "Houdini License Administrator" (hkey) is located in the Houdini installation directory: "bin/hkey".
Link(s):
/opt/hfs[version]/bin

"Non-Graphical Houdini License Administrator" (sesictrl) - This is a standalone utility without a graphical interface, allows you to perform the same actions as the "hkey" utility (and some others), but from the command line (terminal shell), with the ability to expand command management . This allows you to
automate the configuration of the license server.

Click this bar to view the full image.

On Windows, the "Non-Graphical Houdini License Administrator" (sesictrl) is located in the "bin" directory of the Houdini installation. For example:

Link(s):
C:\Program Files\Side Effects Software\Houdini [version]\bin\sesictrl.exe

On MacOS, the "Non-Graphical Houdini License Administrator" (sesictrl) is located in the directory:
Link(s):
/Application/Houdini/Houdini[version]/Frameworks/Houdini.framework/Versions/Current/Resources/houdini/sbin/sesictrl

On Linux, the "Non-Graphical Houdini License Administrator" (sesictrl) is located in the Houdini installation directory: "sbin/sesictrl".

Link(s):
/opt/hfs[version]/houdini/sbin/sesictrl

Link(s):
/usr/lib/sesi/sesictrl

***

License file "licenses"

License file "licenses": This is an ordinary text file (with a name without a file extension!) that contains information about all installed license keys for Houdini-products and license keys for the "Houdini License Server".
That is, this is a text file containing strings of license keys.
In addition to lines containing license keys, this file contains comment lines containing additional help information. For example, information about the date the license key was imported.
The "Houdini License Server" (sesinetd) reads license keys from the license file "licenses" upon startup.
The "Houdini License Server" (sesinetd) verifies that the license keys being read are correct.
The "Houdini License Server" (sesinetd) writes new license keys (in the license file "licenses") that are passed to it by license import utilities or manual license entry utilities. At the same time, it checks the imported data for validity and syntax.
"Houdini License Server" (sesinetd), when writing new license keys, can subject the key strings to additional formatting for ease of visual perception.
To make the information from the modified "licenses" file available to the "Houdini License Server" (sesinetd): restart the "Houdini License Server" (sesinetd).

The license file "licenses" is located:

Link(s):
Windows: C:\Windows\keys\licenses
Linux: /usr/lib/sesi/licenses
Mac: /Library/Preferences/sesi/licenses

* The directory containing the licenses file "licenses" may contain other files named "licenses" but having an extension, for example the file "licenses.disabled" (by default this file is empty and has zero size):
Link(s):
C:\Windows\keys\licenses.disabled

***

"Server Name"

"Server Name" - This is the name of your server on which the "Houdini License Server" is installed.
If the server is located locally, then “Server Name” is the name of your computer that is a member of a domain or a member of a workgroup.

It is very important that your server has the "CORRECT" NAME!!!

The server name must not only be valid from the point of view of the current OS, but also be correct from the point of view of all participants in the network interaction.
The correct server name should be as universal as possible and resistant to possible collisions in the current and future network and hardware environment.

For maximum compatibility with all networks, operating systems, local and remote software and hardware environments, you must strictly follow these naming rules (NetBIOS, DNS, AD, etc):

01. DO NOT USE UNICODE CHARACTERS!!!

02. NEVER USE UNICODE CHARACTERS!!!
03. The minimum name length is 2 characters. But try to use names with at least three characters.
* Be careful !!! When using a two-character name, reserved SID SDDL names are prohibited.
* For example: "AA", "AC", "BU", "DA", etc. (About 70 names in total)
04. The maximum name length is 15 characters.
05. Names can only contain letters (A-Z), numbers (0-9) and a minus sign (-).
* Using the "-" symbol allows you to create "forbidden" names like: "S-1-0", "S-1-5-2", etc.
06. All other symbols are prohibited! Including the characters "." "_" "space" ... etc.
* Especially beware of using the "_" character!
* Although the use of the "_" character is rarely explicitly prohibited, it allows the creation of "forbidden" names like: "DOMAIN_GROUP_RID_COMPUTERS", "SECURITY_LOCAL_RID", "SDDL_SERVICE", "SDDL_ML_SYSTEM", etc.
07. A name cannot consist only of numbers!
08. Use ASCII characters ONLY!!!!
09. When using ASCII characters, the case is NOT DIFFERENT and IS NOT SAVED (therefore, in the name, use all letters in only one, upper case)!!!
10. The first character must be a letter or number (do not use the minus sign (-) as the first character in the name).
11. The last character must not be a minus sign (-).
12. Do not assign the same names to child elements of the same level.
13. Do not assign the same names to child and root elements.
14. Do not use OS Reserved Worlds as names.
* For exemple (for OS Windows): "ANONYMOUS", "NETWORK", "NULL", "PROXY", "USERS", "WORLD", "SYSTEM", "SERVER", "SERVICE", "LOCAL", etc (>30 worlds)
15. Do not use Well-known SIDs as names.

***

"Server Code"

"Server Code" is a unique alphanumeric identifier.

"Server Code" - generated locally on the client side for a specific installed license server.
"Server Code" is generated based on the hardware and network environment of the computer on which the license server is installed and running.

"Server Code" - used to generate the "SERVER" string for the license key for the license server itself:
To generate the "SERVER" key string, two string keys are used: "Server Code" and "Server Name".
For example ("Server Name" == "KSPC", "Server Code" == 8dbde2a9):
Link(s):
SERVER KSPC 8dbde2a9 9CAAB5D4EDB06425663FF56B9C3F5EB821A7DA6709D69

As we have already noted, “Server Code” is generated based on the equipment in the environment in which the “Houdini License Server” is launched.
!!! One of the key devices based on the specifications of which the “Server Code” is generated is the network adapter.
!!! Houdini selects the underlying network device to use its specifications to generate the "Server Code".
!!! Therefore, if virtual network adapters appear/change in your system, the current “Server Code” may not match the “Server Code” previously generated for the “SERVER” key string.
You can view all real and virtual network adapters (and their protocol settings) by entering Command Promt: "ipconfig /all".

***

The License Key for any Houdini-product (or license server) is a string.

This line contains the license type value as the first element:
License type (Type): "SERVER" or "LICENSE" or "INCREMENT" or "UPGRADE" or "EXTEND"

If the type identifier is "SERVER", then it must be followed by the values for the following parameters (separated by a space): "Server Name", "Server Code" and a unique (encrypted and obfuscated) key (Tokien Key) generated based on "Server" Name" and "Server Code".

For example (For: Type == "SERVER", "Server Name" == "KSPC", "Server Code" == 8dbde2a9, Tokien Key == "9CAAB5D4EDB06425663FF56B9C3F5EB821A7DA6709D69"):
Link(s):
SERVER KSPC 8dbde2a9 9CAAB5D4EDB06425663FF56B9C3F5EB821A7DA6709D69

If the type identifier is "LICENSE", then the values for the following parameters must be specified (separated by a space): platform to which the license is attached (platform), service name Houdini-product (product), version Houdini-product (version), number of licenses (available), license expiration date
(expiry_date), server ip address mask (ip_mask), name of the server for which this license is intended (server), license identifier (licenseid), and unique (encrypted and obfuscated) key (tokien_key) generated based on "Server Name", "Server Code" and the values of some other parameters.

For example (For: type == "LICENSE", platform == "Generic", product == "Houdini-Master", version == "19.5", available == "200", expiry_date == "25-dec-2028", ip_mask == "*.*.*.*", server == "KSPC", licenseid == "b1134d5e", tokien_key ==
"9CAAB5D4EDB06425663FF56B9C3F5EB821A7DA6709D69"):

Link(s):
LICENSE Generic Houdini-Master 19.5 200 25-dec-2028 *.*.*.* KSPC b1134d5e 23hvoFhdr3lUnne93vXEkqf1tRuG2cRG@UbFBi4aHdHAIVficwpsQ5IcbW3zG4GQ@fJCAkcuJfC7i9

License keys for all Houdini-products (and "Houdini License Server") are generated by SideFX based on the data provided ("Server Code" and "Server Name"), and are made available for download to the purchaser of these Houdini-products (or made available remotely on " License Server" SideFX (when using
"Login Licensing")).

*!!! Therefore, if you change the name of the computer on which the Houdini License Server (sesinetd) is running, or update some hardware, the license for the license server (SERVER KEY) will become INVALID!!! And, accordingly, all other Houdini-products licenses will become VOID!!!

* On Windows, if the "keys" folder does not exist, it will be created the first time the "HoudiniLicenseServer" (sesinetd) service is started.
The file "sesinetd_peak_usage.bin" will be created in the "keys" folder.

* If the license file ("licenses") and the disabled license file ("licenses.disabled") do not exist, they will be created the first time you import license keys.

All information about all licenses used by Houdini License Server (sesinetd) is stored in the "licenses" file (This file DOES NOT and SHOULD NOT HAVE a file extension!).
The "licenses" file is located in:

Link(s):
Windows: C:\Windows\keys\licenses
Linux: /usr/lib/sesi/licenses
Mac: /Library/Preferences/sesi/licenses

Sometimes, the buyer receives a ready-made "licenses" file (already containing all the necessary license keys) from SideFX.
Alternatively, you can automatically place license keys in the "licenses" file by importing licenses from the SideFX-provided "*.hlic" (Houdini License Files) file using "Import License(s)" in the "Houdini License Administrator" (hkey) utility.
Or, you can automatically place license keys in the "licenses" file by importing licenses from strings using "Import License(s)" in the "Houdini License Administrator" (hkey) utility, manually entering license strings through "Houdini Manual Key Installation Dialog".
You can implement the last two methods on the command line using the "Non-Graphical Houdini License Administrator" (sesictrl).

At the same time, the lines of all imported (by any means) licenses are written to the “licenses” file.
Before each license line there is a commented line containing reference data about the date of installation of the license key.
For example:

Link(s):
...

# Key installed 05:02:26 01/28/23

SERVER KSPC 8dbde2a9 2FDD9175F7723FD64FDEC9E3A77711F958C4DB222E5E52

# Key installed 05:01:40 01/28/23

LICENSE Generic Houdini-Master 19.5 200 25-dec-2029 *.*.*.* KSPC 7f856f5c \
WEBV4AG1zbqRB8NqDB6hv7EEXgsVSTk5usdfFcE0XrjKzNvOtsKjBckwNBhWqhNdU+dKKNxphipd81

# Key installed 05:01:41 01/28/23

LICENSE Generic Render 19.5 200 25-dec-2029 *.*.*.* KSPC 1bcca6fa \
OnzEk7XBYuOpLBoBL0zYCKxmmVOYn7fgpAXRaH1dfhxpvts4Saiswv85FIl5dLC4V8pKUn9RM87UiD
...

In the example above, we see that the license key lines for Houdini-products are split into three lines:
The first line starting with the "#" character is ignored and is a comment.
The second and third line are actually one line. Because the "\" character indicates that the current line should be concatenated with the next one.
License lines are automatically divided into several lines during import for ease of visual perception.
Extra spaces and tabs are not taken into account.
That is, the license file "licenses" is a regular text file that contains lines with comments and license key lines related either to license servers (starting with the identifier - "SERVER"), or to licenses for specific Houdini-products (starting with identifier - "LICENSE").
We can manually edit the "licenses" file by deleting, changing or creating new lines with license keys.
To update the information from the modified "licenses" file in the "Installed Licenses" tab (in the already running "Houdini License Administrator" utility), restart the "HoudiniLicenseServer" service and update the contents of the tab using View -> Refresh (or Ctrl + R).

The information contained in the license file "licenses" can be viewed using "Diagnostic Information" in the "Houdini License Administrator" (displayed last):
"Houdini License Administrator" -> View -> Diagnostic Information

Click this bar to view the full image.

If you have multiple versions of Houdini-18.0/18.5/19.0/19.5 installed on your computer, then it does not matter which version of "hkey"/"sesictrl" you use to enter the keys (but the version of "hkey"/"sesictrl" must be >= 18.0 .287).
"hkey"/"sesictrl" are just service shells for interacting with the licensing system ("sesinetd") and for administering licenses.
In the old "Houdini License Administrator" (version < 19.0) to manually enter keys, use: "Houdini License Administrator" -> File -> Manually Enter Keys...
In the new (version >= 19.0) "Houdini License Administrator" to manually enter keys, use: File -> Import License... -> press button "MANUAL INSTALL"
So you can enter keys generated for Houdini-19.5 using "hkey"/"sesictrl" for Houdini-18.5 (and vice versa). It doesn't matter. As a result, the entered keys will be written to the "licenses" file. Therefore, you can not use “hkey”/“sesictrl”, but edit the license file “licenses” manually .
However, you are responsible for the correctness of the entered license key strings.
When entering license keys via "hkey"/"sesictrl", "sesinetd" checks the license key strings for correct values/syntax.
And if the content of the key is not correct, but does not contain invalid identifiers, then such an incorrect key... WILL STILL BE PLACED IN THE "licenses" FILE!
Such a license, when diagnosed or displayed in the graphical interface of the hkey utility, will be marked as "License is not a valid license from SideFX".

For example:

You cannot import such a license key string using “hkey”/“sesictrl”:

Link(s):
LICENSE Generic Houdini-Master-Experimental 19.5 200 25-dec-2029 *.*.*.* KSPC 54f824cc \
+0T4Ski1YjvXg8Qqvy573Y2RtPqug8ChbRjnBr3GckhUOjXgRRPLrc3pa1DaZ@9SD5TLdb2FKmq48B

You won't be able to import this string using "hkey"/"sesictrl" because there is a line end character in the middle of this string.
But, if you put these lines manually in the "licenses" file, then this license will be displayed as valid and correct.
Because in this case, when reading from the license file, the strings will be concatenated correctly.

You cannot import such a license key string using “hkey”/“sesictrl”:

Link(s):
LICENSE Generic Houdini-Master-Experimental 19.5 200 25-dec-2029 *.*.*.* KSPC 64f824cc \
+0T4Ski1YjvXg8Qqvy573Y2RtPqug8ChbRjnBr3GckhUOjXgRRPLrc3pa1DaZ@9SD5TLdb2FKmq48B

You won't be able to import this string using "hkey"/"sesictrl" because there is a line end character in the middle of this string.
But, if you manually put this line in the "licenses" file, then this license will be displayed, but will be marked as NOT VALID.
The strings will be concatenated correctly, but the decrypted token will return License ID == 54f824cc, while we have License ID == 64f824cc. Since the values do not match, the license will be marked as NOT VALID.
You cannot import such a license key string using “hkey”/“sesictrl”:
Link(s):
LICENSE Gooderic-Fackeric Houdini-Shmaster-Dja 19.5 200 07-feb-2106 *.*.*.* KSPC 44f824cc \
+0T4Ski1YjvXg8Qqvy573Y2RtPqug8ChbRjnBr3GckhUOjXgRRPLrc3pa1DaZ@9SD5TLdb2FKmq48B

And even if you put this line manually in the "licenses" file, this license still WILL NOT be displayed.
String concatenation will work correctly, but "Houdini License Administrator" cannot process dates after "06-feb-2106" (Perhaps SideFX knows something terrible, but is hiding it ). In addition, the decrypted token will not match the specified parameters.

* If the license expiration date is > 14-feb-2091, then the license is marked: "License Is About To Expire"

This string is not valid, but it will be imported into the "licenses" file using "hkey"/"sesictrl".
And this license will be displayed (as not valid).

Link(s):
License Fackeric Houdini-Super 29.0 1000 31-DEC-2050*.*.*.*KSPC 7T866F6K WEBV4AG1GFRV3SGSGSGSVSTKZNVOTSKHBCHBCHBCKKKKKHBCKKKKKKKKKKKHA Nxphipd81

This string is not valid, but it will be imported into the "licenses" file using "hkey"/"sesictrl".
But, this license WILL NOT be displayed.
Link(s):
LICENSE Generic Houdini-Super-Puper 30.0 1000 31-dec-2051 *.*.*.* KSPC 7t866f6с WEBV4AG1gfrB8NqDB6hv3ссXgsVSTk5ssdfFcE0XrjKzNvOtsKjBckwNBhWqhNdU+dKKNxphipd81

This license will not be displayed because it has the same License ID as the previous license (although they are encoded with different characters):
7t866f6k == 00000007
7t866f6с == 00000007

Click this bar to view the full image.

This image has been resized. Click this bar to view the full image. The original image is sized
1026x704.

***

Each new Houdini build does not require a server and a license server of the same version as the build version.
There are minimum licensing service version requirements.

For Houdini 18.5/19.0/19.5, these are:

Min version (non http) - hserver/sesinetd/sesictrl/hkey: 18.0.287

Min version (http) - hserver/sesinetd/sesictrl/hkey: 18.5
Link(s):
https://www.sidefx.com/docs/houdini/news/19_5/licensing.html

Well, this concludes our brief (and very superficial) introduction to the Houdini licensing system...

***

How does the Houdini licensing system work?

We are interested in the "Studio Licensing" licensing system, which uses "floating licenses".
A "floating license" is not strictly tied to one specific user's computer, but rather is tied to one specific license server.
This allows you to run Houdini-products on various computers on the network served by this license server.
A floating license contains information about the maximum possible number of copies of Houdini-product that can be used simultaneously on different workstations on the network.
This allows Houdini-products to run simultaneously on different computers on the network, within the license quota for those Houdini-products.
Multiple running copies of the same type of Houdini-product on the same computer (even if the running copies of Houdini-products are of different versions!) will typically only check out one copy of the license.
The "Houdini License Server" (sesinetd) reads license keys from the license file "licenses" upon startup.
"Houdini License Server" (sesinetd) at startup checks the correspondence between the actual "Server Code"/"Server name" and the "Server Code"/"Server name" specified in the license server license key.
When starting Houdini-product, "Houdini Server" (hserver) must already be running, otherwise (if Houdini version >= 19) "hserver" will be launched from the installation directory ("bin") of the current version of Houdini.
Houdini-product notifies "hserver" that it is running and expects "hserver" to provide available licenses for this running copy of Houdini-product and other related Houdini-products that are launched with it.
"Hserver" queries the current "Houdini License Server" for the availability and availability of licenses for newly launched copies of Houdini-products.
And retrieves from the "Houdini License Server" copies of the available licenses for these Houdini-products.
At the same time, the "Houdini License Server" reduces the number of available license copies for use by these types of Houdini-products.
When Houdini-products is closed, "hserver" returns copies of the taken licenses back to the "Houdini License Server".
At the same time, "Houdini License Server" increases the number of available license copies.
The "Houdini License Server" may be located on the same workstation where Houdini is running, or the "Houdini License Server" may be accessible from a network environment (or there may be a SideFX Remote License Server in this role).

***

!!!! Very important feature of "Houdini Server" (hserver):

On Windows, when installing Houdini 18.0-19.5, the existing "HoudiniServer" service is removed and a new "HoudiniServer" service is installed, the same version as the version of Houdini being installed, even if the version being installed is lower than the current version of "HoudiniServer"!!!

For example:
You already have the "HoudiniServer" service. The version of "Houdini Server" (hserver) is 19.5.493.
On Windows, "hserver" versions 19/19.5 are installed by default in the following folder:

Link(s):
C:\Program Files\Side Effects Software\Houdini Server\hserver.exe

And the "HoudiniServer" service is created and launched specifically for this file:
service: "HoudiniServer"
Link(s):
C:\Program Files\Side Effects Software\Houdini Server\hserver.exe (-options)

If you decide to install/update Houdini-19 (for example, to version Houdini-19.0.873), then:

When installing Houdini-19, the "HoudiniServer" service version 19.5.493 will be removed and the "HoudiniServer" service version 19.0.873 will be installed!
That is, the file "hserver.exe" will be replaced with a file "hserver.exe" with a lower version in the same directory:
Link(s):
C:\Program Files\Side Effects Software\Houdini Server\hserver.exe (-options)

But, if you decide to install/upgrade Houdini below version 19, for example Houdini-18/18.5, then the "HoudiniServer" service will of course be reinstalled and replaced with the installed version.
But, "Houdini Server" (hserver) versions below 19 are installed by default in a different location:

Link(s):
C:\Windows\System32\hserver.exe
C:\Windows\SysWOW64\hserver.exe

And the "HoudiniServer" service is created and launched specifically for this file:
service: "HoudiniServer"
Link(s):
C:\Windows\System32\hserver.exe (-options)

!!!! In this case, the file "hserver.exe" existing in the "Houdini Server" folder WILL NOT BE OVERWRITED!

Link(s):
C:\Program Files\Side Effects Software\Houdini Server\hserver.exe

***

!!!! A very important feature of the Houdini licensing system:

If you have unexpired licenses (whether real or fake) for any Houdini-products, then to use lower versions of these Houdini-products you DO NOT NEED ADDITIONAL LICENSES FOR THESE OLD VERSIONS of Houdini-products!!!

For example:
You have installed fake licenses (usually with a quota of 200 for each Houdini-product) for the entire line of Houdini-19.5-products:

Houdini-Master 19.5
Generic Render 19.5
Karma-Render 19.5
Houdini-Engine 19.5
PDG 19.5
Generic Beta 19.5
Generic Houdini-Escape 19.5
Houdini-Master-Experimental 19.5

This means that these licenses are enough to simultaneously run Houdini-18.0/18.5/19.0/19.5 on two hundred DIFFERENT workstations (on the network served by this Houdini License Server), with all versions of Houdini-products fully available for all these versions of Houdini !!!
For each individual workstation, the number of simultaneously running copies of Houdini-products (any version) is not limited by anything (except for available memory ).

***

Now let's try to understand how the "hacking system" for Houdini, implemented by the "X-Force" team, works.

As we already know, to use "Studio Licensing" with floating licenses, we must obtain these licenses from SideFX by providing SideFX with information about our already installed license server.
Namely: "Server Name", "Server Code", subnet mask.
"Server Name" is the actual name of the machine on which the server is running (We will not consider options with DNS-name, which became available starting with Houdini-19)
"Server Code" is a unique identifier generated locally on the client side for a specific installed license server.
"Server Code" is generated based on the hardware and network environment of the computer on which the license server is installed.

Based on this data, SideFX will generate for our license server:
1. a unique server license key (containing “Server Name”, “Server Code” and some complex text token in which this information is encrypted).
2. unique license keys for each Houdini-product purchased by us, compatible only with our license server.
Each Houdini-product license key contains a complex text token in which all information related to this Houdini-product is encrypted.
Including: number of copies, license expiration date, information about the license server.

Encrypted tokens are generated on the SideFX side using unknown algorithms using a complex (private) and carefully protected encryption key.
In fact, it is an encryption system using a reverse public key encryption.
The key for decrypting tokens is contained (or generated) in the "Houdini License Server".
That is, using this known (public) decryption key, we can only decrypt the data encrypted in tokens.
At the same time, the decrypted token data must contain the same information as the unencrypted parts of the license keys: “Server Name”, “Server Code”, and Houdini-products parameters.
But, in order to encrypt the data (that is, create tokens with the information we need), we need a completely different (private) encryption key. Obviously, we cannot access this key.

How can we create encrypted tokens that will be correctly interpreted by the original license server??!!
NO ONE! THIS IS IMPOSSIBLE !

Therefore, to hack the Houdini licensing system, the same method was used to hack the Reprise Software (RLM) licensing system.
The philosophy behind this hack is that: If we can't generate real license tokens, then let's hack the license server itself so that it decrypts the tokens we generate using our decryption algorithm!

Therefore, hacking the Houdini licensing service using “X-Force keygen/patcher for Houdini” is functionally divided into two parts:
1. Modification of the licensing service file "Houdini License Server" - "sesinetd".
After patching, the licensing service "Houdini License Server" correctly interprets the keys generated using the "X-Force keygen/patcher".
2. Generate a license key for the license server and generate license keys for all Houdini-products.

As we already know, only the “Houdini License Server” is responsible for reading and validating license keys and validating the “Server Code”.
Therefore, we can safely use and update all other Houdini utility utilities, including "Houdini Server" (hserver), "Houdini License Administrator" (hkey).

In the latest implementations of "X-Force keygen/patcher for Houdini" we only have the option to enter "Server Name" and "Server Code" to generate license keys. We cannot determine the number of copies of licenses for Houdini-product and we cannot set an expiration date for licenses.
The values for these parameters are hard-coded for any Houdini-products:
Available == 200
Expiry Date == 25-dec-2029

The algorithm for generating license keys changes very rarely (new types of licenses appear more often).
Therefore, in the "X-Force keygen/patcher" binary we can change the values of several bits responsible for the version number. And the keygen will most likely generate the “correct” license keys (for use with a patched license server) for the version of Houdini we need.
But, in fact, the keygen generates incorrect keys (from the point of view of the original Houdini licensing service).

In order for the Houdini licensing service to accept fake keys and consider them correct, there is a basic function (on Windows) "X-Force keygen/patcher". When you click "Patch License Daemon", the "X-Force keygen/patcher" stops the "Houdini Licensing Service", modifies the "sesinetd" file (and also
attempts to modify existing licenses to be compatible with the modified "sesinetd") and restarts Houdini licensing service.
Previously, there was a different practice for Windows: X-FORCE provided only a key generator and, separately, an already modified “sesinetd” file, which needed to replace the original file.

!!!! On Linux/Mac it is not possible to modify "sesinetd" with "X-Force keygen/patcher" !

X-FORCE provides for these OSes an already modified "sesinetd" file, which needs to be overwritten by the original file manually.
Additionally, ONLY a modified "sesinetd" file and "installation instructions" are provided for MacOS.

!!!! There is not even a license key generator provided for MacOS!
To generate keys, you will need to use the X-FORCE key generator running on any computer running Windows or Linux, entering in "X-Force keygen/patcher": "Server Name" And "Server Code" (taken from your MacOS).

As I've previously shared, Houdini's licensing service is constantly evolving. And, at some point, the patcher can no longer correctly modify "sesinetd".
Of course, an unpatched "sesinetd" considers the keys generated by "X-Force keygen/patcher" to be invalid.

But the Houdini licensing service also has positive qualities that are very important for us.
Each new Houdini build does not require a server and a license server of the same version as the build version.
This means that we only need to install the licensing service once and patch that licensing/licensing service using "X-Force keygen/patcher". After that, generate and enter licenses for different versions of "Houdini", using the "X-Force keygen" intended for specific versions of "Houdini".
In the future, we can install/reinstall any other versions of "Houdini" and they will automatically use the licenses already installed on the system.

!!!! At the same time, you need to understand that with each new installation of "Houdini", you need to uncheck the option in the installer: "Licensing server" !!!
Otherwise, the patched license server will be replaced with a new original license server!
However, changes to the original license server may be incompatible with the current “X-Force keygen/patcher”.
In this case, you will not be able to fix the situation using “X-Force keygen/patcher”.
Because “X-Force keygen/patcher” will not be able to correctly patch the license server!
And then you will have to install an older version of "Houdini" (with check option "Licensing server"), for which "X-Force keygen/patcher" works correctly.
Using the latest published version of "X-Force keygen/patcher" ("SideFX Houdini 19.5 Keygen/Patcher - X-Force 2021"), you can generate license keys for "Houdini-19.5" and patch "Houdini License Server" - "sesinetd" (included in the latest production version of Houdini - 19.5.493).

!!! * Remember that in order for the "X-Force keygen/patcher" to be able to start and stop services, it must be running as Administrator!!!

!!!! * Remember that when you run "X-Force keygen/patcher" it will immediately stop the "HoudiniLicenseServer" service, even if you do not enter or press anything!!!! At least this is true on Windows for the latest version of "X-Force keygen/patcher".
At the same time, the interface in the already running "Houdini License Administrator" utility WILL NOT BE UPDATED! And it will allow you to start importing licenses manually. But after entering the keys, it will freeze and give an error.

Therefore, always before entering keys in the "Houdini License Administrator" (hkey), make sure that you have the "HoudiniLicenseServer" (sesinetd) service running.
To do this, update the contents of the "Server Information" tab using: View -> Refresh (or Ctrl + R).
And restart the "HoudiniLicenseServer" service and update:
"Houdini License Administrator" -> File -> License Tool Services...
"License Tool Services": Sesinetd - press "Start".
"Houdini License Administrator" -> View -> Refresh (or Ctrl + R).
If "HoudiniLicenseServer" is not running, then your local server will not be accessible by "Houdini License Administrator". And "Houdini License Administrator" will issue a warning or prompt you to perform a network login (Log In...)

In Linux: Run the sesinetd startup scriptt located in "/etc/init.d", use:

Link(s):
/etc/init.d/sesinetd {start}

In Mac: In a terminal, use:

Link(s):
sudo launchctl load /Library/LaunchDaemons/com.sidefx.sesinetd.plist

In Windows: you can manage services in Control Panel (Run as Administrator):

check/start/stop "HoudiniLicenseServer" in Control Panel -> Administrative Tools -> Services

Or Run CMD as Administrator and use:

Link(s):
sc start HoudiniLicenseServer

Well, it's just a theory. Let's look at the Houdini installation process with illustrations and explanations.
Target platform: "Microsoft Windows 10 Enterprise 2021 LTSC"(Ru)
There are no internet or network connections.

00. Preinstallation

This shouldn't have a negative impact, but:

00.01. If you have/have previously installed any versions of "Houdini", stop and uninstall the services ("HoudiniServer" and "HoudiniLicenseServer"):
Run cmd as Administrator, Paste these lines into cmd one by one, pressing Enter after each line.
Link(s):
sc stop HoudiniLicenseServer
sc stop HoudiniServer
sc delete HoudiniLicenseServer
sc delete HoudiniServer

And remove all "sesinetd.*.*" and "hserver.*.*" in:

Link(s):
C:\Windows\SysWOW64\
C:\Windows\System32\
C:\Windows\System32\config\systemprofile\AppData\Local\CrashDumps

00.02. Since we are going to generate new licenses for all Houdini-19 products, these licenses will work for lower versions of Houdini (18.0/18.5/19.0/19.5). It doesn't matter whether we have these versions of Houdini installed or will be installed in the future.
Therefore, if you do not have Houdini version lower than 18 installed, you can completely delete the "key" folder in Windows ("C:\Windows\keys").

00.03. Delete these entire folders along with their contents:

Link(s):
C:\Users\User_Name\AppData\Local\Houdini License Administrator
C:\Users\User_Name\AppData\Roaming\SideFX
C:\Program Files\Side Effects Software\License Server
C:\Program Files\Side Effects Software\Houdini Server

00.04. Delete the hiden file:

Link(s):
C:\Users\User_Name\AppData\Local\.sesi_licenses.pref

00. *
Please note that in the directories:
Link(s):
C:\Users\User_Name\Documents\houdiniXX.X

contains settings and configurations for specific versions of Houdini, many of which will be used for the newly installed version of Houdini.

I already have several versions of Houdini installed, the license server is patched and the licenses are installed on the system.
Let's try to install a newer production version of "Houdini" (19.5.493 Python 3.9), with check option "Licensing server":

Download Houdini from SideFX Houdini Daily Builds:

Link(s):
https://www.sidefx.com/download/daily-builds/

For exemple: Download Houdini 19.5.493 for Windows (Python 3.9): "houdini-19.5.493-win64-vc142.exe":
Link(s):
https://www.sidefx.com/download/download-houdini/98114/

In order to access Houdini downloads, you need to register on the SideFX website (It's very fast. You just need any email address to activate your account.)
PART ONE: Installation Houdini and modifi "Houdini License Administrator" ("sesinetd")

01. Install Houdini 19.5.493 with check option "Licensing server".

This image has been resized. Click this bar to view the full image. The original image is sized 996x386.

BEFORE STARTING HOUDINI:

02. Launch the "Houdini License Administrator" (as ADMINISTRATOR !!!):

"C:\Program Files\Side Effects Software\Houdini 19.5.493\bin\hkey.exe"

N.B.: Since the original “Licensing server” was installed during installation, all licenses registered in the system (generated using “XFORCE Houdini Keygen”) are defined as incorrect.

03. Launch the "License Tool Services":

"Houdini License Administrator" -> File -> License Tool Services...

Click this bar to view the full image.

04. "License Tool Services": Sesinetd - press "Stop", Hserver - press "Stop".

05. "License Tool Services": press "Close".

06. "Houdini License Administrator" -> tab "Server Information".

07. Start "XFORCE Houdini Keygen" (as Administrator !!!).

08. "Houdini License Administrator" -> tab "Server Information" -> find your "Server Name" And "Server Code".

09. "XFORCE Houdini Keygen / Patcher" -> Enter your "Server Name" And "Server Code".

This image has been resized. Click this bar to view the full image. The original image is sized
1920x1200.

N.B.: In fact, in order to just patch the “Houdini License Administrator” (sesinetd), we do not need to specify the “Server Name” And “Server Code”. This data is not used to modify sesinetd. This data will only be needed at the stage of generating license keys. Therefore, if you only need to patch the
"Houdini License Administrator" (sesinetd) service file, you can skip the "Server Name" And "Server Code" information.

10. "XFORCE Houdini Keygen / Patcher" -> press "Patch License Daemon"

Click this bar to view the full image.

N.B.: "XFORCE Houdini Keygen/Patcher" reported that:

- detected the installed service "HoudiniLicenseServer", launched from:
"C:\Program Files\Side Effects Software\License Server\sesinetd.exe"
- stopped the "HoudiniLicenseServer" service
- discovered and successfully patched 36 license keys.
- successfully patched "sesinetd".
- successfully restarted the "HoudiniLicenseServer" service.

N.B.: We deliberately stopped Houdini services manually. And we will also restart these services ourselves, manually.
The fact is that "XFORCE Houdini Patcher" sometimes cannot stop/start Houdini services correctly (Even if "XFORCE Houdini Patcher" is run as Administrator!). And very often, "XFORCE Houdini Patcher" cannot correctly start/restart Houdini services after successfully modifying the service (At the same time, it
may be reported that the services were successfully restarted. But, in fact, one or both services may remain not running).

11. "Houdini License Administrator" -> tab "Installed Licensies"

12. "Houdini License Administrator" -> View -> Refresh (or Ctrl + R)

N.B.: We see that the "HoudiniLicenseServer" service is running and the "Houdini License Server" considers that all installed licenses are valid.
But at the same time, the "HoudiniServer" service is not running!

Click this bar to view the full image.

13. Launch the "License Tool Services":
"Houdini License Administrator" -> File -> License Tool Services...

14. "License Tool Services": Sesinetd - press "Start", Hserver - press "Start".

15. "Houdini License Administrator" -> View -> Refresh (or Ctrl + R)

This image has been resized. Click this bar to view the full image. The original image is sized
1920x1200.

16. "Houdini License Administrator" -> tab "Server Information"

This image has been resized. Click this bar to view the full image. The original image is sized
1920x1200.

N.B.: We see that the licensing system is fully functioning, all services are running, all licenses are valid.

All that remains is to generate and enter licenses for the server and all Houdini-products...

PART TWO: Generation and installation Houdini License Keys

N.B.: Generating and installing license keys is an independent procedure. We don't need Houdini services running to generate keys. We don't even need Houdini installed if we know the "Server code" for the target system on which the "Houdini License Server" is installed. Therefore, we can generate license
keys on any Windows or Linux system. For this we only need "Server code" and "Server name".

N.B.: Be aware that once you run "XFORCE Houdini Keygen/Patcher" it will stop the "HoudiniLicenseServer" service!
"XFORCE Houdini Keygen / Patcher" will stop the "HoudiniLicenseServer" service even if you just start it and do not enter/click anything! After closing "XFORCE Houdini Keygen/Patcher" it will not automatically restart Houdini services!!!

N.B.: If you monitor the status of services using already running utilities:
Control Panel -> Administrative Tools -> Services
or with
"Houdini License Administrator" -> File -> License Tool Services...
Then, keep in mind that information about the status of services, as a rule, is not updated automatically!
You need to update information about the state of services manually:
Control Panel -> Administrative Tools -> Services -> Action -> Refresh (or F5, or Refresh in right click context menu)
or
"Houdini License Administrator" -> View -> Refresh (or Ctrl + R)

N.B.: To successfully enter license keys through the "Houdini License Administrator" interface, the "HoudiniLicenseServer" service must be running!

So let's continue...

17. If you have not yet launched "XFORCE Houdini Keygen / Patcher":
Start "XFORCE Houdini Keygen" (as Administrator !!!).

18. If you have not yet launched "Houdini License Administrator":

Launch the "Houdini License Administrator" (as ADMINISTRATOR !!!):
"C:\Program Files\Side Effects Software\Houdini 19.5.493\bin\hkey.exe"

If you have not started/stopped the "HoudiniLicenseServer" service, then when you start the "Houdini License Administrator" you will see the following message:

This image has been resized. Click this bar to view the full image. The original image is sized
1026x651.

19. Close "Log in to SideFX" window and close "Houdini License Administrator Message" window.

20. Launch the "License Tool Services":

"Houdini License Administrator" -> File -> License Tool Services...

21. "License Tool Services": Sesinetd - press "Start", Hserver - press "Start".

This image has been resized. Click this bar to view the full image. The original image is sized
1026x704.

22. "Houdini License Administrator" -> View -> Refresh (or Ctrl + R)

This image has been resized. Click this bar to view the full image. The original image is sized
1027x704.
23. "License Tool Services": press "Close".

This image has been resized. Click this bar to view the full image. The original image is sized
1026x705.

24. "Houdini License Administrator" -> tab "Server Information".

25. "Houdini License Administrator" -> tab "Server Information" -> find your "Server Name" And "Server Code".

26. "XFORCE Houdini Keygen / Patcher" -> Enter your "Server Name" And "Server Code".

Click this bar to view the full image.

27. Launch the "Import License(s)":

"Houdini License Administrator" -> File -> Import License...

Click this bar to view the full image.

28. Launch the "Houdini Manual Key Installation Dialog":

"Import License(s)" -> press "MANUAL INSTALL"

29. "XFORCE Houdini Keygen / Patcher" -> press "Generate Keys"

30. Copy one by one the first five keys generated by "XFORCE Houdini Keygen / Patcher" in the "Houdini Manual Key Installation Dialog" into the "Keys" fields:

Click this bar to view the full image.

31. "Houdini Manual Key Installation Dialog" -> press "ACCEPT"

32. The "Houdini License Administrator Message" window will appear with a message stating that all five keys were Installed successfully.

33. Close "Houdini License Administrator Message" window.

34. Launch the "Import License(s)":

"Houdini License Administrator" -> File -> Import License...

35. Launch the "Houdini Manual Key Installation Dialog":

"Import License(s)" -> press "MANUAL INSTALL"

36. Copy one by one the last four keys generated by "XFORCE Houdini Keygen / Patcher" in the "Houdini Manual Key Installation Dialog" into the "Keys:" fields

Click this bar to view the full image.

37. "Houdini Manual Key Installation Dialog" -> press "ACCEPT"

38. The “Houdini License Administrator Message” window will appear with a message stating that all parts of the key are Installed successfully.

39. Close "Houdini License Administrator Message" window.

40. Close "XFORCE Houdini Keygen / Patcher" window.

"XFORCE Houdini Keygen / Patcher" -> press "Close"

41. "Houdini License Administrator" -> tab "Installed Licensies"

42. "Houdini License Administrator" -> View -> Refresh (or Ctrl + R)

N.B.: The first line of the license key is the license key for the "Houdini License Server" (sesinetd) installed on your server. This key does not appear in the list of installed licenses. Licenses are shown only for Houdini-products.
Therefore, despite the fact that we generated and imported nine license keys, only eight newly installed licenses will be displayed in the "Houdini License Administrator", for eight Houdini-products version 19.5:

Product Name: Houdini FX. Keystring Name: Houdini-Master. Executable Name(s): houdini, houdinifx, hmaster...
Product Name: Renderer. Keystring Name: Render. Executable Name(s): mantra, karma, hrender...
Product Name: Karma Renderer. Keystring Name: Karma-Render. Executable Name(s): karma...
Product Name: Houdini Engine. Keystring Name: Houdini-Engine. Executable Name(s)[Batch]: hbatch, hython...; [Plug-in]: N/A [open with plug-in]...
Product Name: PilotPDG. Keystring Name: PDG. Executable Name(s): pilotpdg...
Product Name: Beta. Keystring Name: Beta. Executable Name(s): ...
Product Name: Houdini Core. Keystring Name: Houdini-Escape. Executable Name(s): houdinicore, hescape...
Product Name: Houdini Experimental. Keystring Name: Houdini-Master-Experimental. Executable Name(s): hexper...

Click this bar to view the full image.

img_32

N.B.: If you have unexpired licenses of any Houdini-products (whether real or fake), then to use lower versions of these Houdini-products you DO NOT NEED ADDITIONAL LICENSES FOR THESE OLD VERSIONS of Houdini-products!!!

We have just installed fresh licenses for all Houdini-19.5-products.

This means that these licenses are enough to simultaneously run Houdini-18.0/18.5/19.0/19.5 on two hundred DIFFERENT workstations (on the network served by this Houdini License Server), with all versions of Houdini-products fully available for all these versions of Houdini !!!
For each individual workstation, the number of simultaneously running copies of Houdini-products (any version) is not limited by anything (except for available memory).
Therefore, we can remove all licenses for Houdini-18.0-18.5-19.0.
During the demonstration, we installed additional licenses for all Houdini-products version 19.5.
These "duplicate" licenses can also be deleted.
You also need to remove all duplicate licenses for the “Houdini License Server” itself.

Click this bar to view the full

image.

43. Open the license file "licenses" in a text editor such as Notepad. I'm using Notepad++.
File -> Open: "C:\Windows\keys\licenses"

N.B.: In the "keys" folder there may be other files named "licenses" with some extension! We need a "licenses" file WITHOUT EXTENSION!!!

44. Select and delete all lines with license keys for Houdini-18.0/18.5/19.0. We also remove unnecessary licenses for the license server. We leave only one key containing the license for our license server. After editing, save the file.

This image has been resized. Click this bar to view the full image. The original image is sized 2945x1200.

45. "Houdini License Administrator" -> View -> Refresh (or Ctrl + R)

This image has been resized. Click this bar to view the full image. The original image is sized 1026x472.

img_34

N.B.: To update the license information in the current "Installed Licenses" view in the "Houdini License Administrator":
"Houdini License Administrator" -> View -> Refresh (or Ctrl + R)
If the license information has not been updated, restart Houdini services and update the view again:
"Houdini License Administrator" -> File -> License Tool Services...
"License Tool Services": Sesinetd - press "Stop", Hserver - press "Stop".
"License Tool Services": Sesinetd - press "Start", Hserver - press "Start".
"Houdini License Administrator" -> View -> Refresh (or Ctrl + R)

46. Launch Houdini-products in any combinations and quantities.

This image has been resized. Click this bar to view the full image. The original image is sized 3835x1200.
 img_35

47. PROFIT !!!

PART THREE: License server update. Repetition is the mother of learning.

Taking into account our experience and expanded consciousness, we will install the latest production build of Houdini 19.5.805 with the activated option: “Select component to install: License Server”.

....

The continuation will be completed after the publication of "XFORCE Houdini Keygen / Patcher" for Houdini-20.0 ...
....

is Offline

26 Thanks, 0 Dislike - iju, Chaolyte, ytre98, perryf, heisenberg198, 2snap, birdy, normal, EvilEnginer, isamarsh, upterror, ustsergrzn1968, tik1, r@nd0mX, vvshnn1, odineight, CGartist999, Hawkeye, Aketano, Ybbgal, Styh, art71, danfuerth, Drovosek, BR_Girl, bombolo thanked for this post

01-30-2024, 04:05:59 PM #2

bombolo but crack is a no work!

/s

Join Date: Nov 2013

Posts: 767
Thanks (Given): 398
Thanks (Received): 870

is Online

01-30-2024, 04:47:06 PM #3

Drovosek Quote:

Originally Posted by bombolo

but crack is a no work!

/s

Use meth
Lol (it just joke)
Join Date: Jun 2015 __________________
Posts: 7,505 List with helpful services:
Thanks (Given): 5634
Thanks (Received): 20858
Link(s):
https://forum.cgpersia.com/f3/guide-how-remove-redirects-advertising-sites-multiup-197272/
https://github.com/Drovosek01/awesome-images-hostings
https://github.com/Drovosek01/awesome-files-hostings/blob/main/Hostings.md

is Online

01-30-2024, 05:03:50 PM #4

danfuerth Good instructions that cover the basics of local license server daemons and license install steps.

Although I can licence this in my sleep, there are advanced steps here such as the virtual network card approach, the OFF Services that turn on during a batch call etc.

I think these instructions should cover the most important steps.

The license server daemon does not need to startup with Windows, it can be called and executed prior to running the main application.

Join Date: Aug 2012

Posts: 1,277 I chose the Virtual Network + batch approach as it offers some benefits such as having your main network connection off and the licensed application running with no issues, then exiting the application and having the virtual connection off, services back to disable and finally turning on your main connection
Thanks (Given): 73 and this happens instantaneously without the user intervention.
Thanks (Received): 996

It sucks we have to go down this route but there is really not much left to do, we must run all these applications on virtual network cards and call up the services as they are needed.

Another benefit of the virtual card which I never mentioned before is that you can choose your own MAC address and thus that OS and application drive image can be moved to another machine without ever breaking the network licence since the Mac address does not change since YOU manually added it
to the virtual network card.

Good Post and hope it helps everyone trying to install and license these applications.
__________________
I did not type this, my pet squirrel did!!

is Offline

1 Thanks, 0 Dislike - Drovosek thanked for this post

01-30-2024, 05:46:20 PM #5

bombolo Quote:

Originally Posted by danfuerth

It sucks we have to go down this route but there is really not much left to do, we must run all these applications on virtual network cards and call up the services as they are needed.

No, we do not "must run all these applications on virtual network cards". That is complete BS, perpetuated in countless threads by exclusively you.

Join Date: Nov 2013

Posts: 767
Thanks (Given): 398
Thanks (Received): 870

is Online

01-30-2024, 06:12:53 PM #6

Ybbgal Wow! what a nice long post. That required lots of work and effort to write. So special thanks for that!

Join Date: Sep 2013

Posts: 357
Thanks (Given): 439
Thanks (Received): 153

is Online

01-31-2024, 01:16:51 AM #7

danfuerth Quote:

Originally Posted by bombolo

No, we do not "must run all these applications on virtual network cards". That is complete BS, perpetuated in countless threads by exclusively you.

Could type for hours on the benefits of the Virtual network card but let's keep it simple...

Join Date: Aug 2012

You can run Windows 10 with all it's services on, no firewall, no antivirus, install the Foundry, Autodesk, Adobe services and leave them running that choice is yours.
Posts: 1,277
Thanks (Given): 73
Thanks (Received): 996
If you do take backups and security seriously though :

Many people here are running the batch and virtual network licensing approach as this does not break the application license if you move that drive to another machine, this is very useful for the OS+Applications backup images transfers in case you want to try all those apps in a new machine for example
without going through the licensing again.

If you install to the local main network connection the license is now broken when you move that OS to another system as the IP, Gateway, and Mac address will be different.
__________________
I did not type this, my pet squirrel did!!

Last edited by danfuerth; 01-31-2024 at 01:37:52 AM.

is Offline

01-31-2024, 02:06:01 PM #8

bombolo I don't want to clutter this researched and extensive thread by timpriest, but I'll answer you this:

Quote:

Originally Posted by danfuerth

Could type for hours on the benefits of the Virtual network card but let's keep it simple...
 "Having benefits" and "being mandatory" are statements 200000 miles apart. Your original statement is "we must run all these applications on virtual network cards". That is again, complete BS, especially when talking about Houdini. And you are replying to timpriest post like he encouraged running Houdini
that way, yet he didn't even implied anything like that.
Join Date: Nov 2013
Posts: 767 Your statements are like this:
Thanks (Given): 398
Thanks (Received): 870 There are benefits to being vegan, therefore - "It sucks we have to go down this route but there is really not much left to do, we must be vegan"

There are benefits to having installed home camera surveillance system, therefore - "It sucks we have to go down this route but there is really not much left to do, we must install home camera surveillance system"

There are benefits leaving city life and start sheep farm, therefore - "It sucks we have to go down this route but there is really not much left to do, we must start a sheep farm"

etc etc

Quote:

Originally Posted by danfuerth

You can run Windows 10 with all it's services on, no firewall, no antivirus, install the Foundry, Autodesk, Adobe services and leave them running that choice is yours.

You are making strawman argument, nowhere in this thread I even implied anything like that, actually if you check my post history on this forum I advised users exactly opposite.

Quote:

Originally Posted by danfuerth

Many people here are running the batch and virtual network licensing approach as this does not break the application license if you move that drive to another machine, this is very useful for the OS+Applications backup images transfers in case you want to try all those apps in a new machine for
example without going through the licensing again.

If you install to the local main network connection the license is now broken when you move that OS to another system as the IP, Gateway, and Mac address will be different.

Define many, and by which method did you come at that number. As for your point of moving drive to another machine, again, it's such a bullshit argument - you gonna try what in new machine? Test apps? You gonna use os drive from 5950x + 3080ti on x570 board machine in your i9-13900K + 4090 on
Z790 board? Yeah, good luck with that.

is Online

Quick Reply

Message:

Fonts Sizes

Options

Quote message in reply?

Post Quick Reply Go Advanced

« The difference between Plasticity CAD and SOLIDWORKS | Free Cascadeur Bridge for Blender »

-- BlueFox CGPersia Forums - Archive - Top