Professional Documents
Culture Documents
Product Updates
Best Practices
Table of Contents
3. Product updates
Starting with version 2013 Avira Professional Security has only one update possibility: download product and detection updates together. It is no longer allowed to deny
the product updates.
If the product decides that after performing a Product update a reboot is required,
the user (or Administrator) will see a notification informing him about this.
Once the update has been completed, a popup will appear requesting a reboot.
If activated, the behavior could be checked at the security environment or any other
group/host object:
Manual updates could either be created on the host itself (see above standalone
installation) or they can be created in the AMC:
On creating a manual update task, it is useful or even necessary to adjust the update
source for manual updates (they are probably different than in the automatic mode).
The manual update source can be adjusted in the update configuration option of the
product. In the following example the local AUM is chosen as the priority server. If the
local AUM can be reached, the updates are loaded from this source.
If it fails (notebook is connected outside the company), the default servers are chosen and the host gets an update directly from the Avira update servers:
With several update status, you can trigger an email. The email alerting can be set up
in the AMC (email is send by AMC) or the host product (professional/server, email is
sent from there).
Please refer to the AMC manual, chapter 7.4 Update overview:
http://www.avira.com/documents/products/pdf/en/man_avira_antivir-smc_en.pdf
The test mode is establishing an additional http port. The default http test port is 7100
and can be adjusted in the AUM network settings:
10
Then you will see two sub groups in the AUM products, one for released updates and
one for test updates:
11
12
Then, assign the productive update server to the concerned productive group:
13
The updates are applied automatically to the test group (see General behavior: Automatic updates vs. manual updates).
After finishing the tests successfully, the test updates can be committed to the productive server:
Again, the updates are applied automatically to the assigned productive group (see
General behavior: Automatic updates vs. manual updates).
14
For the productive environment you also have to assign the productive sources in
both fields:
Please refer to the AMC manual, chapter 7.1.2 Using the AUM in test mode.
http://www.avira.com/documents/products/pdf/en/man_avira_antivir-smc_en.pdf
15
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 Operations GmbH & Co. KG.
Issued Q1-2013
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.
2013 Avira Operations GmbH & Co. KG. All rights reserved.
Errors and omissions excluded.