Credentials for Zero-footprint Inventory

FlexNet Manager Suite 2023 R1 (On-Premises)

For Zero-footprint inventory, the required accounts and their privilege levels vary across computer platforms. For each target server, two accounts may be required:

• The first initializing account allows the inventory beacon to link to the target device, either download the appropriate files (for UNIX) or run a service (for Windows), and invoke the FlexNet inventory agent
• The second operational account is the account under which the FlexNet inventory agent is run.

On Microsoft Windows target devices

• The initializing account:
  • May be either a Windows domain account, or a local account on the target device
  • Requires full access to the Windows Service Control Manager on the target device (specifically, it must have the SC_MANAGER_ALL_ACCESS access right)
  • Must be appropriately registered in the secure Password Manager on the inventory beacon that is responsible for collecting inventory from this target device (for details, see FlexNet Manager Suite Help > Inventory Beacons > Password Management Page and its child topics)
  • May conveniently be the LocalSystem account, since this is required for the following operational stage.
• For the operational account, FlexNet inventory core components (and in particular the ndtrack component) run as the LocalSystem account.

On UNIX-like target devices

• The initializing account:
  • Is a local account on the target inventory device
  • Has ssh privileges on that device
  • Must be appropriately registered in the secure Password Manager on the inventory beacon that is responsible for collecting inventory from this target device (for details, see FlexNet Manager Suite Help > Inventory Beacons > Password Management Page and its child topics)
    Note: When you save the SSH account details in the Password Manager, be sure to specify the additional details for elevation of account privileges with your preferred tool (such as sudo or priv).
• For the operational account, FlexNet inventory core components (and in particular the ndtrack component) run as root.
  Tip: As always, it makes no difference whether you invoke the tracker directly as root, or whether you run as another account and use sudo (or similar) to elevate to root before invoking the tracker.