Jump to content

lleysan

Members
  • Posts

    10
  • Joined

  • Last visited

About lleysan

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Belarus
  1. Hello everyone! Really nobody knows how to implement it?
  2. The main idea behind this implementation is the requirement to clear policies before deleting a device. According to the steps: 1. Reset Endpoint settings 2. Stop computer management 3. Remove computer from database Therefore, to implement the first point, I would like to come up with some kind of container where I would move computers before deleting them. The fact is that the second step is not performed for me, if I do not take the first one, the task hangs endlessly in work and does nothing. I tried to ignore the first two steps and go straight to the third one, but then the next time the device is connected to the network, it again appears in my console as a new but not activated device. Maybe if the options are how to perform the first step in a different way?
  3. Hello everyone! I ran into the problem of missing exceptions or filters to create exceptions. Maybe there is a solution, let me know please. Problem: There is a dynamic group that, when a computer enters there, applies a number of policies to the object. There is a static group to which I want the PC to be removed from the dynamic group and thus the policies set for the dynamic group are not applied to it, but those that are set for the static group are applied. I did not find an option to set the filter for a dynamic group to exclude if the object is in a static group. Also, I did not find any options for setting policy enforcement exceptions. Are there any options how to implement this? I found only an option with duplication of all policies and forced application of parameters, but this is not an option. I then need to duplicate both the policies themselves and then making any change to duplicate each setting.
  4. If you are talking about those companies that do not know who the DevOps is, then yes, you are right. And so current trends show just a fairly confident transition to Linux solutions both in the server part and in terms of user OS. As you can see, this chart is for 2019, and we will soon move on to 2023, this information is, to put it mildly, irrelevant. I won’t say that Windows fades into the background, but if there is a choice, users use more for MAC, and system administrators and other people who are closely familiar with technology and support their ecosystems calmly use various Linux solutions. Since the trend to save money is more relevant than ever these days.
  5. Hello! Yes I also create such trigger with message, but it is temporary solution.
  6. Hi guys! It is a good question! I have the same issue. I have ubuntu server and tomcat 9.31, but Eset Protect indicate that it is not a good version... but this is the latest version that supported ubunty server... Another story with Java... I installed 17, but the system indicate 11.... Outdated Server Components Third-party components used by the ESET PROTECT Server are outdated and should be updated as soon as possible. Web serverApache Tomcat/9.0.31 (Ubuntu) Java Runtime Environment (JRE)11.0.16
  7. Thanks! But if this process is completely automated and takes a month or more, why change the status in the administrator console that the product is outdated and an update is needed? It sounds illogical, but thanks, I will mean that the product is now updating itself. Could you tell me where I can create a support ticket? My local support is not able to solve the problem, and I don’t really want to wait months until they pass it on to the developers or someone even more competent.
  8. I have: ESET PROTECT (Server), Version 9.1 (9.1.2301.0) and ESET PROTECT (Web Console), Version 9.1 (9.1.292.0) And have special task for the update clients to the latest version of EEA. Now the task of updating the version contains the condition of compatibility with the version of the server (not the specific version of the antivirus). As a result, the task is triggered but the update does not occur on the client, although the task was completed successfully. At the same time, manually starting the task also does not lead to a result, and if you start a manual update by selecting a client, then everything works. How to fix the problem? All clients have version 2046 and task triggered twice or more but no results.... A didn't find any other options for update product, only one option acceptable from the Eset Protect tasks.
  9. I started update my clients to the 2057 with the delayed restart. But when client click "remind me later" the message no longer appears and as a result the system reboots without warning. Why doesn't the message appear until reboot? After testing, it became clear that the message can only be received by opening the antivirus menu, in any other case, the timer runs in the background and the user forgets about it, and rebooting the system is a shock for the user.
  10. It is impossible... Ubuntu already sent to users suggestion to update to Ubuntu 22.04.1 LTS.... When you guys provide us support to this version? I paid for the crossplatform antivirus system, but now I need to think what to buy next time, because I have a lot of ubuntu workstations...
×
×
  • Create New...