jedsiem

Member
  • Content Count

    37
  • Joined

  • Last visited

  • 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
    Member

Recent Profile Visitors

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

  1. 2018.10.1.9026 is now on stable. Thanks.
  2. 2018.10.1.9026 is now available on stable. Your issue might be solved now without changing anything 😉
  3. sz What version of EAM is running? Please turn the updatebranch to delayed and check again. The stable version is still containing some issues around network connections.
  4. Was soll das bedeuten? Im Zweifel bedeutet das fĂŒr Server eine andere Software einsetzen und EAM auf en Clients zu halten. Es wirkt eher wie eine verschwurbelte Preiserhöhung. Preis und einfache OberflĂ€che waren bis jetzt Hauptvorteile von EAM. Die Enterrpriseconsole ist auch kompakt. KomplexitĂ€t und Featureflut haben wir ja bei der Konkurrenz genug. Preislich ist sicherlich noch etwas Luft, aber wenn jetzt noch eine Schulung fĂŒr die Preis/Featureliste notwendig wird, dĂŒrfte es Akzeptanzprobleme geben. Da bin ich mal gespannt, wie die Spreizung zwischen Enterprise und Privat gestaltet wird. Gerade was Betatests angeht. Die Netzwerkverbindungs-Probleme mit 2018.9. ware da eine interssante Erfahrung.
  5. Still no issues around network-connections. Looks good. Hopefully we get some more comments about the beta from other people.
  6. The first hours with 2018.10.1.9026 show improvement with connection issue. The next 48h will show if all kind of issues around network connections have been fixed with this beta. So far it looks like a big improvement.
  7. I don't know, that's why I'm asking 😉 I don't like the concept "We know what the enduser needs to know". You might hide things to not confuse users when interacting with support or others. But being able to see changes in engines via version number can help a lot. At least if you run testinstallations of beta,stable and delayed sidebyside. After hours of testing with different scenarios, even the deactivation of the surfprotection in 2018.9 is not always working. The status is deactivated, but the surfprotection looks still on. Only the holistic deactivation ("Pause protection") via the 10min etc. menu is showing an impact when reproducing issue via e.g firefox downloads. When the indication of what is active or not, is buggy, the process of narrowing the issue is very difficult. When most of the customerbase is "driven" onto delayed feed, you will get less information about issues in the future. So you rely on customers which run additional test-installations for beta and stable.
  8. It that the case? Interesting kind of thinking. I'm not sure, how you come to the conclusion that it don't make sense to answer my question.
  9. I don't see the exact versions of the EMSI and Bitdefender versions there. Only the EAM version.
  10. What parts of EAM are still active when all four protection systems are disabled? After running hours of tests, I was able to get crashes from Squiggle (OpenSource LAN Messenger) with all four protection systems disabled under 2018.9.2.8988. Under 2018.6.0.8750 I didn't get the crashes from Squiggle (6 days running without a crash). My first idea with Surf protection causing the issues seems to be wrong.
  11. Did Windows 10 made some updates in the last hours?
  12. Difference is in program code. So detection engine can be different. Signature updates are done in beta,stable and delayed. Older versions of EAM offering direct infos about the version used. I'm still not getting this kind of details infos with the newer EAM versions. Not sure why the developers start to hide or move these infos. The problematic disconnection issue was introduced with 2018.9. The 2018.8 didn't show that issue.
  13. Der verzögerte Feed ist schon arg verzögert. Die EMSI-Engine selbst ist da noch auf 2018.04. Selbst wenn die Gesamtversion 2018.6. lautet. Das Problem dĂŒrfte breit genug auftreten, um nicht im verzögerten UpdateFeed aufzutauchen. NĂ€chste Woche soll auf 2018.8 umgestellt werden. Da war aber noch der alte Surfschutz enthalten. Und der Surfschutz dĂŒrfte die Verbindungen unterbrechen. Mit deaktiviertem Surfschutz klappt die aktuelle 2018.9.2.8988 auch.
  14. Do you run a test installation? Do me it looks like the surf protection is causing the connection issues with MS SQL. When runnning 2018.9.2.8988 with disabled surf protection I don't get any network-related issues either. Would be interesting to see if that is the case on other systems too.