Overview
Default beacon behavior is to record beacon hostname details in agent policy to be used by FlexNet Inventory Agent processes when making a connection to the beacon. However for production deployments it is good practice to configure agents to use a DNS CNAME (alias) record that maps to the appropriate IP address for communicating with beacons. Configuring a DNS CNAME record for each beacon in this way simplifies certificate management, communication through a reverse proxy, disaster recovery, migration, and rebuilding compromised servers.
This article describes how to set the NetworkName setting in the C:\Program Files\Flexera Software\Inventory Beacon\DotNet\conf\BeaconEngine.config file to achieve this.
Configuration steps
Complete the following steps to configure the name that is included in agent policies for communicating with a beacon:
- Configure a DNS CNAME (alias) record that can be resolved by all devices that may need to communicate with the beacon to point to the appropriate IP address. This may be the IP address of the beacon itself, or a device such as a reverse proxy if network traffic is to be routed through such a device.
- Use a text editor to edit the following file on the beacon: C:\Program Files\Flexera Software\Inventory Beacon\DotNet\conf\BeaconEngine.config (adjust the path as necessary if the installation directory of the beacon software is different).
- Modify the networkName property contained within the BeaconEngine.config file to use the DNS CNAME that has been configured.
- Save the file. Optionally, restart the FlexNet Beacon Engine service to have the beacon pick up the change immediately rather than waiting for it to be picked up according to a built-in setting refresh schedule.
Here is an example of how the networkName setting appears in the BeaconEngine.config file:
<beaconCommonSettings [...] networkName="MyServer.MyDomain.com" [...] />
Additional Information
See the following page for additional information about beacon configuration:
Related Articles
How to configure FlexNet Inventory Agent components on a beacon to gather inventory and usage 45Number of Views Configuration of IIS for the beacon web server fails when using a custom website name 15Number of Views Using client certificates for mutual TLS (mTLS) authentication between internet-facing beacons and FlexNet inventory agents 100Number of Views Users show blank or “-” as full name or display name in Snow SaaS Management 75Number of Views Oracle instances may not be imported when different instances on the same host report the host name differently and invent… 6Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago