﻿Avira AntiVir Internet Update Manager (Avira IUM)
Copyright (c) 2008-2011 Avira GmbH
http://www.avira.com



============================
Contents
============================

1 Product information
2 Installation
3 Configuration
4 Operation
5 Frequently Asked Questions (FAQ)


============================
1 Product information
============================

1.1 Functionality

Avira Internet Update Manager lets you download updates for many of your Avira products conveniently and automatically from the Internet.
Individual computers on your network can then update products via your intranet, rather than having to download them themselves from the Internet.
Avira Internet Update Manager comprises the following two components:
* Avira Internet Update Manager Server (for both Microsoft Windows and UNIX)
* Avira Internet Update Manager Frontend (for Microsoft Windows only)
The Internet Update Manager Server runs on one or more servers on your intranet and controls the downloading of product updates on these servers. 
Internet Update Manager Frontend lets you configure and operate one or more Internet Update Manager Servers from a central point (Remote Control).


1.2 System requirements

For Avira Internet Update Manager to work perfectly, the computer system must fulfill the following requirements:
* Computer from Pentium class upwards, at least 1 GHz
* Operating system (UNIX)
    - Red Hat Enterprise Linux 6 Server
    - Red Hat Enterprise Linux 5 Server (5.4)
    - Red Hat Enterprise Linux 4 Server (4.8)
    - Novell Open Enterprise Server 2 (SLES 10 SP2)
    - Novell SUSE Linux Enterprise Server 11 (SLES 11.2)
    - Novell SUSE Linux Enterprise Server 10.3 (SLES 10 SP2)
    - Novell SUSE Linux Enterprise Server 9 (SLES 9)
    - Debian GNU/Linux 5 (stable, lenny)
    - Ubuntu Server Edition 10.04
Note: The libstdc++.so.6 library must also be available on the systems. This usually has to be installed subsequently through proprietary distribution package management.

Note: If you are using a 64-bit version (amd64/x86_64) of the above mentioned Linux distributions, 32-bit compatible libraries must also be subsequently installed. The proprietary distribution software management can usually be used for this.


* Internal memory
    - At least 512 MB RAM
    - At least 500 MB temporary memory on the hard disk (depending on the scope of the product updates).
* An Internet connection (modem or LAN)
* Administrator rights (for installing the Avira Internet Update Manager)

============================
2 Installation
============================


2.1 Installation with Linux

For the Avira Internet Update Manager to function perfectly on your server, ensure that the following requirements are satisfied:
* System requirements are fulfilled
* Administrator rights and root rights are granted for the installation
* IUM network ports are open in the firewall (default: 7100, 7050, 7051 and 7080)
* No other applications are installed that occupy the IUM network ports
Note: If the port is used by other applications, IUM does not start and no error message is displayed at the command line.

Installation of the Internet Update Manager is performed automatically with the aid of an interactive installation script (bash command line).
The script performs the following steps:
* License retrieval (EULA)
* Checking the integrity of the installation files.
* Checking authorizations required for installation.
* Copying the application files and overwriting existing files that are no longer needed.
* Copying the configuration files

2.1.1 Installation procedure

1.	Log in as 'root'. Otherwise you will not have the authorization to perform the installation and the script will issue an error message.
2.	Please extract the current installation package, e.g. to /tmp:
cd /tmp; tar -xzvf avira_update_manager_unix_en.tar.gz
3.	Change the directory to which you have extracted Avira Internet Update Manager:
cd avira_update_manager_unix-<version>
4.	Start the installer:
./install
5.	Read the license agreement carefully. Pressing the space bar will take you to the next page. Accept the license agreement. Then press the "Q" and "Y" keys and click Enter to confirm.
The product is now installed. The destination directory is checked and if necessary created. All the necessary files are copied to the destination directory:
-------------------------------------------
2) installing AVIRA IUM
creating /usr/lib/AntiVir/ium ... done
creating /usr/lib/AntiVir/ium/ssl ... done
....
-------------------------------------------
You will then be asked if you wish to create an icon link to the IUM start script in your system directory:
"Would you like to create a link in /usr/sbin for avium?[y]"
6.	Recommended: y(es). This is not absolutely necessary but simplifies the subsequent retrieval of the IUM.
Do you want Avira Internet Update Manager to be automatically loaded at system start-up?
-------------------------------------------
Please specify if boot scripts should be set up.
Set up boot scripts? [y]:
-------------------------------------------
Recommended: y(es). 
Automatic system start-up is configured:
-------------------------------------------
setting up boot script ... done
installation of AVIRA IUM complete
-------------------------------------------
If you would prefer to start the Daemon Internet Update Manager manually after system start-up, perform the following steps: Select "N" and press Enter.
You will then be asked if weekly updates for Avira IUM should be downloaded automatically.
-------------------------------------------
3) Configuring updates
An internet updater is available with version...
In order to trigger an update you will need to run the command: 
 /usr/lib/AntiVir/ium/avupdate-ium --product=IUM
