Surface Ethernet Adapter Not Working
Microsoft Usb Ethernet Adapter Driver
Ethernet adapters and Surface deployment • • 5 minutes to read • Contributors • • • • • • In this article This article provides guidance and answers to help you perform a network deployment to Surface devices. Network deployment to Surface devices can pose some unique challenges for system administrators. Due to the lack of a native wired Ethernet adapter, administrators must provide connectivity through a removable Ethernet adapter. Select an Ethernet adapter for Surface devices Before you can address the concerns of how you will boot to your deployment environment or how devices will be recognized by your deployment solution, you have to use a wired network adapter. The primary concern when selecting an Ethernet adapter is how that adapter will boot your Surface device from the network. If you are pre-staging clients with Windows Deployment Services (WDS) or if you are using System Center Configuration Manager, you may also want to consider whether the removable Ethernet adapters will be dedicated to a specific Surface device or shared among multiple devices. See the section of this article for more information on potential conflicts with shared adapters. Best american football games for pc windows 7.
Booting from the network (PXE boot) is only supported when you use an Ethernet adapter or docking station from Microsoft. To boot from the network, the chipset in the Ethernet adapter or dock must be detected and configured as a boot device in the firmware of the Surface device. Microsoft Ethernet adapters, such as the Surface Ethernet Adapter and the use a chipset that is compatible with the Surface firmware. The following Ethernet devices are supported for network boot with Surface devices: • Surface USB to Ethernet adapter • Surface USB 3.0 Ethernet adapter • Surface Dock • Surface 3 Docking Station • Surface Pro 3 Docking Station • Docking Station for Surface Pro and Surface Pro 2 Third-party Ethernet adapters are also supported for network deployment, although they do not support PXE boot. To use a third-party Ethernet adapter, you must load the drivers into the deployment boot image and you must launch that boot image from a separate storage device, such as a USB stick. Boot Surface devices from the network To boot from the network or a connected USB stick, you must instruct the Surface device to boot from an alternate boot device. You can alter the boot order in the system firmware to prioritize USB boot devices, or you can instruct it to boot from an alternate boot device during the boot up process.
To boot a Surface device from an alternative boot device, follow these steps: • Ensure the Surface device is powered off. • Press and hold the Volume Down button. • Press and release the Power button. • After the system begins to boot from the USB stick or Ethernet adapter, release the Volume Down button. Note In addition to an Ethernet adapter, a keyboard must also be connected to the Surface device to enter the preinstallation environment and navigate the deployment wizard. For Windows 10, version 1511 and later – including the Windows Assessment and Deployment Kit (Windows ADK) for Windows 10, version 1511 – the drivers for Microsoft Surface Ethernet Adapters are present by default.
If you are using a deployment solution that uses Windows Preinstallation Environment (WinPE), like the Microsoft Deployment Toolkit, and booting from the network with PXE, ensure that your deployment solution is using the latest version of the Windows ADK. Manage MAC addresses with removable Ethernet adapters Another consideration for administrators performing Windows deployment over the network is how you will identify computers when you use the same Ethernet adapter to deploy to more than one computer. A common identifier used by deployment technologies is the Media Access Control (MAC) address that is associated with each Ethernet adapter. However, when you use the same Ethernet adapter to deploy to multiple computers, you cannot use a deployment technology that inspects MAC addresses because there is no way to differentiate the MAC address of the removable adapter when used on the different computers.