Your comments

Hi. 

Unfortunately, we had issue which affected part of accounts. This issue has been fixed yesterday evening. Sorry for the inconvenience. Please let us know if the issue persists

Hi, it has been fixed. Please let me know if the problem persists.

Hi,

About the DC with issue. Does this DC have another DC(like secondary DC) at the same network?

In common case this usually helps:

  1. Uninstall agent from all servers that are in the same domain.
  2. Check in users list that there are no Anturis* users
  3. Check there are no Anturis* users in Local Security Policy->Local Policies->User Rights Assignment for the following policies: Allow log on locally, Log on as a service, Replace a process level token
  4. Delete key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Acronis Monitoring in registry from all servers where Anturis agents were installed.
  5. After that install the latest agent version on each server manually
  6. Connect it to account and setup components & monitors again

About service account for 'logon as a service' it is good point but unfortunately, it is not possible now.

Hi,


Unfortunately, we no longer support Plesk extension.

Hi,


You can add user 'anturis' to group with permission for asterisk. In this case you don't need to use sudo and password.

Please send us log files from C:\ProgramData\Anturis Monitoring You can zip them and send to support@anturis.com We will check.

Hello,


Is it real disk or some kind of virtual disk?

Deleting component works. Also there is a way via rebuild component button:

save image

save image

After this service list will be reread.

Hi,


We support Powershell 3.0 and newer. Please install it and after that recreate component or rebuild component:

save image

Hi,


Please zip and send us log files from /opt/anturis/log/ to support@anturis.com We will check what was wrong.