Author Topic: Problems with Silent Installation  (Read 2087 times)

0 Members and 1 Guest are viewing this topic.

Offline Juanjo

  • Avast Reseller
  • Full Member
  • *
  • Posts: 158
    • Avast Antivirus España - Distribuidor y Mayorista Oficial
Problems with Silent Installation
« on: May 21, 2006, 11:49:54 PM »
Hello all:

First of all, like I always say, sorry about my english. I hope we can get help here. We have received a support request from one of our customers who recently have adquired 50 licenses of avast! Pro.

The problem is the silent installation. He reported us that he can't
install avast! by this metod, but in the normal mode (without using
silent installation) the problem don't appears. The installation in
silent mode works fine, but when Windows reboot avast! shows the tipical
resident icon with the red bar (like when we stop the resident
protection manually). When you make one click on the resident icon to
see all modules configuration, another error appears. You can see the
attachment (error.jpg) to see the captured screen. In english: "The
required resident task was not found. The operation could not be completed".

We requested him to send us the silent installation files (admin.ini and
tasks.xml) and make some test in our machines. The problem appears in
our PCs too. We maked some changes to admin.ini, without satisfactory
result.

Then, we thinked it can be a bug in avast!. We have created silent
installations from 2 of our PCs and we have tried to install to another
2 machines, with the same problem in all cases.

Anybody here have tested to install avast! in Silent Installation mode (with the new version)?

Best regards.

Offline Juanjo

  • Avast Reseller
  • Full Member
  • *
  • Posts: 158
    • Avast Antivirus España - Distribuidor y Mayorista Oficial
Re: Problems with Silent Installation
« Reply #1 on: May 22, 2006, 12:50:23 PM »
Ok, avast! support contacted me and it seems is a bug of the new version that will be fixed in the next one.

To solve it, the trick is to open the file admin.ini, and *delete* the line
that says:

DefTasksTimeStamp=<some-big-number>