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

========================================================
 Content
========================================================

1. Description
2. System requirements
3. Installation 
4. Configuration
5. Adding products
6. Running
7. Setting up clients
8. Support


========================================================
1. Description
========================================================

Internet Update Manager (IUM) is a tool designed to ease deployment of updates for AVIRA products within a local network.
It can mirror updates of AVIRA products from online update servers so that network clients that have restricted access to internet can update their AVIRA products. It can also be used as a mean of saving bandwidth. 


========================================================
2. System requirements
========================================================

IUM runs on linux with glibc version 2.2 or higher. A Microsoft Windows version of IUM exists that is not the subject of this MANUAL.
Supported distributions (Minor Versions / Service Packs included ) are:
- Novell SUSE Linux Enterprise Server 9, 10
- Novell SUSE Open Enterprise Server 2
- Red Hat Enterprise Linux 4, 5
- Debian
- Ubuntu


IUM can also be administred using an frontend (MMC-SnapIn) (optional) for which you will need a Microsoft Windows system. 

Dependencies:
The following library has to be available on the system: libstdc++.so.5
Usually this library has to be installed via the package management of the distribution.

64-bit versions:
If you use a 64bit version (amd64/x86_64) of linux you have to install 32bit compatible libraries before installing  IUM. For that purpose you can use the software management of the distribution.

IUM listens on ports 7021, 7050, 7051 and 7080. In order to run properly you will need to open those ports in firewall


========================================================
3. Installation
========================================================

In order to install IUM you need to unpack, run the ./install script from kit and follow the instructions.


========================================================
4. Configuration
========================================================

You can configure IUM settings by editing /etc/avira/ium.conf.

  <ip value="0.0.0.0"/>

IP address that IUM will listen on.

The default value 0.0.0.0 defines that IUM shall accept connections on all existing network addresses. 

  
  <use_proxy value="false"/>
  <proxy_host value="<your_proxy"/>
  <proxy_port value="8080"/>
  <proxy_use_auth value="false"/>
  <proxy_username value=""/>
  <proxy_password value=""/>

Proxy settings that IUM should use when retrieving updates (default: none) 

  
  <smtp_server value="smtp.your_smtp_server.tld"/>
  <smtp_from value="AVIUM@your_domain.tld"/>
  <smtp_login_required value="false"/>
  <smtp_login value=""/>
  <smtp_password value=""/

After a successful update of the repository you can configure an e-mail notification that will inform you which files have been updated.(default: no email notification) 

  
  <testmode value="false"/>

This option will make IUM create a separate update structure that allows you to test new versions and updates before deploying them. For this purpose a new http server is started that will listen on port 7022 by default.(default: no test mode)

  
  <port value="7050"/>
  <port_async value="7051"/>
  <http_server_ip value="0.0.0.0"/>
  <http_server_port value="7080"/>
  <http_server_port_test value="7100"/>
  <http_server_port_old value="7021"/>
  <http_server_port value="7080"/>

Ports on which IUM listens.


  <http_server_root value="/var/avira/ium/HttpRoot"/>

The location where the retrieved updates will be saved. You can use this location as a DirectoryRoot for another webserver (e.g. Apache) if you want it to provide the updates to clients instead of IUM.

 <scheduler>
         <enable value="true"/>
         <periodicity value="0"/>
         <userdefinedInterval value="0"/>
         <userdefinedIntervalSeconds value="0"/>
         <start value="1219058759"/>
         <state value="0"/>
         <lastRun value="0"/>
         <weekdays value="127"/>
 </scheduler>

Scheduling options for checking and retrieving updates for products from repository. These options make sense only if IUM 
is running in daemon mode (default: no scheduler).
 
Note: If you use the Internet Update Manager in the daemon mode you need to restart it after modifying the configuration. You can do that by running:

/usr/lib/AntiVir/ium/avium restart


========================================================
5. Adding products
========================================================

In order to add products into the repository for retrieving updates you will need to do:

 /usr/lib/AntiVir/ium/ium --add_products

By means of interactive queries you will get a corresponding configuration automatically.

This configuration is saved in /etc/avira/MirrorConfig.xml.

Note: Configuring IUM and adding products can also be done via IUM Frontend (Windows)


========================================================
6. Running
========================================================

There are two ways of operating IUM:

1. Running IUM as a daemon in the background

You can start ium as a daemon by running '/usr/lib/AntiVir/avium start'.

In this way IUM will start a http server listening on port 7080 that will provide clients with the retrieved updates. 
It can be scheduled to retrieve updates from online servers at regular intervals (scheduler option).
It will also be possible to have it configured via IUM Windows Frontend.

Advantages:
 - Does not depend on another webserver
 - It can be configured to check and retrieve updates automatically from online servers
 - Remote administration is possible via the IUM Frontend (Windows)

Disadvantages:
 - Separate process
 - Firewall: additional ports have to be enabled

2. Running IUM without the daemon process

This mode is similar in functionality with the former AVIRA mirrorscript. 
You can setup IUM to create and maintain a structure similar to the online servers without having a permanent daemon process.

In order to retrieve available updates for the products configured in the repository you will need to run:
 
 /usr/lib/AntiVir/ium/ium --get_updates

Note: You may want to set this command as a cronjob in order to get updates at regular intervals.

In this mode IUM will not serve the retrieved updates to clients. You will need to adjust the 'http_server_root value' from /etc/avira/ium.conf to match the DirectoryRoot of a running webserver (e.g. Apache).

Advantages:
 - No running daemon process is necessary
 - Firewall: no changes are necessary

Disadvantages:
 - Remote administration is not possible via Windows Frontend
 - It relies on another webserver to provide updates to clients
 - You need to set up the '--get_updates' command via cronjob to maintain IUM repository updated


========================================================
7. Setting up clients
========================================================

After you have configured IUM to provide updates properly, you will need to adjust clients to update from it.

Windows clients:
  Go to Options->General->Update->Webserver->Download Server and add:
    http://iumserver:7080/upd

This information is valid only for AV8. In AV9 you need to replace
http://iumserver:7080/upd with http://iumserver:7080/update


Linux clients:
   For savapi2 products add these two options in /etc/avupdater.conf:

HTTPUpdateServer 'iumserver':7080
IgnoreRemoteServerSpec yes

For savapi3 products, there are two options that work with IUM:
1. With IDX patching, configure internet-srvs=http://iumserver:7080 in /etc/avupdate.conf
2. Without IDX patching, configure /etc/avupdate.conf as described in avupdater.txt. The following lines should 
   be added in addition to what a default avupdate.conf already has:
--------------------------
intranet-srvs=http://iumserver:7080
product-root=/update
intranet
--------------------------
And customers also need to comment the internet-srvs line that exists by default.

Products that have the antivir binary are savapi2 version wheareas those that do not have are savapi3.

========================================================
8. Support
========================================================

Technical support is available at:
support@avira.com

Please do not hesitate to contact us if you have discovered any problems or have any suggestions.

Also you can find technical descriptions at:
www.avira.com/knowledgebase

