Avast WEBforum
Business Products => Archive (Legacy) => Avast Business => USA Education Products => Topic started by: nibabin on January 09, 2013, 10:56:07 PM
-
Hey all I am having some trouble getting the license to push out to my clients. I'll step you through my progress thus far:
I installed the Avast Enterprise Administration Console and and created a install package to be pushed out to all my clients on the network. The deployment hit most servers, but only about 10% end users. The ones that did receive the install package installed just fine but without the valid license. I am not sure what I need to do to have the install package hit all my end users and have them properly licensed.
-
This or something very similar has happened to me. I decided to deploy in phases. First computer lab worked Aok, and I am thinking "this is simple." Second lab the install worked, but the clients tell me they are running in trial mode. I did not see any errors reported during the installation. I was using the simple console, not the enterprise edition.
Any ideas?
-
Well I tried your suggestion. I created a new group and placed about 10 clients in. I ran the deployment to that group but I got the usual error 0x00000005 which from what I've found off this site is mainly about wrong login credentials. I know I have the correct login in DOMAIN\username format.
Any other ideas?
-
Hello,
Please make sure (if your AEA) that your not over your license count which could end in trial licenses being pushed to the client. If your over your license count you will see a key icon over the client that your trying to push to. Remember that the license count includes both Dynamic Computer Groups (With and Without Server) so if you have old PC's on the Active Directory it's best to remove them to free up the space for the license to push.
The error code 00000005 is either due to a wrong administrative password or not restarting the clients. IF the user name is correct then after the deployment restart the client then refresh the console and you should see that the clients are now seen by the console.
I hope this helps but if not please send an email to edu@avast.com for further help.
Kind Regards
-
Another issue, if your deploying to XP client please be sure the file / printer sharing is enabled or the client will not receive the remote deployment, for Vista or Win 7 please disable the UAC.
Also make sure the ports are open on both the client and server prior to deployment.
-
Has anyone found a solution for this? I have installed the EDU free version on a 2008 R2 server. When an install was pushed to the server there was no issue. An install pushed to a client machine Win 7 installs a trail version. I have plenty of licenses.
-
Usually, you have a client communication port that is not open, when you push, but get no license (AEA):
In a new AEA installation, the default firewall rules configured automatically are:
avast! ADNM Agent access: TCP 16111
avast! ADNM AMS discovery: UDP 6000
avast! ADNM Cisco NAC access: TCP 16103
avast! ADNM Console access: TCP 16102
avast! ADNM Mirror access: TCP 5033
But, you need:
AEA Mirror: TCP 16135
AEA Client Communication Port: TCP 16136
AEA Client Communication Port: TCP 16139
And you have to configure these manually in the Windows Firewall.
Thanks again to Ed!
-
Check to see if your over the license count which consists of both groups in the Dynamic computer group. To check, go to the Dynamic Computer group and find the client with the trial license and see if it has a key icon over it, if so, then your over the license count and I would recommend deleting old PC's so that there is room to push to the license.
-
Thank you J.R. This seems to have resolved the issue!
-
You are welcome! (-:
-
I find it hard to believe that we would need to go to each client computer and open ports or make sure something is disabled in order to make a remote install work. This might be fine with a few pc's but what about places that have hundreds of desktops, laptops, multiple office buildings, etc.? I might have to give this up and look for another solution if a better solution is not found.
-
I only had to open the ports on the server side to make this work. If I had to open ports on all my computers I would do it through the GPO.
Dave
-
The Network Admin can open certain ports for clients on a network so there not done manually. In most cases, clients on an Active Directory or even workgroup can be managed through the network including ports. You can always disable the firewall on all the clients as well however many users rather not, and only open the suggested ports.
Regards
-
I am testing Avast free for Education and have a one year subscription status. At the end of that year how do I go about renewing my license file?
Thanks in advance
-
You will be prompted prior to the renewal but we will soon be having our current EDU customers create a My AVAST account where you will be able to do this directly.
-
How do I request for additional license for our district? Thanks.
-
How do I request for additional license for our district? Thanks.
-> http://forum.avast.com/index.php?msg=949686
-
Just contact us at edu@support and your license seats can be increased, just provide your license customer number.
-
Our licence is for 275 clients.
I have installed the client on only three machines, the only three listed in the console:
- Server
- PC1
- PC2
The Server's client gets the licence and policy fine when the client is deployed. The PC1 & PC2 machines get the client when deployed, but not the license or policy.
After trying to open every port I could find in the AEA guide and the forums on both the server and the clients (Windows 7), I just turned the firewall completely off on both of them. Somewhere I remember seeing it suggested to turn on File and Printer sharing, so I also tried that.
There is no hardware or other software firewall between the server and the clients. In this case they are even on the same switch for testing purposes. They are in the same domain. The admin privileges are working because it installed the client software.
edit: The two clients with no license show up as 'grey'. Not with the 'key' icon that I have seen suggested in other posts in the forums. The client on the server shows as 'green'.
edit2: I also removed the client from the server, in case it there was a conflict there. No change, still no license/policy on the PC1 & PC2 machines.
What else could be causing the licenses/policies from getting to the client machines?
/* Thomas */
-
After reading some more forum threads today, i read a couple about DNS and IP resolution problems. Apparently this was my issue.
When I created package, it automatically "detected" the server name as the fully-qualified DNS name. However, there is no DNS pointed to this test server, the AES was attempting to resolve it as a full DNS name. The clients then had a server DNS resolution error in the log. When I changed the deployment package to point the correct server name, the clients received the licence and policy correctly.
If anyone else seems to have issues, you might check to make sure the server name is correct and that it has the correct IP or DNS name. I figured that the AES knew what it was doing. Apparently the AES just guesses, so double check the server name/IP in your deployment package if your server does not have full a full DNS record.
/* Thomas */