System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

Add support for using one USB Ethernet adapter with multiple computers

With many laptops and tablet devices not having wired Ethernet adapters built in, it is necessary to use USB Ethernet adapters to use OSD with these systems. However, Configuration Manager currently associates the MAC address of the adapter with the first computer it was used on, which causes issues re-using the adapter. Please add an option for the MAC of the USB Ethernet adapter to be automatically removed from Configuration Manager at the end of the OSD sequence. Only the built in wireless adapter should be associate with the device after OSD.

80 votes
Sign in
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Joe shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: facebook google
Signed in as (Sign out)
  • maria smith commented  ·   ·  Flag as inappropriate

    First, if you only wish to share internet connection and not files, both computers need not belong to the same workgroup. All you need to do is to connect the two computers with the Ethernet crossover cable, and then turn on Internet connection sharing in the computer that already has an Internet connection.
    if anyone face outlook issue click here

  • john smith commented  ·   ·  Flag as inappropriate

    In order to physically connect three or more computers, you should use a crossover Ethernet cable. You must be able to plug the Ethernet cables into a device that will allow signals to be transmitted to one another. There are several devices that will allow you to do this: a hub, a switch, or a router.

    If anyone face router issue gets help from this

  • TimW commented  ·   ·  Flag as inappropriate

    This new feature is a backward step compared to managing it via the registry on the primary site server.
    In the new feature you have to MANUALLY add each MAC address by typing it in, you cannot copy and paste the list (e.g. from the registry string) or from a text file.
    No powershell comdlet?

    Waste of time implementing it if it is that broken!!
    We have 200 adapters globally that we need to exclude (approx 5 per office) and this new interface is useless.

  • BankimP commented  ·   ·  Flag as inappropriate

    Allow administrators to determine known/unknown treatment based on MAC Address OR SMBIOS GUID so that in scenarios where the same adapter is being used for imaging Surface devices, duplicate MACs still allow Unknown machines to boot into WinPE.

  • Rico Rosenlund commented  ·   ·  Flag as inappropriate

    SMBIOS GUID is set on the machine and is, as a rule, always unique.
    When PXE booting a machine, ConfigMgr. will first check for deployments to the machine using the SMBIOS GUID before falling back to MAC address.
    This has been true since SCCM 2007 and works just fine for machines without built-in LAN using the same USB adapter.
    So when importing the machine into SCCM, just make sure to add both the SMBIOS GUID and MAC address,

  • Jay Connor commented  ·   ·  Flag as inappropriate

    I think OSD should force it to register the computer with it's SMBIOS GUID if the computer is unknown. This wont break importing via MAC for different situations.
    In addition to this ConfigMgr should have an option to choose the unique identifier it registers such as serial number if the customer has a bad OEM that doesn't have unique GUIDs.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Agree with the comment from Joe. Lenovo being a big lover of non- on-board NIC's on many devices. Cost & logistics of having to use a unique USB NIC for each device to eliminate the MAC issue is annoying. There are ways of removing the MAC systematically but this is not quick enough if you are using a small pool of USB NICs to rotate around a large mobile device deployment in a relatively short timescale.

  • Robby Moeyaert commented  ·   ·  Flag as inappropriate

    Also, and this is more towards the Windows team rather than the ConfigMgr team, add WiFi support to WinPE already!

Feedback and Knowledge Base