I just installed AEA on 2003 server and then deployed Avast Endpoint Protection Suite Plus to the same server and it does not show Green in the console and tells me that is only 29 days remaining of the trial. So it is not taking the wright subscriton. I have deploey to Win XP and that is OK.
Please help?
Till the client is not connected with the AEA/EAS its uses own licence. After the connection between the client and AEA/EAS will be established new licence is downloaded from the server.
The connection is ok. I created Installation packages and deployed to the server. This server that I am talking about is runnig the AEA so it should be talking to it self.
How do I establish connection between the client and AEA?
Try to stop the firewall in your server. Maybe the ports are blocked!
or stop the AEPSP firewall or put the exception on the firewall configuration
There is now firewall active on the server and I am not using AEPSP firewall. Any ideas?
Is there some .ini file that tells the client to talk to specific server?
If the communication between client and server is not being blocked, you can verify avast5.ini file. Location of this configuration file is: C:\Documents and settings\All users\Application data\Avast Software\Avast\avast5.ini.
Make sure, that the IP/DNS name of the server is correct.
Self-defense module has to be disabled in avast! settings., before you will be allowed to make changes in it.
Did you already reboot the server?
the client installation needs a reboot to be propperly communicating with the EA service i have noticed on my clients.
Yes I have done that every time after the deploy.
I have also changed the avast5.ini file (took it from Win XP machine that is communicating) and it still does not communicate with the AEA server. All firewalls are off.
I have tried many ways to deploy the package to this machine and it always says “Subscription status: IN TRIAL MODE”
remembers me of an old problem from the ADNM 4.x version. Exact same problem. The server that was running the ADNM console (in this case the EA console) couldnt deploy to itself or communicate with itself propperly
I have no sollution for you at this moment for this.
If you manually update, where do the updates come from? (im assuming internet server)
Maybe you can run a packetsniffer to capture network traffic
then manually do an update (even if it is up to date)
save the sniff in a logfile
see in the packets if the update tries to get in contact with the console on the ports it uses for this
post the log file here for Avast to analyse maybe?
Ok, now the status is like this.
If have two Win7 and one Win XP communicating with the AE server
If have one Win XP, one Win 2003 and one Win 2008 that do not communcate with the AE server.
I cannot continue to deploy onto more clients and servers with this problem hanging over me. :o
Check the setup.ini what is the FailSafeServer value? it is c:\avast~
It is like this FailSafeServer=http://10.1.1.80:16135
That is the IP of the AEA server
how about avast! Enterprise Client service the status is started? and what happen when you do the vps update…
btw, there is any ACL on your switch configuration?
if your EA server running with firewall, please stop the firewall or add the exception.
The Enterprise Client is started. Ther should not be any ACl on our switch. The firewall is stopped on the server.
On the client I have stopped the firewall also but nothing happend. If i go to browser and put http://10.1.1.80:16135 I get the index of all the updates.
odd, the situation must be no problem.
test this solution, put the license manually to the problem client then do the vps update by click the update button.
do some test installation to the others PC and make sure when you create the package installation the ea server must selected.
I know see that 3 clients that are communicating with the AEA server are not updating the VPS. If I manually update I get already up to date. How is the best way to test connection from the client to the server?