Would you like to create a link in /usr/sbin for avupdate-ium ? [y]: 
-------------------------------------------
7.	Recommended: y(es).
-------------------------------------------
Would you like to check for IUM updates once a week ? [n]
-------------------------------------------
Recommended: y(es).
Finally a report will be displayed confirming that the installation has been successfully completed:
-------------------------------------------
Installation of the following features complete:
AntiVir IUM Updater
AntiVir Internet Updater
-------------------------------------------

2.2 Reinstall Avira IUM (under Linux)

You can repeat the installation script at any time. Other scenarios are possible:
* Installation of a new version (upgrade) of the Avira IUM. The installation script then checks the previous version and installs the requisite new components.
* Enabling or disabling automatic start-up of the Avira IUM at system start-up.

2.3 Deinstallation

To uninstall the Internet Update manager, log in as root and run the following command:
/usr/lib/AntiVir/ium/uninstall --product=IUM

The Internet Update Manager is now completely uninstalled in accordance with the default settings.
However, during deinstallation you will be asked whether you wish to create backups of the logfiles and the configuration files. If you do not want this, press Enter. If you wish to create backups, enter y and then press Enter.
The same applies to the HTTP root directory. If you wish to delete this directory, press Enter, otherwise enter n and then press Enter.

============================
3 Configuration
============================


3.1 Configuration without graphical user interface (Linux)

The most important settings for your Internet Update Manager are contained in the configuration file /etc/avira/ium.conf.

Note: To edit the configuration, open the file in an editor, make the required changes and restart the IUM (see Starting and stopping IUM manually).
Note: Please note that any comments you write in the ium.conf file will be deleted each time IUM is restarted.
Password encryption makes it necessary to configure certain functions via the Frontend.
Note: Currently the Internet Update Manager for UNIX-based operating systems is only available in English. Therefore, do not edit the parameter <language value="en" />.

3.1.1 Server settings

The default value 0.0.0.0 ensures that the Internet Update Manager is listening to all available network interfaces. 
The default setting
<ip value="0.0.0.0"/>
can also be changed as required. Replace 0.0.0.0 with the corresponding IP address or host name.

3.1.2 Setting up a proxy server

Internet Update Manager may use a proxy server for updates. By default, this function is disabled.
<use_proxy value="false" />
Enable it by making the following changes in the ium.conf file:
<use_proxy value="true"/>
Then insert the information required for the proxy server into the configuration file.
The address of the proxy server is defined with the IP address or server name using the option
<proxy_host value="your_proxyserverip"/>
while the port used is defined by entering:
<proxy_port value="your_proxyserverport"/>

Proxy server authentication is disabled by default:
<proxy_use_auth value="false"/>
Activate this by setting the parameter to 
<proxy_use_auth value="true"/> 
You can enter your user name under
<proxy_username value=""/>
in the command line. The password is defined in
<proxy_password value=""/>
Note: Passwords entered via the Frontend are encrypted. If the passwords are entered by manually editing the configuration file, they will be stored in plain text.
It is therefore recommended to enter the passwords via Frontend.

3.1.3 Configuring email notifications

