Jump to content

Ufoto

Members
  • Posts

    44
  • Joined

  • Last visited

Everything posted by Ufoto

  1. Hello, This is just something I needed at the moment because it is very useful information for a person administrating the devices. Now I suppose I will have to create two separate reports - system name/last communication, and another one system name/logged on user. This isn't such a big issue, but it brings out another problem I have with the ESMC reporting - why scheduled reports can't be combined into a single file? For example, I am often interested in more than one set of data, but with the existing reporting, if I want to check different types of reports, the ESMC is only capable of sending them as separate attachments. So for example if I am interested in 10 different reports, I will have to review 10 attachments one by one. Isn't it possible for the ESMC to combine these reports into a single pdf file? The order of the reports in the file can be the same as configured in the task. If there is product idea forum, is this worth raising, or are the product limitations not allowing this at all?
  2. Hello, I am trying to create a very simple report - a table which shows the system name, last connection and logged on user. However every time I add the last connected column, logged on user disappears as possible selection for a new column and vice versa. Is this some sort of limitation? Is there a way to avoid it and create such report? Thank you in advance!
  3. Hello JPritchard, Thank you for the detailed explanation. I understand how the communication works now. Is there any limitations for systems which are only able to connect to the EEE server via the 'cloud proxy' in terms of policies, licensing and user enrollment? I am asking because while reading through the guide I noted the following section: https://help.eset.com/eees/en-US/system_requirements.html?enable-esdirect.html. According to the message on the screenshot, self-enrolment requires clients to communicate directly with the EEE server. Regarding the remote deployment, indeed I might have read about the 'ESET Full Disk Encryption' product which is managed directly by ESMC. It would have been very convenient to be able to deploy the EEE client as well, and somehow pointing it to your own EEE server - either with a configuration in the client task itself, or via policy. Thank you in advance!
  4. Hello Michal, Thank you for the prompt response. Yes, I am referring to ESET Endpoint Encryption. As far as I understand it uses an ESET proxy, therefore no proxy is required on our end, Roaming clients should be able to communicate with our internal EEE server via the ESET proxy? And just one more question, if we use our existing ESMC server to deploy the EEE client, how are we going to point the installed EEE client to our EEE server? Thank you in advance!
  5. Hello, We have an ESMC server in our internal network which uses a HTTP proxy located in DMZ to manage roaming users. We would like to implement ESET Endpoint Encryption in our environment and the question which immediately popped up is: are we able to manage the roaming encryption clients through the same HTTP proxy? I didn't find any official statement about this setup and I am hoping you guys could shed some light? These users never connect to our internal network so this is very important for us.
  6. Hello, I am preparing a deployment for a number of Unbuntu desktops, however looking at the available software I am confused which one to use. Unbuntu is listed as OS for both ESET File Security (although it says Server Security) and ESET Endpoint Antivirus. From your experience, since the machines are not servers, should I go with Endpoint Antivirus? Is there any difference in the products functionalities? Thank you in advance!
  7. Hello, Where I can find release notes/change log for Endpoint Security 8 and ESMC 8?
  8. Hello Martin, We were migrating the systems to a new ESMC which is reachable only through proxy. The policy with the new ESMC address, proxy settings and new agent certificate was assigned at the 'All' group, however further down the group structure there were couple of groups where a custom agent policy was assigned (with no proxy configuration) and both policies got merged together which seems to have resulted into a mixture of settings for both the old and the new ESMC server. On a side note, is there a way to disable policy merging and just apply the policy with most specific assignment and ignore all others? I tried running a new agent installer, but it fails to install as the agent already present on the device is on the same version. How do I access this 'repair' mode as I didn't see such option? Thank you in advance!
  9. Hello, Is there a way to revert a incorrect proxy configuration send to endpoints? During proxy configuration the new policy got merged with an old one configured lower in the group structure and a number of endpoints ended up having a mix of wrong certificate and proxy address which as a result stopped their communication with ESMC. Now we can't push a new policy because these systems are no longer communicating. Is there a way to fix this other than manually uninstalling the old agent locally on each device, and installing a new one with the correct configuration? Is there a config file that can be replaced, or amended in order to restore communication? Thank you in advance!
  10. Hello, Apologies if someone asked about this already, but I couldn't find a reliable source of information. Is upgrading from Endpoint Antivirus to Endpoint Security supported, and is there an official article about the process? For example if I have 200 systems managed by ESMC and using the latest Endpoint Antivirus version, can I easily upgrade them to Endpoint Security? Is it simply a matter of pushing the Endpoint Security installer on top of the already installed Endpoint Antivirus? Thank you in advance!
  11. Hello, We are about to migrate a number of systems from an existing ESMC server to a new one. I already added the license to the new server and I can see that all seats are in use as I would expect. I will migrate the devices via policy change in order to point the agents to the new one. My questions is, when the systems start to appear on the new server, do I have to do anything in term of licensing? Does the same license transfer with the system or do I need to delete the systems from the old console removing the license and then re-license them from the new server? Thank you in advance!
  12. Hello Martin, Thank you for your prompt response. Indeed the reports seem to be objects which inherit everything as I was duplicating reports until now and only changing their access group. When I created a brand new report as administrator into the respective restricted access group, the user was then able to see it. Although not perfect, I believe I can work with that. While I was testing this I discovered that for reports which I want duplicated (in order to avoid creating them manually for every new user/access group), I can simply export them, log in with a test user which shares the same permission set as my restricted accounts and import them. Once imported as user sharing the same permission set, even duplicate default reports work and show correct data. Thank you for pushing me in the direction
  13. Hello, I am using ESMC 7.2 and I am trying to create a permission set which should be used to restrict user access only to a single static group. Everything seems to be working as expected, except reports. I am selecting the static group X as home group for a test user, and I am setting the same group as 'Static Group' during the Permission set creation. As for active permissions I allowed read/use for Groups & Computers and read/use/write for Reports & Dashboards and Server Tasks & Triggers -> Generate report. With the configuration above, I would expect that the user should see all reports (data inside limited to static group X). However, the user doesn't see any reports. I created new reports with filters restricting results only to static group X, but the user is not seeing even these ones. The only way for the user to use reports is either to create them all on his own, or import them. Am I missing something? Is there a way how I as an ESMC administrator can give access to particular reports to users with restricted access? Thank you in advance!
  14. Hello, Could you share any release notes/change log for version 8? I was not able to find anything online. Thank you in advance!
  15. Just a quick update on this. Since you mentioned the Agent policy I did some testing and I understood what was wrong. The ERA proxy has to be added to the server list instead of the HTTP proxy section. Additionally, unlike the HTTP proxy, the ERA proxy actually needs a management agent installed in order to forward the communication. I implemented the changes above and the communication between systems on the old server and our new ESMC server started immediately. The component upgrade task also worked and the systems communicate with our HTTP proxy as soon as they are upgraded. Thank you for your prompt response, it guided me in the right direction.
  16. Hello Martin, Thank you for your response. Indeed we entered the ERA proxy details in the HTTP Proxy section of the Management Agent policy (ERA version Version 6.5 (6.5.522.0)). All sections there have a note that these settings are applicable only for 7+ agents which I would expect as only agent 7+ can use the HTTP proxy. Should we configure the ERA proxy somewhere else? Indeed upgrading the agent is also an option as we upgraded one device locally and it started communicating with the new server. However the component upgrade task requires an upgrade of the entire ERA infrastructure to version 7. I couldn't find an option to upgrade just the agent. Additionally, when I try to create an agent deployment task, there is no option to select a package. On the ERA console agent 6.5 is listed as latest and there are no updates available in order to upgrade it via client upgrade task. Yes, upgrading the entire infrastructure to ESMC is an option, but we really wanted to avoid possible upgrade complications as this old infrastructure will be decommissioned once the systems are migrated over.
  17. Hello, We are trying to migrate endpoints from a remote ERA server to our existing ESMC server which is in another geographical location. Since the endpoints can't communicate with the ESMC directly we've set up an HTTP proxy in DMZ. We've tested the proxy with some test devices and it is working. Now we want to start transferring devices from the old ERA server however we've encountered few issues along the way. Since the ERA server manages Agents 6.x they can't communicate with the HTTP proxy directly. In order to resolve this we've installed an ERA proxy on the same server where the HTTP proxy is installed. Our idea was to follow KB6729 in order to redirect endpoints from the existing ERA server to the new ESMC server via the ERA proxy. However this doesn't seem to work because the relevant policy setting are applicable only for version 7+ agents while the systems managed by the ERA server use agent 6.5. We are aware that we can uninstall the agent locally and install an agent from the new ESMC server and this will migrate the system, but this is not really applicable as we are talking about few hundred endpoints and we don't have the resource to do it manually. We are really lost at this point and I am seeking advice what's the best approach to handle this migration? Thank you in advance!
  18. Hello, I ran the "security management center components upgrade task" task against the ESMC server and it completed successfully. However when I go to the 'About' section I can still see that the server is on version 7.1.717 while I would expect it to be on 7.1.27 as this is the latest version. Could you point us to the log files we can check about the outcome of this task?
×
×
  • Create New...