JoeP

Member
  • Content Count

    20
  • Joined

  • Last visited

  • Days Won

    2

JoeP last won the day on May 15 2017

JoeP had the most liked content!

Community Reputation

1 Neutral

About JoeP

  • Rank
    Member
  1. GlobeImposter 2.0 This ransomware has no known way of decrypting data at this time. It is recommended to backup your encrypted files, and hope for a solution in the future. Identified by sample_extension: .{[email protected]}IQ custom_rule: victim ID in encrypted file Click here for more information about GlobeImposter 2.0
  2. Thanks will do tmrw, i have disabled all rDP and im at home now
  3. I have both AV installed for months and today 4 of our server infected by ransomware Please help
  4. Hi Thanks. I have cleaned with Roguekiller, but anyway here is the log
  5. 1) copy conhost 2) paste to same location 3) rename conhost - Copy to 1 (random name) <- only at this point emsisoft detect it. Another thing, knowing the origin file conhost is indeed a virus, right click the file. Select scan with emsisoft, no virus found.
  6. My server infected with this conhost. I can almost confirmed this is 100% a virus. Roguekiller got it. ESET failed to block it Emsisoft unable to detect it, but.. if i copy/duplicate the file, emsisoft detects it and delete the new duplicated file.. However the original file remains.. haha
  7. Create a light package, copied to the client host, login as local admin. Double click connect bat i get
  8. Manual scanning detected virus already in system.......
  9. Hi We are evaluating whether to change ESET to EAM , but as the screenshot. Our ESET is doing all the job.. Something I did wrong? Luckily i didnt uninstal ESET
  10. Hi When im deploying this client which is server 2008 OS, I'm using TRIAL and the other cdkey given (I'm on trial to evaluate whether to buy and replace ESET or no). I'm not sure what cdkey are those Here attached first screen i saw EAM not connected to EEC, that is what i been trying to do. STATUS at EEC - Not Managed
  11. Server 2012 R2 Client - 2008 R2 Version of EEC and EAM - latest just downloaded 2-3 days ago.
  12. Hi Frank I have similar problem HostJob[28] on 'WORKGROUP\xDSERVER' failed due to error: HostJob[28] failed with the following message: HostJob[28]: Time out error. Communication service was not started for computer 'xDSERVER' My EEC is in domain, but this file server is in workgroup. this file server has no EAM installed before, it is currently been installed via EEC, I tried the batch file to discon from EEC and re-deploy again.. It stuck at WaitAntimalwareConnected for few mins and: HostJob[30] failed with the following message: HostJob[30]: Time out error. Communication service was not started for computer 'xDSERVER' (System.ServiceModel.FaultException`1[A2Enterprise.Entities.Errors.ServerError])
  13. Lol , my bad. Should run this on client, not the server
  14. I setup a trial server and install everything and working fine. Now that i have prepared a new server and wanted to transfer the console to new location i , remove 1 of the client. After remove i ran this C:\Program Files (x86)\Emsisoft Enterprise Console\server\Scripts>disconnect_eam _from_eec C:\Program Files (x86)\Emsisoft Enterprise Console\server\Scripts>echo on C:\Program Files (x86)\Emsisoft Enterprise Console\server\Scripts>cd /d C:\Progr am Files (x86)\Emsisoft Enterprise Console\server\Scripts\ C:\Program Files (x86)\Emsisoft Enterprise Console\server\Scripts>reg query HKEY _LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\EmsiCommService 1>nul ERROR: The system was unable to find the specified registry key or value. C:\Program Files (x86)\Emsisoft Enterprise Console\server\Scripts>if 1 EQU 1 GOT O SERVICE_NOT_EXIST C:\Program Files (x86)\Emsisoft Enterprise Console\server\Scripts>echo CommServi ce was not found CommService was not found C:\Program Files (x86)\Emsisoft Enterprise Console\server\Scripts> New console still unable to take over the control HostJob[6] on 'Qxxxx.LOCAL\Qxxx1' failed due to error: HostJob[6] failed with the following message: HostJob[6]: Impossible to disconnect Emsisoft Anti-Malware on computer 'Qxxx1' from another Console.