Known Issues

FlexNet Manager Suite 2024 R1 (On-Premises)

The following issues relate primarily to the stability of data available for collection from the App-V server.

Renaming packages

App-V allows you to rename packages (without necessarily changing their contents). When a package is renamed, the App-V application record no longer links to usage records within the appropriate App-V database. This means that the App-V server adapter (and, for App-V release 5.0 and later, the AppVMgmtSvr.ps1 PowerShell script) cannot import meaningful data for license consumption calculations. As well, the installer evidence generated from the App-V import now has a different name, which may not match evidence rules for the appropriate application. If that is the case, the consumption calculations for any license linked to an application that was linked to the previous installer evidence from App-V drops to zero (from this import connection).

For this reason, it is strongly recommended that you do not change the name of existing App-V packages in the App-V Management Server interface. Where renaming is unavoidable, remember that you may need to link the new package (represented as installer evidence in FlexNet Manager Suite) to the application to restore consumption calculations (especially for App-V release 4.6).

Updating package versions

Typical "rules" for applying installer evidence to identify applications use the publisher, the application, and the version recorded in the installer evidence. If you use a version number for your App-V packages (such as 1.0), and link exactly this App-V 'installer' evidence to the application record in FlexNet Manager Suite, then updating the version number of the package on your App-V Server (say, to 1.1) may break the link to the application, and the linked license loses its consumption as a result.

You can avoid this problem (at least for minor version changes) by using wild-cards in the linking of evidence to applications. To do this, after you have linked the App-V evidence to the application:

1. Navigate to the Installer Evidence Properties page.
2. Select the General tab.
3. Edit the Version property, using a wild-card percentage sign (%) to generalize the match across multiple versions. For example:
   • The original (say 9.2) is an exact match for only one version number.
   • A value of 9.% matches all the minor releases of version 9.
   • A value of % matches all versions of the App-V package with the same name and publisher.