Command IT
-
Posts
52 -
Joined
-
Last visited
-
Days Won
2
Posts posted by Command IT
-
-
21 hours ago, TheSkymanDC said:
That's about what I'm seeing here. I'd be interested to know what the difference is.
Pushed around 1000 out yesterday with 35% red restart and 65% yellow restart, so the reality ended up better than the test sample, but that's still a large number of red restarts
-
10 hours ago, Marcos said:
If you have upgraded from v7.3.032 to v7.3.2036, a reboot will not be required.
Of the 30 test machines I've upgraded from v7.3.2032 to v7.3.2036 only 2 have had a yellow restart recommended alert. All the rest have had a red restart required alert
-
Thanks @Perry and @Mirek S
I downloaded the GoDaddy CA certs from https://ssl-ccp.godaddy.com/repository?origin=CALLISTO and followed the instructions and it now looks like it's working
John
-
Thanks Mirek. I have a certificate from GoDaddy, but if I configure in the MDM policy it says it's not a valid chain. Is that because GoDaddy certificates require an Intermediate certificate?
John
-
+1
I can find information for ERA 6.5 but it's says don't use this process for ESMC 7
John
-
Ran into an issue with EFS on Hyperv Core.
If I install EFS using the core option on the GUI install it doesn't matter how Livegrid is configured in policies I get a message "ESET LiveGrid® participation is not configured" and I can't see how I can get LiveGrid configured
If I install using commandline "msiexec /qn /i efsw_nt64.msi ADDLOCAL=RealtimeProtection,Rmm" as per the documentation for performing an commandline core install, then I don't get the LiveGrid messages.
John
-
They are all running 32bit 10.0.17134 and disabling Protected Service didn't help.
I suppose we'll just have to wait for 10.0.17763 to get re-released
-
I'm getting Antivirus and antispyware protection disabled on a number of machines running 7.0.2073.1
They are all 32bit machines running Windows 10. I can't re-enable protection from the GUI, but a restart fixes the issue for a short time (maybe 6 hours) but it then re-occurs.
I recall seeing a similar issue on the Home version that only affected 32bit Windows 10 as well which the workaround was to disable the "Protected Service" option within the HIPS settings, but I never saw a real fix for it.
I'll try disabling the Protected Service in HIPS and see if that makes a difference.
-
Is there a timeline for ESMC 7.1 ?
John
-
We found we stopped having the logs after running a repair of the SQL Server Native Client 11.0
John
-
We had a problem with our Fortigate routers preventing ESET acrivation which was fixed in version 5.6.6
John
-
13 minutes ago, Rami said:
Why do you want it to stop showing you about threats or attacks?
I want to get notified when there's something that requires action, so I have email notifications for unresolved threats. These show up as unresolved threats. An analogy would be, I'm interested in knowing if someone walking down the street has tried to open my front door but it was locked (resolved threat), but I really want to know if the door got opened (unresolved threat)
-
I'm seeing a few of these related to CVE-2017-5638.Struts2. The affected servers are not running any Struts code, so I'm assuming this is detecting that someone is attempting to utilize the exploit, but how do I stop ESMC from showing these as threats once the device has been checked to ensure it's not vulnerable?
John
-
SKIP_PENDING_REBOOT_CHECK=1
I suspect is the one you are looking for
John
-
Found that the policy that got carried over from previous versions had "Email Client Integration" under "Email Client Protection" disabled. Even though there were no email clients installed, enabling the mail client integration cleared the error.
John
-
The repository changed worked and both XP and Server 2003 no longer report as outdated, but I have erroneously pushed a V7 upgrade out to both a 2003 and XP machine and both successfully upgraded. Does the non-support of XP and 2003 just mean there is no support, or is it an installer bug that let me install V7 on these machines?
-
Just adding as another one having the same issue, which is fixed temporarily by a reboot of the ESMC server
-
I've created a ticket 175384 and attached the logs
John
-
That's what I was looking for, but kept ending up on the V6 page
So for a ESET File Server Core installation/Upgrade via ESMC I just need to have
QuoteADDLOCAL=RealtimeProtection,Rmm
in the installation parameters?
John
-
No, there's no email clients on any of the servers I've had this on. I'll need to get another machine to fail so I can grab the logs. I've already reinstalled on the ones that have failed so far.
John
-
Is there some updated documentation for command line installation of ESET File Security V7?
Trying to do some Core installations and it appears some of the feature names have changed/gone
John
-
ESET File Security 6.5.12017.0 to 7.0.12.14.0 using ESMC Software Install task
John
-
Uninstall and reinstall generally fixes it, but I've had it on a number of systems now and of course it requires another restart of the server
John
-
Does the update to 7.3.2039 from 7.3.2036 require a reboot?
in ESET Endpoint Products
Posted
Still getting a RED restart alert going from 7.3.2036.0 to 7.3.2039.0