maniac2003

Member
  • Content Count

    50
  • Joined

  • Last visited

Community Reputation

0 Neutral

About maniac2003

  • Rank
    Active Member
  • Birthday 11/18/1986

Profile Information

  • Gender
    Male
  • Location
    The Netherlands

Recent Profile Visitors

3645 profile views
  1. Yes I was. Frank H. PM'ed me with the explanation. So I'm aware that the're separate issues. Hopefully it's fixed in the next release. Grtz, Richard
  2. Windows 10 Pro x64 (fully updated) Meanwhile I got a message from Frank H. that the fix for my issue (notifications and alerts) is different from the Retina resolution issue. I'll keep you posted and when I'm able to take a screenshot of the issue I will post it here.
  3. Looks like I still have the issue on my Lenovo X1 Tablet 3rd Gen (3000x2000) 200% scaling. The flyout after a update is small and cramped. I'll see if I can get a screenshot of it. EAM: 2018.8.1.8923 System is updated en rebooted a day ago.
  4. Hi David, I just e-mailed support. Guards were enabled again after a restart but the connection with the server still gives a error. Hopefully I can work this out with support. Thanks for your reply.
  5. Hi all, EEC: 2018.4.0.3361 Windows Server 2012 R2 x64 (6.3 Build 9600) This morning I logged in to my system and all guards were turned off. The message below is from the Logs I restarted the EEC server. Seems that all clients are disconnected, again, but not all systems have disabled guards. To which certificate is being referred?
  6. Hi @Frank H, I see. Can reproduce the bug. Following you instructions. Good that it will be fixed soon. Cheers, Richard
  7. Ok. While dragging the GUI, as @JeremyNicoll mentioned, I got a smiling BSOD on epp.sys After a reboot I can see the component dropdown list in the GUI. Thanks @JeremyNicoll @m0unds and @stapp
  8. Can you show what you mean, I can only sort the columns. I see no boxes to tick/untick. okay, that sort of works. Still not as handy as before. Also can't recall older scan logs that way, as they don't show up. No prize for me then. Components filter how??
  9. Where can I find my scan logs now? (Yes I know: C:\ProgramData\Emsisoft\Reports) but from within the GUI. If I filter on "scan log" it comes up empty. No personally I found the separate logs way better than this. Faster and more clear.
  10. Hi Frank, Nice to hear from you This morning I've installed the new EEC. From what I can see in EEC the client computer (installed: 31-10) is on 2017.9 When trying to "solve" the issue from within EEC I get the following error: Message: HostJob[357] failed with the following message: HostJob[357]: Impossible to disconnect Emsisoft Anti-Malware on computer '<domain>\<computer>' from another Console. Use Disconnect_EAM_from_EEC.bat to disconnect Emsisoft Anti-Malware or uninstall Emsisoft Anti-Malware before reconnection. Please check documentation for details. Details: HostJob[357] failed with the following message: HostJob[357]: Impossible to disconnect Emsisoft Anti-Malware on computer '<domain>\<computer>' from another Console. Use Disconnect_EAM_from_EEC.bat to disconnect Emsisoft Anti-Malware or uninstall Emsisoft Anti-Malware before reconnection. Please check documentation for details. (System.ServiceModel.FaultException`1[A2Enterprise.Entities.Errors.ServerError]) Followed by: Message: HostJob[357] on 'domain\computer' failed due to error: HostJob[357] failed with the following message: HostJob[357]: Impossible to disconnect Emsisoft Anti-Malware on computer '<domain>\<computer>' from another Console. Use Disconnect_EAM_from_EEC.bat to disconnect Emsisoft Anti-Malware or uninstall Emsisoft Anti-Malware before reconnection. Please check documentation for details. Details: HostJob[357] failed with the following message: HostJob[357]: Impossible to disconnect Emsisoft Anti-Malware on computer '<domain>\<computer>' from another Console. Use Disconnect_EAM_from_EEC.bat to disconnect Emsisoft Anti-Malware or uninstall Emsisoft Anti-Malware before reconnection. Please check documentation for details. (System.ServiceModel.FaultException`1[A2Enterprise.Entities.Errors.ServerError]) at A2Enterprise.Server.Tasks.HostJobExecutor.ExecuteOperationSteps(List`1 steps) at A2Enterprise.Server.Tasks.HostJobExecutor.<>c__DisplayClass17_0.<Run>b__0() at A2Enterprise.Impersonation.Impersonator.Execute[TError](Action action, Entity entity, Func`2 errorBuilder, Identification[] identifications) at A2Enterprise.Server.Tasks.HostJobExecutor.Run(Object state) Seems the only solution is to manually disconnect and re-connect again. As you can imagine I'm a bit tired of that. I don't have the time to repeat this with around 40 clients out of 125.
  11. Hi, Today the issue is back: Running: EEC: 2017.9.1.3212 Client: 2017.9.0.8006 (Windows 10 Enterprise Version 1709) Fresh Windows install on a Acer laptop just out of the box via SCCM. Ran the Prepare_PC_for_Deployment.bat script locally. >> can't this be automated? << Deployed EAM via EEC All was 'green'. Client updated and scanned after deployment. "Protected" status in EEC After a while, didn't time it, I see the client is "Not Protected" in EEC What can I send you to remedy this once and for all? Kind regards, Richard
  12. @pieronip indeed, if they keep getting stuck in the process. Remove EAM from the machine via Windows Uninstall and do a new deploy from EEC. I've set the 'prepare' script as a startup script through GPO. That way I'm sure that the clients have the right settings. @Frank H I've not seen any more EEC connection issues with the new EEC. Hopefully the disconnects are also something from the past with the last update [different topic]. Grtz from The Netherlands, Richard J
  13. Hello Dana, I chime in on this one. At our company we have the same issues now and then. We run 200 client and 25 server licenses. From what I've seen only the clients have these issues. The issue is not something that suddenly started, it's from the beginning we got Emsi. Yesterday I fixed one client (disconnect and deploy EAM again). Today it's unmanaged again. How can we investigate the cause? Best regards, Richard
  14. No further login issues encountered. Looks all good.