Hello,
My customer asked me to customize some of its profiling policies, namely to identify domain machines and which type. that was working fine.
Coming back one week after, I do see that some of the devices (7k in a universe of 26k) have an Unknown endpoint policy, yet when checking their details and profiled attributes I do see the attribute MatchedPolicy = windowsADpolicy as if they were correctly profiled (and they were last week).
None of the devices has had any static assignment (profile or identity group)
I see some Profiler queue size limit reached events in the alarms. Would bypassing the queue limit make as such as these devices are not set to the proper endpoint policy, even though they do match the correct profiling policy ?
The active profiler probes are DHCP, AD, DNS, SNMP, NMAP and RADIUS.
Has anybody seen similar behaviour or explain this strange behaviour?
Regards
Gustavo
