MichalJ

Hi @Thomas F., when you was removing the computers, did you check the option to "deactivate products"? Alternatively, it might have happened, that some of the devices have become duplicated on the licensing side. You can login to either EBA / ELA (based on which platform you use for license management), where you can view all of the activated devices. If you find some, that have not connected for a longer time, you can deactivate them, and this will free the license.

Hello, in case you mean "ESET Full Disk Encryption", then the answer is yes, as this is managed via ESET Protect / Security Management Center Server / agents, which use HTTP Proxy. If you want to use ESET Endpoint Encryption, with a dedicated server, then this solution uses a separate Cloud Proxy component.

Hello @mars_ots no, even the old ESET Remote Administrator 6.x agents and ESET Security Management Center 7.x agents, should be compatible with the latest endpoint. However, upgrade is recommended.

Hello, When you mention "out of date message / yellow icon", you mean the one on the customers computer? This one is only shown in case when either the management agent is not on version 7.2, or when the installed Security software version is within the set defined for EOL due to various issues, described in the banner on the top of this page. Those alerts currently could not be suppressed from the management console, only option is to install the newer version of the Software. As mentioned by MARCOS, when the "computer restart required", there might be impact on the protection, due to the old drivers being still loaded in the system, so the newer application is not able to work completely. Drivers are reloaded only upon a system restart. Since Endpoint 8.0 you will be able to activate the automatic updates, which use a different method than a complete reinstall, when the incremental update is performed by the application itself, prepared, and upon reboot applied. Application continues to run in its previous state, until reboot is performed. This is as well explained by Marcos in the post above. Regards, Michal

Hello @Rootaah in general, the life is easier in case you have the console. I would recommend to combine the installation of the newer endpoint version with the reboot task (basically, set a software installation task, and checked option "reboot automatically when needed". As the reboot is required immediately after the task is executed, and there is impact on the protection of the device during the time, so immediate reboot is required. Therefore, the best practice is to deploy the newer version of the endpoint software during the maintenance window, when the reboot would not cause any harm. You can schedule any task, individually per customer, if your customers are organized into groups. Just define a corresponding trigger, to have it for example executed at a specific time during the week / month. You can even write a specific CRON expression. PS: if your clients currently run Endpoint 7.3, there is no need to hurry with the upgrade, 7.3 is within a full support and has guaranteed compatibility with all relevant operating systems. PPS: You can upgrade the ESET PROTECT management agent anytime, as reboot is not required for its upgrade (you can do this via a "ESET PROTECT Components upgrade task").

Hello @tbsky Thank you for your feedback. The only thing I can promise, is that this name change is the latest. As we are moving both former Cloud Administrator and Remote Administrator closer together, and we wanted to simplify our business offer as well, due to the changes with regards to ESET Brand positioning, the "PROTECT" name was chosen to be the name for the future. Besides that, nothing is really being changed, so consider this as a cosmetic change, but the one to stay.

That might be the reason. Latest links might have not yet been updated correctly, to reflect the V8 release. You simply triggered the update too early, as usually it takes some time, until the changes are reflected around all locations.

Hello, indeed - the Endpoint Antivirus is NOT compatible with server operating systems. For installation in Windows Server Operating system, you should use ESET File Security instead.

Hello, the task itself is indeed set to install the "latest" available version. However, even as of now, you can still create a custom software install task, to install the previous endpoint version.

@TheSkymanDC when you mention "install latest" what particular task have you used? As tasks in ESMC always reference a particular version, meaning the task needs to be updated. Or you selected the "quick action" in the dashboard, to upgrade endpoints, and a new software install task was created?

Maybe, just maybe, are there any rules set for a Firewall by a policy? As in this case, the entire "FW rules list" is set to "read only" and the local client can´t create a new rule. You will have to configure the policy setting in a way, that you will allow merging of the policy based list, and the local list. But that is just a hint.

Also, per my check with the relevant PM for ESET Cloud Administrator, this (number 2) issue should be fixed in the upcoming release, that will happen on December 9. Internal reference P_ESMC-23019

Hello, it is not possible to update that old version of agent due to insufficient compatibility (version is too old, and is no longer tested by ESET for upgrades), by the means of "Security Management Upgrade Task". You will have to make sure that your server is upgraded to ESMC 7.2, and then use a different deployment method, to upgrade the agents (GPO, SCCM, etc.).

Please note, that you have to use a "software install" task (which is a client task), to install Endpoint Antivirus / Security not a server task as it is executed on the "client side", by Agent.

Hello, as the license is not bond to a specific instance of your sever, rather the individual devices are activated against ESET cloud based licensing servers, you do not have to do anything related to license itself. Just set the devices to connect to a new server instance, and all will be OK.

This seems to me that it is a problem related to ESMC itself, rather than a problem with network communication. Did you by any chance looked into the server trace log, and searched for "ERROR" strings there? That might indicate the problem with the license synchronization. I have asked my colleague @MartinK who is our ESMC expert, to maybe advice here.

Hello, currently it is not possible to create an all in one installer for Mac OS in ESET Security Management Center. You have to create an agent installer, and then install the ESET Endpoint Antivirus / Security by the means of "Software Install" task.

Hello @Miami This particular example as shown above, would not work. As the source of this particular problem is actually "Security product". It also states about the Endpoint Security / Antivirus, not about the management agent.

Hello, can you share details about the error that you get upon adding of the license? In general, the change should be reflected in the license screen automatically. You can alternatively click on the "synchronize licenses" button in the license screen footer. Also, when you say "going through EBA", you mean that you do not see the updated date in EBA, or that you can´t add the license via EBA account to your ESMC instance? In all cases, we will most likely need to know details, meaning PLID of your license, screenshot from the error state, and a server trace log from the time, when the unsuccessful license addition attempt was done. I would recommend to create a support ticket, and ship the above-mentioned information to them.

Hello @CPR If I get your topic correctly, you are planning to divide your business (and also existing ECA instance) to 3. Portion will be kept within the original ECA instance, whose license will be "downsized", and two new licenses will be created / ordered for the newly created entities. Please note, that under one EBA account you will be able to create only one ECA instance. So the order of things should be as follows: Order 2 new licenses for the two new tenants + decrease the quantity on the existing license Register two new EBA accounts and create two new ECA instances Deploy the agents from the newly created instances to the machines where the original one was running. Per my knowledge, it should execute "repair" and replace the connection info / certs in the agents. I bet that @MartinK can confirm this assumption. Please note, that by December we will have a new version / successor of ECA, which will be multi-tenant, meaning you will be able to have there users, with access permissions tight to a different groups. You will be able to able to divide the license into sites, and allocate license "parts" to users. But in case those will be totally independent businesses, also with dedicated management for IT, the option one with separate ECAs might be better.

Hello, unfortunately, this is currently not possible in a way you are seeking for. If customer adds his license to EBA account, the only way for you is to have a dedicated login (email address) to every one of such EBA accounts. We are currently analyzing / designing a solution, that will allow reseller management / visibility into the customer´s EBA accounts, and also connected ECA instances, however it will take some time till this is developed. Internal reference: IDEA-1355

Does the computer restart help to resolve the situation?

Hello, the post have been added. We are sorry for a delayed post, we will try to make them available at the date of the actual release, so the accompanying information is always provided:

Hello, I will check with the team responsible. Per my knowledge, there is a plan to adjust the "frequent password reset requirement" in EBA. I will try to provide a more detailed response, once obtained. Internal reference: IDEA-1464

Hello, I will recommend you two solutions, that are in my mind: Forcibly deactivate all of the servers, and then try to reactivate them manually. If there is a glitch, it might correct itself (if your servers are managed by ESMC, you should be able to reactivate them easily by the product activation task from there) If you do not want to do what is in the step 1, create a support ticket, so our teams will check it in the database / backend of EBA, to check, why it shows +1 activate seat Units column indicates the number of concurrent terminal sessions on that partcular server, per my level of knowledge.