I am having a problem where the computers that the endpoint AV is pushed to manage to move themselves into the unmanaged group randomly. Has anyone else seen this or know of a solution? 
It may be a license file issue. View the license file in the console. Is there more than 1 product, or more than 1 date?
Sincerely,
J.R. “AutoSandbox Guy” Guthrie
“At this point in time, the Internet should be regarded as an Enemy Weapons System!”
Thanks for the reply J.R. but in the license area there is a file for one product with one date…
It also seems kinda random as to when it does it…
I had 1 system a couple of weeks ago that was acting exactly like this, and it turned out to be a corrupted database. The database itself had doubled in size for no apparent reason. So, we were not able to backup and restore that database to a new SOA console. If the new console has the same IP address and DNS name, then the clients do not have to be re-deployed.
I had another case where there was incorrect data in the “ini” files in the console. I believe the fault here was wrong IP or DNS of the SOA in that ini file. That customer acknowledged at some point he used wrong data that caused it. That console was also reloaded to clear the issue. Both of these occurred within the last month. Both were solved with a reloaded console.
Remember, we are NOT like Symantec. When our console is NOT online, the clients will update to the avast! update mirrors in the cloud if they haven’t seen a console in 4 hours. Symantec systems completely stop updating if the console fails or is offline.
Sincerely,
J.R. “AutoSandbox Guy” Guthrie
“At this point in time, the Internet should be regarded as an Enemy Weapons System!”
Finally figured out what is making it do it.
We are doing an incremental rollout at the same time we are adding computers to the network.
I find that everytime we push avast out from the server it moves all the computers into unmanaged.
Is it supposed to do this?