Avast NetClient on Laptop

[nounzio]

Hello,

Sorry for my english, I'm french.

We start to deploy Avast with ADNM and we have a little question before doing deployment on our laptops.
People who have laptops can be disconected from our Network (LAN witch ADNM on a server) during several weeks.
They have Internet at home, and our question is : continuous Avast to update itself or must it be connceted with our server (in our LAN) to be updated ?

Thanks

[Vlk]

This is described in the ADNM Administrator's Guide, section 6.4.
http://files.avast.com/files/eng/adnmag.pdf

6.4 Licensing in ADNM
The ADNM provides a very flexible licensing model. All license checking is done on the server. That is, as long as the managed machines are in touch with the server, they use (inherit) its license. There is no need to manually distribute the license file to the clients. In fact, the license file is not even present on the individual machines. This prevents theft of the file. If the license on the server expires, it automatically expires on all the clients, too.

This works in most cases, but not for laptops, which are not permanently connected to the server. The ADNM handles such situations by requiring the notebooks to connect to the server at least once every 21 days. This value is hard-coded into the program and cannot be overridden. After three weeks, all the managed products on the client machine will stop functioning until a connection to the server is established and the server provides a valid license. This includes virus database update.

Note: If someone needs to take a machine out of reach of the AMS for longer than 21 days, a separate license file copy must be locally provided to the machine by hand.

[daaje]

This is described in the ADNM Administrator's Guide, section 6.4.
http://files.avast.com/files/eng/adnmag.pdf

6.4 Licensing in ADNM
The ADNM provides a very flexible licensing model. All license checking is done on the server. That is, as long as the managed machines are in touch with the server, they use (inherit) its license. There is no need to manually distribute the license file to the clients. In fact, the license file is not even present on the individual machines. This prevents theft of the file. If the license on the server expires, it automatically expires on all the clients, too.

This works in most cases, but not for laptops, which are not permanently connected to the server. The ADNM handles such situations by requiring the notebooks to connect to the server at least once every 21 days. This value is hard-coded into the program and cannot be overridden. After three weeks, all the managed products on the client machine will stop functioning until a connection to the server is established and the server provides a valid license. This includes virus database update.

Note: If someone needs to take a machine out of reach of the AMS for longer than 21 days, a separate license file copy must be locally provided to the machine by hand.

How do you do that?  Is it possible to transfer a license from the AMS to remote computers, decreasing the license count on AMS by the number of remote computers which are licensed?  I see that it is possible to open a hole in the firewall but don't think this is a feasible option.