Jump to content


  • Posts

  • Joined

  • Days Won


Everything posted by jedsiem

  1. I did disable the services of EMSI and rebooted. After i was able to remove EMSI via deinstallation and EMSIClean. After that I was able to reinstall EMSI.
  2. I have a few EMSI Business Security installations which seem to have stalled wih the Sep. update. (which seems to not have gone through. EMSI is on 2021.8.0.11131. Perhaps it's the current hickup with the EMC, but I'm not able to reactivate the EMSI Business Security Clients (Win10 20H2 64bit) in the workspace. When I enter the credentials in a EMSI Client, a Code is sent via E-Mail. When entering the code, nothing happens. The code field stays. When entering the code again, the error message "invalid sessions" appears. Complete de-installation is not working. Removed only the shortcuts/folder in the Startmenu. The cleaning tool is prevented too. Using a installation file via the Workspace not working. EmsisoftAntiMalwareWebSetup is showing no activity. The full installation package are correctly indicating that a installation is already existing. So it's a bit kafkaesque. Is the behavior known? Any workaround?
  3. Is there a status page? I wonder if the Management Console is back at 100%. Update, to answer my own question: https://status.emsisoft.com/ Looks like the operations are back to 100%, right?
  4. Thanks, I was aware of the EOL of the Console. Looks like the February Update removed the connection service for EEC on the clientside too. I will now have to look for a GDPR compatible solution. The last time I checked the contract relevant parts where missing.
  5. Turns out that the behavior is intended. Perhaps I had a testsystem, where the connection to the Enterprise console was temporary working. I have the chance to check other clients. The clients are not in a workspace, but connected to the OnPremise-Console. That runs fine, cause no newer options are needed.
  6. Correct, your hint to change the settings via the console worked. Thanks. I will have to investigate, why I wasn't able to override the settings as a local user. Usually the setting was to allow the local user to change such things. There was no enforcement. But that's a different topic. The issue around the Windows Security Center recognition is solved. Thanks and have a nice weekend.
  7. Thanks for the script. It removed both entries of EMSI. PS C:\WINDOWS\system32> Get-CimInstance -Namespace root/SecurityCenter2 -ClassName AntivirusProduct displayName : Windows Defender instanceGuid : {D68DDC3A-831F-4fae-9E44-DA132C1ACF46} pathToSignedProductExe : windowsdefender:// pathToSignedReportingExe : %ProgramFiles%\Windows Defender\MsMpeng.exe productState : 397568 PSComputerName : PS C:\WINDOWS\system32> The windows security center integration was already activated in EMSI (even though I deactivated it before booting). I sense a different kind of root cause here. When trying to switch the update branch or trying to deactivate the "autoupdate" option, the change is not accepted. The change was reverted instantly back. So it feels like EMSI isn't able to keep the change. Any idea beside deinstalling and reinstalling?
  8. Thanks for the PowerShell command. The Emsisoft Anti-Malware registry entry should not be there.
  9. I have this issue on one system (Win 10 64x 19.09) after removing and reinstalling EMSI. The integration into the windows security system is missing. Unchecking the option inside EMSI is not bringing any change. The unchecking does not stick. Looks to me like the option is not triggering anything. Normally when deactivating the option "Windows Security Center integration" , there is a small lag when Win10 is recognizing the command to change the registration. That lag is not there, looks like checking/unchecking has no impact. Is there a best practice? Hints for registry keys to check? Have a nice week.
  10. I had another chance to add a device. Now it worked as intended. I didn't chose the alternative Download this time. Perhaps only a temporary issue.
  11. Thank. The behavior you describe was the expected behavior. When using the downloaded installed with a local admin right, the installer installed EMSI. But EMSI asked for my admin credentials of the EMSI cloud. Trying to connect the installation via command line with the token didn't work either. I will check again.
  12. When adding a device there is an option to download an individual Setupfile or sending an email with a downloadlink. I wonder why the end-user, which is installing the package, is asked for my EMSI admin credentials to activate the license. I would have expect that an individual package is a one-click-installer. What is my mistake?
  13. My post is from 2019 and about the OnPremise Enterprise console. Which is no longer under development or available for download, right?
  14. The question is, if everybody has the "periodic scanning of Windows Defender" set to off. The screenshot of @PoorlyPCNigel seems to lack EMSI as a registered security provider. Looks more like a issue with Windows 10 than EMSI. It 's no seldom that an windows update which reacticates Windows Defender. Or Microsoft Defender, as Microsoft is bundling more and more security features. To completely deactivate Microsoft Defender manually is theses days not that easy.
  15. I share that view. EMSISoft is a fine software and your team deserve respect for building a remote company. The support is personal and has a human touch other companies are already lacking. You seem to be a good CEO 😉 I don't share the vision that an on-premise option like "Emsisoft Enterprise Console" has no business-case. EMSISoft choose to focus on the more popular option. I second that more customers will use that option than trying to install and hassle with a EEC. I don't want to waste your time to go into the pro and cons. I have to accept that EEC is no longer offered. To get ECC in compliance with GDPR for a company is currently not working flawless. I'm happy to get responses from European customers which already did the move.
  16. I'm still looking for the technical and organizational measures as integral part of the contract for using the ECC. Currently nobody cares. But that will change. Currently the ECC is hosted in the Hetzner datacenter in Germany. Many technical and organizational measures will be from Hetzner, but the remote worker from EMSISoft are still uncovered by technical and organizational measures.
  17. Emsisoft Enterprise Console, will no longer be supported after December 31, 2020. https://blog.emsisoft.com/en/34808/moving-to-the-cloud-the-emsisoft-anti-malware-management-roadmap/ I'm happy that it will be not 2019. That will leave me enough time to find a different AV with local support. As long as I have to follow GDPR, a cloud system for the enterprise is not suitable for my customers. Most companies currently ignore the rules, but at least two European AV companies still offer an on-premise console.
  18. EEC is no longer under active development. They want you to move everything to the cloud.
  19. EMSI found a infected Attachment and labeled it "Trojan.GenericKD.32440367". The Naming is from EMSI? Till e.g. VirusTotal will combine different namings to a new finding, where can I find more infos about that Trojan? Any hint?
  20. No, I didn't checked the Cloud Console. Having everything local is an important factor for my clients and myself. With the new pricing scheme, EMSI business licences are in the pricerange of Endsecurity solutions. So I would expect to see EMSI moving the Client into that direction too. The "competition" is coming from Windows 10 too. I see people asking to ditch third party antimaleware at all. I'm currently opposing that, but once Win7 is EOL it will become harder to convince customers to see the benefits of EMSI in comparison to EndSecurity solutions (bundled with SPAM filter etc) or the plain Win10 defender tools. But back to the main topic of Enterprise Console: Currently the Enterprise Console seems to not offer all settings of the EMSI client (e.g. Appearance: Dark / Bright is not found in the policy/settings)?
  21. Thanks for your help. I tried drag'n'drop before. Did it again. It worked. Feels a bit very sensitive, but working. Thanks.
  22. EEC 2019.3.0.3456 How can I add a different Group on the same level as e.g. "New computers"? Only way is to rename the items preconfigured. Is that intended? I can clone certain items, but not a new one on the same level. Unusual behavior to me. Perhaps I have overlooked something.
  23. Today I got again a few PCs with broken Firefox-Installations. The issue that EMSI is interfering with Firefox Update / Helper is not new. And in the last few months it got more visible. "Behavior.HiddenInstallation" in "C:\Program Files\Mozilla Firefox\updated\uninstall\helper.exe" "Behavior.CodeInjector" in "C:\Program Files\Mozilla Firefox\updated\firefox.exe" Doesn't happen with Chrome updates. Wasn't the case the last years. EMSI or Firefox changed something in their routines. Since EMSI now sells a Enterprise-Line it's time to debug accordingly.
  24. This behavior is not limited to a certain Firefox version. It's happen very often. EMSI is breaking Firefox installations when an Firefox update is running. Not always and everywhere. But you end up with PCs without a working firefox every few weeks.
  25. Let's see it as a feature request for EMSI. Creating a RescueCD/USB or offering an external tool for that. People switching from other AV-Tools might expect such a feature. WinPE or Linuxbased are offered by competitors. But I'm not sure how many users/customers are waiting for such a feature. Without a backup tool, the rescue promise is often falling short. And endusers often skipping creating and updating the boot-cd/usbstick. Looks like a lot of work with little impact on the userbase.
  • Create New...