natem50

We're using ERA 6. We have 6.1.2227.0 clients advising that new version 6.2.2021.0 is available. When we push out a software install and select the new version, the upgrade actually comes from ESET's public servers and not from our ERA server. We did not see this behavior when we rolled out the 6.1.2227.0 clients. Are there software files we need to install on the ERA server or is this expected behavior?

We've recently migrated from ERA 5.x to ERA 6.x.

We are trying to architect an ERA plan that will take into account laptop devices that are often not on our corporate network for long periods of time. We can always tell the local client to communicate directly with the ESET servers, but we also want the client to communicate with our ERA environment for auditing and tracking purposes. Is there a recommended design or plan that ESET has to allow for this? My first thought is to put an ERA proxy on our DMZ that will communicate with our ERA server. I would like to get other opinions and hear what others are doing for scenarios like this. Thanks in advance.

We are attempting to install the MDM on a cloud service VM so our mobile devices can check in regardless of what network they are on. We are treating the installation like a DMZ install and want to lock down the ports as much as possible. I have the list of ports that need to be opened for MDM (9980 and 9981), but is that all that needs to be opened up to the public facing side? What ports then need to be opened to the internal facing ERA server?