Newly added beacon is not being used/seen by agents for uploads

[kevin_christens]

Checking uploader.log and find that the beacon we added a month ago is not being referenced for prioritization or uploads and is not found in /var/opt/managesoft/etc/config.ini on *nix or "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Common\UploadSetting" on Windows platforms.
Shouldn't new beacons automatically appear?
We are using On-Prem FNMS 2023 R1 with hot fixes 1 and 2 applied.

[tjohnson1 · Accepted solution]

Do you see the beacon listed in %ProgramData%\Flexera Software\Beacon\BeaconPolicy.xml on one of your other beacons? If so, please check if you are using the Inventory Groups feature (https://docs.flexera.com/FlexNetManagerSuite2023R1/EN/WebHelp/index.html#tasks/InvSet-InventoryGroupSettings.html) which limits the beacons that are provided to agent devices. You may just need to add the new beacon to your existing groups.

[tjohnson1 · Accepted solution]

Do you see the beacon listed in %ProgramData%\Flexera Software\Beacon\BeaconPolicy.xml on one of your other beacons? If so, please check if you are using the Inventory Groups feature (https://docs.flexera.com/FlexNetManagerSuite2023R1/EN/WebHelp/index.html#tasks/InvSet-InventoryGroupSettings.html) which limits the beacons that are provided to agent devices. You may just need to add the new beacon to your existing groups.

[kevin_christens · Accepted solution]

Thank you.  That was the issue.  I had forgotten we had defined a group of beacons and the new beacon was not part of that group yet.