Jump to content

Markovskij

Members
  • Posts

    14
  • Joined

  • Last visited

Everything posted by Markovskij

  1. If this causes no trouble, then alright. I have found the problem with unsuccessful Agent updates, i had to edit the linux script after server upgrade to use sec=ntlm and vers=2.0 (smb1 is disabled now everywhere). Thanks.
  2. Sorry if it sounds awkward, i was also confused when it happened. Later i found out that the Agent files in "Program Files" directory were the latest version (6.5), but Web Console reported the Agent to be 6.2. Installation, repair or uninstall did not work with any version of agent_x64.msi package. So i manually removed the Agent, and manually reinstalled the latest version and now everything is OK. I'm not sure what has happened. I had problems with remote installations, because smb1 is disabled on windows now, so i had to edit Linux server scripts to use smb=2.0, maybe something went wrong in between. Thank you for your reply!
  3. I cannot find anything like my problem on the forum. My Ubuntu linux server time is correct, all pc's time is correct, but the log written to trace.log is off by 3 hours. It's 9:45 but the log writes 6:45, the timestamp of trace.log is 9:45. I now have the latest version of the product. I don't know if this is causing any problems or just to ignore it. Because i'm having trouble updating agents, maybe this could be one of the reasons. Thank you.
  4. Maybe i can hijack this thread? When trying to update agents to the latest version, i get errors like "access denies or file not found". It appears that the installer wants the old version of agent_64.msi file to uninstall the old agent, but in that location a new version of agent_64.msi is already present for installation, so uninstall cannot continue and rolls back. The same happens through Web Console or manual installation with bat file. Is this a bug? Where can i download old versions of agent.msi to uninstall them? [EDIT] i found old installer on the computer and it did not help, it reject those files, says they're not a valid installation package, i'm reading about manual removal now, i hope it will help: https://support.eset.com/kb6007/?locale=en_US&viewlocale=en_US
  5. Ok, i tried few more times. Once i selected the latest version of the product, it installed fast and without problems. Thank you, i see you have improved, great job, good luck! ESET Remote Administrator (Server), Version 6.5 (6.5.417.0) ESET Remote Administrator (Web Console), Version 6.5 (6.5.388.0)
  6. I installed the Agent on the server, ran the server upgrade, task completed successfully and i see that Web Console has upgraded, but the server did not. There's no information in the server logs at all, just like nothing happened. I'll try the manual upgrade, this has taken too much time already. ESET Remote Administrator (Server), Version 6.3.148.0 ESET Remote Administrator (Web Console), Version 6.4.266.0
  7. Wow, i did not know that. Thank you, i'll let you know if i'm successful.
  8. Hello, I cannot find a way to upgrade linux ERA server to a newer version through web console, there's a task for this, but i need to select a target. If i select any computer, it says it completed successfully, but nothing happens really. I cannot select my server, because it's not in any of the lists. I was referring to this manual, it says select any computers and you can upgrade ERA Server, but HOW? (hxxp://help.eset.com/era_install/65/en-US/index.html?components_upgrade.htm) List of upgraded components: •ERA Server Task Type: Remote Administrator Components Upgrade Remote Administrator components upgrade settings Automatically reboot when needed: Yes Reference Remote Administration Server: ESET Remote Administrator Server; version 6.4.304.0 for linux (Red Hat 6, 7, CentOS 6, 7, Fedora 19, SUSE 11, OpenSUSE 13, Debian 7, Ubuntu 12.04 LTS, 14.04 LTS) ESET Remote Administrator (Server), Version 6.3.148.0 ESET Remote Administrator (Web Console), Version 6.3.114.0 I missed a few versions, so now i want to upgrade to the latest version one by one.
  9. Solved: At last we found the reason. New computers had older Agent version (6.2.190.0), that's why reinstall of Agent helped, because i reinstalled new version. Also one computer had Eset Antivirus v5 installed and Agent listened to port 2225 (this was mentioned in another thread), removing the Antivirus and installing Agent solved the problem also. Suggestion: Eset could improve error reporting to report mismatching Agent and Server versions. Because it was a pain to find the reason
  10. A few minutes ago i installed 4 agents with "bat" file into 4 computers, 3 computers appeared and are managed ok, 1 is unmanaged. I just don't understand, no errors, status is ok. How to debug this? I'm out of ideas, tried deleting and adding users to ERA, tried AD sinchronization, restarting server multiple times, logs show no errors, don't know where to look. EDIT: Tried to reinstall the agent with bat file on one pc, and it appeared in ERA as managed. At last, some progress. Will try to reinstall more agents. Maybe it's the sysprep fault, because the computers are cloned...
  11. I saw that thread, but i thought that this was only applicable to ERA 6.3.12, because my version is 6.3.148. I updated the files, restarted server and will wait some time, because i don't know how to force agents to connect to server. It looks like it didn't help, same clients are still unmanaged.
  12. Hello, I tried for a few days and cannot solve this problem. Some of the new computers with Windows 10 don't connect to Remote Administrator, they're shown as unmanaged, in the details section no information is provided. I installed agents through Remote administrator. Tried multiple solutions i found on the forum, like enable multithreading, increase db wait lock timeout, restarting server, nothing helped. Looks like the problem could start after server upgrade to newer version, but i'm not sure. We are changing some old computers with new ones. They are installed using Windows Sysprep. I am getting one error on the server, but i don't think its relevant, because this computer is showing in the Remote Administrator (2016-04-21 07:13:33 Warning: CDataMinersModule [Thread 7f7b77fff700]: CRemoteWriteLogHandler: Failed to write log of type DYNAMICGROUPS_CONTENT_STATUS from 'some_computer.domain' with uuid 89a7bf7f-0c4e-4fdb-9c61-0b6fbca23b14 with error: Duplicate value for 89a7bf7f-0c4e-4fdb-9c61-0b6fbca23b14 with meta (146122674200138,146122674200100), possibly cloned or reverted machine) Server version Ubuntu 14.04.3 LTS ESET Remote Administrator (Server), Version 6.3.148.0 ESET Remote Administrator (Web Console), Version 6.3.114.0 Agent version 6.3.136.0 An example log from one computer: Last Error was 10 days ago CReplicationModule 2016-Apr-11 09:50:29 CReplicationManager: Replication (network) connection to 'host: "eset_server.domain" port: 2222' failed with: Unable to resolve any endpoints.resolve: (0x2afc), The requested name is valid, but no data of the requested type was found Status.html Last successful replication 2016-Apr-21 06:52:04 OK Successful replications: 23 All replication attempts: 23 Server trace.log has no errors. Agents are running on those computers. But show as unmanaged in the Remote administrator, like they're not connecting. As there are no errors i don't know where to look for the problem.
  13. Hello, MartinK, both your suggestions worked! I had installed mariadb from habit, and missed that it should be mysql. Could not switch mariadb to mysql, so i reinstalled the server, this time ubuntu-server, second time is much easier and smoother. Now the status messages work. I also added "sec=ntlm" to UnixWindowsNetworkRemoteInstall.sh script and agent was deployed succesfully! This not default security option is probably needed because of our AD configuration, haven't digged deeper yet, because it works now this way. Now i get handshake errors from agent, which cannot communicate with server, but i'll create another thread if i won't be able to find the problem myself. Thank you very much for fast and accurate solutions! 2015-12-01 09:00:46 Error: CReplicationModule [Thread 4ef8]: CReplicationManager: Replication (network) connection to 'host: "192.168.100.120" port: 2222' failed with: Receive: NodSslWriteEncryptedData: Handshake failed to complete. 2015-12-01 09:01:46 Error: CAgentSecurityModule [Thread 3a90]: Certificated user verification failed with: VerifyDnsSubjectAltName: Hostname does not match any supported record in certificate SubjectAltName extension (10.1.179.46,Ubuntu64-bb,Ubuntu64-bb.BB.LOCAL) 2015-12-01 09:01:46 Error: NetworkModule [Thread 53d8]: Receive: NodSslWriteEncryptedData: Handshake failed to complete., ResolvedIpAddress:192.168.100.120, ResolvedHostname:, ResolvedPort:2222 2015-12-01 09:01:46 Error: NetworkModule [Thread 53d8]: Protocol failure for session id 16, error:Receive: NodSslWriteEncryptedData: Handshake failed to complete.
  14. I have hard time deploying new linux server to manage our clients, as old server crashed. I managed to solve most of the problems and installation steps with documentation, this forum and google. Thank you for this post https://forum.eset.com/topic/4069-remote-administrator-on-linux-help-file-changes/ It's my first try, i'm using Ubuntu Desktop 14.04.3 at the moment. I have two problems now. First, there are no status messages about server tasks. I saw in ESET videos, that after starting the task, there are statuses "running", "finished" etc. But there are none in my remote administrator web console. Though i managed to complete 'Static Group Synchronization' and i see all the computers from AD, but task details executions are empty, as though it never happened. Second, server cannot deploy Agents to computers, web console shows no reports, no statuses, nothing at all. But the log file on the server Trace.log has messages about failed mount. + LANG= mount -t cifs -o username=Administrator //user-pc.domain.com/ADMIN$ /tmp/era_remote_deploy_wn_sdf654sdgf64/cifs mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) * [Exit code = 32] With the help of linux forums i narrowed the problem. Mount command has to provide additional security mode for my shares "sec=ntlm", so this line works: mount -t cifs -o username=Administrator,sec=ntlm //user-pc.domain.com/ADMIN$ /tmp/era_remote_deploy_wn_sdf654sdgf64/cifs Question - how to make ESET to update its mount command? I did not find any settings files, or script files where i could edit this command. I think linux also cannot force to always use ntlm mode in mount by default. Any help or links to help articles are appreciated.
×
×
  • Create New...