Summary
This article documents the behavior witnessed in bug FNMS-29295 where a beacon will revert to the default install directory during a self upgrade
Symptoms
Once a beacon gets / performs a self upgrade because a new version was deployed centrally (batch server) it removes the value in
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Beacon\CurrentVersion\BaseDirectory
This causes significant issues e.g. the beacon loads an outdated configuration looking into an outdated path, if existing at all. What can be done to prevent the change to the BaseDirectory value?
Resolution
This behavior is caused by a known issue. When an inventory beacon perform a silent upgrade it will automatically revert to the default install directory. The only current workaround for this issue is to manually modify the changed registry keys following the install. This issue can be tracked through reference FNMS-29295
