100024  self closes when there is no wmi violation.
When there is a violation triggered by the scan engine with action_param = mac = $mac, tid = 100002, type = INTERNAL then it does not close itself. I configured the violation to allow the user to self remediate (e.g. uninstall an unwanted software) end re-enable network access.

Il 10/08/2017 16:44, Akala Kehinde ha scritto:
Hi Cristian,

The 100024 id doesn't trigger. No logs, nothin. Only the 100025 does.
Just to be sure of the Reg. and Post Reg scan operations, the Reg.scan works just when authenticating and the Post Reg. after authentication. And does the violation (the wmi violation itself) self close when you don't fix it?

Mammoli Cristian
System administrator
T. +39 0731 22911
Via Brodolini 6 | 60035 Jesi (an)

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
PacketFence-users mailing list

Reply via email to