How to Push a New Beacon URL in Agent Policy

5 years ago

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.

Expand Post

cdubs76
5 years ago
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.

Expand Post

Related Product Forums