I have installed the new Avast! Business Protection suite. I have deployed a couple test clients successfully. It is program version 1.1.131.7 and database version 1277.
After rebooting the client computers, they are reporting back as “Attention” with a yellow exclamation point instead of “Secured” with a green check. I took a look at the client interface and there is an Antispam Shield that is not started and Avast! reports there is a problem. I click the “Fix Now” button and nothing happens.
I actually would like to disable this feature but my problem is I don’t see any Antispam Shield control settings on the server console. I see every other shield but the antispam. There appear to be some antispam settings under the Expert Settings section but I don’t know what the possible values mean.
Can someone explain why there is an antispam feature on the client but no antispam feature to control it on the server console?
I am experiencing the same issue. I had an open support ticket regarding it and was told this is an issue that will be resolved this month in the next update version. I know this doesn’t help you at the moment, but at least it has been acknowledged as a known bug now and is supposedly being worked on… so there is hope. Every day I am getting new helpdesk tickets from users saying they are concerned about the messages that say they are unsecured and try hitting the fix button but it isn’t working.
Thank you for the link Paul, but that simply isn’t a viable fix in my situation. I have nearly 800 machines I have been pushing the client to, most of which are remote laptops for sales reps. Going to each machine individually and uninstalling that component from add/remove programs is not going to happen, nor is scheduling a time with each of them to remote in and do it!
I need to be able to fix this from the server/console level.
I am glad the issue has been ackknowledged and they are looking into it. Hopefully the release of this update won’t take as long as the release of this new Business Protection console did. Other than this issue and a couple other minor ones I am very happy with the new console. WAAAAY better than the old ADNM console.
I also have to agree with VanEck. We have multiple different client networks with anywhere from 5-50 computers each. It is not at all an option to log into each one individually. That defeats the purpose of using the centralized console.
Just curious as to why you believe this console is WAY better then the old ADNM? Maybe I’m missing something? I agree, the web interface is very nice and smooth, but I believe it’s lacking functionality. I have no way to remotely manage malware pushed to the chest, clients no longer show up RED when a malware is discovered, and the deployment seems to be shaky at best (as evidince of this thread). Again this may be things I have not learned yet, just looking for answers.
For me the old ADNM console was very convoluted compared to competing consoles like Trend or Symantec. It was not easy to use at all if you have never worked with it. The new console is extremely easy to use. Install of the console is a breeze and deployment has worked very well for me with the exception of these settings issues. There are definately problems with the new interface but to me it appears it has the potential to be much better if these issues get resolved. Again, these small issues are holding it back. If they don’t get resolved then it is no better than the old one. I love the fact that I can access it from a web browser on any server I am logged into remotely. That is extremely useful for my team. We are a consulting firm so the fact that my techs can install this on a server easily and deploy clients and set settings centrally with no training the first time they do it is awesome.
Other than that, there was no way to centrally set exclusions in the old ADNM. That killed us in a couple of networks.
I have not had any malware detected so I haven’t noticed that it doesn’t show red. That is a huge problem I was not aware of.
I have just recently purchased the Business Protection Pro and now I am having problems with receiving and sending emails thru Outlook using the POP account? Do I need to make any kind of adjustements either in Avast or Outlook to repair this problem?
Issues are unfortunately only halfway fixed, and some new problems are happening. :-\
I have done some testing after updating to the new 1.1.132.15 and this is what has changed for my situation:
The newly installed clients now come up green, and the AntiSpam Shield is not installed. Fantastic! This includes not only new PCs without any Avast client installed, but PCs with the old 4.8 client installed are upgraded properly.
Unfortunately, after deploying and rebooting, the client shows with an expired license. A 2nd reboot was needed to clear the licensing state. But after the second reboot, the Avast client hangs for a couple minutes and the FileSystem Shield was not enabled. I had to open the client and click the Fix Now button and everything was resolved and the client now shows with no issues.
As far as the existing installs with AntiSpam Shields that are stuck on disabled, redeploying the client to these computers did not uninstall/cleanup the AntiSpam Shield. It stays in its current state with the AntiSpam Shield still installed but stuck on disabled and reporting the yellow question mark in the admin console.
What’s really interesting is that one of the old installs with the AntiSpam shield is now showing up as green in the admin console, even though the AntiSpam shield is still installed and stuck being disabled. The weird thing is I didn’t even touch this client. So nothing has changed and it is in the exact state as the other yellow exclamation PCs but it is showing green in the console. This makes no sense and is really throwing me for a loop.
The good news is for new BP console installs and new deployments I think it will probably work fine. I hope the second reboot and needing to click Fix Me was a one-time fluke for that computer. I’ll try additional test installs to see if it goes smooth. That is probably what Avast development was focusing on fixing. Unfortunately they left the early adopters of the new console hanging without a fix for their already deployed clients.
I’ll try emailing business support. So excited for the new update and so let down when it finally came out. But at least there is some progress for new installs.