slarkins
Members-
Posts
165 -
Joined
-
Last visited
About slarkins
-
Rank
Newbie
Profile Information
-
Location
USA
Recent Profile Visitors
1,272 profile views
-
How to Schedule Task to update Client Agent
slarkins replied to slarkins's topic in ESET PROTECT On-prem (Remote Management)
Got it...thanks -
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?
-
MarcFL reacted to a post in a topic: Eset Server Security Non-Functional After Last Module Update
-
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.