Jump to content

Unigarant Verzekeringen

Members
  • Posts

    3
  • Joined

  • Last visited

About Unigarant Verzekeringen

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Netherlands
  1. First I have to thank you for listening and reading our posts here regarding v6. Second, my two companies that have together 100 clients have extended licenses for one more year since we are very happy with v5 product we are monitoring v6 development and have postponed decision for antivirus switch on to next year. The main reason we don't need product like v6 is usability on administration side. For example, yesterday you had problem with your antivirus definition database. With the blazing speed I was able to see that version is 13102 on my ERA v5 server and that clients most probably have this version since they don't have any other way to download definition update other than mirror. This is very important to us, because with your v6 solution you force us to use third party product that only routes clients to your servers and I have no easy way to see which version is current. I say no easy way because you force us to use HTML interface to customize this interface in very strange way. In v5 I only had to click Tools - Server Options... - Updates and BANG! all information is in single location. Having console information with all clients listed in first plan and with single click of mouse to open Threat log and see what is threat on clients (that self updates, no HTML refresh!) is something your team should have foreseen even for "next gen" product. Having control of update on single point like mirror is mayor thing for us. You helped with mirror tool for v6 but this is not as easy as v5 was. With selecting all my clients and with few clicks (in responsive console interface) I was able to push new database to clients in few seconds. I was very confident in my actions knowing that all my clients will get database from ERA server and all almost at same time. With v6 you force everything with so many clicks and page refresh. This is in moment of panic like yesterday frustrating. And I wonder did I click that HTML button did it send HTTP POST to ERA... What about situations where I am unable to connect to ERA web interface? Don't you think there should be some alternative? Do you really think sys admins love administration tools in HTML? We do, but when we monitor things that are not critical, like I do with Unifi wifi controller. But when things get complicated we need robust tools like console management. If there is no plan to change this, and as you say there is none I expect that you at least return mirror feature within interface. Do you think that would be possible? Thanks again for reading! Regards. bbahesWe are an insurance company and thus have to comply with a lot of policies. Which means none of our machines have direct internet access. It took some effort, but everything accept for the agent deployment, is done "offline" in our company. We have all of our 150+ servers and 400+ workstations available in one view. Rolling back the definitions yesterday took te exact same amount of time on ERA6 and ERA5: less than 2 minutes for all clients to revert (we use both, migrating now). Just saying: it is possible not to route it through ESET and have the same amount of control you have in v5. We use an update proxy (mirror) and the shared local cache. There is only one machine in our network that is allowed to get updates directly from the internet. That beïng said: it takes much more effort to setup initialy than v5 which just works. (The agent we still download from the internet, simply did not get an offline install to work...). If you need help setting up a local mirror you may send me a pm, should not be a problem. The webinterface is better in 6.3, and I can understand why they chose a webinterface. Resellers of ESET are able to manage multiple installations. However: they certainly did not think this through. They should have known a lot of clients want the same kind of install as with 5: single mirror for all the clients. I think they are listening though
  2. First of all: good to see replies by ESET staff in this thread. It tells me you are now indeed listening to customers' feedback. We are now using version 6.3 of ERA and we are still having some issues. Some of them (reset cloned agents) we have already escalated through ESET Netherlands. Since version 6.3 we have seen big improvements, specifically for tasks. However, I do hope that the agent/av itself receive some love as well: in all the years we have been using ESET we hever had any problems with installing clients. Untill version 6.2 of the clients and agents: msi installer failures over and over on all of our machines. It has been fixed in 6.3, but still... I hope you can reply to our no-go and other issues: 1: No-go for deployment on all our vdi's: reset cloned agent. We deploy a new machine for everyone that logs on to our enviroment. After the log off the machine is immediatly deleted. With the current setup we are not able to reset the agents of cloned machines during boot or when entering the domain. This means we have lots of machines using the same agent id. Resetting the agents every minute is not an option as you can imagine. This need to be fixed before we can deploy version 6 to our vdi enviroment. I know we might be a bit ahead of a lot of companies in this area, we are very willing to help ESET fix this issue (testing, thoughts, etc.). If you would like our help on this please let us know! 2: Annoying: no synced active directory groups. We, as do many other companies, have setup AD groups for particular workstations/servers. Either for testing, rolling out software, etc. ERA6 does NOTHING with these groups. It only uses OU's. I mean: you are not going to put a machine in a different OU to roll out some software or test something. Dynamic groups mostly don't cover the needs, which means a lot of manual work or workarounds 3: Annoying: not working dynamic group templates. This is probably also due to lack of documentation. It is not always clear what syntax to use in particular dynamic group triggers. Some examples might be nice. Also just document where it will check for particular info. For example: I want to create a trigger for a machine that has some software installed. Where does it look for the exact name of this software? WMI query? I have one job that should check for "ESET File Security" that simply does nothing whilst the EXACT SAME job that checks for "Remote Administrator Agent" works absolutely fine and shows all the machines. After having 3 colleague's look at it we concluded it is a bug and gave up... All things considered we still like ESET (even with the bad definition update yesterday...) but it would have saved us at least 80 ours of work if we had just upgraded our v5 license and installed v5 on all of our servers. I am glad to see it is going in the right direction, but still a bit dissapointed about how it started off.
  3. Hello Jim, I am not sure why this works for you, but for us id did not. I have edited the command to be as follows, after which it works: msiexec /qr /i "hxxp://repository.es.../Agent_x64.msi"ALLUSERS=1 /norestart P_CONNECTION_CHOSEN=Host P_HOSTNAME=Our.FQDN P_PORT=OurPort Just the REBOOT=Reallysuppress has been replaced by /norestart. I think the first is meant to be used in the config of the .msi file itself? Also I am not giving a portnumber, just the fqdn. Thank you for the help! @ ESET: upgrading this via the remote administrator components upgrade tasks fails for me with a 1603: fatal error during installation. Also it is very messy since it tries to update components that are not installed. Not very clean and I would not recommend it!
×
×
  • Create New...