/build/static/layout/Breadcrumb_cap_w.png

KACE reporting incorrect MAC addresses

Hello all. Our KACE is showing 78 devices with the same mac address. I cannot figure out why. When I do an ipconfig /all, the machines show their true MAC address. Why would 78 out of 200 devices show the same MAC address when at least the ones I have checked show a completely different MAC. I am not even sure where that MAC address came from.

2/16/2018 update: I had a web-ex session with Quest Support and found that in the inventory xml file, every network adapter is listed with the one listed at the top as primary. So, on our devices showing the same MAC address, they all have RAS Async Adapter listed as the primary netowk device. I have been searching online for two hours trying to figure out what this is and how I can disable it. I believe it may have something to do with remote access to the computer, but I cannot confirm that. I seriously have no clue exactly what this is and how to demote it or turn it off. Is anyone familiar with RAS Async Adapter on Windows 7?

7 Comments   [ + ] Show comments
  • Are the erroneous hardware addresses appearing in a report or in the actual inventory? If it's a report, can you post your query? - chucksteel 6 years ago
    • It is appearing in the inventory as reported from the agent. I have a report that runs and emails the the results each night prior to the rules that set the asset information to match the inventory information in the event that something goes wrong. I have all the information prior to the rule running so I can hopefully correct any errors in information. the report that runs is using the query:
      SELECT
      A.ID AS AID,
      A.ASSET_TYPE_ID AS ATID,
      A.NAME AS ANAME,
      M.NAME AS MNAME,
      AD5.FIELD_10003 AS SERIALNUMBER,
      AD5.FIELD_10011 AS AOS,
      M.OS_NAME AS MOS,
      AD5.FIELD_10008 AS AMANUFACTURER,
      M.CS_MANUFACTURER AS MMANUFACTURER,
      AD5.FIELD_10012 AS AIP,
      M.IP AS MIP,
      AD5.FIELD_10013 AS AMAC,
      M.MAC AS MMAC
      FROM MACHINE M, ASSET A, ASSET_DATA_5 AD5
      WHERE A.NAME = M.NAME
      AND A.ASSET_DATA_ID = AD5.ID
      ORDER BY AD5.ID

      The MAC address in the Machine table (Inventory) is directly from the agent on the device and that is where the information is incorrect. So I am not sure how to correct it since it is not editable as far as I can tell. - jessburd 6 years ago
      • If you run a more simple query like:
        SELECT NAME, MAC FROM MACHINE
        are they all the same then? - chucksteel 6 years ago
      • Yes. And if I add the MAC address column to the Inventory table, they show there as the same. And disturbingly, we now have 85 devices with that MAC address... - jessburd 6 years ago
  • My only guess would be that KACE is picking up some intermediary network device (like a switch or router) that the affected devices are connecting through. - JasonEgg 6 years ago
    • They are spread out though our various locations, each location in a different gateway. There does not appear to be a common device that all are hitting. Other devices in the same locations are showing up correctly. I did notice this, they're all windows 7 computers. No Windows 10 computers and not all Windows 7 computers are showing it. But all that do show that stray MAC are WIN 7. - jessburd 6 years ago
      • Were all of these machines imaged with the same image? Perhaps there is something in the image causing the agent to pick up the wrong address. - chucksteel 6 years ago
      • I honestly do not know. These are all computers that were already in place when I started working here. It is crazy that when I check the details on the network or do an ipconfig /all, the MAC addresses are showing as something else. - jessburd 6 years ago
  • My only other thought is that your rule to update the asset is changing the machine table, that doesn't seem very likely, but I guess it is possible. Does the machine history show that the MAC is changing? - chucksteel 6 years ago
    • I checked a computer that has been in the inventory the longest (since 05/09/2017). It shows no changes to the MAC address during the entire machine history.

      An interesting tidbit is that they are all windows 7 computers. None of our Windows 10 computers are showing this odd MAC and not all Windows 7 computers are showing it. But all that do show it are WIN 7.

      My rule to set the asset information regarding the MAC address is as follows (It doesn't hurt to have another set of eyes see this again but like you, I don;t think it is likely as over 100 computers are correct in KACE as far as I can tell):
      SELECT AD5.ID
      FROM ASSET_DATA_5 AD5
      JOIN ASSET on ASSET.Asset_Data_ID = AD5.ID and ASSET.ASSET_TYPE_ID = 5
      JOIN MACHINE on MACHINE.ID = ASSET.MAPPED_ID
      WHERE AD5.FIELD_10013 != MACHINE.MAC

      UPDATE ASSET_DATA_5
      set FIELD_10013 = (select
      MACHINE.MAC
      FROM ASSET
      JOIN MACHINE on MACHINE.ID = ASSET.MAPPED_ID
      where ASSET.ASSET_DATA_ID = ASSET_DATA_5.ID and ASSET.ASSET_TYPE_ID = 5)
      where ID in (<TICKET_IDS>) - jessburd 6 years ago
  • Delete one of the machines from the inventory and force an inventory from the command line. That should create a new inventory record. - chucksteel 6 years ago
  • Okay, check this out. I had a web-ex session with Quest Support and found that in the inventory xml file, every network adapter is listed with the one listed at the top as primary. So, on our devices showing the same MAC address, they all have RAS Async Adapter listed as the primary netowk device. I have been searching online for two hours trying to figure out what this is and how I can disable it. I believe it may have something to do with remote access to the computer, but I cannot confirm that. I seriously have no clue exactly what this is and how to demote it or turn it off.

    At the moment, I do not have access yet to select "Don't allow connections to this computer" under the Remote tab in system properties so I cannot disable it on the computer that I am testing (the user is out of the office so I have free reign at the moment).

    So, is anyone familiar with RAS Async Adapter on Windows 7? - jessburd 6 years ago
  • I also have this problem with our Dell Optiplex 3010s. Kace is aware of the issue and it is currently in the bug fix state. Looks like it was not fixed in the latest update. - breanne 6 years ago
  • it's 2020, a year later and the issue still continues.
    I was told "the defect id is K1-19884."
    The problem is that the KACE Agent grabs the first IP from the list of different adapters that are installed on the local machine.
    This has the potential of grabbing the Wireless, BT or any other adapter. I have about 8 on my Dell laptop. - IDeLeon007 4 years ago

Answers (0)

Answer Summary:

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