I always recommend and it is frequently implemented to put the SoldTo.DisplayName in the Notice field when defining a license model. This way the application can read this data from the license and use it in for example a help/about screen. Example syntax for a license model Notice field for this would be: Sold To {SoldTo.DisplayName} Other common Pre-Defined substitution variables include: Serial Number = {EntitlementLineItem.activationId} (if not already using this for other reason) Also {Entitlement.id} If you are using FlexNet Publisher TS activation including the {Fulfillment.id} can be helpful. Issuer = Hard code company name that is issuing the entitlement and license.   Additional Note: the OP asked about a "comment" for a license file. There is a way to specify  hard coded text to appear at the top of an FNP license file by building it into the VCG, but it does not use the substitution variables. Second additional Note: the OP asked about custom attributes to be added to a license. FNO does allow the creation of custom license attributes that essentially become substitution variables (they're just not pre-defined) that can be used in VENDOR_STRING, NOTICE, etc. See online help section title "Custom Attributes in License Strings". ... View more

Regarding FlexNet Embedded: The CONTAINER_ID host/device ID type is not meant for nodelocking since it is easily changeable. But it is great for a license server to distinguish between one running container and another. Use the license server to enforce the total number of containerized clients that can be run at one time. i.e. license server can not serve licenses from a VM and don't use CONTAINER_ID for a license server. Best choice is to use a Cloud License Server if you have that option available to you. You may need to adjust the borrow-renew interval to get the right balance of quickly freeing up a license if the client goes away vs having the client frequently check with the license server. Revenera has plans to include CONTAINER_ID host id type to FlexNet Publisher in a future release. Regards, Walt ... View more

Ravikiran I just noticed you asked your question on the FlexNet Publisher forum. I want to clarify that I was referring to FlexNet Embedded. FlexNet Publisher does not natively support .NET Framework or .NET CORE. Only C libraries are provided for FlexNet Publisher. ... View more

I would add while FlexNet Embedded supports .NET CORE, that there is a separate SDK for it. If you only have access to the FNE .NET XT SDK, you will need to purchase the FNE .NET CORE XT SDK. ... View more

Hi Andy,   End users do NOT have to provide their identifiable information in order to use the web reg key. The reseller could do the registration. You should make your resellers a partner account type. This will allow you to grant them a bulk entitlement and register it to an anonymous (to you, but not to them) end customer account. The partner or the end customer can then activate without providing details. The device will be owned by whatever account name the partner provides when registering with the web reg key. The end customer, just gets an activation code and activates, they would have not ability to view entitlements or licenses.   You could do a similar process without web reg keys, but requires the partner account to use the Transfer Entitlement Line Item function in the  FNO customer portal.     See the attached screenshot of a partner owned entitlement in the customer portal prior to Transfer. While your original question seems simple, there are many subtleties to it, like does the end customer need ESD? Would some resellers share end customer info? Do reseller's end customers turn into or are at the same time direct customers? Who owns the device? Who is providing support? It is very typical for a software producer that is providing product support to an end customer to REQUIRE the partner to provide end customer information. Just because a partner/reseller doesn't want to provide end customer info, doesn't mean they can't be convinced that it is to their benefit to provide it. Let me reiterate, that if your "customer" wants to resell your software products, they aren't a customer but a partner.   ... View more

Hi Andy, If your "customer" is reselling your product, then they are really a Reseller (channel partner). A common approach to addressing this use case that we call "make to stock"... In FlexNet Operations, you can create Bulk Entitlements that will provide you a list of Web Registration Keys. Provide the WebRegKeys to your partner for resell. They or their customer can use the WebRegKey as an activation code. Typically software producers want to collect end customer registration info, but if your agreement with your partner doesn't allow that, you can limit the reg info you collect. You have the option to bill your partner based on the number of activations over the last month, quarter, etc. if you can't get them to pre-pay for the WebRegKeys. If the use case is more of a "make to order", then you can just create regular entitlements for your partner with activationIDs that they can re-distribute. All activations will look as if they belong to the partner.   Bulk entitlements and Web Registration Keys are covered in the documentation and online help. ... View more

This type of question should be directed to the software producer. In this case Tableau tech support. ... View more

ablihash, You should contact the provider of your licensed compiler product about support for early return of a borrowed license. This forum is meant for software producers using FlexNet Publisher to add licensing to their products. Your question as an end user of a Flex-enabled product may find an answer here but it is less likely to be monitored by anyone with that type of experience. I suggest you post your question to the FlexNet Manager discussion which is viewed by other end customers that may have similar experience and knowledge to share as yourself. https://community.flexera.com/t5/FlexNet-Manager-Forum/bd-p/FNMS-Discussion ... View more

Hi Paul, I understand that you are trying to understand the encoding of information in the FNE error string. I think you are more likely to find success getting an answer to your question by contacting Flexera Tech Support. If you still want to explore using the community forum to understand the error encoding then maybe someone else can comment, but I do not believe there is anything in the product documentation about it other than the description of the FlcErrorRef struct and its related functions. Maybe you've already figured out the problem with input parameter and the actual error message is now irrelevant, but if you still want to explore using the community forum to resolve the bad input parameter, it would help if you provided a code snippet or example of the function call that is throwing the error. ... View more