Keyboard Activation

FlexNet Operations 2014

Devices that cannot or are not permitted to access the internet can still have their features activated in FlexNet Operations—provided FlexNet Embedded (FNE) licensing is configured on the device to support keyboard activation.

The keyboard activation model requires a license template and assumes the device can generate a keyboard activation request code (an FNE-based, short code request), and that the device's user can communicate that code to the FlexNet Operations servers. Subsequently, a keyboard activation response code generated in FlexNet Operations must be delivered to the device so that it can be applied on the device to activate the requested features.

Note: An FNE device is not required to be known to FlexNet Operations; during the activation process, FlexNet Operations creates the device and sets its type to the default value configured in System Configuration > Embedded Devices.

As a disconnected device cannot communicate with the FlexNet Operations server over the internet, the keyboard activation response code might be sent from a separate terminal, spoken over a phone connection, or otherwise delivered to be input into the administrative console, but such implementation details are outside the scope of FlexNet Operations documentation.

The following subtopics discuss how to use FlexNet Operations to support incoming keyboard activation request codes.

Note: FlexNet Operations does not support Machine Types of Physical or Virtual for keyboard activation of unknown devices.

Note: FlexNet Operations does not support required custom host attributes for keyboard activation of unknown devices.

See Also

Configuring Embedded Devices Settings

Open topic with navigation