Avast WEBforum
Business Products => Archive (Legacy) => Avast Business => Avast Endpoint Protection => Topic started by: wpn 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?
-
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.
-
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
-
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.