dmitrea

Emsisoft Employee
  • Content Count

    42
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by dmitrea

  1. I've received the logs and passed them to the devs. We'll get back to you as soon as possible.
  2. It might be a server issue then. We'd need the debug logs in order to investigate the issue. I will drop you a PM with instructions on how to collect them.
  3. Hi Chris, What OS do you have on the client endpoints you're trying to deploy on? Is this error happening on all client hosts or only on specific ones?
  4. In this case, we'd need to grab the logs and see what's happening on your server host. I'll drop you a PM with instructions on how to collect them.
  5. I think that the autoupdate to EEC 2017.9.1 solved the issue reported by onbox. You could eventually try to install the new build published on the website over the existing one and see if it makes any difference wrto the server service startup.
  6. Good news! Let us know if you run into further issues.
  7. Hi, It's good that the policy settings were transferred in the end to EAM. Usually, when there are changes performed in the policies, you have the option to sync them manually by hitting the sync button from the top panel, or you can wait around a minute and the system will sync them automatically. About the first error, is it reproducible on a consistent basis? If yes, can you please collect the logs and drop them to me into a PM? Cheers, Dana
  8. Hi, It looks that you have an issue with the database backup/restore process. The dev team needs the logs and eventually the backup databases in order to be able to pinpoint the problem, so can you please send them to me in a PM? If you have issues with respect to that process, let me know and I will get back to you with a PM containing instructions on how to collect the logs. Best regards, Dana
  9. That's great news! Thank you for your feedback, it's good to know that the fixes are working. Best regards, Dana
  10. Hi Richard, We are aware about these disconnects and we've added this month a potential cure for these annoying issues. We are going to release in a few days (around September 1st) a new EEC version which should fix part of the disconnection issues we're currently having. I'd suggest you to wait a few more days until you switch to the new EEC version. If the disconnects still pop up after that, we'd probably need a set of debug logs so that the dev team can investigate this thoroughly. Best regards, Dana
  11. Ok, cool, it's good that the issue is solved! Cheers, Dana
  12. Hi, Typically, these issues occur when there are issues with permission rights, the installer is not accessible (typically because of the network hiccups) or simply there is not enough space on the server host (EAM installer uses around 270 MB). 2% means that download has been started, so we can assume that the permissions are just fine. If you still have enough space on the server (so we can cut out this reason), my advice would be to try to restart Emsisoft Enterprise Console Server Service. If you're still having download issues after restarting the server, let me know and we'll go from there. Best regards, Dana
  13. Hi grzegorz, Is there any error you see when the client attempts to connect to EEC? Best regards, Dana
  14. Indeed, we had these sort of issues on the previous EEC version (2017.6.0.3099). What I suggest you is to download the latest stable version we've released the last week (2017.7.0.3153) and install it over your current version. The new install won't affect any of your existing settings. If the issue still persists, let me know and we'll go from there. Best regards, Dana
  15. In order to install EAM (which is the Anti Malware solution), you just have to download it from the website (https://www.emsisoft.com/en/business/antimalware/) and install it like any windows application. EEC is a different thing, it is Emsisoft's solution which handles Emsisoft AntiMalware installations and management over the network. You can find more info about it in the user guide (https://dl.emsisoft.com/EmsisoftEnterpriseConsoleManual.pdf). Being a desktop solution, it can be installed as a regular windows app, but I'd recommend you going first through the documentation in order to understand exactly the way it works and its capabilities. Best regards, Dana
  16. Hi, Unfortunately, at this point, EEC and EAM do not support non-windows operating systems, so you won't be able to use them on Linux. Best regards, Dana
  17. Hi Roger, When a previously connected client is listed as 'Not managed' into EEC Console, it means that the communication between the client and the server was interrupted somehow. EEC User guide contains info regarding the ways to troubleshoot client-server connection issues (Chapter 15 from https://dl.emsisoft.com/EmsisoftEnterpriseConsoleManual.pdf), but to answer your questions: Q1: We cannot say for sure why did it happen, until we take a look at the server logs. There can be network issues or something else. If the issue persists after rebooting the client hosts, let me know and I will send you a PM with instructions on how to collect the logs. Q2: In order to reconnect the clients to the server, you have to do the following: 1. Disconnect EAM from EEC: Login on the Emsisoft Enterprise Console Server machine and copy Disconnect_EAM_from_EEC.bat script (located in Emsisoft Enterprise Console installation folder) to the Emsisoft Anti-Malware client machine. Login on the client machine. Run Disconnect_EAM_from_EEC.bat script with elevated privileges. 2. Reconnect EAM to EEC: Login on the Enterprise Console Server machine and generate a light package. Copy the light package folder to the client machine and run Install.bat script with administrator privileges. The steps above are explained in a bit of more detail in User Guide, chapter 15. Let me know if you're still having connection issues after performing the steps above. Best regards, Dana
  18. Alright, keep us posted if you have further issues while connecting the console to the server host.
  19. Hi Aldus, Can you try and see if the following steps work for you? 1. Close Emsisoft Enterprise Console 2. Go to System Services and start manually Emsisoft Enterprise Console Update Proxy Service 3. When the UP service is started, restart Emsisoft Enterprise Console Server Service 4. Once the server service is restarted, open again Emsisoft Enterprise Console At this point, Emsisoft Enterprise Console should be able to connect to the server. Let me know if that helps. Best regards, Dana
  20. Hi Alex, Right, the error happens when you hit the heart button in the Login screen - it's an issue already logged in our internal bug database and will be addressed as soon as possible. However, you should not get any error once you log in into EEC Console and click that heart button. You should be redirected to Emsisoft's facebook page in this case. Best regards, Dana
  21. Hi, You can copy the environment variable you want to use (e.g. from a text file), open the GUI client and go to Policies > Computer policies > Computer settings view. Under Exclusions section, there are the two options: 'Exclude from scanning' and 'Exclude from monitoring'. When opening any of then, the exclusions window you will open and you're gonna see a 'Paste' button. Hit it and it will paste the user variable. Another option would be to edit an already existing exclusion item - just click on it and it becomes editable. You can also select a standard variable from the drop down list displayed in the right hand side of each exclusion line and then fill the rest of the var name by hand.
  22. You're welcome! You're right, it seems that this little feature was somehow missed from documentation, we'll include it into the next user guides. Cheers, Dana
  23. Hi Mike, EAM licenses are computer-based and not user-based, so when a particular license is going to expire for one computer, all the computer users will be affected. You can see the license used by each computer in Clients view, by adding License column into the clients grid (Right click and in the context menu use Select columns > License). You can sort the grid data ascending/descending by the license key. However, if you have lots of clients listed in the Clients view and you find hard finding out the computers using a specific license, you can try using a custom filter for the clients view, based on the license key you're interested in. You can also create that custom client view automatically, by double clicking on the license listed in Settings > Licenses screen. Best regards, Dana
  24. When you installed EEC on the domain computer, were you logged in with a domain admin or with a local admin? Domain computer listing should definitely work for the domain admins.