The Internet Update Manager can send information about completed repository updates by email.
The SMTP server used for sending the emails:
<smtp_server value="smtp_server.tld"/>
The sender and the recipient of the notification email can be configured by editing the following parameters:
<smtp_from value="AVIUM@your_domain.tld"/>
<smtp_to value="IUM_Admin@your_domain.tld"/>
By default, if enabled, the email notifications are sent only when errors occur:
<smtp_level value="error"/>
To receive email notifications for warnings and errors, modify the smtp_level value to warning:
<smtp_level value="warning"/>
To receive email notifications after successful updates, for warnings and errors, modify the smtp_level value to info:
<smtp_level value="info"/>
Authentication on the SMTP server is disabled as the default setting:
<smtp_login_required value="false"/>
Change the parameter to 
<smtp_login_required value="true"/>
to enable it.
Note: SMTP authentication can only be fully configured via the Frontend, because the application encrypts the password, and plaintext cannot be used.
It is therefore recommended to set only the user name in the ium.conf file
<smtp_login value=""/>
leaving the parameter for the password unchanged
<smtp_password value=""/>
The password should be entered via the Frontend.

3.1.4 Selecting the location for saving updates

The location where updates are to be saved can be chosen as required. You can specify it by editing the following parameter in the ium.conf file:
<http_server_root value="/var/avira/ium/HttpRoot"/>
Note: The Internet Update Manager creates a specific folder structure in this directory. The files it contains should not be changed manually.

3.1.5 Changing the ports of the integrated HTTP server

The default settings of the IUM HTTP server are as follows:
<http_server_enable value="true"/>
<http_server_ip value="0.0.0.0"/>
<http_server_port value="7080"/>
<http_server_port_test value="7100"/>
If the port for the production server (7080) or the port for the test server (7100) is already used by another application, it should be changed into other unused port. 
If you do not wish to use the integrated http server, change
<http_server_enable value="true"/>
from "true" to "false".

3.1.6 Changing the preset download server

The ium.conf file contains a default list of download servers:

<http_server_list_orig value="http://dl1.pro.antivir.de,http://dl2.pro.antivir.de,http://dl3.pro.antivir.de,http://dl4.pro.antivir.de,http://dl1.antivir.net,http://dl2.antivir.net,http://dl3.antivir.net" />

Note: Please DO NOT edit this list.
If you would prefer to use a proprietary server for the update instead of the official servers, change the following parameter from "false" to "true":
<override_server_list value="true"/>

3.1.7 Editing the list of servers

If you have specified that you wish to use your own download servers, you can specify several custom download servers, separated by commas:
<http_server_list_user value="ip_address:port" />

3.1.8 Editing the product list

New products can be added as follows:
/usr/lib/AntiVir/ium/ium --add_products
You can use interactive queries to add or remove a product from the repository. After running this command the configuration is saved in /etc/avira/mirrorconfig.xml.
Note: In order to run --add_products it is essential that the Internet Update Manager daemon is not running, otherwise the command will fail.

3.1.9 Configuring the repository update schedule

By default the scheduler for the Internet Update Manager is deactivated. An update schedule has to be created manually be editing the ium.conf file.
First, set
<enable value="false"/>
to "true".
Then you can configure the interval at which Avira Internet Update Manager scans for available product updates and downloads them. This requires adding certain options to the configuration file. For example:

<scheduler>
<enable value="true"/>
<periodicity value="1"/>
<userdefinedInterval value="0"/>
<userdefinedIntervalSeconds value="0"/>
<start value="1293015226"/>
<weekdays value="127"/>
</scheduler>

Frequency of the updates:

The frequency of the updates is set with the parameter:
<periodicity value=""/>
Available values:
0 = once
1 = hourly
2 = daily
3 = weekly
4 = monthly
5 = user-defined
If you select 5, you must also set a user-defined interval. This is done with 
<userdefinedInterval value=""/>
The specification is made in hours, i.e. 1 = one hour, 2 = two hours, etc.
You can use
<userdefinedIntervalSeconds value=""/>
to set the seconds.
The interval (in seconds) is then yielded from the sum of the two specified values: userdefinedInterval * 3600 + userdefinedIntervalSeconds.
Note: The selected interval must be at least 5 minutes longer than the interval set for the automatic copying of files in test mode.
In order to set the scheduler for certain days of the week, use:
<weekdays value=""/>

Available values:
0 = once
1 = Sunday
2 = Monday
4 = Tuesday
8 = Wednesday
16 = Thursday
32 = Friday
64 = Saturday
127 = every day

Start time:

