Jump to content

mxp

Members
  • Posts

    36
  • Joined

Everything posted by mxp

  1. Nonetheless, there is an issue with updating the jp_JP Version. I can't update because the referred repository is not available.
  2. If this happens to you again in the future, a re-installation of the Management Agent on your Appliance does the trick pretty reliably: https://help.eset.com/esmc_install/70/en-US/component_installation_agent_linux.html#:~:text=Installation of the ESET Management,Possible connection formats.
  3. Ah, now I understand your issue. As I mentioned in my post above. You could use the .MSI Installer and let a GPO handle the installing.
  4. https://help.eset.com/esmc_smb/70/en-US/deployment_tool.html Are we talking about the same deployment tool? ESET Remote Deployment Tool works only with all-in-one Installers created in ESMC. If you have a functioning ESMC in place, why don't you use the client-task designed to do exactly what you're trying to do. What you could do, if you do not want any ESET Management Agents installed with your security product, you could install ESET Endpoints via GPO. That would work, but I don't understand why you want to do this. If there's no management agent installed, you won't be able to include them in your ESMC.
  5. Is there a particular reason why you do not want to use the tools given by the ESMC? If I understand you correctly, you have >2500 Clients in your console, across multiple networks I guess? ESET Remote Deployment works by sitting on a server (or any other client which reaches all the devices) and deploying the installer and the associated commands over your network. So when you're working for multiple clients, you have to manually connect to their networks and use ESET Remote Deployment from one of their devices. Why have a Remote Management solution in place, and then not use it? It would be way easier to just use the client task "install software", which you can use from the comfort of your ESMC without having to manually connect to all of your clients networks. If you have a single network with over 2500 clients, I would still use the client-task in ESMC. Using the ESET Remote Deployment Tool for this one would kill your network with all the traffic caused by pushing the installer files to all the devices. You would have to do it in batches of a few devices at a time. tl;dr Use the client task in ESMC, it's easier, faster and more reliable
  6. nothing so far, german support seems to be not receiving my support requests and as far as my licenses for our customers go, nothing has changed by now as well. it's now updating the license unit quantity for over 7 days
  7. ...and I'm facing the same issue again. I updated the license unit quantity of a license yesterday before lunch and wanted to add another seat to it today. Updating license unit quantity for about 23 hours now.
  8. I can't confirm this. I installed the update yesterday on one of my computers for testing. Only thing configured in the used policy is RDP. Device control is deactivated and I still got the red alert stating a reboot is needed.
  9. You did not misstate, nobody knows what you are talking about or are referring to. What product are you referring to? What exactly is your problem/ question?
  10. Greetings, this is the notification that I get after I login to msp.eset.com I see that it's written that this may take a while, but 5+ hours?
  11. Greetings, i tried to update the Management Components via the ESMC and now the esmc won't connect to itself as it seems i can still access the web interface and the console of the appliance itself. but it looks like the Management Agent won't connect(?) to itself correctly? everything else works completely fine, it's just that ESMC itself that seems to have problem.
  12. @larzillo have you opened the ports needed to access the esmc? Port 2222 is needed for the Management Agents to communicate with the esmc Port 443 is needed to access the web-interface of the ESMC
  13. As you see, the URL that was tried is blocked by ESET's internal blacklist. Without researching the link, i'd say that it will have it's reasons to why it's blocked by ESET. If this is an URL your users need to get access to, you can manually set the policy to allow connections to that specific URL. The event gets logged as "unresolved" as you as the admin haven't checked the problem yet. Basically ESETs way of saying "Hey, we did something for you, maybe you wanna have a look on it real quick?" You should be fine, nothing to worry about here.
  14. Thanks for the answers, but still I can't understand why I get limited in the special characters that i use at all. Seems kind of counter-intuitive to me. Doesn't this make the password less secure as an attacker now knows which special charactere he doesn't even have to try?
  15. I know this sounds ridicolous, but it really stresses me out and annoys me: I just got an email notification that our Account has been successfully moved over from the EMA to the new EMA2 and I went on to change my password. Can anyone explain me, why I'm suddenly limited to dots, commas and exclamation marks? i just don't get my head around why I get limited in how I create my password for a security centric portal.
  16. greetings, is it possible to filter for the last time an agent connected with the ESMC? i'm trying to find out, why some machines do not follow their respective policy and don't do their weekly scans. it is a tedious work to search through the list this graph from the dashboard spits out when you click on "more details" after right clicking one of the bars.
  17. In order to update the Management Agent on Client-machines you have to use a different task listed under "ESET Security Management Center > Upgrade Security Management Server Components"
  18. sounds very much like a malfunctioning hardware. have you tried using a different mouse already?
  19. greetings, i'm trying to set up a dynamic group which purpose it would be to trigger a scan, if the device hasn't been scanned in x days. is there a way to set this up? I've gone through all the possible dynamic group-templates, but i couldn't find a way to implement this. am i missing something?
  20. Try using an older version of your product. I just encountered the same error and after going through some log files, I came across one particular line that stated that the used version is not compatible with the operating system that's in use. Also was OS Win7 SP1
  21. The policy was set to replace both policies and clients' settings. Well but that was the only thing it did. Mails coming from domains being on the exception list got marked as spam. As I was already able to fix this problem by overwriting the exception list with another policy, I'd rather not play with those settings again and getting those messages would definitely cause user interference which is not desired. As I understand this as a bug, is there any place to report this?
  22. Update: I created a new policy, where I've put a non-existing mail address in the global exception list, set it on "Force" and applied it to the PC. After the policy got applied, i checked the configuration again and this time only the fake address is listed, effectively flushing the other addresses out of the exception list. Even though I could work around the issue, this behaviour isn't normal, or is it?
  23. Greetings fellow ESET enthusiasts, I'm currently confronted with a problem with the global exception list inside ESET Endpoint Security for a Client-PC. I wrongfully added a few mail addresses to the Global Exception List and logically so, all mails send from those addresses get marked as spam. I changed the policy accordingly and removed those addresses from the list. This worked for all PCs in the client's network except for one machine. From what information I get from the ESMC, the policy get's used, but if I have a look at the Configuration i can still see those addresses in the exception list. So it seems like the exception list does not get flushed correctly after applying changes to it. I already tried to "force" the corrected policy but this doesn't change anything. I'll have another look on it later, but it seems like I have to connect to the machine and empty the global exception list by hand. Has anyone else encountered such a problem before, or am I just missing something here?
×
×
  • Create New...