Author Topic: Documentation Lacking for Remote Deployment  (Read 1394 times)

0 Members and 1 Guest are viewing this topic.

Offline Lt Lemming

  • Newbie
  • *
  • Posts: 14
Documentation Lacking for Remote Deployment
« on: March 21, 2019, 06:42:22 AM »
I've been scouring the documentation but am unable to find an answer to this one.

What interface/protocol does Avast use to query AD for the remote deployment?

Every time I try to do it on our network I just get "The Master Agent can not connect to Active Directory" but it doesn't tell me why it's failing.

Is there a log I can check to see where the error is?

Offline andrey.01015

  • Newbie
  • *
  • Posts: 6
Re: Documentation Lacking for Remote Deployment
« Reply #1 on: March 21, 2019, 04:07:25 PM »
ActiveDirectory by Microsoft or Samba server?

Offline Lt Lemming

  • Newbie
  • *
  • Posts: 14
Re: Documentation Lacking for Remote Deployment
« Reply #2 on: March 22, 2019, 03:34:09 AM »
Both.

Offline Gombos

  • Newbie
  • *
  • Posts: 1
Re: Documentation Lacking for Remote Deployment
« Reply #3 on: April 18, 2019, 08:42:44 AM »
Same problem here.... Do you have any solution yet?

Offline .: Mac :.

  • Avast √úberevangelist
  • Ultra Poster
  • *****
  • Posts: 5051
Re: Documentation Lacking for Remote Deployment
« Reply #4 on: April 24, 2019, 12:49:05 PM »
Can you provide more detail about your network? Are the console and the AD Controller on the same subnet? Is there any intra-VLAN routing happening? Often times there is an issue with firewalls or ACLs blocking access between the two.
"People who are really serious about software should make their own hardware." - Alan Kay

Offline Lt Lemming

  • Newbie
  • *
  • Posts: 14
Re: Documentation Lacking for Remote Deployment
« Reply #5 on: May 28, 2019, 05:08:43 AM »
Can you provide more detail about your network?

I'd rather not post details about our network in a public forum.

Are the console and the AD Controller on the same subnet?

Yes, but this is still the sort of information that should be included in the documents surrounding this.

Is there any intra-VLAN routing happening?

Lots, the domain controller and the master agent and clients all share one vlan though.

Often times there is an issue with firewalls or ACLs blocking access between the two.

Great! What ports? what protocols? in which directions?

NONE of this is documented besides one mention of port 7074 on the console page where it tries to connect to the domain controller.

In short, the documentation is as I've said. Severely lacking.

Offline mickey.b

  • Business Senior Support Technician
  • Moderator
  • Jr. Member
  • *
  • Posts: 64
    • Avast Business Technical Support
Re: Documentation Lacking for Remote Deployment
« Reply #6 on: June 11, 2019, 05:21:44 PM »
Every time I try to do it on our network I just get "The Master Agent can not connect to Active Directory" but it doesn't tell me why it's failing.

If you haven't already, please submit a case at https://www.avast.com/business-support-contact

Most likely, we will need to collect debug logs. Please also see How To Submit Avast Business Log Files for more information.
- Mickey B.
Avast Business Senior Support Technician
https://www.avast.com/business/support