Home
Troubleshooting
Update
Update of the AimBetter Agent on Windows OS Server

Update of the AimBetter Agent on Windows OS Server

Download of the AimBetter Agent

To update the AimBetter Agent, download the “Aimbetter_Agent.zip” file to the Agent Server.

https://update.aimbetter.com/Aimbetter_Agent.zip

Run the file, and that’s it!

All the previous configurations will remain, and all lights should be green.

If you want to configure additional servers to monitor, follow the steps in the Installation Guide.

If there is some problem with the update, check the Update Troubleshooting below.

Update Troubleshooting

1- There is a red light in the AimBetter Configuration window

If the AimBetter Configuration window shows a red light, check its meaning on the Troubleshooting Installation Issues page.

2- The update is taking too long – more than 1 minute

The update of the AimBetter Agent shouldn’t take more than 1 minute. If it’s taking longer, we recommend manually stopping the AimBetter Agent.

This problem occurs because the AimBetter Agent service must be stopped during the update/deletion process, and when the user running this service has restricted permissions, the program can’t do it by itself.

3- The update program can’t be executed

In rare cases where the AimBetter_Agent.exe can’t be executed in the Agent server’:

1. Login to the Agent server. To find out which one is the Agent server, go to Settings -> Servers and look up the Agent IP column. If there is more than one Agent Server, proceed with the following instructions for each Agent Server.

2. Stop AimBetter Agent service from Services.

3. Look for the following path:

C:\Program Files (x86)\AimBetter\Monitor\Agent\data

4. Copy the agent.bs file to an external path.

5. Download and run the AimBetter_Agent.exe file on another station until the “Activate your account” step. Exit the program.

7. Copy the full content of the AimBetter Folder created on the external station to the same path in each of the Agent servers:

C:\Program Files (x86)

8. For each server, paste the agent.bs file copied (step 4) to the following path:

C:\Program Files (x86)\AimBetter\Monitor\Agent\data

9. Start AimBetter Agent Service.

10. Once you are done, check that the servers are monitored in the AimBetter console https://app.aimbetter.com

4- There is an update error: ‘Error 1402. Could not open key: UNKNOWN…’

If, during an update of the AimBetter Agent, the following Error is received,

it may be related to insufficient or incorrect permissions on the named registry keys or parent container of such registry keys.

The error can be fixed following these steps:

Back up your computer or the registry. Microsoft’s built-in backup program allows for the “system state” to be selectively backed up. Alternatively, ZIP up the windows\system32\config directory while running in a backup operating system (this is where the registry hive files are located).
Log in as the ‘administrator’ (or an account with full administrator access) and disable the “UAC” (User Access Control). To disable the UAC, open the “User” control panel applet and select the Change User Account Control Settings. In Windows 10 the next dialog box will display a slider, simply set it to Never Notify.
From the START menu, execute Run… (press WIN+R) and then type “regedit“.
Navigate to the following registry root:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components Note: The ‘S-1-5-18’ key may be different on your computer.
Right-click on the Components registry key, and then choose Permissions…
The Permissions for Components dialog box will be displayed.
Click the [Add…] button and add in the “Administrator”, “Administrators” and “SYSTEM” accounts. You might also want to add a local account having administrator privileges.
On the first Permissions for Components dialog box, click on each account (in the top-list) and make sure each has the “Full Control = Allow” and “Read = Allow” permissions.
Click the [Advanced] button to display the Advanced Security Settings for Components dialog box.
On the Permissions tab, turn on the Replace all child object permission entries with inheritable permission entries from this object checkbox, and then click the [Apply] button.
Repeat the above steps once more. There should not be any errors regarding not being able to update the permissions on the child keys.
Click the [OK] button to exit the dialog boxes. The main registry editor will become the active window.
Re-run the CivilGEO installer or uninstaller by right-clicking on the respective icon and select “Run as administrator…” (if available) from the displayed context menu.
If the “Could not open key” message is displayed on the exact same keys, it means the above operations were not implemented correctly. Repeat the above steps for the main registry root node.