As mentioned in this document Understanding Machine Groups and the Machines View agent scans will not update the machine groups in View > Machines because View > Machines is only updated through an agentless scan. Therefore you will have to can the machines agentlessly in order to put them in a certain group in View > Machines. There is no work around for this.
I have solved My Problem. In the machineview I have grouped my machines to Agendpolicy. Now I can see, wich (agend)Group need some updates.
So if my machines are remote, and cannot be scanned "agentlessly," I cannot put them in a machine group? Is that what I'm understanding?
1 of 1 people found this helpful
Your understanding is correct. There is not currently a workaround to the matter of agents going into a no name group. As previously mentioned, the machines would need to be able to be scanned agentlessly first in order for them to appear in a specified machine group. My best recommendation to make this known that you would like to see this changed is by submitting a feature request as this goes directly to our product manager to assess the need for this option to be added in future releases of Protect.