Managed Clients & hair pulling

Avast Business Avast Endpoint Protection
1

I’d be lying if the previous ADNM+V4 managed client system was particularly reliable, but moving over to AEA+v7 seems borderline impossible. In two days, I have successfully managed to get two workstations to show up as having the agent installed; the rest just sit there and won’t talk to the server.

Does anyone have any hit lists of things to try? I’ve tried removing the old managed client, using the removal tool, then installing. I’ve tried installing over the top (which removes v4), and I’ve tried doing the former routine repeatedly.

I’m trying not to make this a rant, but I’m at that point where I’m about to scrap the whole system.

2

Review the firewall rules in the AES. Here are the ports that AEA use: http://forum.avast.com/index.php?topic=107144.0

When we have to migrate our customers from ADNM 4.8 to AEA 7, this is the procedure we use:

  • We create a task in ADNM 4.8 to uninstall avast! NetClient and avast! NetServer 4.8 in the machines. Reboot.
  • We create a task in AEA 7 to install new avast! in the computers that were uninstalled in the previous task. Reboot.
3

Hi there, thanks for the reply.

These are things I’ve tied, although to rule out firewalls, I have disabled them on both the server and clients.

(bloody recaptcha!)

4

Try to add the FW rules anyway.

You could also make the following test:

  1. Ping the server.
  2. Ping few of the clients.
  3. NSLOOKUP the server hostname/FQDN from the clients and check the resolved IP address.
  4. NSLOOKUP the server IP address from the clients and check the resolved hostname/FQDN.
5

He there,

I’ve done so, and network connectivity (and DNS resolution) is fine. I’d settle for manually installing EPS on each machine, and directing it to the server, but there doesn’t seem to be an option for specifying the server when doing so.

6

Well in that case the entAgent.log could help us identifying the issue.
You can locate the file in:
C:\ProgramData\AVAST Software\Avast\log or C:\Documents and Settings\All Users\Application Data\AVAST Software\Avast\log

Cheers

7

Thanks for your reply. This is the basic (repeated) information on one of the problem machines:

[2012/11/22 16:41:55.683,312] CClient::Popup() entered...
[2012/11/22 16:41:55.683,896] Going to popup information from server...
[2012/11/22 16:41:55.683,896] CClient::GetConnection() entered, m_dwConnCount=0
[2012/11/22 16:41:55.683,896] Session for processing requested
[2012/11/22 16:41:55.683,896] Going to initialize adnmClient.dll...
[2012/11/22 16:41:55.683,896] Synchro timeout: 15000
[2012/11/22 16:41:56.699,896] DNS of local computer: GSL-DAR
[2012/11/22 16:41:56.699,896] Local IP address: 192.168.100.201
[2012/11/22 16:41:56.699,896] Cannot obtain server address!!!
[2012/11/22 16:41:56.699,896] Obtained server IP address: 0.0.0.0
[2012/11/22 16:41:56.699,896] Creating server connection socket...
[2012/11/22 16:41:58.965,896] Cannot obtain LAST server address!!!
[2012/11/22 16:42:07.964,896] Cannot connect to the server, winsock error 0x7FFF1001 occured...
[2012/11/22 16:42:07.964,896] Cannot initialize socket object, error 0x7FFF3002 occured...
[2012/11/22 16:42:07.964,896] Connection to server created with 0x7FFF3002 error code...
[2012/11/22 16:42:07.964,896] clnAgentConnection() failed with 0x7FFF3002 error
[2012/11/22 16:42:07.964,896] Cannot connect to server, error 0x7FFF3002...
8

[2012/11/22 16:41:56.699,896] Local IP address: 192.168.100.201
[2012/11/22 16:41:56.699,896] Cannot obtain server address!!!
[2012/11/22 16:41:56.699,896] Obtained server IP address: 0.0.0.0
[2012/11/22 16:41:56.699,896] Creating server connection socket…
[2012/11/22 16:41:58.965,896] Cannot obtain LAST server address!!!

Are you sure that NSLOOKUP resolved the IP address correctly?

Also you could check the following avast5.ini settings:
[Communication]
ServerAddress=Here-You-Should-See-Your-AEA-Server-Address

[AdnmSettings]
ServerAddress=Here-You-Should-See-Your-AEA-Server-Address

The file is located in:
C:\ProgramData\AVAST Software\Avast\log or C:\Documents and Settings\All Users\Application Data\AVAST Software\Avast\log

9

Resolution is definitely ok.

The plot does appear to thicken; the ServerAddress property in avast5.ini has no value!

10

Maybe, when you created the installation package you didn’t put the IP address for the AES.

11

That’s the weird thing; I definitely did. I recall using the detect function, so I’ll try it manually tomorrow. Thank you for your help today.

12

You can also try to create a new A Record in your DNS called avastms pointing to the IP address of the management server.
I am not sure if that will work, since this was a feature in 4.8. Only avast! Team may know the answer.

13

Hi again,

Just popping in to say thank you. After deleting the deployment task and recreating it, the installation package was used correctly and the clients received the appropriate server information.

14

Great! :wink: