slarkins

Currently have ESMC V 7.2. Have mix of 7.x and 6.x endpoints. It looks like ESMC V 8 isnt available any more but upgrading to V9 is. If i upgrade to V9, will the Eset Protect V9 console complain about the older v7 and v6 endpoints and will those endpoints function and be managed correctly by the new V9 management console?

Looking to create a master Windows 10 image and clone 5 pc's using Acronis SnapDeploy. All my current endpoints are connected to an ESMC server. Should i include Endpoint AV install in the master or wait until each clone is made to install endpoint and agent? What is the proper procedure with regards to cloning WIn 10?

Why do you say upgrading in the following weeks is crucial?

You misunderstand my question....i dont want to update the older 5.x and 4.x endpoints on some of the older xp and 2003 computers...can 7.2 manage the older 5.x and 4.x endpoints? If so, how do i move the older endpoints to point to the esmc server for policies and updates?

Is there anything special i need to do when creating policies specific for the older endpoints? How do i move them from era to esmc? do i just change the admin server ip in the 5.x endpoint to point to the ip of the esmc server?

I have an older 5.x ERA server and a dozen or so endpoints connecting to it. FOr various reasons i need to leave some on the older 5.x era server but will migrate a few to newer 7.x platform. The endpoind connection are a mix of 5.x Endpoint AV and 4.5.x File Security. Can ESMC 7.2 manage any off the older 5.x or 4.x platform?

I got this error on a couple older win 7 pcs when i tried to install new version of endpoint AV...turns out that both those computers were way behind on windows updates....as soon as i got them caught up then eset installed....20H2 just came out didnt it? Are you using the newest versions of software...i know only the latest will work on the latest feature releases of Win 10

I thought that license structure was for a thin client connecting...?? every client connecting is coming from a windows 10 computer which all those have Eset endpoint AV installed...even Microsoft licenses Office like that..if the connecting client has Office already licensed then the terminal server does not also need a license..the TS uses the "license" from the client

Should i install Eset File Security on my Windows 2016 server before or after i enable "terminal server mode"? I know most other apps need to be installed after server has been converted to an RDS server but not sure about AV

I realize that...but why all of a sudden does the latest endpoint/agent all in one installer that i created on ESMC locally all of a sudden have an issue? I have created at least 5 or 6 AIO installers over the years and have done the exact same thing without issue

What is the combo of endpoint/nic that has issues...i am in a holding pattern upgrading my 2016 server endpoint until i hear what the cause is.

I created the all-in -one installer via ESMC on premise...never had issues in the past with previous AIO installers i created..if i run the AIO instller via the network share i get no Smartscreen popups...only if i copy the same installer to the local desktop will i get the popup...

I created an all in one instal package for latest version of endpoint AV and agent. If i install from server share there is no issues. If i copy the install file to the desktop, i get a smartscreen pop up which blocks the install. While i can bypass the smartscreen and install anyway, why is this happening to begin with? I have never had any issue over the past few years creating install files and installing from a copy of the file from the local desktop (Windows 10)

When i choose the endpoint then click Actions at the bottom, the only item in the list that would apply is remove. CLicking this is the same option/process as removing the endpoint from the management server itself. I am almost done with my upgrades. I will just ignore for now then delete and recreate new task at new time i need to update

Is there a certain combo of endpoint version and/or network card driver that has the bug? I am in middle of upgrading all my endpoints/agents but will hold off on the 2016 servers after seeing this...

I have one endpoint that will not update via a task. The overall task itself is 99% green with completed status but it always shows that one endpoint in yellow. How do i remove that failed endpoint from that upgrade task so that the task itself shows 100% success?

Is it possible to update agent and endpoint on a Mac via tasks?

SO my initial task to update agent on my laptop with an asap trigger worked......i dont see a way to use the task and modify endpoints and triggers...am i overlooking or do i need to create a duplicate task?

I want to do a few test endpoints first.... seems like my agent upgrade task worked ...i did my laptop only...agent must not need a restart when upgraded like the actual endpoint

please stop hijacking my thread...your question (not related to my post) gets answered...not my followup question ok..your screenshot shows a group of 2..i assume if i click that i can pick and choose which clients i want to update?

ok..your screenshot shows a group of 2..i assume if i click that i can pick and choose which clients i want to update?

If i choose the route of click the icon and do update installed eset products....will the next screen allow me to pick the endpoints i want to update?..so with 7.2 i can only update endpoints this method?

Can we get back to my original question that started this post? How do i set up tasks properly to update agent and/or endpoint version?

already disabled automatic SQL exclusions....

Just upgrading ESMC to 7.2....i used the all in one installer which also updated SQL express. I am now seeing in the event log every 15 minutes... SQL Server Native Client 11.0: Unable to load sqlnclir11.rll due to either missing file or version mismatch. The application cannot continue. I have disabled SQL in automatic exclusions to generate and also added the entire SQL server folder in the exclusions list...i am still seeing the event logged every 15 minutes...how do i fix?