We just did a fresh install on a network of 35 computers (they already had avast! pro/server), and are updating to the managed edition step-by-step.
I finished a few clients with the netclient version, the client shows the message “cannot read license file” when the avast splash screen appears. (when the user opens avast)
However, when right clicking the avast! icon, pressing “about” and then license, it says it uses a managed license. No date is mentioned though…
Is this normal behaviour? Or am I missing something?
Is this a bug? Because this is what’s stopping me from deploying the netclient to all the other computers. (to avoid problems for myself in the near future)
I have completely reinstalled all severs that are on my network as far as the O/S is concerned, rejoined every server back to my domain, and then isntalled avast after I installed my server applications. I get the same screens and everything that are listed in this thread. I am about to have to migrate an entire company to these severs and need this AV to coopperate with me. Has anyone found a solution? I have only one difference in my licensing files have more licenses, and the fact that I’m running Enterprise Edition SP-1 of Server 2003.
What is an avaliable solution, I’ve already tried to uninstall and reinstall the ADNM, and cleints after a full uninstall. What else can I try??? I have also talked to my sales rep for tech support, and has passed this on to Alwill as well, I need a solid solution very quickly…
the same problem, there is a message on client’s computer:
“cannot read license file”
I thought if client’s computer couldn’t connect to adnm server, but everything was fine, I could ping adnm server…
Up until now I didn’t upgrade the ‘whole network’ yet, but the client’s being invoiced for the licenses.
Is it safe to upgrade all clients, because the warning on the license does seem to give a different impression. Or should we await a bugfix of ADNM/Netclient ?
A netclient program update (4.7.599) has just been released, and fixes the issue. All you need to do is update to this latest build (as soon as your mirror gets synced - which has probably already happened) and the problem should be solved.