We have seen how to query WMI for information on network adapters. But what we didn’t get was information about the addresses allocated to the NICs. We need a different class for that
Get-WmiObject -Class Win32_NetworkAdapterConfiguration
Today Manning are offering 50% their best selling books including PowerShell in Practice.
See www.manning.com to order
Get-WmiObject -Class Win32_NetworkAdapter
will show us a list of network adapters. We can narrow this down to a specific adapter
Get-WmiObject -Class Win32_NetworkAdapter -Filter "DeviceId='11'" | fl *
What if we know that there is a...
Ok – just to help out we can do this to see the useful information we need to complete our IPconfig listing
Get-WmiObject -Class Win32_NetworkAdapter -Filter "NetEnabled='$true'" | Format-List NetConnectionID, Description, MACAddress, Speed
This gets a display like...
Network adapters are a fundamental part of our system – without them our networks grind to a halt because the machines can’t communicate. We have a good tool in ipconfig for looking at NIC information but we can extend this using PowerShell and WMI. Let’s start by seeing what is...
Working with WMI dates can be awkward sometimes. For instance if we look at the last boot up time of our system
$machine = Get-WmiObject -Class Win32_OperatingSystem
We get a non-intuitive...
We have seen how to discover the total physical memory in a system but how is that memory arranged.
it seems that the WMI provider I mentioned last time is effectively discontinued in Office 2010.
I’ll see if I can get a machine set up with Office 2007 to investigate further
If you have Office 2010 installed you should find an msapps12 namespace on your machine.
The classes exposed by this namespace can be found with
Get-WmiObject -Namespace root\msapps12 –List
There are a lot of them! The classes seem to be broken down by Office...
The ntds.dit file is used to store Active Directory data on a domain controller. Knowing how big this file is getting is a useful piece if information. One way is to log on to each domain controller and test the size using Windows explorer. A better way is to use WMI PS> "server02", "dc02"...