slarkins

is there an eset documented process for upgrading file security on a terminal server?

I have an exe with updated Agent and Server Security created using the on prem eset protect console. When i run that on a terminal server, do i need to put the server in install mode first?

Got it...thanks

V11..Protect on Prem...i want to schedule a task to update the agent on the remote Windows clients. How is that done? I dont see Agent as an option to pick for what the task needs to do

Any eta on hotfix for this? I would rather roll out V11 with latest hotfix....

I have all my endpoints set with password protection. To pause protection the password is required. I do not want to give my users the password to the endpoint. Is it possible to password protect all settings but give the end user the ability to pause protection without entering the password?

Will all 6 items that failed to start(showing in Protect console) automatically start working after the HIps module update later today? As long as i install the latest revision for V8,V9 or V10, i will be good with regards to the expired cert? Are any version of V7 affected? I still have a few of those left i need to upgrade...a couple are on servers i need to install the windows update with regards to azure code signing

Marcos...can you chime in here with best approach with minimal server restarts? This thread is kind of all over the place with regards to actual fix...and no mention of v8... running Server Security 8.0.12013...on Windows Server 2019...upgrading to 8.0.12015 failed....what are the proper steps to fix this? If i switch to pre-release and get Hips 1467.3...what will that allow me to do? Upgrade existing without failure? I really do not want to go to V10 yet...i would rather stay in V8 but if V9 is only path...then i will do V9...i wasnt sure if any version of V8 overcame the cert issues

So some of my servers (v8 flavors) are on hips 1467.2.....the 2 windows 2019 servers with 8.0.12013 are still at 1466 HIPS....it is not possible to set the system clock back as it is part of a domain...for some reason these 2 servers didnt update hips modules...i actaully have a win 2012 server running 7.3.12005 and it is running the 1467.3 hips module...so i know the current hips modude is installing on some servers...dont know why the 2 2019/8.0.12013 are stuck at 1466.... I am running various versions of 7 and 8 Server Security on various versions of Win Server...I am working on getting the V7 updated to V8...it sounds like some of the older "sub versions" dont work any more....for V8, 9 and 10, what is the minimum full version that overcomes all the SHA256 and cert expiration? I am not one to install latest and greatest version until the bugs have been worked out...but i want to install a good stable version( lately seems to be messing up terminal server, freeze and hang and not responsive) that will be supported for a while. This continuous breaking and updating Eset AV versions is getting dangerous(not know if a server will work properly after upgrade) and tiresome

Same here...but i am running Server Security 8.0.12013...on Windows Server 2019...reboot server this morning and have 6 differtn things showing as non functional...tried to upgrade to 8.0.12015 but it said it failed/not successful. I see that an updated HIPS module (in prerelease currently) fixes the problem? Any idea when the updated hips module will be in production channel? Once the Hips module is updated, will this fix 100% or is something else(like upgrading to v9 or 10) required?

while the status appears green on the server...my eset protect console shows all 7 of my 2012 servers as critical status...how do we clear eset protect critical error showing on eset protect console... with message...Antivirus and antispyware protection disabled..

I only see this issue so far on my 7 windows 2012 servers...ver 7.x and 8.x...first notice was 3.29pm eastern(about 50 minutes ago)

Add me to this list....only 2012 servers so far. if i dismiss error on the server...protection status shows green across the board...both 7.x and 8.x versions of file security...

If i do the Stop Managing option....does that also uninstall the agent from the endpoint ?

My main ask would be how do i remove it from showing up in the eset protect console in the pc list (and prevent it from reconnecting to protect server automatically)...but leave endpoint AV installed and running on the client? Keeping policy the same on the endpoint once its not managed any more isnt a huge deal...it would be nice but not super critical....i wasnt sure if choose option 2 in the remove was the correct thing to do...it looks like running a stop management task or uninstalling agent would work for what i am trying to accomplish? Does uninstalling agent on windows require a restart? i think running the stop managemnt task may be best option? Stop computer management You need to suspend the connection between Endpoint and ESET PROTECT otherwise the removed computer will reconnect as a new one. Run Stop managing task or uninstall Agent or a security product locally on a computer. Endpoint will not report a status of running tasks after management is stopped.

