Highlighted
Active participant

Re: Inventory Agent Configuration to Point to Beacon DNS rather than FQDN

Jump to solution
Hi,

Thanks a lot for your explanation. Could you also guide me abput below two points:

* which file are we referring to for this xml, please if you could provide location and file name.
* If we would like to have failover of beacon also.
* and if we need to change reporting beacon later, as this is devopment and later we would need to point agents to Production server.


Thanks in advance.

Thanks & Regards,
Fawad Laiq


$3nt fr0m h@ndh3ld, e>
Thanks & Regards,
Fawad Laiq
0 Kudos
Highlighted
Frequent contributor

Re: Inventory Agent Configuration to Point to Beacon DNS rather than FQDN

Jump to solution

Hi Fawad,

This is not an XML file. The configuration information is stored as text in the [HTTPAccessData] column in the [FNMSCompliance].[Beacon_MT] table.

There is one row per Beacon in this table. Obviously, you need access to the SQL Server database for updating these data.

All Beacons in your environment are configured as "Fail-over Beacons" by default.

In case you want to update an existing Beacon and point it to a different FNMS environment, follow these steps:

  • In the old (testing) FNMS environment, delete the Beacon from the FNMS Web UI
  • Create a new Beacon in the Web UI of the new (production) FNMS environment using the "Configure a Beacon" button.
  • Give the Beacon a name and generate a new unique ID for the Beacon
  • Download the new Beacon XML configuration file from the production FNMS environment to the existing Beacon
  • Update the old BeaconUID value in the Windows Registry on the existing Beacon in the HKLM > Software > WOW6432Node > ManageSoft Corp > ManageSoft > Common branch to match the new BeaconUID value. Leave the curly brackets {} around the BeaconUID value.
  • Import the new XML config file into the existing Beacon

After completing and saving your configuration on the Beacon, your Beacon should start communicating with the new FNMS environment.

 

0 Kudos
Highlighted
Active participant

Re: Inventory Agent Configuration to Point to Beacon DNS rather than FQDN

Jump to solution

Hi Erwin,

 

Thanks a lot for your help. I checked in BeaconEngine.config which I already changed. Now I have checked database also and it shows DNS, but agent still has FQDN.

 

Do I need to change something else as I did this change in BeaconEngine?

 

Thanks & Regards,
FL 

Thanks & Regards,
Fawad Laiq
0 Kudos
Highlighted
Active participant

Re: Inventory Agent Configuration to Point to Beacon DNS rather than FQDN

Jump to solution

Hi @erwinlindemann 

Moreover Fail-over Beacons setting still shows FQDN. Please help me as you wrote manually changing might be a little frustration.  Seems like I am missing something here.

 

Thanks & Regards,
Fawad Laiq
0 Kudos
Highlighted
Frequent contributor

Re: Inventory Agent Configuration to Point to Beacon DNS rather than FQDN

Jump to solution

Hi Fawad,

Updating the contents in the [FNMSCompliance].[Beacon_MT].[HTTPAccessData] column in the SQL Server database to contain the correct DNS name between the <NetworkName></NetworkName> tags followed by enforcing a refresh of the Policy and the "BeaconPolicy.xml" files on the Beacon as recommended previously should solve the problem.

The Beacon configuration - including the "NetworkName" property of the Beacon - will typically be downloaded from the FNMS Inventory Server to all Beacons in the "BeaconPolicy.xml" configuration file. This file is generated dynamically and will be downloaded to the following folder on the Beacon(s): \ProgramData\Flexera Software\Beacon. You can check this file for the correct DNS name of your Beacon(s).

Flexera agents will download selected data from the "BeaconPolicy.xml" - aka: the "Policy" - on a daily basis.

To speed this up, you can:

  • Enforce an update of the Policy by saving the configuration in the Web UI ("Discovery & Inventory > Settings") manually
  • Trigger the immediate download of the updated "BeaconPolicy.xml" to any beacon by clicking on the "Rules > Update Rules" button on the Beacon UI (this runs every 15 min by default)
  • Trigger the download of the Policy to any agent by running "mgspolicy -t machine" from a command prompt with elevated privileges on the computer running the Flexera agent (this runs daily by default)