Process Overview

Upgrading from the 2014 or later (web-based) releases to FlexNet Manager Suite 2024 R1 is conceptually very straight-forward:

• For any 2014 release, if you had installed any language packs (localizing the user interface into, for example, German or Japanese), these should be uninstalled first. (The current release installs language support for all available languages.)
• Run the scripts provided to upgrade the underlying databases.
• Run the installer on (each of) your central application server(s) to update the product itself.
• If you had previously implemented any custom scheduled tasks on your application server (or, in a multi-server implementation, your batch server), consider upgrading these to use the shadow copy approach that helps meet high-availability goals by allowing live updates to Windows .NET assemblies (and dependent libraries) without interrupting normal operations of FlexNet Manager Suite.
• Manage your inventory beacon updates:
  • If migrating from 2014, visit each inventory beacon and run the installer (available through your updated web interface of FlexNet Manager Suite) to update the beacon. While there, you may prefer to tweak the default schedules in the new, in-built beacon scheduler; and you need to update connection details for adapters previously run as Windows Scheduled Tasks.
  • If migrating from 2014 R2 or later, your inventory beacons are self-updating. You can manage the upgrade process (including testing, pilot groups, and roll out) as described in FlexNet Manager Suite Online Help > What Is an Inventory Beacon? > Upgrading Inventory Beacons.

At this point, your system is upgraded and functional. You may also choose, as part of the upgrade project, to extend your implementation with some of the newly supported features, as described in the Features by Release documentation. In general, details about these enhanced features are not included in this document, which focuses on the upgrade process itself.