I have a few old legacy OS's that are creating(cluttering) warnings on my Eset Protect Server console. These are not able to be updated to remove the warning as the OS is not supported any more. While i can mute the warning in the PC list, there is no way to remove from the Dashboard. I would like to keep the existing endpoint installed with the current policy that is being sent from the Protect server but remove the managing aspect so it doesnt appear in the Dashboard/PC list any more. What is the proper way to do this? I realize that if i have any policy changes i will have to manually update on each endpoint

So installing the security update(and prerequisites ) list for each OS above will turn off the OS out of date warning for that particular server?

I understand Windows 8 and WIndows 7, Windows 2008 server and probably 2012 triggering the OS out of date(BTW ESET...i dont need my AV vendor telling me the obvious and no way to turn off the warning cuttering up my admin console)...but why are some of my 2016 server triggering this message? What exactly is ACS support and what needs to be installed to meet the criteria?

This is not computer specific...it is doing on both my Macs running same OS version....one hasnt been used(just sitting there at login ) for weeks...i find it hard to believe this is a computer specific issue since both are experiencing same issue.

I have 2 production Macs running OSx 12.5 and running 7.1.1700 and 7.2.1600. Seems like this started late last week but both now show red in the Eset Protect console with ESET Web and email protection is not configured error. This only happens when a Mac is restarted or not initially logged in. Once a user logs in , i can see the red dot on the Eset endpoint icon disappear after a few seconds and the Eset Protect console error clears. I thought it might be 7.1.1700 so i upgrade one to 7.2.1600. Same issue. One Mac the user left a couple of months ago so it has been sitting waiting for the initial login for weeks now without throwing any errors (until i noticed today) and as far as i know, not updating any other software in the background as it is not actively used. Something changed late last week with either OSx or the Eset endpoint modules that is now throwing this warning as i have never seen it before today.

I have one Windows 10 pc running AV 10.0.245.0. It randomly has issues updating its definitions. Happened last Friday for a while. I did a remote clear update cache and a remote update definition tasks which seem to fix the issue. The same computer tripped same error today. Below is what i get via email regarding the error. Is there anything i can do to permanently fix this? 4/6/2023 12:24:37 PM - During execution of Update on the computer (computername), the following event occurred: Compiler error (1af8). 4/6/2023 12:24:37 PM - During execution of Update on the computer (computername), the following event occurred: Error occurred when applying differential update to base file.

thanks...i am going to wait until the rest of my Win 10 endpoints update to v10.x...then make policy change one other question...all my Windows servers are either v7 or v8 end point file security. Is major version auto update for servers affected on v7 or v8 or do the servers need to be on v9 or later for auto updates to happen?

removing the all group from the default auto update policy....or enabling (lightning bolt red) on my custom end point policies...that will just turn off major version updates...i assume security updates within same major product version will still happen?

I have not modified policies for at least a year...if there was a policy "modified" on 3/10 it was me going in to the policies on 3/10 to determine why endpoints were updating to 10.x. Maybe i might have toggled Auto updates on and off but never saved any chnages. No changes were made. the Windows 10 endpoints are in 2 folders (locations) and each has their own endpoint policy which have the same settings. Auto updates were turned off way back when that option was available in the policy options....below are screen shots of the 2 location containers that only have windows 10 endpoints ..each is a unique policy..neither have auto update enabled...does the log file say which policy name the was modified on 3/10 and which one the auto update was coming from? Do i need to do the steps in the link below and assign the policy to the containers my endpoints are in that i dont want auto updating major version? https://support.eset.com/en/kb8147-opt-out-from-auto-updates-in-eset-protect-and-eset-protect-cloud?ref=esf

log file has been uploaded eea_logs.zip