Mac agents going unmanaged

[acidfire52]

We have an issue with our Mac clients going unmanaged in ePO. Seems to affect Mojave and Catalina. Agent version from 5.60 to 5.6.6 ePO version is 5.10. Found a KB talking about agents going unmanaged if ENS was installed manually instead pushed from ePO, but we are pushing ENS from ePO. Agent is installed manually since it difficult to push from ePO. We have lost hundreds of Macs from the console. Anyone else seeing this behavior?

[cdinet]

Are they in actual unmanaged mode, or just failing to communicate?  You might need to open ticket with McAfee as we will need to see agent and server logs to see what is going on.

[acidfire52]

They go unmanaged in ePO, but if i remote in and run a agent send props it checks back in, but not till then.  Will open the ticket.

Thanks

Ash

[cdinet]

Once an agent checks in as managed, as in their previous state, the only way it will show unmanaged is if it is a new entry in epo.  The never change from a managed to unmanaged state in epo in the original entry.  Are you removing old agent and reinstalling?  If so, that would give the system a new agent guid, hence a new entry in epo.  However, that new entry should be managed if the agent checked in.  So, the question is, how is the system tree being populated?  The only way an unmanaged system would show up is if a new system is added either manually, add systems by file and add to system tree, or by active directory sync.  Otherwise, if an agent checks in on its own, it will always be in a managed state.  Check for duplicate entries.