Setting License Model Policies

Policies allowed by a license model are configured after the license model attributes are defined. These settings affect all entitlement line items using the license model, and they are applied to activation both from the Producer Portal and from the End-User Portal.

All of these policies are applied per entitlement line item. For activations done with a Web register key, policies are applied per the entitlement line item in the simple entitlement created when the Web register key is redeemed.

License Model Policies

Policy

Description

Number of Rehosts

The number of times a customer can rehost a license generated from a particular entitlement item.

Number of Returns

The number of times a customer can return a license generated from a particular entitlement item.

Number of Repairs

The number of times a customer can repair a license generated from a particular entitlement item.

Number of Extra Activations

The number of extra activations allowed for an entitlement line item. This is the additional number of unpurchased copies of a product the customer is allowed to activate.

Cancel License Policy

If Yes, on a return, a returned license is credited back to entitlements.

Virtualization Policy

For trusted or embedded license models, determine whether to allow activations on virtual machines. This policy can be set or reset at the license model level or at the entitlement level. Selections are:

• Specify Value Now, then click Yes or No
• Specify Value at Entitlement Time

If an activation request comes from a virtual machine, FlexNet Operations evaluates the product’s virtualization policy. When virtual machine activations are allowed, FlexNet Operations attempts to use the product’s virtualization-aware transaction key to configure trusted storage. (If no virtualization-aware transaction key exists, FlexNet Operations reports an error.) When virtual machine activations are not allowed, the activation fails.

If an activation request comes from a physical machine, the virtualization policy is not evaluated at activation time.

The virtualization policy is supported for licenses generated by FlexNet Publisher version 11.10 or later.

For trusted license models, if virtual machine activations are allowed, determine whether to deny license repair if the virtual machine’s ACPI Generation ID (UMN5) is changed. This policy can be set or reset at the license model level or at the entitlement level. Selections are:

• Specify Value Now, then click Yes or No
• Specify Value at Entitlement Time

By default, this is set to Specify Value Now/Yes. Repair requests from physical machines are not impacted.

The repair policy is supported for virtual machine licenses generated by FlexNet Publisher version 11.12.1 or later.

Redundant Server Policy

Redundant servers are supported with certificate-based licensing only for floating counted, floating uncounted, and nodelocked counted license models.

Do you want to configure redundant servers?

• Yes—The license model supports three-server redundancy for failover support. This is a capability available with certificate-based licenses. When you activate the license, you define the three-server host IDs that are a part of this configuration. For more information about three-server redundancy, see the FlexNet Publisher Licensing Toolkit documentation.
• No—The license model does NOT support three-server redundancy.

Number of Reinstalls

If a customer has reinstalled a host’s operating system (for example, due to a system crash), the trusted storage on the host is lost. Activation must be reconfigured. In this case, you can choose to allow the customer to obtain a license without consuming the entitlement count.

FlexNet Operations determines whether a user is reconfiguring activation for a specific host using host identifiers like UMN Types 1, 2, 3, and 5 and MID (Machine Identifier).

FlexNet Operations tries to match the host using host identifiers according to the FNP client version and host identifiers sent in the request. (Not all activation requests contain the FNP client version or all of the host identifiers.) If the FNP client version is not sent in the request, the order the host identifiers are checked is UMN1, MID, then UMN2. For FlexNet Operations to correctly handle requests from a range of FNP client versions, UMN values are checked from UMN1 to newer UMN versions, and lastly MID is checked.

• You can choose to enforce the same policy for any host identifier received. To configure this, click Specify Value Now and provide a value.
• If you want to specify different policies for each host identifier, click Specify Value Now and select Advanced. Then specify the policy for each host identifier.
• If you want FlexNet Operations to always provide the license to the user without decrementing count for a reinstall operation, and not enforce any policy, then select Ignore Policy.

Note:Depending on the machine that issued the request, FlexNet Operations may not receive all identifiers in a given activation request. Refer to the FlexNet Publisher Licensing Toolkit documentation for more information on host identifiers.

Host ID Policies for Producer Portal

A host ID is an identifier used to uniquely identify a specific machine. A host ID policy is a rule that defines what type of information about the system is used to identify the machine. Example host ID types are host name, IP address, disk serial number, etc. This policy allows you to specify which host ID types (for example, the host name and IP address) are available when activating a license.

When you activate a license, you can define a server host ID to ensure the license is used on only on a specific license server. In addition, you can define a nodelocked host ID that allows only a specific client (or user) to check out the feature and run your application.

The policies in this section affect activations performed using the Producer Portal. These settings do not apply to activations performed in the End-User Portal. See Host ID Policies for Portal UI to separately configure host ID policies in the End-User Portal.

There are two policies for you to define:

• Server Host ID Policies—This policy helps publishers restrict host ID types for server hosts.
• Nodelocked Host ID Policies—This policy helps publishers restrict host ID types for nodelocked hosts.

For each policy, select a value:

• Specify Value Now—Define the list of valid host ID types for this license model. All licenses generated using this license model can use only these host ID types.
• Specify Value at Entitlement Time—Host ID types must be specified at entitlement time. This gives the publisher flexibility to specify different host ID types for different entitlements.
• Ignore Policy—Any host ID type can be used.

Notice that host ID types are grouped into families related to their platform/environment: legacy, virtualization-aware (prefixed with PHY, VM, VMW, HPV, or LMB), and cloud-specific (prefixed with AMZN). For more information about the host ID type options displayed, see Special Host ID Types.

Host ID Policies for Portal UI

Publishers can restrict host ID types used during license generation from the End-User Portal using this policy. Refer to Host ID Policies for Producer Portal for information on policy settings. Also see Special Host ID Types for details about the host ID type options displayed.

Note:If users who have override policy permission log in, all host types are displayed to them, regardless of the policy settings, as they can choose to generate licenses for host types not allowed by policy.