View Source

The information on this page refers to License Statistics v6.7 and newer, which introduced the License Statistics Agent.

The License Statistics Agent enables client usage monitoring for applications that are licensed on an end-user host rather than running on a license server. The License Statistics Agent communicates between these applications and License Statistics. Currently, the License Statistics Agent allows monitoring of Autodesk license usage on end-user hosts.

Installation

The License Statistics Agent runs as a service in background.

License Statistics Agent is currently available only for Windows (64-bit).

Requirements:

Windows 10 or Windows Server 2012+ (64-bit)
memory: 1GB
cpu: 2 cores
disk: 1GB

Installer (msi) is available on website in the same place as licstat installers.

It's also included to licstat windows installer as separate msi file in "tools" directory (by default: C:\Program Files\X-Formation\License Statistics\tools).

Architecture:

all of the application files are kept in Program Files by default
all user data is kept in C:\ProgramData\X-Formation\License Statistics Agent folder (includes logs, configuration file, etc)

Installer steps:

Initial screen
EULA
Installation folder
Configuration form
Confirmation
Summary (with option to start the service)

Configuration

One of the installer steps is configuration form. In contains 2 fields:

License Statistics URL which is an endpoint to specific license server configured in licstat. It can be taken from licstat administration page using "Copy Agent URL to clipboard" action available on the Realtime License Servers grid available for all Autodesk license servers.

Agent API Token which is an authorization token. It can be generated in Preferences->API. The token should contain Agent scope, only administrators can generated tokens with this scope.

Uninstalling

Uninstaller is standard solution. Uninstaller stops the service and removes it from the system. Optionally it can also remove user data, which are logs, configuration file etc.

If the user data will stay, it will be re-used again in case of Agent next installation, eg. configuration data will be automatically fill-out on the configuration installer form.