First of all, I cannot believe we cannot get basic phone support after paying thousands for Avast enterprise software and I have to resort to forums. A true shame because this software has so many problems.
I noticed that my mirror servers are not updating their definitions and in turn the endpoint clients are not updating. I’ve had MONTHS old definitions on some clients. If I run mirror.exe on a mirror server, it says all’s fine, nothing to update, yet it has old definitions.
The Root EAS appears to have the latest definitions, I ran mirror.exe anyway on the root server and it pulled from avast servers. I reinstalled the mirror on the root server from the console, I also deleted the entire mirror folder and left servers.def file in there and it redownloaded everything from avast.
I can’t think of anything else to do on the root EAS. The mirrors can reach the root EAS server through the network and inbound TCP port 16135 is open on all servers in question.
If I try to manually update the endpoints that have old definitions, they simply say they have the ‘latest’ definitions which is wrong. I understand I can use the ‘update from internet’ if mirrors are unreachable feature, but that is a disaster because if it’s on, the entire network gets flooded with the endpoints trying to download half gig of definitions. I do NOT want that.
nevermind the post above. I just wiped the mirror folder yet again, left servers.def file, and re-ran mirror.exe. It pulled the entire def. database from avast servers successfully.
Sadly, the bulk of my issues have not been solved. The mirror servers cannot update their definitions from the EAS. I’ve reinstalled the mirrors from the consoles now, in addition to everything else I posted up above, but no go. The log file basically says it tries to update from the EAS but fails, then it tries to update from avast servers, and it gets error 404’s.
I am starting to re-think whether avast endpoint protection suite is even compatible with Server 2012 R2?? Is there any documentation that shows it is? I honestly had no problems when I was on 2008 R2 until I started using this new server. I did a fresh install to begin with, and it is running SQL 2008 R2 standard, not express.
Is my console out of date? are there any updates to this thing? My console shows APRIL 2016
I don’t use a avast server product, so all I can do is using a bit of logical thinking…
According to the avast website:
Microsoft Windows Server 2003 and 2003 R2 (any edition with latest Service Pack, 32-bit or 64-bit, incl. Small Business Server)
Microsoft Windows Server 2008 and 2008 R2 (any edition with latest Service Pack, 32-bit or 64-bit, incl. Small Business Server, except Server Core)
Microsoft Windows Small Business Server 2011 (any edition with latest Service Pack, x64bit)
new iconMicrosoft Windows Server 2012 and Server 2012 R2 (any edition with latest Service Pack, x64bit, incl. Small Business Server/Essentials, except Server Core)
I take it you have the latest SP installed ?
If so, using 2012 shouldn't be a problem.
Even if the console is old(er), it shouldn’t be a problem.
I do see however multiple complains about updating the vps on “home” versions of avast as well as installing avast with the on-line installer.
There are definitely problems there that avast should solve a.s.a.p.
No clue if it will work or even is possible.
As it is about the vps, I wonder if it is possible the latest vps and deploy it to the mirrors?
Just a thought…
