Author Topic: upgrade adnm 4.8 client to v6 SBC client  (Read 4024 times)

0 Members and 1 Guest are viewing this topic.

wpn

  • Guest
upgrade adnm 4.8 client to v6 SBC client
« on: August 04, 2011, 11:27:59 AM »
I used a client to test deploy the v6 client to. On this client there was the 4.8 managed client installed.

The deployment went successful. No problems there.

Then i went checking the program files directory.
As expected there was the avast installation of the new v6 client. BUT i also saw the old directory of the Avast4 installation.

This is pollution, can the upgrade installer completely remove the directory please or get a message to the business console that upgrade succeeded but there is leftovers that need to be removed?

Offline avadas.de

  • Avast Reseller
  • Sr. Member
  • *
  • Posts: 259
    • avadas.de
Re: upgrade adnm 4.8 client to v6 SBC client
« Reply #1 on: August 04, 2011, 11:53:38 AM »
Hello,

maybe you can uninstall it by GPO using msiexec /X{GUID} /QN? In case of a password to protect the program settings it could be a problem tough. I would recommend to unset the password using the old ADNM first.
Feel welcome to also visit the German Avast Community Forums for support and discussions with other security specialists as well as beginners!

Avast 19.6.2383 German Release Notes

wpn

  • Guest
Re: upgrade adnm 4.8 client to v6 SBC client
« Reply #2 on: August 04, 2011, 12:47:43 PM »
Thanks for the possible option but it should be solved by the (un)installer from Avast self.

Its not an option to have to use that (GPO / msiexec) way to uninstall the old client before deploying the new client


basicly what i mean is that the remainders of a fosil should be removed without extra handlings from an administrator in any way

Offline avadas.de

  • Avast Reseller
  • Sr. Member
  • *
  • Posts: 259
    • avadas.de
Re: upgrade adnm 4.8 client to v6 SBC client
« Reply #3 on: August 04, 2011, 07:44:29 PM »
Hi wpn,

I totally agree with you. There should be an upgrade or automatic removal, because it should be handled silently and without a gap in protection.

My above suggestion is just a "workaround" I have used in some migration scenarios in the past. Other product -> avast.
Feel welcome to also visit the German Avast Community Forums for support and discussions with other security specialists as well as beginners!

Avast 19.6.2383 German Release Notes