keenlogic

Member
  • Content Count

    48
  • Joined

  • Last visited

Everything posted by keenlogic

  1. I am writing a monitor for my RMM for Emsisoft since they do not support it natively. I need to be able to see if the signature files are current. Can someone help me find that information so I can update the JSON file needed by the RMM. The RMM is Autotask Endpoint Manager (AEM). The clients are Windows 7, Windows 10, Windows Server 2008, WIndows Server 2012, Windows Server 2016
  2. Thank you Dana! That was exactly what I was looking for. I did not know I could double click on the license number. Is that documented somewhere? I could not find anything that told me that. Take care, Mike
  3. Is it possible to find out what computers are assigned to specific licenses within EEC? I want to know which users are expiring, not just the license number. That way I can get the renewal taken care of with the customer. Thanks, Mike
  4. I have sent you the DB and the logs in a PM. Thanks!
  5. I edited the configuration database (a2econfig.db3) and turned off the debug logging and then restarted the server. I am now able to login to the console GUI. I would still like an explanation on why this happened.
  6. Hi dmitrea, If I delete the a2econfig.db3 database will I lose the configurations for the existing clients and settings that we have deployed?
  7. I noticed in the logs that Debug logging is turned on. Is it possible to turn off Debug Logging with out being in the GUI?
  8. EEC Version: 2017.5.0.3046 Windows Server 2012 R2 The EEC console has stopped responding when I try to login. The console shows "Connected" for the localhost, but if I enter a password (correct or incorrect password) it goes unresponsive. I have rebooted the server several times and the problem is still there.
  9. Thanks. I was able to do the reset by connecting remotely to the console instead of from the server itself. I am not sure why it made a difference, but it worked.
  10. This has worked previously, but it does not appear to be working today. I tried clicking on the "Forgot?" link on the EEC login screen but it does nothing. Can you help me with this? I need to get into the console to add some users and keys. Thanks!
  11. EEC: 2017.4.0.3002 Running on Windows Server 2012 R2 I am trying to uninstall the services on a client as the connection to the EEC is broken and I want to reinstall the connection. The documentation says to run the Disconnect_EAM_from_EEC.bat file. This was previously on the EEC serer, but I can no longer find that file. Where did it go? It states that it should be in the Emsisoft Enterprise Console installation folder. I have used this script previously but cannot find it in this recent update to EEC.
  12. Thanks Kevin. I am the IT support for this. I was just wondering if there was a decryptor available. I have rebuilt this computer now. I appreciate your response. Take care, Mike
  13. Do you have a decrypter for the Osiris ransomware?
  14. These users are also getting a pop-up on their client stating that the license is expired, even though the EAM GUI shows 231 days until expiration.
  15. I entered several licenses into the EEC today and they all show as "Unknown" and "License has not been updated". These are currently functioning licenses on existing clients. Is something broken in the EEC infrastructure?
  16. I think I found the reason. When I looked at it, the license key is incorrect. I do not recognize the key, and it says it is expired. I am not sure where that key came from.
  17. Computer: Windows 10 Pro 10.0.14393 Server: Windows Server 2012 R2 Datacenter Build 9600 I have a client that was connected yesterday to the EEC. Today when I look it is no longer communicating with the server, but the three other computers in the same office are working fine. How can I find out why it is no longer communicating?
  18. I want to be able to change the license key on several machines using our RMM tool. Is it possible to change the license key from the command line? Thanks, Mike
  19. They appear to be running fine. Thanks!
  20. Here are the current log files. Addition.txt FRST.txt scan_150608-130135.txt
  21. The fixlog.txt file is attached. Fixlog.txt
  22. I have attached the log files per the instructions. Thanks, Mike Addition.txt FRST.txt scan_150603-190018.txt
  23. Thanks Kevin. Attached are the logs from the final scans. Take care, Mike a2scan_150518-121006.txt Addition.txt FRST.txt