I was updating my NIC driver the other day and happened to notice a new checkbox in the setup wizard. Intel has added a PowerShell Module to manage the NIC? How cool is that?
Let’s take a look at the module and see what is included.
|
1 |
Get-Module -ListAvailable |
The module name is IntelNetCmdlets, from there we can easily determine what cmdlets are available.
|
1 2 |
Import-Module IntelNetCmdlets Get-Command -Module IntelNetCmdlets |
Let’s try out one of the command to see what kind of information we can get.
|
1 |
Get-IntelNetAdapter |
…and the full output.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 |
Get-IntelNetAdapter | select * PSComputerName : TESTPC01 __GENUS : 2 __CLASS : IANet_PhysicalEthernetAdapter __SUPERCLASS : IANet_EthernetAdapter __DYNASTY : CIM_ManagedElement __RELPATH : IANet_PhysicalEthernetAdapter.CreationClassName="IANet_PhysicalEthernetAdapter",DeviceID= "{01A966F4-8F3C-4944-8DE4-13D8D8DBEE09}",SystemCreationClassName="Win32_ComputerSystem",S ystemName="TESTPC01 __PROPERTY_COUNT : 77 __DERIVATION : {IANet_EthernetAdapter, CIM_EthernetAdapter, CIM_NetworkAdapter, CIM_LogicalDevice...} __SERVER : TESTPC01 __NAMESPACE : root\intelncs2 __PATH : \\TESTPC01\root\intelncs2:IANet_PhysicalEthernetAdapter.CreationClassName="IANet_PhysicalEthernetAdapter",DeviceID="{01A966F4-8F3C-4944-8DE4-13D8D8DBEE09}",SystemCreationClassName="Win32_ComputerSystem",SystemName="TESTPC01" AdapterStatus : 51 AdditionalAvailability : {3} AlignmentErrors : AutoSense : Availability : 3 BusType : 7 Capabilities : {32, 33, 34, 58...} CapabilityDescriptions : {, , , ...} Caption : Intel(R) 82579LM Gigabit Network Connection CarrierSenseErrors : ConnectionName : Local Area Connection ControllerID : 54 CreationClassName : IANet_PhysicalEthernetAdapter DeferredTransmissions : Description : Intel(R) 82579LM Gigabit Network Connection DeviceID : {01A966F4-8F3C-4944-8DE4-13D8D8DBEE09} EEELinkStatus : 0 EEPROMVersion : 0.13 EnabledCapabilities : ErrorCleared : ErrorDescription : ETrackID : ExcessiveCollisions : ExtendedStatus : 0 FCSErrors : FrameTooLongs : FullDuplex : True HardwareStatus : 1 IdentifyingDescriptions : InstallDate : InternalMACReceiveErrors : InternalMACTransmitErrors : LastErrorCode : LateCollisions : Location : 0:25:0:0 MaxDataSize : MaxQuiesceTime : MaxSpeed : 1000000000 MediaType : 1 MiniPortInstance : {01A966F4-8F3C-4944-8DE4-13D8D8DBEE09} MiniPortName : e1cexpress MultipleCollisionFrames : Name : Intel(R) 82579LM Gigabit Network Connection NegotiatedLinkSpeed : 65535 NegotiatedLinkWidth : 1 NetworkAddresses : {402CF4EB9320, 402CF4EB9320} OctetsReceived : OctetsTransmitted : OriginalDisplayName : Intel(R) 82579LM Gigabit Network Connection OtherCapabilityDescriptions : OtherEnabledCapabilities : OtherEnabledCapabilityIDs : OtherIdentifyingInfo : OtherMediaType : OtherPhyDevice : OTPVersion : PartNumber : PCIDeviceID : VEN_8086&DEV_1502&SUBSYS_17aa3083&REV_04&0&c8 PermanentAddress : 402CF4EB9320 PHYDevice : 0 PortNumber : 65535 PowerManagementCapabilities : PowerManagementSupported : PowerOnHours : SanMacAddress : SingleCollisionFrames : SlotID : 0:25:0:0 Speed : 100000000 SQETestErrors : Status : OK StatusInfo : 3 SymbolErrors : SystemCreationClassName : Win32_ComputerSystem SystemName : TESTPC01 TotalPacketsReceived : TotalPacketsTransmitted : TotalPowerOnHours : Scope : System.Management.ManagementScope Path : \\TESTPC01\root\intelncs2:IANet_PhysicalEthernetAdapter.CreationClassName="IANet_Physica lEthernetAdapter",DeviceID="{01A966F4-8F3C-4944-8DE4-13D8D8DBEE09}",SystemCreationClassNa me="Win32_ComputerSystem",SystemName="TESTPC01" Options : System.Management.ObjectGetOptions ClassPath : \\TESTPC01\root\intelncs2:IANet_PhysicalEthernetAdapter Properties : {AdapterStatus, AdditionalAvailability, AlignmentErrors, AutoSense...} SystemProperties : {__GENUS, __CLASS, __SUPERCLASS, __DYNASTY...} Qualifiers : {dynamic} Site : Container : |
This definitely demonstrates how widespread PowerShell has become, as hardware vendors are now building their administration and functionality directly into PowerShell!
