Jump to content

Recommended Posts

Posted

I've been forced by Eset to migrate the virtual appliance (centos). This is something in years of ownership I've not been required to do before..

The push to the cloud solution is pervasive, the nomenclature is misleading. it took 3 attempts at reading guides, not understanding the nomenclature to find out what was required or the problem was.

I now know that the upgrade involves me creating a new virtual machine, the instructions are spartan and not thorough. They tell me to make a new machine and spec the gen and ram but they don’t tell you to use the provided VHDX… I guess obvious but these are instructions not vague guides. Their support said they expected users to be familiar with hyperV! I thought I was going crazy, missing a step!

Got a new problem, can’t log in to new VM, can’t find the answer, ask again tech support… article, great… Article says what the issue is and how to fix, type in the instruction “blah blah blah”….

Where? How? Again No Details…just assumptions.

Terminal on the VM, nope, no option, SSH.. maybe but won’t accept credentials… reset credentials.. complexity not met?!?!! (fine) too short 18 or more chars….FFFS.. fine.. (existing creds just created 30 minutes ago didn’t meet these either but FML I guess.)

Finally login as Admin… you need to be root to make these changes…… buttt clench. Root access denied.. access denied…. FFS.. more reading “root can’t use SSH” FFSS SFGSFS.

This is why FULL instructions are needed! I hate ESET! I’m not renewing, this blows.

  • Thanks 1
Posted
We got rid. The locally hosted solution was a hot mess - not sure if that was the because of the configuration that was used (not by us) or it was just a janky product, but I happily moved to Defender a few years back.
Posted

I do feel you. Did mine earlier this summer (Linux appliance and VMWare here.) I hate VMWare a bit more but mine didn't go too badly. I remember there being a few odd bits in the instructions Linux-wise but I half know it of old so think I just worked around it.

 

Was still a 3/10 did not enjoy job. Also had I think the same thing with the admin not logging in and had to do "something" with the SHA-1 or SHA-256 setting somewhere.

 

I agree this was EXTREMELY poorly implemented, and I'm certain is motivated by an obsession to have everyone cloud-ify.

Posted

I'm really F upset "admin" and "administrator" are NOT the same account... a single admin has to use 4 FOUR sets or credentials to use the ESET product... this is fricking insane! root, user, admin, administrator.... I'm doing the SHA1 downgrade which IS a terminal action but terminal will freeze if you use the type from clipboard! (NICE)

 

Now the instructions are pointing me the use "server settings" it even has a picture....Do I have server settings of course NO! yay, another tech support loop! 6 months and this thing is DEAD.

Posted (edited)

Heavens this looks bad.

Thoughts and prayers and all that.

 

EDIT - also remembered I had clients duplicate themselves over and over and a load not check in. I had something in an agent connect policy left in place for the old appliance (I changed IPs for the new one.) Upcoming one to enjoy maybe!

Edited by JRA

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...