Hi,
I have a scenario where FQDN and the DNS name is different for beacon. We are using DNS and the communication between agents , beacon and app server is on SSL.
I did change mgssetup.ini and point it to my beacon DNS. Policy download works fine, but upload fails from agent to beacon as in registery under Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Common\UploadSettings\{611F1577-A91E-43DD-XXXXXX} Host registry points to FQDN, same goes for DownloadSettings. I did change manually but then when I restart the service it change it back to FQDN. Which cause agent communication issues.
Thanks and Regards,
FL
‎Mar 10, 2020 10:33 AM
‎Mar 10, 2020 12:13 PM
Hi Fawad & JJensen,
Actually, the 'BeaconEngine.config' file in the \Program Files (x86)\Flexera Software\Inventory Beacon\DotNet\conf folder on your Beacon is being created and may be overwritten based on the content of the [FNMSCompliance].[Beacon_MT] table.Editing this file manually might result in a little frustration.
If you check the contents of the [HTTPAccessData] text column for your Beacon, you should see a XML snippet that looks like:
<?xml version="1.0" encoding="utf-16"?>
<HTTPEndPointStatus xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DownloadPath>ManageSoftDL</DownloadPath>
<UploadPath>ManageSoftRL</UploadPath>
<Protocol>https</Protocol>
<Port>443</Port>
<SelfHosted>false</SelfHosted>
<CredentialsRequired>false</CredentialsRequired>
<NetworkName><your-beacon-FQDN></NetworkName>
</HTTPEndPointStatus>
Obviously, you can customize the text between <NetworkName></NetworkName> to use the correct Beacon DNS name.
Then:
You should see that the 'BeaconEngine.config' as well as the .ndc file for failover settings on your Beacon(s) are being updated.
‎Mar 10, 2020 01:12 PM
‎Mar 10, 2020 10:41 AM
Hi @jjensen
Thanks for the quick response. So that means if I change this value over there this would automatically change the host name on my agents when they would retrieve the policy next time?
As I can see in ProgramData\Flexera Software\Staging\Common\ClientSettings\Default Failover Settings, there it is still pointing to FQDN name which I can see at agent in Program Files (x86)\ManageSoft\Launcher\Cache\Common\ManagedDeviceSettings file contents.ndc which seems same like registry still points to FQDN.
I tried changing settings in Default failover then my agent stopped downloaing the machine policy.
Thanks and Regards,
FL
‎Mar 10, 2020 11:00 AM
‎Mar 10, 2020 12:13 PM
Hi Fawad & JJensen,
Actually, the 'BeaconEngine.config' file in the \Program Files (x86)\Flexera Software\Inventory Beacon\DotNet\conf folder on your Beacon is being created and may be overwritten based on the content of the [FNMSCompliance].[Beacon_MT] table.Editing this file manually might result in a little frustration.
If you check the contents of the [HTTPAccessData] text column for your Beacon, you should see a XML snippet that looks like:
<?xml version="1.0" encoding="utf-16"?>
<HTTPEndPointStatus xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DownloadPath>ManageSoftDL</DownloadPath>
<UploadPath>ManageSoftRL</UploadPath>
<Protocol>https</Protocol>
<Port>443</Port>
<SelfHosted>false</SelfHosted>
<CredentialsRequired>false</CredentialsRequired>
<NetworkName><your-beacon-FQDN></NetworkName>
</HTTPEndPointStatus>
Obviously, you can customize the text between <NetworkName></NetworkName> to use the correct Beacon DNS name.
Then:
You should see that the 'BeaconEngine.config' as well as the .ndc file for failover settings on your Beacon(s) are being updated.
‎Mar 10, 2020 01:12 PM
‎Mar 10, 2020 01:24 PM
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:
After completing and saving your configuration on the Beacon, your Beacon should start communicating with the new FNMS environment.
‎Mar 10, 2020 02:18 PM
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.
‎Mar 11, 2020 01:48 AM
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:
‎Mar 11, 2020 03:06 AM
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
‎Mar 11, 2020 01:35 AM
1.Did you configure the cert to use the alias
2.You have to add the alias to edit the BeaconEngine.config file
‎Mar 11, 2020 08:59 AM
Here are some notes to clarify points which were made earlier in this discussion thread which I think may not be quite correct:
‎Mar 16, 2020 06:56 AM