{"id":12471,"date":"2011-10-07T00:01:00","date_gmt":"2011-10-07T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2011\/10\/07\/use-powershell-to-identify-your-real-network-adapter\/"},"modified":"2011-10-07T00:01:00","modified_gmt":"2011-10-07T00:01:00","slug":"use-powershell-to-identify-your-real-network-adapter","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/use-powershell-to-identify-your-real-network-adapter\/","title":{"rendered":"Use PowerShell to Identify Your Real Network Adapter"},"content":{"rendered":"

Summary:<\/strong> Learn how to use Windows PowerShell to identify easily the real network adapter.<\/p>\n

 <\/p>\n

\"Hey,Hey, Scripting Guy! I have a problem that perhaps you can assist with. I know about WMI, and I know there is a class that represents a network adapter. The problem is that when I run the command, I get back lots of stuff that is not a real network adapter. I am sure I am not the first person to see this problem, so I want to know how other people solve this problem.<\/p>\n

—BP<\/p>\n

 <\/p>\n

\"Hey,Hello BP,<\/p>\n

Microsoft Scripting Guy Ed Wilson here. This is one of the problems with technology—it is always changing. In the old days, it was relatively simple to use WMI to work with network adapters. All one needed to do was to choose the adapter that had the ipenabled<\/b> <\/i>property set to true<\/b>. An example of a script that uses this technique is in the How Can I Change the IP Address Assigned to a Computer?<\/a> blog post.<\/p>\n

On my laptop today, that approach still works. The command to find a network adapter that is IP enabled is shown here along with the associated output:<\/p>\n

PS C:\\> Get-WmiObject win32_networkadapterconfiguration -Filter ‘ipenabled = “true”‘<\/p>\n

 <\/p>\n

DHCPEnabled      : True<\/p>\n

IPAddress        : {198.134.88.47, fe80::fd99:3ef6:799f:dc0b}<\/p>\n

DefaultIPGateway : {198.134.88.1}<\/p>\n

DNSDomain        : portseattle.org<\/p>\n

ServiceName      : netw5v64<\/p>\n

Description      : Intel(R) Wireless WiFi Link 4965AGN<\/p>\n

Index            : 13<\/p>\n

Cool. However, there is a problem. This command retrieves the configuration of the network adapter; it does not get the network adapter itself. For example, if I want to change the IP address or the DNS server address, I use the Win32_networkadapterconfiguration<\/b> class. If I want to enable or disable a network card, I use the win32_networkadapter<\/b> class. The bad thing is that the Win32_Networkadapter<\/b> class does not have an ipenabled<\/b> <\/i>property. When I attempt to use such a command, an error is displayed such as the one shown here:<\/p>\n

PS C:\\> Get-WmiObject win32_networkadapter -Filter ‘ipenabled = “true”‘<\/p>\n

 <\/p>\n

Get-WmiObject : Invalid query<\/p>\n

At line:1 char:14<\/p>\n

+ Get-WmiObject <<<<  win32_networkadapter -Filter ‘ipenabled = “true”‘<\/p>\n

    + CategoryInfo          : InvalidOperation: (:) [Get-WmiObject], ManagementException<\/p>\n

    + FullyQualifiedErrorId : GetWMIManagementException,Microsoft.PowerShell.Commands.GetWmiObject Command<\/p>\n

The good thing is that both the Win32_networkadapterconfiguration<\/b> class and the win32_NetworkAdapter<\/b> WMI class both share the index<\/b> property. This means I can use the result of one query to feed into a query for the other class. In the following example, I find the network adapter that is ipenabled<\/b>, <\/i>get the index number of that adapter, and return the network adapter itself:<\/p>\n

PS C:\\> $a = Get-WmiObject win32_networkadapterconfiguration -Filter ‘ipenabled = “true”‘<\/p>\n

PS C:\\> $a.Index<\/p>\n

13<\/p>\n

PS C:\\> Get-WmiObject win32_networkadapter -Filter ‘index = 13’<\/p>\n

ServiceName      : netw5v64<\/p>\n

MACAddress       : 00:1F:3B:AD:FF:6D<\/p>\n

AdapterType      : Ethernet 802.3<\/p>\n

DeviceID         : 13<\/p>\n

Name             : Intel(R) Wireless WiFi Link 4965AGN<\/p>\n

NetworkAddresses :<\/p>\n

Speed            : 36000000<\/p>\n

Another way to find a specific network adapter is to look at the maker of the adapter or the description of the adapter. For example, on my laptop the same company makes both the wired Ethernet connection and the wireless network adapter. You cannot rely upon using only the network adapter that is connected, because more than one network adapter could be connected at the same time. Fortunately, both win32_networkadapter<\/b> and win32_networkadapterconfiguration<\/b> WMI classes contain a description<\/b> property. On my laptop, the two outputs are identical:<\/p>\n

PS C:\\> Get-WmiObject win32_networkadapterconfiguration -Filter ‘index = 13’ | select description<\/p>\n

 <\/p>\n

description<\/span><\/p>\n

Intel(R) Wireless WiFi Link 4965AGN<\/p>\n

 <\/p>\n

PS C:\\> gwmi win32_networkadapter -filter ‘index = 13’ | select description<\/p>\n

 <\/p>\n

description<\/span><\/p>\n

Intel(R) Wireless WiFi Link 4965AGN<\/p>\n

 <\/p>\n

One of the tricks I use so that I can always find the correct network adapter is assign specific names to the network adapters. Using WMI and the Win32_networkadapter<\/b> class, I can create a new name for the netconnectionID<\/b> property. This technique is shown here. Note<\/b>   This command requires administrator rights.<\/p>\n

$adapter = Gwmi win32_networkadapter -Filter ‘index = 13’<\/p>\n

$adapter.NetConnectionID = “ScriptingGuys”<\/p>\n

$adapter.Put()<\/p>\n

The commands and their associated output are shown in the following figure.<\/p>\n

\"Image<\/a><\/p>\n

The following figure shows that the command was successful.<\/p>\n

\"Image<\/a><\/p>\n

After I have an easy-to-use network adapter name, I can use it in queries directly:<\/p>\n

PS C:\\> gwmi win32_networkadapter -Filter ‘netconnectionid = “scriptingguys”‘<\/p>\n

 <\/p>\n

ServiceName      : netw5v64<\/p>\n

MACAddress       : 00:1F:3B:AD:FF:6D<\/p>\n

AdapterType      : Ethernet 802.3<\/p>\n

DeviceID         : 13<\/p>\n

Name             : Intel(R) Wireless WiFi Link 4965AGN<\/p>\n

NetworkAddresses :<\/p>\n

Speed            : 48000000<\/p>\n

I have always made it a practice to name my network adapters. In the past, it required a pretty extensive VBScript to accomplish<\/a>, or it required manual intervention (or it required using netsh). Now, a very short Windows PowerShell command accomplishes the task.<\/p>\n

Well, BP, that is all there is to working with the network adapter, index names, and NetConnectionIDs. I invite you to join me tomorrow for more Windows PowerShell cool tricks.<\/p>\n

 <\/p>\n

I invite you to follow me on Twitter<\/a> and Facebook<\/a>. If you have any questions, send email to me at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n

Ed Wilson, Microsoft Scripting Guy<\/b><\/p>\n

 <\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Summary: Learn how to use Windows PowerShell to identify easily the real network adapter.   Hey, Scripting Guy! I have a problem that perhaps you can assist with. I know about WMI, and I know there is a class that represents a network adapter. The problem is that when I run the command, I get […]<\/p>\n","protected":false},"author":596,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[37,3,4,45,6],"class_list":["post-12471","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-networking","tag-scripting-guy","tag-scripting-techniques","tag-windows-powershell","tag-wmi"],"acf":[],"blog_post_summary":"

Summary: Learn how to use Windows PowerShell to identify easily the real network adapter.   Hey, Scripting Guy! I have a problem that perhaps you can assist with. I know about WMI, and I know there is a class that represents a network adapter. The problem is that when I run the command, I get […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/12471","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/596"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=12471"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/12471\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=12471"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=12471"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=12471"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}