To specify the start time, you must calculate the seconds since 1970. The date command can be used to calculate the current time in seconds
date +%s
Accordingly, a specific time can be converted to this format with the command 
date -d "Year-Month-Day Time" +%s, 
e.g. 
date -d "2010-08-24 9:07" +%s
Enter the result as the start time, e.g.
<start value="1277483495"/>
Each subsequent update takes this data as the starting point.
After enabling the Scheduler, the Avira IUM Server adds the following parameters to the configuration file, which you should not change:
<state value="3"/>
<lastRun value="0"/>
<clienttimezoneoffset value="-60"/>

* state returns the status of the update task: 0 (task completed successfully), 1 (task failed), 2 (task in progress), 3 (task not run yet)
* lastRun shows the time (in seconds, like the start parameter) when the task has lastly been run
* clienttimezoneoffset is used by the server to compensate any time zone differences


============================
4 Operation
============================



4.1 Operation with Linux (without graphical interface)

Note: To change the configuration, stop the Internet Update Manager, open the configuration file in an editor, make the required changes and restart the IUM (see Starting and stopping IUM manually).

4.1.1 Testing the updates

This function provides a separate optional update structure which enables you to first scan new versions and updates before releasing the files for all your productive systems.
Technically this means starting a further HTTP service which is by default provided via the HTTP port 7100. 
Ideally, you can provide a small test environment for these test releases and scan the updates before using them on your productive systems.
The test mode is disabled by default:
<testmode value="false"/>
To enable it, change the parameter in the ium.conf file to:
<testmode value="true"/>
If the test files have been downloaded, you can start an application to check that your systems are still fully functional with the updated files.
Enter the path to the application that is to be tested, in the parameter:
<start_after_update value="" />
This application must be certified by Avira GmbH in order to prevent the misuse of this option by unauthorized persons. Please contact the support beforehand.
The test files can then be copied to the release folder automatically. To do this, change the parameter
<auto_commit_enable value="false" /> 
to
<auto_commit_enable value="true" /> 
You can also define an interval for copying the test files to the release folder. The time unit is one minute. According to the default setting
<auto_commit_interval value="60" />
the test files will hence be copied automatically after 60 minutes.
Note: The selected interval must be at least 5 minutes less than the interval set for updating the products.
If problems occur while testing the updates with the test repository, the automatic copying process of the test files can be terminated, with the command:
/usr/lib/AntiVir/ium/ium --drop_automatic_commit
This means that automatic product commit remains enabled but the currently queued commit is dropped. The next commit will not be queued until the next update download (after running /usr/lib/AntiVir/ium/ium --get_updates).

4.1.2 Starting and stopping IUM manually

If you wish to start the Internet Update Manager daemon, enter
/usr/lib/AntiVir/ium/avium start
in the terminal.
The Internet Update Manager daemon can be stopped with the following command:
/usr/lib/AntiVir/ium/avium stop
To restart the daemon enter the command:
/usr/lib/AntiVir/ium/avium restart
To check whether the Internet Update Manager is running, you can use the command:
/usr/lib/AntiVir/ium/avium status

4.1.3 Updating products

Products are updated manually with the command
/usr/lib/AntiVir/ium/ium –-get_updates
The Internet Update Manager checks if there are any new updates for the products in the repository and then downloads these immediately.
Note: If the Internet Update Manager daemon is started, after issuing --get_updates, it will be in charge of getting the updates for the repository .
Note: When the Internet Update Manager daemon has been started, the output of --get_updates is written in the logfile. If no daemon is running, the output will be displayed directly in the terminal.

4.1.4 Canceling a download (prematurely)

If you wish to cancel a download prematurely, terminate Internet Update Manager using the crtl+c shortcut only, or with 
/usr/lib/AntiVir/ium/avium stop 
if the Update Manager is running in the background.
Note: Using kill -9 can lead to problems with the program requiring a computer reboot. 
By sending SIGKILL to the ium process semaphores are created, which prevent further execution of the service. These can be removed via the following command:
ipcrm -s
ipcrm -s _semaphore-id_
This means that for example the command ipcrm -s _918270815_ deletes the semaphore with the ID 918270815. 
Please follow the same procedure with other semaphores.

4.1.5 Updating Avira IUM automatically

