After update the ASOA console to 1.3.3.5, you can see that you system needs a lower version (1.3.2.21)
(see picture)
system
2
we are seeing the same… that seems to happen after every update.
avast3
3
IYHO, What does that mean?
system
4
It means that whatever web process they have setup to return “avast is up to date” for the SOA administrator is doing a version != check instead of a version <= check… So if you have a newer version it informs you that the older version is available for download, which really isn’t helpful.
Usually a day or two later, the website is updated and the erroneous message goes away.
system
5
We just noticed the same…Basically you will need to re-deploy to the clients if updating from the console so the client matches. If you check the SOA, the mirror is up to date but there wasn’t a program update task in the SOA before unlike AEA.
This message below
After update the ASOA console to 1.3.3.5, you can see that you system needs a lower version (1.3.2.21)
This message is only temporary after an update.
But please note : To update the clients to the new program from SOA they must re-deploy since the job chosen is only to update the VPS Definitions.
To update the clients to the new program from SOA they must re-deploy since the job chosen is only to update the VPS Definitions.
How do you re-deploy the clients in a workgroup environment (without a global “administrator” user)?
avast3
7
Workgroup requires using the “managed.exe” to be executed at each workstation.