offbyone

Normally we use /qn, but to check if settings apply we use interactive mode. However possibly in silent mode settings will apply whereas they do not in interactive mode. I will give it a try and report back. Thanks again for your input.

Hello Martin. Thanks for you answer. The reason is that we heavily use automation for deploying solutions to our customers. And it would be nice if could also roll out ESET to our customers unattended. The properties you mentioned are the ones we also found from the MSI file. For testing we began with the first dialog page of the setup wizzard, which is "Participate in improvement program". The related property seems to be "P_ENABLE_TELEMETRY" however from our testing it seems that initializing it with "0" simply does not work, so we stopped testing. Maybe you have a hint how to disable "Participate in improvement program" in an unattended way? Cheers.

Is it possible to install esmc server component via script on Windows? I just took a look on the PROPERTIES of the MSI file but it seems that they cannot be passed via MST or command line. Thanks for any suggestions.

Routenverfolgung zu 91-228-167-25.ptr.eset.com [91.228.167.25] über maximal 30 Abschnitte: 1 <1 ms <1 ms <1 ms XXX.XXX.XXX.XXX 2 5 ms 4 ms 5 ms p3e9bf089.dip0.t-ipconnect.de [62.155.240.137] 3 12 ms 18 ms 12 ms pd9ef2ca2.dip0.t-ipconnect.de [217.239.44.162] 4 14 ms 14 ms 13 ms 80.157.201.198 5 14 ms 14 ms 14 ms be3187.ccr42.fra03.atlas.cogentco.com [130.117.1.118] 6 19 ms 18 ms 18 ms be2960.ccr22.muc03.atlas.cogentco.com [154.54.36.254] 7 25 ms 25 ms 25 ms be3462.ccr52.vie01.atlas.cogentco.com [154.54.59.181] 8 31 ms 27 ms 28 ms 149.6.174.42 9 26 ms 26 ms 26 ms 91-228-167-25.ptr.eset.com [91.228.167.25] Routenverfolgung zu 91-228-166-23.ptr.eset.com [91.228.166.23] über maximal 30 Abschnitte: 1 <1 ms <1 ms <1 ms XXX.XXX.XXX.XXX 2 18 ms 5 ms 4 ms p3e9bf089.dip0.t-ipconnect.de [62.155.240.137] 3 26 ms 26 ms 26 ms pd9ef2e3e.dip0.t-ipconnect.de [217.239.46.62] 4 26 ms 26 ms 26 ms 80.150.170.82 5 26 ms 25 ms 26 ms dupdevs-static-222.213-81-253.telecom.sk [213.81.253.222] 6 * * * Zeitüberschreitung der Anforderung. 7 * * * Zeitüberschreitung der Anforderung. 8 30 ms 31 ms 30 ms 91-228-166-23.ptr.eset.com [91.228.166.23] Access Provider is "Deutsche Telekom"

Same thing again today 91.228.167.25 -> slow 91.228.166.23 -> fast To circumvent the problem I set --repositoryServer to hxxp://91.228.166.23/v1 which seems to work.

OK thanks for clarification. So agents get updates from era6. May I suggest to update docs of mirror tool for clarification. It also should be pointed out that you have to insert the term "mirror" in the update URL after the server name although it is not part of the server's path to reach the appropriate directory. Seems that this is just a hint for the update client that target is a mirror and seems to get stripped off from the URL which is used to access the mirror path. Just my 2 cent.

Removed - Could not be verified by additional test.

But how would they find their updates in a disconnected environment then?

So now I know what to enter for Updates on ESMC and Endpoint Clients. But what to enter for Updates on Management Agent? Same URL as Endpoint Client? THX again.

THX again. BTW: Support seems to be quite convincing here.

Seems that I have another question. Is it correct that the product code for ESMC 7 is era6? I found this in an KB article for mirror tool. Just want to get sure that this is correct and not something that was not updated in the docs. THX.

Hi Marcos, THX for clarification.

Hi Marcos, thanks for the fast response. That's really strange. Two day ago when I was working with the ESMC Web Console, I got a message that I should close and restart it because an update was applied, otherwise parts of the GUI could be displayed incorrectly. Regards.

Hello. Is it possible to disable auto update of ESMC? Thank for your suggestions.

We are doing both. Currently we are trying to mirror repo. Downloading is done from 91.228.167.23 which worked fine for one msi file. Then for what I can see on the next msi it switched to 91.228.167.25 and stall again. Cheers.

It is even worse. Running the tool the first time runs without problem. Running it a second time is getting incredible slow (hangs)? To recover from it you have to reboot the machine.

We have a strange problem with mirror tool. Whenever a mirror task gets interrupted for whatever reason. Subsequent mirror tasks run incredible slow. This is absolutely reproducible. Only chance to recover from this is to reboot the computer. Is this a known problem and is there any workaround for that? THX for you help.

Maybe we can solve the problem by blocking it via firewall as it uses a dedicated port and host (have to see how to handle fallback via 443). Nevertheless we have additional customers where I know this will be getting discussed. From what I understand the ESET product is targeted also as an on premise product (you can choose). The problem is that there are customers which are explicity after an on premise solution and are very picky about connecting to cloud services. So far from what I understand all cloud features could be disabled (expect EPNS). Is that correct? If ESET want to address those customers also they really should make EPNS an optional feature.

There is a permanent connection held open to a host outside the corporate network from every client for triggering actions on that client. This is something not being tolerated and I really can understand that point of view. This is even more senseless if your clients are on the same network segment as ESMC server. This should be configurable similar to cloud based feature. It seems that customer will choose a different product for this reason. Cheers.

We are currently evaluating ESET and have the demand from one of our customers to disable Wakeup-Call (EPNS). We were not able to find something in the policies to disable this unwanted "feature". Did we overlook anything or what are the ways to disable it. For cloud based protection this is possible. Thanks for your help.

To answer my own question: Seems that the certificate file needs to be in DER and not PEM format. Working with DER seems to work as expected.

We are trying to import our CA certificate into ESMC 7.2.221.0 as described in the manual but it fails with the following escpetion: sk.eset.era.g2webconsole.server.modules.connection.rpc.RpcException: Creating certification authority failed. Check input parameters for invalid or reserved characters. Any idea how to solve this. We are currently evaluating ESET and without using our own certificates is mandatory for us. Thanks a lot for suggestions.