Showing results for 
Show  only  | Search instead for 
Did you mean: 

How to Push a New Beacon URL in Agent Policy

We setup a new beacon as a replacement of old but it is not appearing in RegKeys with agent installation, How can I push a policy update so that agents will be able to discover the new Beacon URL 

(1) Reply

Ideally---you would stand the new one up and connect it to the app server.   Once that happens, when they connect to the original, the agent would have a chance to update their policy to include the new one.  Once that's done, you could then remove the old beacon from FNMS, and next time policy updates--it would be removed from the list the agent keeps in the registry.

If that process isn't possible---(old beacon already gone, new beacon alive and ready)...then you'll have to update the "Bootstrap Server 1" reg key:


"Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\Common\DownloadSettings\Bootstrap Server 1"  --> Host: <new beacon FQDN>

whether you script that change or push via SCCM or something....after you make the change, you'll have to restart the "Flexera Inventory Manager managed Device" service.