• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Raynor

  1. Thanks Frank, your reply was very helpful. Cheers! Raynor
  2. Could I get a quick reply on my two little questions please ☺️🤗 By the way: I have noticed that workspaces cannot be deleted. I assume this feature will be added later? Thanks! Raynor
  3. I just started playing around with the new "My Emsisoft Cloud Console". My first experiences have been quite positive. 🙂 Two little things that I would like to suggest for improvement: 1) I use only one policy for the whole network (i.e. workspace). This is why I delete all computer groups except "New Computers" (which cannot be deleted). I then set all required policy settings/options on the highest possible level, which is the "root" group called "Workspace". These settings are then of course inherited by the "New Computers" group (and possibly some other groups that I might add later). The problem is that whenever you re-visit the "Protection Policies" section by clicking in the navigation bar on the left hand side, the view defaults to the "New Computers" group. So if I'm not very careful, I'll change settings in this group instead of the root group "Workspace". It would be nice if the selection could default to "Workspace" whenever you re-visit the Protection Policies section. 2) Using the Enterprise Console, it was easy to see at a glance if the settings on some client PCs deviated from the original policy setting (the overview in EEC then shows a little round arrow next to the policy name in the "Computer Policy" column). In the cloud console, you must have a detailed look at the settings of each client PC to see if there is anything different to the original policy. It would be very helpful to be able to see policy vs. current client settings differences directly on the overview dashboard. (please bring back the round arrow 😉) Furthermore, there are some minor cosmetic issues: - When clicking on the menu of the root protection group "Workspace", the menu item "Clone" is not greyed out. It is clickable, but (as expected) nothing happens. It should be greyed out like the rest of this group's menu items. - Some German translations don't fit into the UI (mostly on buttons) - When using browser zoom (I use 120% by default) some lines around some UI fields get cut off And two final questions: - I was wondering what the setting "Detect registry policy settings" in the Scanner Settings section does (see attached screenshot). -Why does my license vanish from the "Licenses --> Personal Licenses" section after assigning it to a workspace ? Is this by design? This seems confusing to me... What happens if I delete a workspace - will the license be returned to the "Personal Licenses" section? What about client PCs that are NOT associated with the workspace - will they have licensing problems (I don't want to add all my PCs to the workspace)? Thanks for the great job so far! Raynor
  4. 1) OK, nice 😁 PS What about a dedicated "cloud console beta" section in the forum 😋 EDIT: Thanks for consolidating the various beta sub-forums into a more general "Beta Community" forum.
  5. Hi Frank, thanks for the quick reply. Overall this sounds like a good plan. 1) Any hint on how this might work (as there won't be a local, centrally installed proxy on a server anymore...) 2) OK, not a big problem IMHO 😀 I will definitely do some testing in the near future 👍
  6. Ha! Thought so, thanks Suggestion: why not add this little bit of info to the explanatory text, that might save other users from having the same question/confusion.
  7. With the new cloud-based console ("My Emsisoft workspaces") in BETA, I was wondering what the future holds for the "classic" (i.e. locally installed) EEC. Having deployed EEC in my company, we might want to migrate to the cloud-based console at some point in the future, but certainly not before it has become utterly reliable and stable. For how long (rougly) is the classic EEC going to be supported in the future? Oh, and two additional question that have crossed my mind: 1) What about the local update caching proxy that is supplied by EEC? How is this feature going to be transferred to cloud-managed installations? Are you planning some kind of peer-to-peer update caching similar to the Delivery Optimization feature of Windows 10? 2) Is there going to be a way to import profiles from EEC to the cloud console (including perhaps automatically transferring locally managed clients to being cloud-managed)? That would ease the transition process quite considerably... Thanks! Raynor
  8. Quick Question: I just had a look around the "My Emsisoft" account settings and stumbled across the new option "Enable two-factor authentication" (see attached screenshot). I was wondering: What's the second factor ? How is this supposed to work exactly ? I would perhaps like to enable it, but I wouldn't want to risk locking myself if things go wrong... Thanks!
  9. I've been digging a bit into methods for securing PowerShell, and the following question has come to my mind: Does EAM use the new Windows 10 scanning interface called "AMSI" to scan PowerShell scripts for malicious code when they are executed ? For more info on what I'm talking about please refer to: https://blogs.technet.microsoft.com/poshchap/2015/10/16/security-focus-defending-powershell-with-the-anti-malware-scan-interface-amsi/ Judging from the following post it seems that this might be the case, but I'm looking for a definite confirmation. https://support.emsisoft.com/topic/29757-new-in-20187-improved-file-guard-performance/ Thanks :)
  10. Thanks for this confirmation Jonathan. I thought I was going crazy. @Emsisoft: Please let me kindly ask that the process of verifying the client certificates is reviewed with regard to EEC's/EAM's behaviour after upgrading to a new semi-annual Windows version. I would really appreciate if this issue could get squashed once and for all. Thanks ☺️
  11. Please also add a configuration option to Emsisoft Enterprise Console to allow supressing/disabling this prompt. I wouldn't want it to be shown to the users in the company I work for, as we use other means for malicious website protection. Thanks ☺️
  12. *Bump* Sorry for being so persistent 😀, but I find it hard to believe that we are the only ones suffering from this issue. Why ? because our Server 2016 is totally run-of-the-mill, nothing fancy, no special configuration at all. Just one server (fresh install, about one year ago), acting as Domain Controller for a bunch of workstations, and as a file server, and hosting the EEC. No additional firewalls/proxies/security appliances running in the network. As I said, no fancy stuff 😆 Please let me reiterate my question: If the "Server certificate verification" fails according to the EAM log on the clients after upgrading Windows to a newer semi-annual build, something on the clients must have changed in a way that the certificate is no longer valid. I don't think that the server could be the culprit, as nothing whatsoever has changed on the server side. Again, any help would be greatly appreciated, as the current situation is quite unsatisfactory. Thanks Raynor
  13. Uh, any plans / ETA for a fix ? Speedy updates after the computer starts are very important IMHO... You know, people tend to start checking their emails right after startup, opening all kinds of attachments with viruses in them 😋 Thanks 🤗
  14. We have just started upgrading a few clients from v1803 to v1809 for testing purposes. At the moment they are running EAM 2018.8.1 (delayed feed). Our Server 2016 is running the latest EEC version. The issue still persists. Clients are losing connectionto EEC after upgrading to v1809. Manually reconnecting the clients from the EAM User Interface is necessary and works flawlessly and instantly... The EAM Logs say: Connection with Emsisoft Enterprise Console SERVERNAME:8082 failed. 276: Server certificate verification failed. Connection aborted. Any insights ? What could cause the certificate verification to fail ? We really need to get this fixed, we can't run around manually reconnecting each and every client from now until forever 😪 Thanks! Raynor
  15. Thanks for the info. According to the reports 2018.8 should still be fine
  16. Unfortunately I don't have a test environment up and running at the moment, sorry. But thanks for the heads-up about the surf protection. I might disable it using the enterprise console as an extra security measure. But the issue of the surf protection interfering with SQL connections must really be thouroughly solved before switching the delayed feed to a newer version (see above).
  17. An das Emsisoft-Team: bitte stellen Sie sicher, dass die SQL-Verbindungsprobleme und alle anderen Netzwerkverbindungsprobleme 100% vollständig gelöst sind bevor der verzögerte Updatefeed ("delayed feed") von 2018.6 auf eine neuere Version umgestellt wird. SQL-Datenbankverbindungen sind für uns in der Firma von größter Wichtigkeit, und selbst kleinste Störungen in dem Bereich würden dazu führen, dass ich wie ein Depp dastehe. Warum ? Weil ich derjenige war, der sich dafür eingesetzt hat, unsere vorheriges Antivirus mit EAM zu ersetzen, indem ich überall erzählt habe wie toll und problemfrei EAM doch sei. Softwarestabilität ist für uns von äußerster Bedeutung, daher benutzen wir auch nur den verzögerten Updatefeed. Und wenn der auf eine problematische Version ungestellt wird, dann gute Nacht! Dann müsste EAM sofort verschwinden von allen Rechnern. Liebes Emsisoft-Team, bitte lasst mich nicht im Stich 🤗
  18. There are more reports of SQL disconnection issues in the German forum even with v2018.9.2.8988 . The delayed feed version 2018.6 is reported to work fine. https://support.emsisoft.com/topic/30051-sql-verbindungsabbrüche-über-odbc/ Please make sure that all these issues are fully and thoroughly fixed before even considering switching the delayed feed to anything newer than 2018.6! SQL server connections are mission-critical in our company, and we depend on software reliability. This is why we are useing the delayed feed. If the delayed feed was switched to version that causes SQL connection issues, my bosses would pretty much kill me leading to me probably having to ditch EAM as a security solution altogether. I put my reputation on the line by telling everybody how great EAM was and that we should therefore switch to EAM as our security suite. Please do not let me down 😥 This does not seem to be the case unfortunately...
  19. Good. Thanks for the clarification. Then the info given by MS is false 😁... and this will not be as big an issue as I thought it might be. 👍
  20. Fair enough, but what's with fresh installations of v1803/v1809 ? According to MS, the memory integrity feature is always switched on on qualifying modern PCs (with virtualization support, UEFI and stuff) when Windows is installed from scratch. Wouldn't then "average" users be greeted by a big fat blue screen when they try to install EAM ? Or am I missing something here / am I getting something wrong ?
  21. Upgrade to v1809 with EAM 2018.06 went fine, no issues. Thanks for your replies.
  22. Thanks for the confirmation and the quick reply. This should be documented somewhere to save others the hassle. E.g. in the release notes, as a sticky in the forum, or as a message in the installer. I was unable to find this info, which led to me being puzzled and wasting quite some time. Not a biggie at the moment, but compatibility with this feature would certainly be welcomed for the future. Other AV vendors (Kaspersky comes to mind) are also struggling with this feature, but they have been communicating it more openly. Thanks again Raynor
  23. There is a new security feature in Win 10 v1803 / v1089. It is called "Core Isolation". It can be found in the Windows Security Center under "Device Security". The core isolation feature includes a sub-feature called "Memory Integrity" (clicking on "core isolation details" reveals a switch that can be used to turn this feature on). It is enabled on fresh Windows installs, but not for existing installations that have been upgraded to v1803 or v1809. According to MS, these users can opt-in using the switch. For me, the switch turns on fine (no driver incompatibility warning given), but the required reboot ends with a blue screen KERNEL_SECURITY_CHECK_FAILURE. The welcome screen is shown for few seconds, then the BSOD is shown. I had to go into the BIOS, turn off virtualization, reboot and then disable the memory integrity setting in the registry. This happens on BOTH my PCs (main work PC - recent hardware, Z270 chipset - and my small Intel NUC7i5 media PC with no special stuff installed). Tried it under Win 10 v1803 a couple of months ago and now again yesterday with v1809 (x64). Same results always. After pulling out some hair, I decided to uninstall EAM. And behold, the feature turns on successfully on BOTH PCs. Trying to re-install EAM with Memory Integrity turned on immediately causes the above mentioned BSOD during the installation (i.e. not on reboot, but immediately while the EAM installer is running). Here is another user reporting exactly the same issue: https://www.wilderssecurity.com/threads/win-10-1803-core-isolation-and-memory-integrity.407342/#post-2776118 "With Core Isolation and memory integrity turned on I got a green screen of death trying to install Emsisoft and could only recover using Macrium Reflect backup. Turned off memory integrity and EAM installed fine." The information given in the German section of the Emsisoft forum that it "should" be compatible is obviously FALSE. While EAM is certailny compatible with the basic "Core Isolation" feature, it does NOT work when the memory isolation sub-feature is switched on. https://support.emsisoft.com/topic/29479-windows-10-1803-kernisolierungspeicherintegrität/ Botom line: please make it compatible 😁 Thanks and best regards Ranyor
  24. With Win 10 v1809 around the corner and me using the delayed update feed (Version 2018.6 at the moment), I would like to quickly ask whether there are any known compatibility issues to be expected when upgrading to v1809 in the next few days. Thanks!