Frank H

Emsisoft Employee
  • Content Count

    1480
  • Joined

  • Last visited

  • Days Won

    30

Everything posted by Frank H

  1. Excuse me for the delayed reply, you posted in the wrong section. Emsisoft Enterprise Console is different/separate product. Emsisoft Cloud Console threads should be posted in the Emsisoft Anti-Malware section, as both product are tightly connected with each other. Regarding your questions: A workspace is a customer environment in Emsisoft Cloud Console. As soon as the Windows login screen shows-up. waiting for password, EAM will already connect to the workspace. A traffic relay is one EAM instance that act as tunnel to ECC and the Emsisoft update-servers. you can setup one traffic relay per policy group. You define traffic relays per workspace. You can assign any traffic relay to any policy group. I wonder why you setup 2 traffic relays ? When you assign a Traffic relay to a policy group, it will be pushed to all devices in this group. All devices then will connect to the traffic relay and connect to ECC though the Traffic relay. Program updates and signatures will be cached locally on the traffic relay device. EAM has a default update interval of one hour. An update is initiated by every single EAM. Traffic relay will connect to our update servers and get the required files. The next EAM that requires the same files, will get the locally cached ones from the traffic relay. I hope this helps
  2. Hi Excuse me for the delayed reply, you posted in the wrong section. Emsisoft Enterprise Console is different/separate product. Emsisoft Cloud Console threads should be posted in the Emsisoft Anti-Malware section, as both product are tightly connected with each other. Regarding your question: The password feature only needs to be activated when you want to limit permissions for local administrator users, as Emsisoft Anti-Malware gives full access to local admins by default.. When you revoke permissions for regular windows accounts, there is not need to set the password. When you want to limit local administrators to get access to settings, you have to set the password AND assign other than 'Full access' permissions
  3. We’ve just released Emsisoft Anti-Malware 2019.9.0.9753 beta. You will have to enable beta updates to get this version. Several tweaks and fixes.
  4. This beta2 mostly included improvements related to Emsisoft Cloud Console, which not many of you beta testers are using. Couple of UI related fixes for dark mode. Added Forensic logging for policy initiated setting changes. Added Forensic logging for relay proxy related status changes.
  5. We’ve just released Emsisoft Anti-Malware 2019.9.0.9749 beta. You will have to enable beta updates to get this version. Several minor tweaks and fixes.
  6. Thanks for your feedback. This option mainly will be used by enterprise users and it's disabled by default. We did not add the silent mode parameter to avoid that remote devices would not reboot when a screensaver or similar thing that triggers silent mode, is blocking the set restart.
  7. We’ve just released Emsisoft Anti-Malware 2019.9.0.9737 beta. You will have to enable beta updates to get this version. New Automatic device restart feature. New device info panel in Emsisoft Cloud Console. Several minor tweaks and fixes.
  8. FYI: EAM 2019.8.1.9715 just has been released to stable
  9. we got feedback from another AdGuard user:
  10. We’ve just released Emsisoft Anti-Malware 2019.8.1.9715 beta. You will have to enable beta updates to get this version. Fixed: issue with 'Detect registry policy settings' when connected to Emsisoft Cloud Console. Fixed: issue related to an inaccessible Forensics log. Fixed: unexpected license dialog pop-ups. Improved: product uninstall.
  11. Syncro is preparing licence related improvements which will be available very soon, stay tuned !
  12. for existing EAM installs you can only use the webinstaller. The MSI just installs EAM and connects it to the WS. When EAM already is installed it will give you an error. adding /silent parameter should suppress user dialogs. >From your comment re ECC and EAM, I guess ECC questions should now go the EAM forum. yep
  13. You can just run the little 2mb webinstaller you download from the workspace, on all your devices. It will detect if EAM is installed. if so, it will disconnect from EEC and connect to the WS, and apply its license. The installer requires to run under elevated permission or SYSTEM account. ECC and EAM are tightly connected, so there is no need for a separate forum.
  14. You should find a 'Delete WS' link in the bottom of the WS settings page.
  15. Hi xeon, If AdGuard uses WFP, i can image that this causes incompatibilities with EAM, as EAM Surf Protection does the same. When did this problem occur ? We did not make any changes to the EAM SP in recent builds.
  16. Those buttons are right aligned with the tile above them.
  17. EAM gets the Windows and 3rd party Firewall status from Windows. If that FW isn't recognoized as such, we cannot do much. FRST logs and EAM debuglogs that cover a computer restart might provide details why.
  18. We have identified the problem and it will be fixed in an upcoming release of Emsisoft Cloud Console. Thanks for your feedback.
  19. Firefox probably doesn't like its connections closed forcefully.
  20. We’ve just released Emsisoft Anti-Malware 2019.8.0.9681 beta. You will have to enable beta updates to get this version. Few UI related improvements.
  21. This is an issue that occurred in early beta versions. if you could provide me with the GUID (the cryptic code in the URL) of the workspace or workspace name we can try to set that counter to 0.