Skip to main content

PowerShell list physical adapters


How to check physical adapters from virtual NICs?

In today’s world virtual is reality already.  Virtual servers, virtual computers, virtual attitude of people almost anything now can be virtualized.

How to check people with virtual attitude?  PowerShell is not able to help with that, what PowerShell can help is to check physical NIC from virtual network adapters.

This script below will be useful in an environment where Hyper-V is installed. It will list physical and virtual NICs.

To check physical adapters the value is true, false if not physical adapter.


Here’s the script to check and list physical and virtual network adapters.

===================================== 

$nic = Get-WmiObject -class Win32_NetworkAdapter

Write-Host "Number of NICs: "$nic.Count

foreach ($nicx in $nic) {
     "Network Adapter name is: " + $nicx.name + "Network Adapter is Physcial: " + $nicx.physicaladapter
}

=====================================

Sample output;

Number of NICs:  10
Network Adapter name is: Microsoft Kernel Debug Network AdapterNetwork Adapter is Physical: False
Network Adapter name is: VirtualBox Host-Only Ethernet AdapterNetwork Adapter is Physical: True
Network Adapter name is: Atheros AR9285 Wireless Network AdapterNetwork Adapter is Physical: True
Network Adapter name is: Qualcomm Atheros AR8152 PCI-E Fast Ethernet Controller (NDIS 6.30)Network Adapter is Physical: True
Network Adapter name is: Bluetooth Device (RFCOMM Protocol TDI)Network Adapter is Physical: False
Network Adapter name is: Bluetooth Device (Personal Area Network)Network Adapter is Physical: True
Network Adapter name is: Microsoft Hosted Network Virtual AdapterNetwork Adapter is Physical: False
Network Adapter name is: Microsoft ISATAP AdapterNetwork Adapter is Physical: False
Network Adapter name is: WAN Miniport (SSTP)Network Adapter is Physical: False
Network Adapter name is: WAN Miniport (IKEv2)Network Adapter is Physical: False


Cheers..Enjoy.. 


Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

WMIC get computer name

WMIC get computer model, manufacturer, computer name and  username. WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided. Why would you need a command line tool if there’s a GUI to check? If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username. If you have remote computers, you need to delegate someone in the remote office or location to check. Or you can just write a batch file or script to automate the task. Here’s the code below on how get computer model, manufacturer and the username. Open an elevated command prompt and type:     wmic computersystem get "Model","Manufacturer", "Name", "UserName" Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name. A...
Post a Comment
Read more

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...
6 comments
Read more

How to check office version from command line

The are quite a few ways to check office version it can be done via registry, PowerShell or VBScript and of course, good old command line can also do it. Checking Windows office version whether it is Office 2010, Office, 2013, Office 2016 or other version is quite important to check compatibility of documents; or just a part of software inventory. For PowerShell this simple snippet can check the office version: $ol = New-Object -ComObject Excel.Application $ol . Version The command line option will tell you where’s the path located; the result will also tell whether office is 32-bit, 64-bit and of course the version of the office as well. Here’s the command that will check the office version and which program directory the file is located which will tell whether it’s 32-bit or 64-bit. Command to search for Excel.exe: DIR C:\ /s excel.exe | find   /i "Directory of"  Above command assumes that program files is on  C: drive. Sample O...
Post a Comment
Read more