![]() In the above log, the device lookup result did not return a matching record from the database and it treats this device as "unknown". ![]() Log file snippet of SMSPXE.log: This is a boot attempt of Surface Pro 3 (B) with default Configuration Manager PXE enabled DP and Unknown Computer support enabled. Note that the lookup occurs using both the MAC and SMBIOS GUID (UUID) of the device to try to find a matching existing record. If either MAC or SMBIOS GUID(UUID) is found in the database then the device is "known".ĥ0:1A:C5:FE:AA:8C, 11F6E606-84D1-4E74-AF7C-3B54377D15E3: device is not in the database. After the devices are completely installed, they will connect to corporate network via WLAN or a docking station with a built-in Gigabit Ethernet port.Įxample of a classic PXE initiated deployment with unknown computer support enabled Please note that this scenario could use a device similar to a USB to Ethernet adapter that provides a wired Ethernet connection such as aĬonsider the below Surface Pro 3 (A) and Surface Pro 3 (B) have to be installed using the same Surface Ethernet Adapter. This is a common scenario for companies running a dedicated imaging location for new devices before handing them over to their end users. As an example we are going to image severalĪnd started via PXE. The USB to Ethernet Adapter is used because the devices lack a built in Ethernet port and ConfigMgr OSD does not support imaging the devices using the built in wireless NIC. You are using a single USB to Ethernet Adapter to image multiple devices via a ConfigMgr OSD Task Sequence. Please see the below link for further information:Ĭonsider the following scenario. ![]() The solution in the below blog post is now a native feature in ConfigMgr starting in ConfigMgr Current Branch 1610. First published on TECHNET on Aug 27, 2015 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |