pieronip

Member
  • Content Count

    28
  • Joined

  • Last visited

Posts posted by pieronip


  1. I found another strangeness and am posting it in case it has any bearing.

     

    This is a capture of part of the 'Managed Devices' page.

    Capture.JPG.8cad64906b8585dc2bea22d263c60409.JPG
    Download Image

    As you can see, there are 29 devices (correct), Protected 21 (correct), offline 8 (correct), Unused seat 1.  This last is NOT correct, there are 28 seats available so this should show -1 UNLESS the three seats from the other licence, which has used only one seat is taken into account which would add 2 to the available count and make the Unused count 1.  Is this how it works?


  2. Hi

     

    Can anyone advise me on a couple of questions on licensing please?

     

    We have two licences.  One is for three seats and covers our server and has two seats unused.  The other is for 27 workstation seats.

     

    I had been under the impression that I could create two workspaces, assigning one of the licences to one workspace and the other licence to the other workspace.  I could then apply the appropriate installation token to the existing EAM installations to assign one licence or the other.  This does not seem to work however, and ALL my devices, 28 in number, except the server have placed themselves under the first (27 seat) licence.  This has resulted in that licence being oversubscribed.  When I try to fix this by removing a device it just pops back in again as a ‘Not Managed’ device.  The server cannot be seen at all.

     

    Also, when I go to 'Workspace Settings' – 'Licence' there is no option to change the seat count by removing or purchasing additional seats.

     

    Am I doing something wrong?  What do I need to do?

     

    FYI - I was offered a merge of the licences to manage all under one licence but the boss wouldn't go for it as the cost of so doing was greater than two distinct licences.

     

    TIA


  3. 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.


  4. 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.


  5. 2 hours ago, GT500 said:

    Any possibility of a memory dump from a2service.exe when it crashes? We have instructions for configuring WER to save automatic crash dumps at the following link (be sure to enable full crash dumps):
    https://helpdesk.emsisoft.com/en-us/article/204-how-do-i-configure-automatic-crash-dumps-in-case-of-application-failures

    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. 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.


  9. 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!

     


  10. Quote

     

    Hi

     

    I shall attempt this later but I may not succeed because the main difficulty is that the console locks up as soon as I sign in.  I have to use Task Manager to kill it.  This means that I am only able to access the console functionality maybe once in 20 attempted logins.

    I'll try your suggestion this evening if I can, but I really need to understand and avoid the lock-ups.  There is nothing in the event log and Task Manager simply show 'Not Responding'.

     

    Thanks.


  11. Hi

     

    I am having this issue on version 2017.9.0.3177.  I tried to re-install over the top of the existing installation which has resulted in all the workstations becoming 'Not Protected.  'Solve' is unable to complete the 'Disconnect from the Console' step so I'll have to run the disconnect batch file on  them all.  Is there an issue with this latest version?

    Edit - Console is on Server 2012 Essentials.

    Thanks.