All Workstations Disconnected in SOA

Avast Business Avast Endpoint Protection
1

Using SOA version 1.1.132.15.

This morning, after uninstalling a version 8.x client and reinstalling a 7.x client on a Windows 7 Ultimate workstation to cope with the ongoing bogus “invalid certificate” issue, the reinstalled 7.x client was unable to connect to the server.

I opened the SOA to find it reporting that ALL client workstations are “disconnected”.

I rebooted the SOA server and checked again. All workstations still “disconnected”.

I can log into the SOA web interface remotely from another workstation. So there is no physical connection problem with the server.

I logged into the Avast! client running ON THE SERVER (the machine is not a server OS; it’s just Windows 7 Ultimate; it runs an Avast! client along with the SOA just fine). In the Avast! client on the server I did a virus pattern/engine update. The screen for this reported that the client WAS connected to the server, and it processed the update just fine. I then rechecked the SOA; it still reported that all clients, including the one I had just updated, were disconnected.

I then logged into the Avast! client running on a Windows XP machine. It reported that it was “connected” to the server. I ran a pattern/engine update on this client, which was successful. I then went back to the SOS. It still reports that all workstations, including that one, are disconnected, and have not communicated with the server since yesterday.

Now I have a machine on the network that is unprotected because it can’t get the license from the SOA.

Please don’t tell me to install the “new” SOA; I am not willing to risk losing the ability to retain use and control of version 7.x clients on this network until Avast! acknowledges and fixes the “invalid SSL certificate” bug.

So what can I do now?

2

This is apparently caused by a new problem: The SOA is spuriously claiming that my license is invalid. See my post “LicenseUtil.exe Windows Exception Code 0xc0000409”.

3

Had the same damn problem, had to manually install the new versions and download the setup from the link within SOA.

4

Are you saying you were unable to manage version 8.x clients from within the SOA version that comes with version 7.x?

Or are you saying you had to uninstall/reinstall all clients to get them to talk to the SOA?

The “license warning” message I’m now getting says pretty clearly that in the “waiting for trial” state the SOA won’t be able to connect to clients. Did you have a license warning?

5

What happened with me is once I updated the SOA to the newest release, I did a maintenance job and updated the program and definitions with the new SOA control panel.

Then I created a job to uninstall a few workstations for Testing. I also ran the deployment job without “Force” and then lost 95% of my workstations.

After which I became desperate, so I decided to run a full deployment again, this time with a full force and restart if needed and I gained about 75% of my workstations back.

The rest I manually went and upgraded them from their local machine.

Didn’t have time to waste here, waiting for support to never answer.

I think after this 130 days is up, I am possibly dropping Avast.

Then again, why bother with some other software that will have the same kind of problems.

Who knows.