You can set Avira IUM to carry out a self-update, after it updates the products’ repository, by changing to "true" the value of the parameter:
<automatic_selfupdate value="false"/>
If you use Avira IUM via Avira SMC (Security Management Center), you can notify the attached SMC Server about available updates, using the parameter:
<automatic_mode value="true"/>
If you answered yes during the installation (see Installation procedure), when asked to set automatic updates of Avira IUM, the update command (/usr/lib/AntiVir/ium/avupdate-ium --product=IUM) is run automatically once a week.
To set custom automatic updates of Avira IUM on Linux, you can insert a cron job similar to the one optionally created at the installation. For example:
# cat /etc/cron.d/avira_updater
16 12 * * Tue root /usr/lib/AntiVir/ium/avupdate-ium --product=IUM > /dev/null
Available update files are downloaded and automatically installed.
Note: If you are running Internet Update Manager in daemon mode, it must be restarted after changing the configuration, for the new settings to be accepted: 
avium restart
or:
/usr/lib/AntiVir/ium/avium restart
Stopping AVIRA Internet Update Manager...
Stopping: ium
Starting AVIRA Internet Update Manager...
Starting: ium

4.1.6 Displaying the logfile

The logfile records the activities of the Internet Update Manager Server.
The logfiles for Internet Update Manager can be accessed in the directory: /var/log/ium.

Log level

You can define which kind of messages are logged by editing the parameter:
<log_level value="info" />

info
The default is info. It means that errors, warnings and some status messages will be logged. You can decide on the extent of the log file by choosing how much detail is to be logged. From error to debug the log file becomes more and more detailed, the default info being the medium setting.

error
In error-mode only errors are logged.

warning
In warning-mode errors as well as warning are logged.

trace
In addition trace superficially traces the service and saves it to the log.

debug
Debug is the setting which delivers the greatest detail. When <log_level value="debug" /> is chosen, the service is reproduced line after line in the log file, in order to monitor at which passage in the code the service has encountered a problem.

Log file backup

By default the Internet Update Manager creates only one single logfile. If you would like to start a new logfile after every restart, set 
<log_append value ="true" />
to false.
This also gives you the option of setting a maximum file size in kB by using the parameter:
<log_max_size value="1024" />
If this file size is reached, the current logfile is backed up and a new logfile is created.
The number of backups can also be limited via the following parameter
<log_backup_count value="10" />
The earliest backup will be deleted at the creation of a new one.

5 Frequently Asked Questions (FAQ)

What must I look out for when configuring the Avira AntiVir Windows Workstation?
Avira Internet Update Manager generates the required update structure automatically! It is important when updating via Fileserver/Share to enable the destination directory on the server, so that the update can by carried out by the Avira AntiVir Windows Workstation.

5.1 Procedure for updating via Fileserver/Share

1.	Under Configuration - General - Update, enable the via Fileserver/Share option.
2.	Go to the Configuration - General - Update - Fileserver tab. 
3.	In the Download area, enter the path to the upd folder (for AntiVir Products Version 8) or update (from AntiVir Products Version 9 and above) in the destination directory specified in Avira Internet Update Manager.
	Example for version 8:
	file://192.168.1.1/IUM_share_name/upd
	
	Example for version 9 and above:
	file://192.168.1.1/IUM_share_name/update
4.	Where necessary, enter the server login data in the Server Login area.

5.2 Procedure for updating via Webserver (http)

1.	Under Configuration - General - Update, enable the via Webserver option.
2.	Go to the Configuration - General - Update - Webserver tab. 
3.	In the Download area, enter the address of the webserver from which the updates are to be downloaded.
Examples for version 8: 
http://192.168.1.1:7080/upd
http://server:7080/upd
Examples for version 9 and above: 
http://192.168.1.1:7080/update
http://server:7080/update
4.	Where necessary, adjust the proxy server settings in the Configuration - General - Update - Webserver - Proxy area.

5.3 Procedure for updating SAVAPI 3-products

To update SAVAPI 3 products supported by IUM (Avira AntiVir WebGate, Avira AntiVir MailGate, Avira AntiVir Server for UNIX, Avira AntiVir Professional for UNIX), you have to configure /etc/avupdate.conf by commenting out the internet-srvs line and inserting three new lines:

--------------------------
#internet-srvs
intranet-srvs=http://iumserver:7080
product-root=/update
intranet
--------------------------

5.4 Avira Support

You can also find questions and answers on our FAQs pages: http://www.avira.com/en/support-for-business-faq
Our Knowledgebase containing important information on our products is also available: http://www.avira.com/en/support-for-business-knowledgebase-search

------
Document last updated: February 2011, v 2.6.6