0 Replies Latest reply on Aug 22, 2011 2:09 PM by joeleisenlipz

    Network scanning with power management

    joeleisenlipz

      We are having difficulty managing duplicate asset records, due in part to workstations that are "sleeping". It would seem that no amount of rescanning and tinkering with the Asset Matching Rules will prevent a duplicate asset record from being created.

       

      Example:

      Scan 1 = WRKSTN001 is found, and is awake. Full details are available, using credentials.

       

      Scan 2 = WRKSTN001 is found, but is asleep.

      IP and DNS name are populated in a new (duplicate) record, but no MAC and no OS. <-- This should be merged based on Matching Rule, but isn't.

       

      Scan 3 = WRKSTN001 is found, and is awake. Full details are available, using credentials, no duplicate is created.

       

      Scan 4 = WRKSTN001 is found, but is asleep.

      IP and DNS name are populated in a new (duplicate) record, but no MAC and no OS. <-- This should be merged based on Matching Rule, but isn't.

       

      Scan 5 = WRKSTN001 is found, but is asleep.

      IP and DNS name are populated in a new (duplicate) record, but no MAC and no OS. <-- This should be merged based on Matching Rule, but isn't.

       

       

       

      Now I have 4 records for the same asset... no bueno!

       

      Am I missing something?

       

      Thanks,

      --Joel