![]() ![]() The log file in /var/log/eset/RemoteAdministrator/EraServerInstaller.log shows: Status of current installation is: UPGRADEĮrror: User login failed (invalid credentials provided) or eval will cause future versions of the shell to abort as Posix requires Server-Linux-x86_64.sh: line 496: warning: syntax errors in. Server-Linux-x86_64.sh: eval: line 496: syntax error: unexpected end of file Server-Linux-x86_64.sh: eval: line 495: unexpected EOF while looking for matching `"' Server-Linux-x86_64.sh -skip-licenseĪrchive extracted to /tmp/tmp.lK8FpNVE9q.Ĭhecking OpenSSL. You would have to do it in batches of a few devices at a time.When attempting to upgrade using the instructions here on CentOS: hxxp:///kb3670/, specifically step 9: Using the ESET Remote Deployment Tool for this one would kill your network with all the traffic caused by pushing the installer files to all the devices. ![]() ![]() If you have a single network with over 2500 clients, I would still use the client-task in ESMC. It would be way easier to just use the client task "install software", which you can use from the comfort of your ESMC without having to manually connect to all of your clients networks. Why have a Remote Management solution in place, and then not use it? So when you're working for multiple clients, you have to manually connect to their networks and use ESET Remote Deployment from one of their devices. If I understand you correctly, you have >2500 Clients in your console, across multiple networks I guess? ESET Remote Deployment works by sitting on a server (or any other client which reaches all the devices) and deploying the installer and the associated commands over your network. Is there a particular reason why you do not want to use the tools given by the ESMC? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |