Mismatch of license information on AV admin console and on local clients

[rlemke]

When checking the Avast license on local clients I stumbled across a mismatch of licensing information given on the admin console and on some of the AV clients. The console tells me to renew license file in August 2014 but local clients show test licenses which expire in 15 days. The deployment job on the console correctly shows updates on all of the local clients. How can I resolve this issue?

[giogio]

Hi and welcome,
some time is only necessary a reboot of the clients to take the license correctly.
But can you tell to us wich version and type of console are you using (AEA or SOA)?

[rlemke]

Well, the console version is still program version 1.1.132.15, database version 1348. Subscription is valid until August 2014. The clients affected many times have been rebooted since initial installation and rollout last year. This is the BPO product and the console looks more like the AEA. I compared the screen shots of the initial installation with the documents provided for AEA and SOA. My screen shots do not fully match the AEA document (http://www.avast-antivirus.es/pdf/Quick_Guide_AEA.pdf) but it doesn't match at all the SOA guide (http://files.avast.com/files/documentation/soa-administrators-guide.pdf).

[.: Mac :.]

Do you have different groups of licenses with different expiration dates? I may be wrong but I do not believe the ASOA console shows the expiration of the different groups. Example 20 Endpoint protection suite expires on June 1st and 30 Endpoint protection expires on November 1st. Some clients would be in the group of 20?

[rlemke]

Meanwhile I found the document which best describes the installed console, it is the document "Administration Console For avast Business Protection (Plus) Administrator's Guide" (http://files.avast.com/files/documentation/business-protection-plus-administrators-guide.pdf ). This document doesn't give an indicator, that the license file has to be installed on every client. Therefore I trusted on the deployment process which is scheduled daily.
I don't know of different groups of licenses and I only own one license file. The only thing that I could imagine is that some clients had been installed before the console has been installed and deployment has been configured. At least the license file arrived later. Therefore all versions started to run in eval mode. Perhaps I have a chance in a week to ask the guy who installed initially (a year ago).

[rlemke]

It isn't quite easy to find the right answer to the question about AEA or SOA. Now I requested additional information for the recommended upgrade from console version 1.1.132.15 to the current version 1.2.2.28 released 12.07.2012. When clicking "Learn more ..." I get an overview at http://www.avast.com/release-history-console and this overview now lets me assume: It is a SOA version because only such versions match the given version numbers. All AEA consoles show version numbers greater than 7.