Starting way back with Current Branch 1610, Configuration Manager has a feature to handle these USB network adapters that you might have missed (I did for a couple branch builds). Microsoft happens to make both devices without Ethernet ports and the tool that manages them, so we’re in luck. There are several fixes that have been used over the years including modifying task sequence deployment settings, deleting the client associated to the USB network adapter in SCCM, or even running a scheduled CM database query.
#Mac image for deployment mac#
Since USB network adapters tend to get around, their MAC addresses are no longer unique to a single system and you can’t reuse them without some cleanup in the SCCM console.
This collection is commonly used for OS deployment because it’s safe (it protects existing systems from being imaged) and easy (new hardware will PXE-boot out of the box with no additional setup). This meant that by default, a USB network adapter would be associated with a system after deployment and wouldn’t be allowed to PXE-boot another system without some additional configuration.Ī more technical explanation: Configuration Manager has a special collection called “Unknown Computers” that contains all systems that are not managed (their MAC address and GUID do not exist in the CM database). Not only was the port missing, but the MAC address which was previously hard-coded to a system was now “portable” across devices using the same USB network adapter. A few years ago (ok, maybe a decade) when laptops/tablets started shipping without Ethernet ports, it threw a wrench in the PXE-booting process used for OS deployment. PXE-booting has been around for a long time and is still used today for OS deployment in Configuration Manager and many other tools.
0 kommentar(er)
