Frank H

Emsisoft Employee
  • Content Count

    2079
  • Joined

  • Last visited

  • Days Won

    28

Frank H last won the day on April 11

Frank H had the most liked content!

Community Reputation

88 Excellent

6 Followers

About Frank H

  • Rank
    Forum Veteran
  • Birthday 06/24/1964

Profile Information

  • Gender
    Male
  • Location
    Portugal

Recent Profile Visitors

12055 profile views
  1. Your use case is rare. Most enterprises have multiple groups. To avoid users to not make changes on Workspace level by error, we decided to jump to the 'new computers' group by default, like in Emsisoft Enterprise Console. Sure. Please note that Emsisoft Cloud Console is a first beta, bugs and missing features exist. We are working hard to improve step by step. With this setting you can instruct Emsisoft Anti-Malware to not scan certain registry settings, as they are commonly used by system administrators: example: "HKEY_LOCAL_MACHINE\software\microsoft\windows\currentversion\policies\system", "DisableTaskMgr" This is by design. A License can be linked to a users OR Workspace. Users cannot delete Workspaces yet. We understand that you now mis certain info related to seat usage, for example,. In a near future ECC release we will improve this,l ike showing the devices that use the same license but have not been connected (yet). I hope this helps.
  2. Hi Charlie, yes, but that will be changed in a next EAM version. Yes, we will provide 2 easy ways to connect existing installs. One thing i need to stress is that a workspace must be seen as a customer area. That means that you can connect the devices of 1 customer to 1 workspace. You will have to contact our sales team to split your existing key into keys per customer. For security and permission related reasons, the architecture of the Cloud Console allows one license per workspace/customer. please note that Cloud Console is in beta stage, so bugs are expected. We will check and fix when needed. thanks ! Thanks
  3. When we do not provide details, the fixes are mostly internal and/or with minor graphical improvements or fixes.
  4. We’ve just released Emsisoft Anti-Malware 2019.3.1.9367 beta. You will have to enable beta updates to get this version. Fixed: Issue with Emsisoft Anti-Malware not automatically connecting to a Workspace after installation.
  5. Hi Raynor, 1) yes there will be Even current EEC update proxy is a separate process that runs separate from EEC's processes. Thanks
  6. Hi Raynor, We currently don't have concrete plans to end Emsisoft Enterprise Console. If we ever come to that point, we would make an announcement at least one year in advance to provide planning safety for our customers. 1) Local update caching will become available later. 2) We have no plans to offer a profiles migration path, for now. Re-connecting existing devices from EEC to ECC will become an easy procedure and can be automated. We are working hard to add new features to Emsisoft Cloud Console. Feel free to start testing it and see how stable it is. You can connect existing Emsisoft installs manually as of version 2019.3. Thanks
  7. Thanks peter. build 9253 just has been released to beta beta and stable.
  8. We’ve just released Emsisoft Anti-Malware 2019.3.0.9353 beta. You will have to enable beta updates to get this version. Several minor tweaks and fixes.
  9. We’ve just released Emsisoft Anti-Malware 2019.3.0.9350 beta. You will have to enable beta updates to get this version. Several minor tweaks and fixes.
  10. Several minor tweaks and fixes like the fixed Forensics filter
  11. We’ve just released Emsisoft Anti-Malware 2019.3.0.9342 beta. You will have to enable beta updates to get this version. Several minor tweaks and fixes.
  12. We’ve just released Emsisoft Anti-Malware 2019.3.0.9337 beta. You will have to enable beta updates to get this version. Improved device/license mapping. Now supports multiple computers with the same name on the same license. Several minor tweaks and fixes.