Avira AntiVir MailGate 3.2 Migration from version 3.1.x to 3.2.x. HowTo

Transcription

1 Avira AntiVir MailGate 3.2 Migration from version 3.1.x to 3.2.x HowTo

2 Table of contents 1. Manual product update via command line Manual product update via Security Management Center (SMC) Automatic product updates via the cron job Automatic product update via Security Management Center (SMC) Uninstalling and reinstalling MailGate Overwriting the old MailGate-version (local only) MailGate 3.2 Migration HowTo (Status ) 2

3 Manual product update command line 1. Manual product update via command line In the case of manual product updates you can use the Avira Updater since version 3.x. In addition to the component scanner (only VDF and engine updates) it also supports the product component MailGate. Due to the subdirectory changes of the installation path that have been introduced with version 3.2, all relevant paths for INIT scripts, configuration files, product keys and symbolic links will be adjusted automatically with the product update. The changes include the following installation paths: Old /usr/lib/antivir/ /etc/ New /usr/lib/antivir/mailgate/ /etc/avira/ Note The service will be temporarily not accessible because of the product update, since important files have to be replaced. Therefore we recommend that you ideally carry out the product update within a free maintenance window. The product update is launched using the following command (shortened output): root@mailgate:~# avupdate --product=mailgate Updating, please wait... starting mailgate upgrade Update finished successfully After the successful product update, we recommend a subsequent check of the most important binaries as well as configuration files: root@mailgate:~# /usr/lib/antivir/mailgate/avmailgate.bin -V operating system: Linux (glibc-2.2.5, i686) product: Avira MailGate product version: gui root@mailgate:~# /usr/lib/antivir/mailgate/avupdate.bin -V update library version : avupdate version : MailGate 3.2 Migration HowTo (Status ) 3

4 Manual product update SMC Control of key configuration files: /etc/avira/avmailgate.conf /etc/avira/avmailgate.acl Provided that all settings have been applied correctly, you have now MailGate 3.2 at your disposal. 2. Manual product update via Security Management Center (SMC) In the case of a manual product update via the SMC you should first ensure that all the necessary files are up to date in the Internet Update Manager (IUM) repository. Check the product Avira AntiVir MailGate in the IUM at Released Products : Should the version number not match with 3.2.x, you should trigger the repository update manually or define the planner accordingly. MailGate 3.2 Migration HowTo (Status ) 4

5 Manual product update SMC Unless you want to use the new version of MailGate also for new installations, you should make sure that the software packages have been updated by the IUM (enabled by default): Note The service will be temporarily not accessible because of the product update, since important files have to be replaced. Therefore we recommend that you ideally carry out the product update within a free maintenance window. MailGate 3.2 Migration HowTo (Status ) 5

6 Manual product update SMC Now select the item Update in the desired group (or individual clients) via the context menu at Commands Avira AntiVir MailGate (UNIX) : MailGate 3.2 Migration HowTo (Status ) 6

7 Manual product update SMC The update dialog will then appear. Choose Product now instead of Scanner : You will start the product update by clicking on OK. The update will be started either immediately (Push) or after the defined interval (pull), depending on the agent configuration. MailGate 3.2 Migration HowTo (Status ) 7

8 Manual product update SMC Within the view Product version it will show now the new version number 3.2.x after a successful product update. We then recommend an inspection of the main settings of MailGate. Provided that all settings have been applied correctly, you have now MailGate 3.2 at your disposal. MailGate 3.2 Migration HowTo (Status ) 8

9 Automatic product update cron job 3. Automatic product updates via the cron job. The product update can also be controlled regularly and automatically via a cron job. This requires only that the following line is entered in etc/cron.d/avira_updater: * * Tue root /usr/lib/antivir/avupdate --product=mailgate > /dev/null The time and day of the week maybe freely chosen here of course. If the product update should be executed only once, we recommend the program at : root@mailgate:~# at 12pm at> /usr/lib/antivir/avupdate --product=mailgate at> [STRG]+D There will now be a product update according to the time defined by you. Note The service will be temporarily not accessible because of the product update, since important files have to be replaced. Therefore we recommend that you ideally carry out the product update within a free maintenance window. 4. Automatic product update via Security Management Center (SMC) In the case of an automatic product update via the SMC you should first ensure that all the necessary files are up to date in the Internet Update Manager (IUM) repository. MailGate 3.2 Migration HowTo (Status ) 9

10 Automatic product update SMC Check the product Avira AntiVir MailGate in the IUM at Released Products : Should the version number not correspond with 3.2.x, you should trigger the repository update manually or define the planner accordingly. MailGate 3.2 Migration HowTo (Status ) 10

11 Automatic product update SMC Unless you want to use the new version of MailGate also for new installations, you should make sure that the software packages have been updated by the IUM (enabled by default): Note The service will be temporarily not accessible because of the product update, since important files have to be replaced. Therefore we recommend that you ideally carry out the product update within a free maintenance window. MailGate 3.2 Migration HowTo (Status ) 11

