MAC address is an identifier for endpoints that we want to use to compare PEAKS data against scans of our network. In that context it would be great if MAC Addresses could be moved up to full fields (not as dynamic attributes) for exporting ease rather than having to deal with data cleanup with attribute exports. If we can't easily export PEAKS data with MAC addresses to pull into a local database to compare against scan data, we will likely continue to maintain local equipment databases, which is a time waster. If a one-to-many setup for equipment to MAC address is not feasible, then even if we just got MAC1, MAC2, MAC3, and MAC4 fields put in as full fields, that would help with exporting the data to run queries against scan data to find unmatched endpoints.
MAC address is an identifier for endpoints that we want to use to compare PEAKS data against scans of our network. In that context it would be great if MAC Addresses could be moved up to full fields (not as dynamic attributes) for exporting ease rather than having to deal with data cleanup with attribute exports. If we can't easily export PEAKS data with MAC addresses to pull into a local database to compare against scan data, we will likely continue to maintain local equipment databases, which is a time waster. If a one-to-many setup for equipment to MAC address is not feasible, then even if we just got MAC1, MAC2, MAC3, and MAC4 fields put in as full fields, that would help with exporting the data to run queries against scan data to find unmatched endpoints.
Votes: 6 Author: jruhe Voters: jruhe,rcasteli,shchee,vanslyke,cfsiever,jlutang