Jump to content

jedsiem

Member
  • Content Count

    64
  • Joined

  • Days Won

    1

jedsiem last won the day on November 9 2018

jedsiem had the most liked content!

Community Reputation

1 Neutral

About jedsiem

  • Rank
    Active Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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.
  3. 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.
  4. 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
  5. Thanks for the PowerShell command. The Emsisoft Anti-Malware registry entry should not be there.
  6. 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?
  7. 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.
  8. 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.
  9. 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?
  10. My post is from 2019 and about the OnPremise Enterprise console. Which is no longer under development or available for download, right?
  11. 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.
  12. 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 offere
  13. 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.
  14. Thanks, but I don't use the ECC in customer installation. I use the EEC (local server), which didn't have that option. ECC is no option as long as GDPR status is unclear for DPOs of my customers.
  15. Thanks. They switch constantly between Office etc. I think something was changed inside EMSI which lowered the trigger to acticate SilentScreen and now is fixed. But as the update no longer works on EMSI running with that bug, I don't see an automatic fix to that issue.
×
×
  • Create New...