Inventory Beacons running in a proxy environment require both inventory settings and MSIE configuration.
Configuration of the FlexNet Beacon software (that operates on an inventory beacon server) is normally completed by the installer or may be configured manually, as described below.
Proxy support in FlexNet Beacon has the following limitations:
There are several possible settings affecting inventory beacon operation with proxy servers. This is because:
In smaller implementations that have only a single proxy server managing Internet access for an inventory beacon, it remains necessary to configure these multiple settings as described below.
The following process shows placeholders proxyServerURL and portNumber that must be replaced with the appropriate values for your implementation. As well, the special case [Registry] has the following default values on different systems:
This process must be completed on the inventory beacon.
When both the proxy server and the inventory beacon have been configured as described above, communications between FlexNet Beacon and the central application server operate as normal, allowing for downloads of rules and update packages for installed FlexNet inventory agents, and uploads of gathered inventory files.
This information is partially replicated from the online help for FlexNet Manager Suite. The online help is available both in FNMS and the Documentation Center. Note that the online help is customized for either on-premises or cloud implementation so that each type shows only the information relevant to the appropriate audience. In both cases, the relevant topic is available at FlexNet Manager Suite Help > Inventory Beacons > Inventory Beacon Reference > Configuring for Proxy Servers.
FNMS Cloud Online Help:
Dec 02, 2020 09:31 AM