Jump to content

cliffennis

Members
  • Posts

    15
  • Joined

  • Last visited

Posts posted by cliffennis

  1. I've had a few cases where a computer was built and activated then immediately replaced with another using the same name.  This caused the same issue where the reported license usage was higher than I'm actually consuming.  Like MichalJ mentioned it's best to run the deactivation first, but in those cases I had to have ESET support manually remove them.

  2. I think the order I ran them in was:

    1. Attempt "stop managing" task (pretty sure that did nothing)

    2. Manually remove the record from the database:

    • Open the era_mdm_db database
    • select * from Device (to get the DeviceID you want to delete)
    • delete from Device where DeviceID='yourdeviceid'

    3. Rebooted server

    4. Deleted in the ERA Web UI

     

    Hope that helps.

  3. I had a kernel update that required a reboot so I went ahead and rebooted the ERA server.  I was then able to delete the device and it did not return.

     

    @MichaelJ, you had suggested that I stop the MDMcore service.  I see that in the documentation that it should be registered as a service in linux and allow for the 'service MDMcore stop/start' commands but that was not the case on my system which is Debian 8.  I did locate mdmcore at /opt/eset/RemoteAdministrator/MDMCore/eramdmcore but have not found any documentation on how to stop/start/recycle it individually.

  4. Just adding to this with an update... I started with mobile connector 6.3 so mine wasn't a record from 6.2 or previous.  I haven't had the chance to stop the MDMCore service but attempting to remove it from the database didn't work.  I took a guess on which database and table, used database era_mdm_db and table "Device".  The device is still there in L&F.

×
×
  • Create New...