12 Automatic product update SMC Now select the item Update in the desired group (or individual clients) via the context menu at Commands Avira AntiVir MailGate (UNIX) : MailGate 3.2 Migration HowTo (Status ) 12

13 Automatic product update SMC The update dialog will then appear. Choose Product now instead of Scanner : MailGate 3.2 Migration HowTo (Status ) 13

14 Automatic product update SMC By clicking on Schedule this command you will be taken to the dialog of the planner. Enter a name of your choice for the update and select either the item One time or Weekly : MailGate 3.2 Migration HowTo (Status ) 14

15 Automatic product update SMC By clicking on Next you can now define the exact start time: MailGate 3.2 Migration HowTo (Status ) 15

16 Automatic product update SMC The task for the selected computer will be visible in the view Tasks after clicking on Finish : MailGate 3.2 Migration HowTo (Status ) 16

17 Automatic product update SMC Within the view Product version it will show now the new version number 3.2.x after a successful product update. We then recommend an inspection of the main settings of MailGate. Provided that all settings have been applied correctly, you have now MailGate 3.2 at your disposal. MailGate 3.2 Migration HowTo (Status ) 17

18 Uninstalling and reinstalling 5. Uninstalling and reinstalling MailGate If the only option is a new installation, you can uninstall the old product by using the uninstall - command as follows. We recommend *not* to remove all key files and configuration files (if necessary, also existing log files) as well as the rejecteddirectory: root@mailgate:~# /usr/lib/antivir/uninstall --product=mailgate Would you like to back-up these key-files? [n] y Would you like to back-up these log-files? [n] y Would you like to back-up these conf-files? [n] y Do you like to remove the rejected directory from mailgate? [y] n Avira AntiVir MailGate successfully uninstalled All backed up files can then be found at /var/backups/avira. Thereafter, the current MailGate package can be unpacked and installed: root@mailgate:~# wget mailgate/unix/en/antivir-mailgate-prof.tgz root@mailgate:~# tar xzf antivir-mailgate-prof.tgz root@mailgate:~# antivir-mailgate-prof /install Follow the instructions of the install dialog. After installation, the previous backup configuration file in /var/backups/avira should * not * be applied 1:1 since some new parameters have been added! Instead, we recommend an adoption of the configuration parameters that you have made in the new configuration at /etc/avira/avmailgate.conf. Additionally, the backed up key must be copied back into /usr/lib/antivir/mailgate/ or should already be specified within the installation dialog. Provided that all settings have been applied correctly, you have now MailGate 3.2 at your disposal after a service restart. Note Please note that an uninstall and reinstall of MailGate is also possible via the SMC using the context menu at Installation Avira AntiVir MailGate (UNIX) Uninstall or Install. However, a separate backup of key files and configuration files is not necessary since this data is stored by the SMC. MailGate 3.2 Migration HowTo (Status ) 18

19 Overwriting old MailGate version 6. Overwriting the old MailGate-version (local only) Another possibility of product updates is by overwriting the existing version. This behavior strongly resembles the behavior of product updates via the updater. This requires only the current package to be downloaded and installed. The installer automatically detects the existing installation and completes the migration: wget mailgate/unix/en/antivir-mailgate-prof.tgz tar xzf antivir-mailgate-prof.tgz antivir-mailgate-prof /install Enter the path to your key file: [] (Das Keyfile wird automatisch aus /usr/lib/antivir übernommen) no key file will be installed Boot scripts for Avira MailGate have been found. Should they be overwritten? [y] After the successful product update, we recommend a subsequent check of the most important binaries as well as configuration files: root@mailgate:~# /usr/lib/antivir/mailgate/avmailgate.bin -V operating system: Linux (glibc-2.2.5, i686) product: Avira MailGate product version: gui root@mailgate:~# /usr/lib/antivir/mailgate/avupdate.bin -V update library version : avupdate version : Control of key configuration files: /etc/avira/avmailgate.conf /etc/avira/avmailgate.acl Provided that all settings have been applied correctly, you have now MailGate 3.2 at your disposal. Note Due to security reasons this update procedure is *not* supported by the SMC! We recommend in this case to follow the steps either in chapter 2,4 or 5. MailGate 3.2 Migration HowTo (Status ) 19

20 This manual was created with great care. However, errors in design and contents cannot be excluded. The reproduction of this publication or parts thereof in any form is prohibited without previous written consent from Avira GmbH. Errors and technical subject to change. Issued Q AntiVir is a registered trademark of the Avira GmbH. All other brand and product names are trademarks or registered trademarks of their respective owners. Protected trademarks are not marked as such in this manual. However, this does not mean that they may be used freely Avira GmbH. All rights reserved. Errors and technical subject to change. Avira GmbH Kaplaneiweg Tettnang Germany Telephone: Facsimile