We had an installation of 4.x managed clients. I began testing the move to the latest 5.x managed clients.
I created the auto-deploy package for a select group. I choose to NOT reboot after deployment. I left all the rest as default. The admin guide states that previous versions of avast would be removed for the install. I ran the job for deployment to test.
The PC in that group began the installation, and then began a reboot even though I removed that option in the deployment job. Was this due to the uninstallation of 4.x? If yes, how can I suppress that?
After the PC restarted, version 5 was ready and I could see it in the console. Testing some apps, MS outlook would give an error when opening. "The Add-in Avast ...aswOutXt.dll cannot be loaded". Obviously, the previous 4.x had an email shield or something similar for outlook. The auto-remove of 4.x didn't remove this entry from Outlook.
Now everytime Outlook starts, the user will have this error.
I'm going to go through and see if I can script a solution to unregister the DLL and remove the reg key for this addon. Somehow, I'll get that script to run after Avast is installed....
Does anyone have a better solution for this?