Jump to content

emilota

ESET Staff
  • Posts

    47
  • Joined

  • Last visited

Posts posted by emilota

  1. Hello @peters,

    We are aware of issue with device name synchronization and have this on our radar. Unfortunately, ESET BUSINESS ACCOUNT is in maintenance state and no new features shall be introduced into production (more about EOL can be found here).  But I am happy to inform you, that we are already working on a next-gen product, that will have all important features of EBA and some additional enhancements. The feature that you suggested is something that we consider in this new license management tool.

  2. Hello @Marek Zahumensky, EBA does not have feature like EPC. EBA provides basic device management whereas EPC is ready for advanced device management.

    There are two workarounds:

    1. Reinstall ESET product on affected endpoints (using client tasks in EPC). The Seat Name in EBA will be updated automatically by new hostname afterwards.
    2. Rename the given seat name manually to a correct name in EBA (Activated Devices > select device > Change Seat Name)

    If this does not meet your needs, I recommend you to report your request to ESET Customer Care and responsible team will take care.

  3. @Mauricio Osorio, ESET PROTECT Complete On Premise allows you to use on-premise ESET PROTECT security management console, but does not allow you to activate and use ESET Cloud Office Security. ESET PROTECT Complete allows you to use ESET PROTECT as well as ESET PROTECT Cloud security management consoles and activate and use ESET Cloud Office Security

    So, if your customer buys ESET PROTECT Complete On Premise, he / she can't activate and use ESET Cloud Office Security. He / She can either upgrade ESET PROTECT Complete On Premise to ESET PROTECT Complete or buy single ESET Cloud Office Security license in addition to ESET PROTECT Cloud On Premise. 

  4. Hello @Lockbits,

    In EPC, you can use the Rename Computers task to rename computers to FQDN.

    In EBA, you can change the seat name but not the device name (name of the device as viewed by the installed operating system). Device name is not FQDN.

    Could you please explain, why it is important for you to have FQDN in EBA as well as update of FQDN?

    Greetings.

  5. Hello @Ryan O

    Just the additional info - you can migrate licenses from ELA to EBA while at the same time you can decide whether your devices should be intact or deactivated. Find step-by-step guideline here.

    I just would like to make sure about one thing - by "(500) current licenses" - do you mean 500 seats/units or 500 individual licenses (license owners)? If the second is your case, than the migration of all 500 licenses could be little tricky, because:

    • you need to process the migration manually 500 times by which you need to know and enter 500 license passwords
    • if the license you would like to migrate will be not registered to the same email which you will use for EBA account then this license will need to be verified by license owner (system sends email to license owner to verify that his/her license will be managed by other EBA account). If all your licenses are registered to 500 different email addresses, then you need to process this 500 times.

    Let me please know, if this is your case or if you have more questions. 

×
×
  • Create New...