Manually Configuring an Inventory Beacon
FlexNet Manager Suite 2022 R1 (On-Premises)   
        Each inventory beacon must first be registered with the central
                    application server (see Register an Inventory Beacon).
                This is necessary so that:
            - The inventory beacon shares its GUID that identifies all its uploads
- The application server prepares packages of rules and other control information ("beacon policy") for download by this inventory beacon.
Once registered, an inventory beacon may need
                its details updated in such circumstances as:
- A password change on its parent system left the inventory beacon unable to download from, or upload to, its parent
- When installing the central application server, simple (unqualified) server names were registered for the batch server or inventory server; but for the inventory beacon, you need to edit these to fully qualified server names
- You wish to re-parent an inventory beacon.
Tip: If you use this process to re-parent an inventory beacon,
                the central application server is updated the next time the inventory beacon checks for updates. This means you can manage the
                re-parenting of inventory beacons within your hierarchy either from
                the inventory beacons themselves, or from the web interface for FlexNet Manager Suite. The built-in communication
                processes mean that your changes are synchronized within about 15 minutes (by
                default).
 Use the following process to update the parent connection details for an
                inventory beacon: To manual configure an inventory beacon:
FlexNet Manager Suite (On-Premises)
2022 R1