Jump to content

jwilkins@adamsaai.com

Members
  • Posts

    2
  • Joined

  • Last visited

About jwilkins@adamsaai.com

  • Rank
    Newbie
    Newbie

Profile Information

  • Gender
    Not Telling
  • Location
    USA
  1. I am having the same issue. Here is what im trying to do: Ultimately i want to automate the upgrade of existing agents (and endpoints) once I install and test said upgrades. This is what i have done so far: 1. I have created a dynamic group template to search for a specific ERA Agent. 2. Attached the group to a parent test group which my test client is in. 3. Setup the trigger to run when the client joins the dynamic group. The command i have running is this: msiexec /qr /i "hxxp://repository.eset.com/v1/com/eset/apps/business/era/agent/v6/6.4.283.0/Agent_x64.msi"ALLUSERS=1 REBOOT=ReallySuppress P_CONNECTION_CHOSEN=Host P_HOSTNAME=<omited for security> P_PORT=<omited for security> Please let me know what i can do to resolve this.
  2. I am fairly new to administering the product (about a 1.5 years now.) I have to agree that ERA 5 was much easier to use. I have no doubt after digging into v6 that it has some advantages over v5, but ihavent decided if they are worth it. I have a small test group in production. If i cant get past some of the issues i am having i will revert back to v5. I reached out to ESET support via the website email form, and heard crickets (correction, i went back and looked, they replied with a posting to the forum that addresses the issue, which i had already read). Eventually I stumbled through enough forum posts and google searches to solve most of my problems on my own. From an administrative standpoint its taking me more time to setup ERAv6 than it did v5. Perhaps i should have gone to another product if i had to start from scratch. If it wasnt for the fact that i wanted to use the newer AV client i would not have migrated to v6 at all. p.s. i volunteered in the testing for ERA6 and I hated it then as I do now, I communicated this to your dev time. I feel like you lose simiplicity when going to a web based app vs. the fat version, everything feels like it takes more steps. I like the reporting features from the dashboard of the web but thats it (you can keep that). My opinion, scrap web version ERAv6 and give us back a fat console. Don't mean to step on any hearts, im sure your dev team is proud of the product. Maybe i am just old school and like the a a traditional program vs web version. Don't just take my word, do a unbias survey or something. Listen to your customers. As far as your move to a web admin console your not alone, lots of companies are moving toward web based management consoles (i hate most of them), even cisco has versions of it. In some cases thats all you get, in some cases the web version is suplemental. Give us both if you love your web version so much. Thanks for reading my rant.
×
×
  • Create New...