0 Replies Latest reply on Feb 22, 2011 5:21 PM by drewwurfel

    New Intel Gigabit CT adapter created on each machine

    drewwurfel

      We are in the process of trying to create a Win2k8R2 image that can be cloned to multiple machines (all with identical hardware).  The machine the image is being created on (machine A) has an onboard NIC that shows up in device manager as "Intel(R) 82578DM Gigabit Network Connection", and an add in card that shows up as "Intel(R) Gigabit CT Desktop Adapter". After the image from machine A is applied to machine B, on machine B the onboard NIC retains all of its settings from machine A but the add in card NIC gets a new device instance named "Intel(R) Gigabit CT Desktop Adapter #2" which now has all of the defaults.  Looking through the Device Instance Path's; the on board NIC has a number appended to the end that looks like X&XXXXXXXX&X&XX and does not change across motherboards, the add in card NIC has what looks like the mac address with some extra bytes in it (for example, if the MAC was 11-22-33-44-55-66 then 112233FFFF44556600 would be appended to the Device Instance Path).  My first thought is that, in the case of the add in card, the driver or OS is appending the MAC to establish uniqueness across the system; something that you already have guaranteed for the onboard.  The problem with this is that no settings will persist when imaging to another machine or when swapping the NIC.  Does anyone know if there is a way around this; essentially an override for when the OS or Driver will consider the hardware it sees as being a new node. NOTE: the addin card NIC will always be plugged into the same slot.