Hi Avast Brainiacs!
We have been looking through the documentation and some of the forums and have yet to find a definitive answer for the “Best Practice” method of configuring Avast Netclient on Laptops that roam in and out of the network. We are a bit leery of opening additional attack surface on our firewall by opening ports on the outside interface for the roaming clients to connect to and update defs and check in. We have also thought about running Avast pro as a stand alone but then we are unable to efficiently check AV status from ADNM. What I would like is a way to tell the Avast installation on the laptops to try and contact the Avast server for updates, and on communications failure, go out to the net and download them from there. Anyone come up with a good way to do this?
Actually, it’s already setup like that.
If you take a managed client laptop away from the network, it will automatically download updates from the internet if the Avast Management Server cannot be contacted.
However, if you make changes to the way that the client behaves, the laptop that is away from the network won’t get updated with that info until it gets back on the network. Other than that, your setup should work fine.
Thanks Scythe!!
The documentation is a little unclear on this. It does indicate that it will try to contact the management server a certain number if times but it doesn’t indicate that it will go out and download defs from the inet. Yes totally understood that management tasks will not be applied to roaming clients until they return to the LAN and check in. Thanks again for the quick reply.
You’re quite welcome, and belated welcome to the forums.