Author Topic: AEA Console and Remote Clients  (Read 2934 times)

0 Members and 1 Guest are viewing this topic.

VCW

  • Guest
AEA Console and Remote Clients
« on: December 04, 2013, 11:25:28 PM »
We have a server running AEA with different groups within the computer catalog to manage different clients. When creating our installation package we set the EAS Server to remote.domain.com and everything worked fine. Well, now we have a new public IP address and previously installed clients are no longer communicating with the console. Installations since the new public IP address are communicating so we know it's working correctly.

Looking at the avast5.ini file on prior installations under LastServerAddress= shows our old public IP address. What I'm thinking is that when it's initially installed it resolves the remote.domain.com address and puts the public IP address into the avast5.ini file and never checks again. Is there a way to force these clients that are no longer communicating to update the IP address?

nannunannu

  • Guest
Re: AEA Console and Remote Clients
« Reply #1 on: December 04, 2013, 11:34:58 PM »
do you have a way to get these remote clients to run a program or script?

Anyway, if you can it would be trivial to compile a script to use the iniread and iniwrite function in autoit to check for an imporper value and write the proper value into that file.

http://www.autoitscript.com/autoit3/docs/functions/IniRead.htm
http://www.autoitscript.com/autoit3/docs/functions/IniWrite.htm

« Last Edit: December 04, 2013, 11:46:32 PM by nannunannu »

VCW

  • Guest
Re: AEA Console and Remote Clients
« Reply #2 on: December 05, 2013, 04:28:10 PM »
How do you propose getting around the ini editing permissions lock?  I did some research on the forums, and people suggested opening an elevated notepad to edit the file, but that hasn't worked.  We've only been able to hand edit in safe-mode.

nannunannu

  • Guest
Re: AEA Console and Remote Clients
« Reply #3 on: December 05, 2013, 05:19:26 PM »
I believe it would work as a login script item if you have it set to run avast services after others load, but if didn't already have that set, that option is out too...

Offline JayZ

  • Avast team
  • Newbie
  • *
  • Posts: 13
Re: AEA Console and Remote Clients
« Reply #4 on: December 06, 2013, 11:27:52 AM »
The easiest solution is to simply redeploy a new installation package with the new server address over the old installation.

Barring that, if you could get the new server on the address of the old one for a short time to use the console to disable the self-defense (under troubleshooting options) that is blocking the ini, you could then use the script to change the inis.