Over the years we have upgraded beacons and removed beacons from our FNMS environment but if you look in uploader.log or installer.log you still see the old beacons, as well as new, being referenced. I have verified the old beacons are still in /var/opt/managesoft/etc/config.ini on Unix and in the registry of Windows devices in the DownloadSettings and UploadSettings of Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Common\.
Is there a simple method to remove all the beacons defined in the agent config.ini or registry and allow the agent to receive a new list of beacons, based on the "Bootstrap Server 1" of DownloadSettings? Would be nice to have an option to force all devices get a current list of beacons.
Would configuring Inventory Group Settings with a target of devices work to refresh the list of beacons?
Oct 28, 2022 02:39 PM
The agent will leave the DownloadSettings and the UploadSettings in registry (Windows) and config.ini (Linux/UNIX) to help with a reinstall. If you delete these entries prior to the install then you should only see the bootstrap beacon and then the beacons from the failover list which will be downloaded from the bootstrap beacon. There's currently no way of enforcing a refresh of these lists locally on the agent side, but please feel free to create an idea in the ideas portal as there may be other forum members interested in this functionality too.
Thanks,
Oct 31, 2022 04:06 AM
The agent will leave the DownloadSettings and the UploadSettings in registry (Windows) and config.ini (Linux/UNIX) to help with a reinstall. If you delete these entries prior to the install then you should only see the bootstrap beacon and then the beacons from the failover list which will be downloaded from the bootstrap beacon. There's currently no way of enforcing a refresh of these lists locally on the agent side, but please feel free to create an idea in the ideas portal as there may be other forum members interested in this functionality too.
Thanks,
Oct 31, 2022 04:06 AM