Zen11t
-
Posts
48 -
Joined
Posts posted by Zen11t
-
-
Hi Guys!
I want to make this exclusion:
C:\ProgramData\MySQL\MySQL Server 5.7\Data\*
Need I use quotation mark?
So this is the good?
"C:\ProgramData\MySQL\MySQL Server 5.7\Data\*"
I don't find this in the help:
https://help.eset.com/ees/10/en-US/idh_performance_exclusion.html?idh_exclude_format.html
Thx,
Zen11t
-
It will be nice if VA will support this feature.
-
- Tomasz Trynkowski, BlueBear, labynko and 1 other
- 4
-
Hi!
I need some help:
If i want to use auto-update future but want to stay on specified version, this policy correct?
Or I just stay 9.1 version, I have to use this? 9.1.*
Thank you,
Zen11t
-
On 12/12/2022 at 4:54 PM, MartinK said:
We have encountered this issue recently. Could you please confirm this error happens when you are in "Create client task" wizard and try to switch type of the task (combo box with type of tasks)? Solution in this case is to avoid this kind of switching, i.e. either start generic client task wizard and select proper task type or use flow which preselects proper task type from the start.
Hi @MartinK
I can confirm this, thank you.
Zen11t
-
Hello Guys,
I have one question:
v10 will not support Windows 7 (https://help.eset.com/ees/10/en-US/sysreq.html) so it not will try to auto-update to v10, does it?
Or I have to disable auto-update feature?
Thank you.
-
Thanks @Marcos, send in PM, because bigger than 100 MB.
-
Do I think right that all endpoints should have been updated by now? Auto updates started 1 month ago.
I have some 8.1.2037.9 clients which not updating with manual Check For updates button neither.
I enabled advanced logging, and will send to Peter.
-
Thank you the info @Marcos
-
Any news about uPCU to v9 update?
-
Yes, the agent is upgraded to v8, but with a big upgrade (250+ client) I don't want to check every PC it was successfully or not.
-
Any news about it? Will be fixed?
-
For me it's Programfájlok (x86) and ProgramData, but Antivirus is installed to Program Files directory.
-
I tested it now with another PC:
upgraded Endpoint 7 to v8, reboot and send agent upgrade task. It's show task failed message too, but the new V8 agent installed and working good on the machine.
trace.log show the same line.
-
After upgraded to ESET Protect I made Agent upgrade task to 3 test PC (Win 7 32 bit, Win 10 64 bit), task finished with error but Agent upgraded on the machines successfully.
trace.log last line show:
ReadUpgradeStatus: Upgrade of Agent from version '7.2.1266.0' to '8.0.1238.0' failed. Unexpected updater service Win32ExitCode 0x42b
-
Hi!
I want to join to beta too. Thank you.
Zen11t
-
Thank you, I found this option but 2 problems with it:
- I can not see when last connected the client, so the agent version is old because update task has not run yet, or because its stucked old version.
- I can not order the list by computer name, so I have to look through the whole list. (OK, in CSV I can order it )
-
Hello!
I made an upgrade agent task to version 7.2.1266, but found a client, where task finished successfully, no error but the agent did not upgraded, stuck version 7.1.717. Not a big problem, because I deleted it manually, and installed the new version, but it would be great to see the agent version in computers table.
-
-
I don't want upgrade client one by one, so made a client task to computer lab group (it's a school), but next day when students turn on computers, and upgrade finished they will see this window. I just don't want annoy them with it, if restart immediately not so necessary.
It will be good, if we can disable/enable this notification in ESMC.
Thanks,
Zen11t
ui: do I write it as a function request?
-
I upgraded EES on clients to the latest 7.1 version with client task, is there any way to disable computer restart recommended window after upgrade?
-
On 4/12/2019 at 11:32 PM, MichalJ said:
Yes, this mean that clients starting with latest version of 7.0 will be automatically updated to 7.1 once the micro PCU is enabled on our servers and in the Endpoint settings. Previously the functionality was ready, but was not enabled due to it´s behavior, where the "reported version" was not changed in ESMC, even when the client was updated over micro PCU. This is now changed and we will be enabling it soon.
When PCU will be enabled on ESET servers?
-
Hi @Haresh2015!
Try this:
https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows
Select your OS, install the update and then try again install ESMC.
Regards,
Zen11t
-
I use this standalone internet browser: https://www.avast.com/secure-browser#!
https://en.m.wikipedia.org/wiki/Avast_Secure_Browser
I am talking about this, not Banking protection.
News unavailable
in ESET PROTECT On-prem (Remote Management)
Posted
ESET PROTECT (Server), Version 10.1 (10.1.2267.0)
ESET PROTECT (Web Console), Version 10.1 (10.1.274.0)
From the VA I can download the xml with wget.