Specifying Agent Version for Auto-Updates (or Adoption)
FlexNet Manager Suite 2024 R1 (On-Premises)
The upgrade of deployed FlexNet Inventory Agents is controlled by settings stored in
the central operations databases. For that reason, this procedure is initiated
on your batch server/reconciliation server (or whichever server
includes that functionality, such as your processing server, or application server in smaller implementations).
Tip: The database
setting grants permission (through policy) to the FlexNet Inventory Agents to
perform self-upgrades (or even downgrades) to the specified version. The
setting, therefore, can only be put into effect on those platforms where the
FlexNet Inventory Agent includes self-update functionality, and where new
versions of the FlexNet Inventory Agent are included in the operations databases
(these are normally updated as part of a product upgrade). Currently, FlexNet Inventory Agents on Debian or Ubuntu Linux do not include self-update
functionality. On these platforms, you can do any of:
You can change the settings for self-update of the FlexNet Inventory Agent in either of two ways:- Deploy new versions of FlexNet Inventory Agent manually
- Use your preferred third-party deployment tool to publish updates to FlexNet Inventory Agents
- Uninstall the old version(s) of FlexNet Inventory Agent, and once again target the devices for adoption through FlexNet Manager Suite.
- In the web interface FlexNet Manager Suite (for details, see Inventory Agent for Automatic Deployment)
- By using the command-line utility described below.
Warning: If you are already using a third-party tool (such a Microsoft Endpoint Configuration Manager (previously Microsoft SCCM)) to install
updates of FlexNet Inventory Agent, do not allow FlexNet Manager Suite
to apply automatic updates as well – that is, prevent automatic updates
of FlexNet Inventory Agent by FlexNet Manager Suite by entering only the
following command line (see description
below):
.\ConfigureSystem.exe clear-agent-upgrades
Otherwise,
you risk your two technologies fighting over updates, because their target
versions are out of sync (so that the first upgrades to 13.5.0, and then the
second downgrades back to 13.4.0, or similar). This conflict can lead to damaged
installations and orphaned FlexNet Inventory Agents that cannot report
inventory. If this happens, the only cure is to completely uninstall, and then
reinstall, FlexNet Inventory Agent.Tip: With the command line
tool, options (such as
select-agent-upgrade
) must be spelled
out in full; but where an option requires additional parameters, these may
be:- Identified with a single dash, then a single character (normally the
first of the parameter name), followed only by a space to
separate the value. Example:
-v 13.2.0
- Identified with two dashes, then the full parameter name,
followed by either a space or an equals sign to separate the value.
Examples:
--version 13.2.0 --version=13.2.0
To configure FlexNet Inventory Agent self-updates by command-line utility:
Note: The change to new
authorized versions (one for each platform) of the FlexNet Inventory Agent is
applied globally. Each installed FlexNet Inventory Agent receives the self-upgrade
instruction in the same policy update, at whatever time they collect it. This may
result in many client devices downloading, self-updating, and uploading new
inventory in similar time frames.
The ConfigureSystem
executable allows other configuration settings besides those for installation and
updates of the FlexNet Inventory Agent – for example, managing licenses installed on
your application server, or managing your SAML (single sign-on) configuration.
For more information about the actions available with this utility, use either of these
commands:
.\ConfigureSystem.exe help
.\ConfigureSystem.exe help action-name
FlexNet Manager Suite (On-Premises)
2024 R1