Avast Enterprise Edition Administration

[NorCalTechSupport]

I have the newest version of Avast and several hundred seats.  I am in testing phase now as I am moving from Avast 4.8 to 7.0. 

I have detected my network and found all 4 domains with great success.  I have installed Avast 7 on Windows 7 and Windows 8 and none of my four test installs received the licenses? 

What do I need to do to push the licenses with the install package?

[avast@@dvantage77.com]

The client port is not open.  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.

[NorCalTechSupport]

Thanks for the Firewall tip.  I guess I am off to writing a new rule or 3 for my Active Directory users.

[NorCalTechSupport]

By default all of my Windows Firewalls are turned off so does this mean I need to open these ports on my Routers?  Thanks in advance.

[avast@@dvantage77.com]

Your license file may mot be compliant with the new console, if it has not been converted.  Please email it to me, and I can check it.  J.R.

[NorCalTechSupport]

I have sent my Licenses.avastic to Avast and to Robert @ Inland Tech Support (my vendor) and everybody says my licenses file is fine but for some reason my test computers are not getting a licensed copy of Avast installed when I push Avast out? 

Your TCP/IP protocol blocking just may be my problem as I have the routers set to block when in doubt and I only open ports when I find they need to be opened.

[NorCalTechSupport]

My network has the TCP & UDP ports blocked to the outside world but there is no blocking between my many sites thanks to VPNs running throughout the network.  My 150 mile long network is a big LAN not a WAN thanks to VPNs.  I run several medical, dental and Tribal Government offices within my network so for privacy and security reasons I am very hesitant to open ports to the outside world.

Why do I need the TCP & UDP ports open to the world if they are open within my network?

My ".avastic" licenses file has been sent back to my vendor, then off to Avast themselves and then the vendor got me to send him the one repaired by Avast and when it came back in it's 3rd iteration it finally only shows up as a single year's license file and not 2 licenses about to expire and the good one covering a years time.

If for security reasons I am unable to open my network's outside TCP & UDP ports does anyone know how to create a MSI package that includes the licenses file?  I have tried twice to create a MSI package and each time it is Avast sans the licenses file?

[frankcz]

tought that same setup would work.. license reset on reboot for us...

[NorCalTechSupport]

I have Avast Server working and creating MSI packages with the licenses included.  Turns out I missed checking the Server box where the EAS licenses server lives. 

Now I want to see if I can do the push and I am betting I can as the aforementioned TCP & UDP ports are open in my network just not out to the internet.

Somehow I got my PC deleted from the domain list so does anyone know how to get a computer back in the domain list?  I ran the Find Computers Server side task over night but my PC did not come back?  I may try running it again?

PS When I get finished figuring out the Push I think I will make a quick 10 picture manual on how to get Avast running on a 300 computer network.  Now that the MSI package works I have real hope for this program.

[NorCalTechSupport]

OK, I got my Push Installer running.  In the Client Side task I made a new push installer and fought with it for awhile but I am getting very close using the MSI package I built last week.  By fight I mean the domain field is filled in with my subdomain and the administrative account has the same subdomail entered:  ie subdomain\admin is the admin user name.

Now I think the only thing I am fighting is a conundrum.  My MSI packake deletes my old Avast and installs the new version 7 just fine.

My MSI package when delivered with a push from Avast will result in an error simular to this one:
03/11/13 11:04:40:   InstSvc begin
03/11/13 11:04:40:   avast! Remote Install Service
03/11/13 11:04:40:   Avast is installed in C:\Program Files\Alwil Software\Avast4
03/11/13 11:04:40:   DSA_FileVerify C:\Program Files\Alwil Software\Avast4\Setup\Sfx\avast.setup error
03/11/13 11:04:40:   InstSvc end 0

So what I did was manually delete the old Avast from the Windows 7 Control Panel / Programs & Features

Then I tried my push routine again, the one that generated the above error and everything works.  Avast installed.  So I guess I have to find a way to delete "old" Avast from my client machines using Avast and then chain my "push" routine to the delete routine?  Does anyone have any good ideas as to why my MSI package just works from the desktop and fails from a push?