AMS damaged from adding second AMS

Avast Business Avast Distributed Network Manager
1

I did not see any thing that looked like this problem, so sorry if this has been covered and I missed it.

I am implementing an Avast roll-out here at the company I am working for. I installed and configured the AMS, created a MSI package, and began rolling out the net clients to the desktops (not using any server clients at the moment). Things seemed to be working just as intended. The server configuration included a weekly scan, daily pattern updates, daily infection reports, and weekly coverage reports. All of these tasks ran fine for a few weeks while the clients were being installed.

This company has more than one location, so to cover the other large office, we decided to add a second AMS to cover those machines. Both are located on separate subnets, both private and connected via the office firewalls (10.0.1.X and 10.0.3.X). The second server was installed by the instructions in the Admin guide and the secondary AMS subscribed to the first AMS. I was trying to create an MSI package for the second AMS clients, when I noticed that the scheduled and run tasks were not running. Also all the clients from the 1st AMS no longer show as on-line (black icon instead of green). When the clients are ‘pinged’ they show as connected, but the server still does not see them. It has now been a few days and resets later (services and machines), and none of the clients seem to be talking to the AMS anymore. Nor are any of the scheduled tasks running that were previously working fine. I have tried separating the AMS servers and getting things back to the state they were in with one AMS, to no avail.

At about the same time the second server was installed, I updated the ADMN tools and programs on both AMS machines to the latest version. Is there some thing I can do to refresh the first AMS machine and get it working like it was before and any ideas why adding a second AMS server might cause this.

Any help in this matter will be greatly appreciated.

2

Hi,

first, I didn’t quite understand your network topology.

So, the two AMS’ are in different (geographical) locations? If so, how are they connected with each other (private line, VPN etc)? Do they “see” each other?

Can the machine with AMS A e.g. ping (or even directly connect to) the machine with AMS B?

Did the “Subscribe to Root AMS” command complete successfully?
Are you using MSDE or full SQL?

Thanks
Vlk

3

The two networks are at to separate sites, both firewalled and using two separate ISPs. The Firewalls have a VPN tunnel between them to route traffic between the two sites.

Both machines are in the same AD Domain and can ping and connect to each other.

I believe the “Subscribe to Root AMS” worked. I had to attempt several times, but finally I did not get an error message when connecting and the ‘subscribing’ server was listed on the server list of the Root server.

We are using MSDE on both of the servers. Also, I did go through the steps to activate the Named Pipes and TCP/IP on both MSDEs.

Since talking to you, I have attempted to break the connection between the two by deleting the ‘subscribed’ server from the root. I have been attempting to move back to the previous state, before the connection of the two servers. This seems to have had no effect on the root server (where most of my problems are evedent).