Author Topic: failure to manage clients from SOA  (Read 1721 times)

0 Members and 1 Guest are viewing this topic.

Offline dave49

  • Newbie
  • *
  • Posts: 1
failure to manage clients from SOA
« on: December 08, 2016, 11:34:21 AM »
I have installed SOA on a windows 10 machine in the office, created a group for the SBS2011 server and left all the other machines in the default group.
most if not all machines already had End point protection installed but not the managed version.

i had to change the forced restart setting as it forced the restart of 4-5 machines repeatedly when it ran the deploy/update job, the users were getting upset that every 20mins or so their PCs would just shut down with no option to delay.

The only machine that SOA has managed to install End point protection on is the machine SOA is installed on.(i think)
9 further machines it claims are disconnected (despite from here being able to see from my desk that at least 5 are in use at this moment)
the rest "have never been sucessfully connected to the Avast SOA"

i set this up on monday and was expecting that by thursday it would have managed to install on every machine by now.

any great ideas?

Offline .: Mac :.

  • Avast √úberevangelist
  • Ultra Poster
  • *****
  • Posts: 5080
Re: failure to manage clients from SOA
« Reply #1 on: December 15, 2016, 01:16:17 AM »
So this is a workstation that the SOA console is installed on?

First ensure this workstation has a static IP address. Then check that the clients can reach this machine, try disabling the windows firewall to see if this allows the clients to connect.
"People who are really serious about software should make their own hardware." - Alan Kay