• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About pieronip

  • Rank

Recent Profile Visitors

969 profile views
  1. Thanks again Frank The instructions here https://help.emsisoft.com/en/2607/deployment-via-group-policy-on-windows-servers-active-directory/ refer to download and installation of the .MSI installer. Does this have the same effect as the web install or should I change the GPO to execute the Web installer? If I follow this method will it be transparent to end-users? Thanks. From your comment re ECC and EAM, I guess ECC questions should now go the EAM forum. Thanks.
  2. I can see from the documentation how to INSTALL multiple clients by GPO. I can see how to CONNECT a client from the command line but I cannot see how to CONNECT multiple clients. What I would like to do is connect a substantial number of clients automatically to ECC, disconnecting them from EEC so that end-users need take NO action and, ideally, would see no messages. Is there a method to do this? As an aside, now that ECC is no longer Beta, are we going to get a dedicate forum for it? TIA.
  3. Many thanks. I just could NOT see that. Must get new eyes!!
  4. I have accidently created an extra workspace which is not required. How can I remove it? Thanks.
  5. This is a production server so the opportunities are a bit limited. I shall try to get this for you however. Chers. Paul
  6. Hi Sorry to 'Thread Crash' but FYI I am seeing a very similar problem with EAM for Server. Errors are as shown below. The symptoms seem identical and it's on a server so potentially quite serious. Error Application Error Tue May 22 17:37:44 2018 1000 Faulting application name: a2service.exe, version: 2018.4.0.8631, time stamp: 0x5ae8995d Faulting module name: ntdll.dll, version: 6.2.9200.22376, time stamp: 0x5a90c271 Exception code: 0xc0000374 Fault offset: 0x00000000000da535 Faulting process id: 0x3a0 Faulting application start time: 0x01d3f18e954cfd11 Faulting application path: C:\Program Files\Emsisoft Anti-Malware\a2service.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 7360d968-5dde-11e8-9462-6805ca172017 Faulting package full name: Faulting package-relative application ID: Information Application Popup Tue May 22 05:56:04 2018 26 Application popup: smss.exe - Bad Image : C:\PROGRAM FILES\EMSISOFT ANTI-MALWARE\a2hooks64.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0xc0000428. Thought an uninstall and re-install of EAM might help.
  7. Hi I am running EEC in a domain environment. Occasionally, for no obvious reason, a client machine will show as 'Not Protected. Not Managed' in the console. I cannot re-connect the machine by using 'Deploy', which always fails at the 'Disconnecting Anti-malware' step. I cannot re-connect from the client which shows 'Connected'. The client can disconnect but cannot reconnect - it times out. To solve the issue, I have to run a deployment package (Emsisoft already installed) on the client machine. Firstly, can I check that the account details I am using to deploy from the console are correct? I am using the Domain Admin account for both entries as the console is on the Domain Controller and the Domain Admin is a member of the Local Admins group and is hence a local admin on all client machines. Does this sound OK? If this is OK, can you suggest what might be wrong, as a trip to individual client machines is a bit time- consuming? Many thanks. Paul
  8. Sorry. I was a bit impatient there! The file hadn't finished uploading. Logs should be with you now. Thanks.
  9. Hi and thanks. The issue started a couple of days ago when the new build installed. I have re-installed a downloaded version over the top of the existing installation and this has not helped. I have removed EEC, keeping settings, and re-installed. No improvement. Services are running OK. Suggestions would be welcome! Thanks.
  10. How did you resolve this issue? I also have the problem. Thanks.
  11. Right! Now having a problem that at close of business one day all machines are 'Protected' and the next day some, apparently at random, are 'Unprotected' and 'Not Managed'. Will running the 'Prepare' script at startup help with this?
  12. Hi Yes. Thanks. Your suggestion was sound and re-Deploy fixed the majority of the machines. Two machines remain problematic. The Deploy job for these two stuck at 'Installing Emsisoft' step after which a retry would fail at 'disconnect' step. I could then disconnect using the batch file and I would be back at failure at 'Installing'. These machine already have Emsisoft on them. Should I uninstall manually do you think. FYI, Policies are all as required and I did try 'Prepare Machine for Deployment' with no better result Nearly there!