update is still same like ADNM from add and remove program I guess, but there is problem when doing the wizard for upgrade.
here I attach the message
I just ignored the message and select No, the installation goes normal, AEA and EAS running well after upgrade, and new client deploy was update and running well also.
Upgrade the endpoint from AEA with push upgrade was successfully but the endpoint program wasn’t upgraded only the VPS update was successful.
Mostly complaining from customers (they are really need this feature) are using AEA is why the Client can do the uninstall and no password protect the uninstall like ADNM, and for me this not a minor issue but major issue. For the administrator mean they not have any power to protect the client to do uninstall the avast! Enpoint application.
@MarkVi why can we still not choose ourself where we want the mirror to put the mirror files? This is an Enterprise product, not a home product. In SBC this option was finally, after a nice discussion, build in and now its ripped out again… (technically it never was in this console product since its the revamped version of ADNM)
This really is non-compliant with IT policies in companies that state that USER data is not supposed to the placed on the Windows installation partition and program data is supposed to be in the program files directory. Disk mirrors are part of this equation too!
@MarkVi, any future request allow? please suggestion to put the password protection on the Endpoint when the user want to remove the avast endpoint from the user computer. Like WPN said unprotected application was also not compliant in corporate and Enterprise company.
I just ran the latest SOA (Small Office Administration console) update and it failed. Although, it said no changes had been made to my system.
Unfortunately, it has completely removed my existing SOA console. So, I currently have nothing on my server. I will have to reinstall the previous version and hope that the data is still there.
Not impressed.
Update: I can confirm that the entire installation folder (including the SQL information) has been removed as a result of this bug fix update. I did run the backup routine from within the console (before running the update), but I suspect the backup information was stored within the same folder (and is also gone).
Well, the second time I ran the upgrade it worked!
I’m not sure what went wrong on the first attempt. However, the SOA was no longer listed within Add / Remove Programs (Windows Server 2003), so I was worried that I had also lost the database AND the backup.
When I ran the upgrade again (using the custom option), it found the original database (db.sdf) and then completed without error. I can confirm that all the existing workstations / servers connected to the console.
Do you still want me to send the troubleshooting package, as everything now seems to be ok?
yes please, if you could send me the troubleshooting package, we would try to figure out what was wrong during the previous installation. There may be still some logs from the previous run in the package.
