Jump to content

helis

Members
  • Content Count

    16
  • Joined

  • Last visited

Profile Information

  • Location
    Russia
  1. Ok, nevermind, I installed the agent and upgraded the server with the "Security management center components upgrade" ta, it completed successfully. But now I have server v 7.1 and web console v 7.0. I get this warning and I do indeed experience errors and unexpected behaviour. Mainly, this (this is on the "Threats" screen). Rebooting the system didn't help.
  2. Ah, looks like it's a misunderstanding on my part. I have to install the agent on the server with ESMC as well? That's pretty strange, if it's a necessary component, then why isn't it installed out of the box along with ESMC straight away? Oh well, ok. So, as soon as I install it, the notification should pop up? Anyway, how should I go about it, deploy the agent from the server onto itself? As for the agent communication problems, I'll figure this issue out after I've updated the server. Maybe it'll go away on its own after that.
  3. This manual https://help.eset.com/esmc_admin/70/en-US/update_product.html says I need to click the "Update product" button in the "Help" menu, but there's no such button there. I have So there should be an update available, right? Is there some other way to update the server? I've updated the client agents to the latest version and now they seem not to be working communicating with the server correctly. I'm having the same problem as here: httpsg://forum.eset.com/topic/21520-new-agent-does-not-work/ It's said I should update the server, so that's what I'm trying
  4. Hi, I'm trying to fetch static groups from AD, can't get it to work. I create a server task, put in the credentials but when trying to browse for the needed subtree (the "Browse" button in the "Distinguished name" input field) I get this error: Using ESMC on a Debian 9 server. Anybody could point me in the right direction? UPD Nevermind, I figured it out, needed to install the libsasl2-modules-gssapi-mit package.
  5. Okay, this is not getting less weird at all. I tried deploying the agent with Deployment tool to four machines, all in the domain. For the first two it worked, but for the second two it reported "Success" but looks like the installation was incomplete? The folder is there in "Program Files", but there's no entry in installed software list and the machines don't appear in the ERA. What does that mean?
  6. I did try to install the agent locally with the bat file, and yes it is installed just fine. The only issue is, it didn't want to install until I rebooted the target machine. I assume it has something to do with the previous failed deployment attempt? Anyway, how does this information help me? Meanwhile, I tried deploying the agent on another Win10 machine, with the same result as in the first post. All-in-one installer, deployed or no, isn't the best way in my case because quite a few machines in the network have old versions of AV software (Endpoint 5 or 6 or even Nod 32 in some ca
  7. Greetings. I have ESET Management Center and recently I've been trying to deploy the agent. It keeps failing and I can't figure out why. Let's say I just need to install it onto a single machine. I manually add it to the computer list. Then I create a server task "Agent deployment" and input all the credentials. The target machine is in a domain, so I use the recommended domain\user format for login (the user has domain administrator privileges). After running for some brief time, the task fails, the report shows error 22. The target machine is Win10 Pro, the server is Debian 9. The
  8. One would think it's pretty basic stuff, but I can't get it right. So, I have a computer with an IP address of 10.X.Y.Z and mask 24. I've tried templates "IP subnet is equal to 10.X.Y.0" and "IP address is greater than 10.X.Y.1 AND IP address is less than 10.X.Y.254". I assume the computer should automatically fall into the group, right? Yet it doesn't. I don't understand.
  9. I see, gonna try doing that tomorrow. Thank you!
  10. Ahhh, I think I finally get it. Instead of making settings on individual clients, I should create individual policies which would contain only this specific setting overriding that of the main policy. Is this how it's supposed to be done?
  11. Yes, I got that, but I need the rules to be editable on clients, so what do I do then? PS Sorry for the mess with the links, I was editing that out, but you've replied already, so there's no point I guess.
  12. Thank you for your reply, Marcos, but as I said, what you're suggesting doesn't work either. I'll just illustrate what I'm doing: 1. Before I do anything: hxxp://puu.sh/E8f9v/594d86f669.png 2. After I click "Edit": hxxp://puu.sh/E8fcG/52cfbdde72.png 3. I add a rule hxxp://puu.sh/E8fdi/28a413cbf1.png hxxp://puu.sh/E8fdw/891ddd384a.png 4. I click "Save". Voila, the rules are not editable on clients hxxp://puu.sh/E8fe3/f7408cc858.png 5. I click the icon you've marked as "2" hxxp://puu.sh/E8ff3/ea3b2bc041.png 6. And then "OK" in the warni
  13. I'm trying to create a device control policy that is as follows: 1. All usb storage devices are blocked by default on the clients. 2. On some individual clients some particular usb storage devices (specified by their serial numbers) are allowed either for read-only or for full access. 3. On some individual clients all usb storage devices are allowed for full access. When I tried doing it on a local machine with Endpoint 7 installed, I created multiple rules: one that blocks all usb storage devices and several others that allow certain devices. I placed the blocking
  14. Nevermind, fell back to older MySQL and ODBC and installed fine.
  15. Hi. I've been trying to install ESET Security Management Center Server Installer (version: 7.0.471.0) on a Debian server and ran into something I can't quite figure out. The command is (passwords and IPs omitted) ./server-linux-x86_64.sh --skip-license --db-driver="MySQL ODBC 8.0 Driver" --db-hostname=127.0.0.1 --db-port=3306 --db-admin-username=root --db-admin-password=*** --server-root-password=*** --db-user-username=nod32 --db-user-password=*** --cert-hostname=*** --disable-imp-program --locale=ru-RU The output: ESET Security Management Center Server Installer (vers
×
×
  • Create New...