We're leveraging the Flexera Inventory Agent. When looking in the policy.log, we see the $(DownloadRootURL) referenced many times. Can anyone tell me where on the local matching I can see what that's referencing? The main reason is we're taking non production servers and trying to get them to report to a different Flexera environment for testing. Just trying to understand how things work!
Thanks in advance!
May 25, 2023 10:59 AM - edited May 25, 2023 12:10 PM
In Windows. Its not required
DEPLOYSERVERURL is sufficient.
Please verify upload URLs in problematic device.
May 26, 2023 07:31 AM - edited May 26, 2023 07:33 AM
Understood. But once the installation is completed, is that value stored locally on that machine somewhere? I see in the registry a reference to the DownloadRootURL, but where is it finding the true value on the local machine?
May 26, 2023 08:40 AM
The DownloadRootURL preference value is dynamically determined and set within agent processes based on the beacon that a process is currently attempting to reach. Its value is stored in-memory in the agent processes, and will normally be a URL such as the following:
May 30, 2023 04:42 AM - edited May 30, 2023 04:51 AM
Thanks Chris. We have a use case where we need to switch an agent from our prod environment to our UAT environment for some testing purposes. We've updated the DEPLOYSERVERURL in the local .ini file to point to where we want it to go. After a reboot and allowing it to run for a few days, we're still seeing it go to the original endpoint in the uploader.log.
How can we properly change the endpoint that an agent is reporting to? How would we update that value in memory?
Jun 01, 2023 08:13 AM
Details of beacons to connect to for uploading and downloading data are all stored in the registry on Windows under HKLM\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Common\DownloadSettings and ...\UploadSettings. On Unix-like operating systems the values are stored in the /var/opt/managesoft/etc/config.ini file.
You can update beacon details in these locations manually. These details may also be updated automatically by various agent processes. This includes when the agent performs a policy updates (it will download current details of all available beacons), and various other times when the agent keeps a record of the most recent successful beacon it has connected to.
Jun 09, 2023 03:10 AM