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)
we are seeing the same… that seems to happen after every update.
IYHO, What does that mean?
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.
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)?
Workgroup requires using the “managed.exe” to be executed at each workstation.