Clients showing in console as grey icons

[tohoken]

I have some clients showing up in my console as grey icons meaning that they haven't communicated in a while with the AMS server.  When I check those clients everything appears to be running fine.  Any ideas as to why some clients are showing up as grey icons?  I have checked the Server side events and I see this entry:  User at <computername> has been automatically disconnected.  What could be happening?

[Vlk]

Is there anything relevant in the <avast>\data\log folder on the clients in question?
E.g. in error.log?

Thanks
Vlk

[tohoken]

There are no entries that relate to the clients in question.  Also, there is no error.log file.  The computers just seemed to have been "kicked off" by the server.  If they reboot then they show backup as green, however this will become a problem as our workstations aren't rebooted everynight.  Any ideas?

[tohoken]

As a follow up I have attached a .jpg of the server-side events showing clients getting disconnected.  There is always the same event ID and the object is always guest.  Any ideas?

[Vlk]

So can you confirm that as soon as you see this "automatically disconnected" message, the netagent on that client won't connect any more until it's restarted?
Could you also post a screenshot of the Computer Catalog? (or you can copy the data to clipboard by selecting the rows and using Ctrl+C).

Thanks Vlk

[Voltorb]

Here's what it looks like now.  By 10am, most will be gray.

[Vlk]

Do you have any scheduled tasks on that clients?

[Vlk]

Also, Voltorb, do you have the "automatically disconnected" messages in the Events folder?

[tohoken]

Vlk,

My catalog shows the same stuff as Voltorb's.  I do not have any scheduled tasks on the PC's.  Any ideas what could be causing this?

Thanks,

[Voltorb]

No scheduled tasks on any of the gray PC's.  If they reboot, they will come back to green until an hour or two after they log on.  Also, I have the same automatically disconnected messages in the log as above.  I'm willing to help test, or to further troubleshoot this issue.  I'm out of town until Sunday, but will be happy to try anything you suggest to resolve this issue.  Thanks for your consideration!

[Vlk]

The problem will be fixed in the next update. I think we've found and fixed the cause. Thanks.

[Voltorb]

Fantastic news!  I'll be looking for an announcement!

[tohoken]

That is great news.  Any ideas when the next update will be?  Also, is there a work around that we can take advantage of until the next release or do we just need to wait?

[Voltorb]

Vlk, Do you have an idea of when the update will be available to fix these issues?