There could be plenty scenarios where you may need to know your device IP address, including when you need to let other users access resources (e.g., files or printer), when setting up an internet connection, or to troubleshoot network problems.

Whatever the reason it might be, typically, most Windows 10 users would just launch Command Prompt and run the IPConfig tool to find out the current TCP/IP configuration. However, if you have a Surface Laptop or another device running Windows 10 S, you won't have access to Command Prompt, PowerShell, or any other command-line app.

Thankfully, if you're running Windows 10 S, there are still ways to find the IP address assigned to your device using the Settings app, Task Manager, Control Panel, and even System Information.

1. Jan 11, 2014  Talking of the MAC address, you can now find it easily using the Modern Interface, plus there’s the same old method of using the command prompt as well. Method 1 – Using the Modern Interface Find the Physical Address of MAC Address in the Modern Interface of Windows 8.1 is a very easy and straightforward process.
2. Jun 11, 2016  How to locate/change MAC Address in Windows 10/8.1 on Surface Pro Posted on June 11, 2016 by Windows 8 rt/pro The MAC Address is hardware address assigned by the manufacturers of network interface cards and are resolved by Address Resolution Protocol.

In this Windows 10 guide, we'll show you four quick ways to find your device TCP/IP configuration without having to use command-line tools.

How to find IP address using Task Manager

Here's how to find your MAC address in Windows 10 so you can use it in your router settings. Surface Laptop 3 Fail. (or 'media access control') address. You can find the MAC address for.

The quickest way to find the current IP address of your device is using Task Manager.

1. Right-click the Taskbar and select Task Manager.
2. Click the More details button if you're using the experience in compact mode.
3. Click the Performance tab.
4. Select the network adapter.

In the network adapter section, you'll find your current IPv4 and IPv6 configuration of the device.

2. How to find IP address using Settings

On Windows 10 S, the Settings app is another place you can use to look for the networking configuration of your device.

Wi-Fi

1. Open Settings.
2. Click on Network & Internet.
3. Select Wi-Fi.

4. Click the wireless network you're connected.

Under 'Properties,' you'll find your current network address in the IPv4 address field. Additionally, in this section, you'll find other networking information, such as the DNS address, wireless signal protocol and SSID (Service Set Identifier), MAC address and more. However, for some odd reason, you won't find your current IPv6 information.

Ethernet

1. Open Settings.
2. Click on Network & Internet.
3. Select Ethernet.

4. Click the Ethernet connection.

Under 'Properties,' your IP address will be displayed in the IPv4 address field.

3. How to find IP address using System Information

On Windows 10 S, you can even use the System Information tool to figure out the IP address and other networking information about your device.

1. Open Start.
2. Search for System Information and click the result to open the tool.
3. Expand the Network group.
4. Select Adapter.

On the right side, look for the name of your adapter, and you'll find your current address next to the IP Address field, but note that if your adapter has IPv4 and IPv6 configurations, they both will appear in the IP Address field.

4. How to find IP address using Control Panel

Alternatively, you can use the networking options within Control Panel to see the IP address currently assigned to your device along with several other networking configurations.

1. Open Control Panel.
2. Click on Network and Internet.

3. Click on Network and Sharing Center.

4. On the left pane, click the Change adapter settings option.

5. Double-click the network adapter you want (e.g., Wi-Fi or Ethernet0).

6. In the 'General' tab, click the Details button.

In 'Network Connection Details,' the IP address for your device will be shown in the IPv4 Address field. If you're looking for the IPv6 address of your device, then this information will be shown in the Link-local IPv6 Address field.

Also, note that in this section you can find a lot of additional information, such as physical address (MAC), DNS address, whether your device is using DHCP server to obtain its TCP/IP configuration and the TCP/IP lease expiration date.

More Windows 10 resources

For more helpful articles, coverage, and answers to common questions about Windows 10, visit the following resources:

Microsoft may have delayed Windows 10X and Surface Neo beyond 2020

Microsoft's upcoming Windows 10X and Surface Neo products may not be shipping in time for the holiday after all, according to a new report from ZDNet's Mary-Jo Foley. This means that other Windows 10X devices from third-party manufactures also won't be launching at the end of this year like originally planned. Microsoft's dual-screen Windows 10X effort has been put on pause.

This article provides guidance and answers to help you perform a network deployment to Surface devices including Surface Pro 3 and later.

Find Mac Address Microsoft Surface 1

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 Microsoft Endpoint 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 Manage MAC addresses with removable Ethernet adapters section of this article for more information on potential conflicts with shared adapters.

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 Surface Dock use a chipset that is compatible with the Surface firmware.

The following Ethernet devices are supported for network boot with Surface devices:

• Surface USB-C to Ethernet and USB 3.0 Adapter

• Surface USB 3.0 to Gigabit 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:

1. Ensure the Surface device is powered off.
2. Press and hold the Volume Down button.
3. Press and release the Power button.
4. 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.

The simplest solution to avoid MAC address conflicts is to provide a dedicated removable Ethernet adapter for each Surface device. This can make sense in many scenarios where the Ethernet adapter or the additional functionality of the docking station will be used regularly. However, not all scenarios call for the additional connectivity of a docking station or support for wired networks.

Another potential solution to avoid conflict when adapters are shared is to use the Microsoft Deployment Toolkit (MDT) to perform deployment to Surface devices. MDT does not use the MAC address to identify individual computers and thus is not subject to this limitation. However, MDT does use Windows Deployment Services to provide PXE boot functionality, and is subject to the limitations regarding pre-staged clients which is covered later in this section.

When you use a shared adapter for deployment, the solution for affected deployment technologies is to use another means to identify unique systems. For Configuration Manager and WDS, both of which can be affected by this issue, the solution is to use the System Universal Unique Identifier (System UUID) that is embedded in the computer firmware by the computer manufacturer. For Surface devices, you can see this entry in the computer firmware under Device Information.

Surface 3 Os

To access the firmware of a Surface device, follow these steps:

1. Ensure the Surface device is powered off.
2. Press and hold the Volume Up button.
3. Press and release the Power button.
4. After the device begins to boot, release the Volume Up button.

New Microsoft Surface Pro 5

When deploying with WDS, the MAC address is only used to identify a computer when the deployment server is configured to respond only to known, pre-staged clients. When pre-staging a client, an administrator creates a computer account in Active Directory and defines that computer by the MAC address or the System UUID. To avoid the identity conflicts caused by shared Ethernet adapters, you should use System UUID to define pre-staged clients. Alternatively, you can configure WDS to respond to unknown clients that do not require definition by either MAC address or System UUID by selecting the Respond to all client computers (known and unknown) option on the PXE Response tab in Windows Deployment Server Properties.

The Surface Pro

The potential for conflicts with shared Ethernet adapters is much higher with Configuration Manager. Where WDS only uses MAC addresses to define individual systems when configured to do so, Configuration Manager uses the MAC address to define individual systems whenever performing a deployment to new or unknown computers. This can result in improperly configured devices or even the inability to deploy more than one system with a shared Ethernet adapter. There are several potential solutions for this situation that are described in detail in the How to Use The Same External Ethernet Adapter For Multiple SCCM OSD blog post on the Ask Premier Field Engineering (PFE) Platforms TechNet blog.