If these computers are able to download packages from ePO server then it means they can connect through the agent-to-server port so they should also be able to upload their config package.
You can try to launch a cmdagent /s from one computer that appears as unmanaged and check if it can upload a package to ePO. If it's able to upload then it must appear in ePO console but perhaps duplicated so try to make name search or ip search from main panel
I suspect these unmanaged PCs can be having duplicate GUIDs and could show as unmanaged in Detected Systems.
Do you employ PC images in creating new systems? Like reimaging some of the old PCs that previously were managed?
Thank you for your answer. Done some progress. cmdagent /s run OK and no duplication. But have noticed that all machine set as unmanaged are moved to Rogue systems but also remain on their container ! When I push back the machine to their container for some reason EPO bring them back to rogue. Most of the impacted machine are used by remote user.
Thank you in advance for your assistance.
EPO 4.5 sp 3
Vs8.7 sp 3
HIPS 7 1159
The answer may lie with your ePO server version. ePO 4.5 patch 3 is not yet blocking clients with invalid GUID. Remote users likely to connect via VPN which could assign the same MAC to all clients (seeing from inside the corporate network). When the clients disappear from ePO directory (because of "-no-show") and later reappear, ePO searches for their GUID, does not find it, then searches for the MAC and finds one (for the very first user connecting via VPN, ePO won't find the MAC and therefore creates its record, but for any further clients it does not) to which it thinks that client belongs to.
So this way practically most of the remote clients reports to one single node record and picks up policies, tasks of that record, and they appear in parallel in Rogue systems, because RSD won't find their node record.
As far as I remember from ePO 4.5 patch 4 you will have the option to have these duplicate clients listed in the database, and ePO will block them/reject them.
Ultimate solution is to upgrade to agent version 4.0 P3 or 4.5 and upgrade ePO as well (at least to Patch 6) so the automatic GUID regeneration can take place. Please consult KB67473. Be warned that you need to enable two server tasks for this feature to work!
Also, please read article KB52949 on how to prevent the above VPN confusion from occurring.
Thank you for the answer. Since couple of days we noticed that the same pb occur on other EPO servers in others Domain (server in product since many year without any recent change) Have tested all the recommendations from the KB you've passed me no change. Now I start upgrading from EPO 4.5 p3 to 4.