id like to note that this only happens if i use IP Fingerprinting.
Not a known problem ... and I'm pretty sure I used IP Fingerprinting on a 2008 R2 based LANDesk Management Suite 2016.3 Core ... (though that customer is also moving to Server 2012 at least ).
... so the logical steps would be:
- Pull up a clean (test) server - see if the issue duplicates.
- If it's a recent version (9.5 is already EOL for a while, 9.6 started going EOL) then we may look at it.
- ... either way, I'd really recommend switching over to Server 2012 or a Server 2016 based Core (with v-next, we should support Server 2016) truth be told - for security consideration alone.
Hope that helps?