![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/3757.Sat007.png\" "\\"Image")
<\/a><\/p>\nNote<\/b> PowerShell Saturday #007<\/a> will be held in Charlotte, North Carolina on February 8, 2014. This will be an awesome chance to meet and to learn from some of the best PowerShellers around. In fact, five of the speakers are also speakers at the PowerShell Summit this year. There are a limited number of tickets still available for this event, so you’ll want to sign up now. The Scripting Wife wrote a great post that provides a quick overview of the event: Psst…Charlotte PowerShell Saturday Details Leaked<\/a>.<\/p>\n One of the great things about Windows Management Instrumentation (WMI) is the way that it can provide detailed information. The bad thing is that it requires a specialist level of knowledge and understanding to effectively use it and to understand the information. (Either that or a good search engine, such as BING<\/a>, and an awesome repository of information, such as the Script Center<\/a>.)<\/p>\n One of the cool things about Windows PowerShell, since version 1.0, is that it provides easier access to WMI information. The bad thing, of course, is that it is still wrestling with WMI, which some IT pros seem to hate (or at least dislike). The great thing about using raw WMI is that it provides compatibility with older versions of the operating system. For example, using raw WMI and Windows PowerShell would make it possible to talk to Windows XP, Windows 2003 Server, Windows 2008 Server, Windows Vista, Windows Server 2008 R2, and Windows 7, in addition to the modern operating systems of Windows 8.1, Windows 8, Windows Server 2012 R2, and Windows Server 2012.<\/p>\n So how do I do it? I used to be able to find our real network card by finding the one that was bound to TCP\/IP. I would query the Win32_NetworkAdapterConfiguration WMI class, and filter on the IPEnabled<\/b> property. Using this approach, I would have done something like this:<\/p>\n Get-WmiObject -Class Win32_NetworkAdapterConfiguration -filter "IPEnabled = $true"<\/p>\n The problem with this methodology these days is that some of the pseudo adapters are also IP enabled. The previous command would eliminate many, but not necessarily all, of the adapters.<\/p>\n A better approach is to look at the Win32_NetworkAdapter class and query the NetConnectionStatus<\/b> property. By using this technique, I return only network adapter devices that are actually connected to a network. Although it is possible that a pseudo adapter could sneak in under the wire, the likelihood is more remote. In this command, I will use the Get-WmiObject<\/b> Windows PowerShell cmdlet to return all instances of Win32_NetworkAdapter class on the computer. I then create a table to display the data returned by the NetConnectionStatus<\/b> property.<\/p>\n Get-WmiObject -Class Win32_NetworkAdapter |<\/p>\n Format-Table -Property Name, NetConnectionStatus –AutoSize<\/p>\n The fruit of our labor is somewhat impressive. I have a nice table that details all of the fake and real network adapters on our laptop, and the connection status of each. Here is the list from my laptop:<\/p>\n Name NetConnectionStatus<\/p>\n —- ——————-<\/p>\n WAN Miniport (L2TP)<\/p>\n WAN Miniport (PPTP)<\/p>\n WAN Miniport (PPPOE)<\/p>\n WAN Miniport (IPv6)<\/p>\n Intel(R) PRO\/1000 PL Network Connection 2<\/p>\n Intel(R) PRO\/Wireless 3945ABG Network Connection 0<\/p>\n WAN Miniport (IP)<\/p>\n Microsoft 6to4 Adapter<\/p>\n Bluetooth Personal Area Network<\/p>\n RAS Async Adapter<\/p>\n isatap.{51AAF9FF-857A-4460-9F17-92F7626DC420}<\/p>\n Virtual Machine Network Services Driver<\/p>\n Microsoft ISATAP Adapter<\/p>\n Bluetooth Device (Personal Area Network) 7<\/p>\n 6TO4 Adapter<\/p>\n Microsoft 6to4 Adapter<\/p>\n Microsoft Windows Mobile Remote Adapter<\/p>\n isatap.launchmodem.com<\/p>\n isatap.{647A0048-DF48-4E4D-B07B-2AE0995B269F}<\/p>\n Microsoft Windows Mobile Remote Adapter<\/p>\n WAN Miniport (SSTP)<\/p>\n WAN Miniport (Network Monitor)<\/p>\n 6TO4 Adapter<\/p>\n 6TO4 Adapter<\/p>\n Microsoft 6to4 Adapter<\/p>\n Microsoft Windows Mobile Remote Adapter<\/p>\n isatap.{C210F3A1-6EAC-4308-9311-69EADBA00A04}<\/p>\n isatap.launchmodem.com<\/p>\n Virtual Machine Network Services Driver<\/p>\n Virtual Machine Network Services Driver<\/p>\n Teredo Tunneling Pseudo-Interface<\/p>\n isatap.{647A0048-DF48-4E4D-B07B-2AE0995B269F}<\/p>\n There are two things you will no doubt notice. The first is that most of the network adapters report no status what-so-ever. The second thing you will notice is that the ones that do report a status do so in some kind of code. The previous table is therefore pretty much useless! But it does look nice.<\/p>\n A little work in the Windows SDK looking up the Win32_NetworkAdapter WMI class, and I run across the following information:<\/p>\n Value Meaning<\/p>\n 0 Disconnected<\/p>\n 1 Connecting<\/p>\n 2 Connected<\/p>\n 3 Disconnecting<\/p>\n 4 Hardware not present<\/p>\n 5 Hardware disabled<\/p>\n 6 Hardware malfunction<\/p>\n 7 Media disconnected<\/p>\n 8 Authenticating<\/p>\n 9 Authentication succeeded<\/p>\n 10 Authentication failed<\/p>\n 11 Invalid address<\/p>\n 12 Credentials required<\/p>\n The value of 2 means the network adapter is connected. Here is the command I wrote to exploit the results of our research.<\/p>\n Get-WmiObject -class win32_networkadapter -filter "NetConnectionStatus = 2" |<\/p>\n format-list -Property [a-z]*<\/p>\n Such ecstasy is short lived, however, when I realize that although I have indeed returned information about a network adapter that is connected, I do not have any of the configuration information from the card.<\/p>\n What I need is to be able to use the NetConnectionStatus<\/b> property from Win32_NetworkAdapter and to obtain the TCP\/IP configuration information from the Win32_NetworkAdapterConfiguration WMI class. This sounds like a job for an association class.<\/p>\n In VBScript, querying an association class involved performing confusing AssociatorsOf queries. (Refer to the MSPress book, Window Scripting with WMI: Self Paced Learning Guide<\/a> for more information about this technique.)<\/p>\n By using the association class with Windows PowerShell, I come up with the FilterAssociatedNetworkAdapters.ps1 script shown here:<\/p>\n FilterAssociatedNetworkAdapters.ps1<\/p>\n Param($computer = "localhost")<\/p>\n function funline ($strIN)<\/p>\n {<\/p>\n $num = $strIN.length<\/p>\n for($i=1 ; $i -le $num ; $i++)<\/p>\n { $funline = $funline + "=" }<\/p>\n Write-Host -ForegroundColor yellow $strIN<\/p>\n Write-Host -ForegroundColor darkYellow $funline<\/p>\n } #end funline<\/p>\n <\/p>\n Write-Host -ForegroundColor cyan "Network adapter settings on $computer"<\/p>\n Get-WmiObject -Class win32_NetworkAdapterSetting `<\/p>\n -computername $computer |<\/p>\n Foreach-object `<\/p>\n {<\/p>\n If( ([wmi]$_.element).netconnectionstatus -eq 2)<\/p>\n {<\/p>\n funline("Adapter: $($_.setting)")<\/p>\n [wmi]$_.setting<\/p>\n [wmi]$_.element<\/p>\n } #end if<\/p>\n } #end foreach<\/p>\n I begin the script by using a command-line parameter to allow us to run the script remotely, if needed. I use the Param<\/b> statement to do this. I also create a function named funline<\/b> that is used to underline the results of the query. It makes the output nicer if there is a large amount of data returned.<\/p>\n Param($computer = "localhost")<\/p>\n function funline ($strIN)<\/p>\n {<\/p>\n $num = $strIN.length<\/p>\n for($i=1 ; $i -le $num ; $i++)<\/p>\n { $funline = $funline + "=" }<\/p>\n Write-Host -ForegroundColor yellow $strIN<\/p>\n Write-Host -ForegroundColor darkYellow $funline<\/p>\n } #end funline<\/p>\n I print out the name of the computer by using the Write-Host<\/b> cmdlet as shown here. I use the color cyan so the text will show up nicely on the screen…unless of course your background is also cyan. Then the output will be written in invisible ink. That might also be cool.<\/p>\n Write-Host -ForegroundColor cyan "Network adapter settings on $computer"<\/p>\n Then I get down to actual WMI query. To do this, I use the Get-WmiObject<\/b> cmdlet. I use the –computername <\/b>parameter to allow the script to run against other computers, and I pipe the results to the ForEach-Object<\/b> cmdlet.<\/p>\n Get-WmiObject -Class win32_NetworkAdapterSetting `<\/p>\n -computername $computer |<\/p>\n Foreach-object `<\/p>\n I need a way to look at the netConnectionStatus<\/b> property of the Win32_NetworkAdapter class. This class is referred to by the reference returned from the association query. It is called element. To gain access to this class, I use the reference that was returned and feed it to the [WMI] type accelerator (it likes to receive a path, and this is what the reference is).<\/p>\n Because the reference refers to a specific instance of a WMI class, and because the [WMI] type accelerator can query a specific instance of a class, I am now able to obtain the value of the netConnectionStatus<\/b> property. So I say in our script, if it is equal to 2, I will print the name of the network adapter, the configuration that is held in the setting property, and the adapter information that is held in the element property. This section of the script is shown here:<\/p>\n {<\/p>\n If( ([wmi]$_.element).netconnectionstatus -eq 2)<\/p>\n {<\/p>\n funline("Adapter: $($_.setting)")<\/p>\n [wmi]$_.setting<\/p>\n [wmi]$_.element<\/p>\n } #end if<\/p>\n The result of running the script is that it displays information from the Win32_NetworkAdapter WMI class and information from the Win32_NetworkAdapterConfiguration class. It also shows us that I only have one connected network adapter:<\/p>\n Microsoft created NetSh<\/b> in 2000, and it has been a staple of networking ever since. When I open it these days, it displays a message that says it might be removed in future versions of Windows, and therefore, I should begin using Windows PowerShell. Here is the message:<\/p>\n Now, because NetSh<\/b> is an old style menu type application, it is possible to enter NetSh<\/b>, and walk my way down through the menus until I arrive at the proper location. Along the way, if I get lost, I can use the ?<\/b> to obtain Help.<\/p>\n The problem is that the Help is quite often not very helpful; therefore, at times it takes me nearly a dozen times before the command is correct. The great thing is that, for the most part, when I figure out a command, I can actually keep track of my location in the program, back out all the way, and enter the command as a one-liner. Here is the NetSh<\/b> command to display network interface information that is bound to IPV4:<\/p>\n netsh interface ipv4 show interfaces<\/p>\n The output is shown here:<\/p>\n If I have the advantage of Windows 8.1, Windows 8.1, Windows Server 2012R2, or Windows Server 2012, I have the built-in NetAdapter<\/b> module. Due to the way that modules autoload in Windows Powell, I do not need to remember that I am using functions that exist in the NetAdapter<\/b> module. I can use Windows PowerShell 4.0 or Windows PowerShell 3.0, and the behavior will be the same. (Windows 8.1 and Windows Server 2012 R2 come with Windows PowerShell 4.0 and Windows 8 and Windows Server 2012 come with Windows PowerShell 3.0.)<\/p>\n The Get-NetAdapter<\/b> cmdlet returns the name, interface description, index number, and status of all network adapters present on the system. This is the default display of information, and it is shown in the following image:<\/p>\n To focus in on a particular network adapter, I use the Name<\/b> <\/i>parameter, and I supply the name of the network adapter. The good thing is that in Windows 8 and Windows Server 2012, the network connections receive new names. No more of the “local area connection” and “local area connection(2)” to attempt to demystify. The wired network adapter is simply Ethernet<\/b> <\/i>and the wireless network adapter is Wi-Fi<\/b>. <\/i>The following command retrieves only then Ethernet<\/b> <\/i>network adapter:<\/p>\n Get-NetAdapter -Name Ethernet<\/p>\n To dive into the details of the Ethernet <\/i>network adapter, I pipe the returned object to the Format-List<\/b> cmdlet, and I choose all of the properties. (The following command uses the fl <\/b>alias for the Format-List<\/b> cmdlet.)<\/p>\n Get-NetAdapter -Name ethernet | fl *<\/p>\n The command and output associated with the command are shown in the image that follows. <\/p>\n There are a number of excellent properties that might bear further investigation. For example, there are the AdminStatus<\/b> <\/i>and the MediaConnectionStatus<\/b> <\/i>properties. The following command returns these properties:<\/p>\n Get-NetAdapter -Name ethernet | select adminstatus, MediaConnectionState<\/p>\n Of course, there are also other properties that might be interesting. These properties are shown here, along with their associated output (this is a single logical command broken on two lines):<\/p>\n Get-NetAdapter -Name ethernet |<\/p>\n select ifname, adminstatus, MediaConnectionState, LinkSpeed, PhysicalMediaType<\/p>\n <\/p>\n ifName : Ethernet_7<\/p>\n AdminStatus : Down<\/p>\n MediaConnectionState : Unknown<\/p>\n LinkSpeed : 0 bps<\/p>\n PhysicalMediaType : 802.3<\/p>\n I decide to look only for network adapters that are in the admin status of Up<\/b>:<\/p>\n PS C:\\> Get-NetAdapter | where adminstatus -eq "up"<\/p>\n <\/p>\n Name InterfaceDescription ifIndex Status<\/p>\n —- ——————– ——- ——<\/p>\n vEthernet (InternalSwi… Hyper-V Virtual Ethernet Adapter #3 22 Up<\/p>\n vEthernet (ExternalSwi… Hyper-V Virtual Ethernet Adapter #2 19 Up<\/p>\n Bluetooth Network Conn… Bluetooth Device (Personal Area Netw… 15 Disconn…<\/p>\n Wi-Fi Intel(R) Centrino(R) Ultimate-N 6300… 12 Up<\/p>\n To find the disabled network adapters, I change AdminStatus<\/b> <\/i>from Up<\/b> <\/i>to Down<\/b>, as shown here:<\/p>\n Get-NetAdapter | where adminstatus -eq "down"<\/p>\n I go back to my previous command, and modify it to return Wi-Fi<\/b> information. This command and associated output are shown here (this is a single logical command):<\/p>\n PS C:\\> Get-NetAdapter -Name wi-fi |<\/p>\n select ifname, adminstatus, MediaConnectionState, LinkSpeed, PhysicalMediaType<\/p>\n <\/p>\n ifName : WiFi_0<\/p>\n AdminStatus : Up<\/p>\n MediaConnectionState : Connected<\/p>\n LinkSpeed : 54 Mbps<\/p>\n PhysicalMediaType : Native 802.11<\/p>\n If I want to find any network adapters sniffing the network, I look for PromiscousMode<\/b>. <\/i>This command is shown here:<\/p>\n Get-NetAdapter | ? PromiscuousMode -eq $true<\/p>\n When I combine the Get-NetAdapter<\/b> function with the Get-NetAdapterBinding<\/b> function, I can easily find out which protocols are bound to which network adapter. As shown in the following command, I send the results to Where-Object<\/b> and check to see if the enabled property is equal to True:<\/p>\n Get-NetAdapter | Get-NetAdapterBinding | ? enabled -eq $true<\/p>\n Here is an example of the command and the output from the command:<\/p>\n If I want to find which network adapters have the Client for Microsoft Networks bound, I need to first see which protocols are enabled (using the syntax from the previous command), and I need to see which one of the enabled protocols have the display name of Client for Microsoft Networks. This requires a compound Where-Object<\/b> statement. Therefore, I cannot use the simplified syntax. Also, because only one of the protocols begins with Client<\/b>, I can use that to shorten my query just a bit. Here is the command I use (this is a one-line command that I broke at the pipe character to make a better display):<\/p>\n Get-NetAdapter |<\/p>\n Get-NetAdapterBinding |<\/p>\n where {$_.enabled -AND $_.displayname -match 'client'}<\/p>\n The command and associated output are shown in the following image:<\/p>\n Join me tomorrow when I will continue Network Adapter Week by talking about enabling and disabling network adapters.<\/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","protected":false},"excerpt":{"rendered":" Summary: Microsoft Scripting Guy, Ed Wilson, talks about using Windows PowerShell to identify network adapter characteristics. Microsoft Scripting Guy, Ed Wilson, is here. Today I am kicking off Network Adapter Week. Note PowerShell Saturday #007 will be held in Charlotte, North Carolina on February 8, 2014. This will be an awesome chance to meet and […]<\/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":[36,34,332,37,3,61,45],"class_list":["post-2247","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-client-side-management","tag-hardware","tag-network-adapters","tag-networking","tag-scripting-guy","tag-weekend-scripter","tag-windows-powershell"],"acf":[],"blog_post_summary":" Summary: Microsoft Scripting Guy, Ed Wilson, talks about using Windows PowerShell to identify network adapter characteristics. Microsoft Scripting Guy, Ed Wilson, is here. Today I am kicking off Network Adapter Week. Note PowerShell Saturday #007 will be held in Charlotte, North Carolina on February 8, 2014. This will be an awesome chance to meet and […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/2247","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=2247"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/2247\/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=2247"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=2247"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=2247"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Using raw WMI to identify network adapters<\/h2>\n
Using NetSh<\/h2>\n
<\/a><\/p>\n<\/a><\/p>\nUsing PowerShell in later versions<\/h3>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n