Joe Glines wrote:
BTW- I borrowed & tweaked my code from that original post but I can't claim to understand a lick of it (nor can I follow yours) Could you go back and annotate it to help me understand what they are doing?
ROFL. I've seen some of your posts on http://the-automator.com/
and you're streets ahead of me!
For creating WMI queries from scratch I still tend to use the Scriptomatic V2 for Win 7
HTA to construct the initial query then check out AHK - WMI - Snippets
) to see whether I have the AHK code right.
I'm sure someone will correct me if I'm wrong but, to me, all this means is to run a WMI query against the
collection and return the result for the object named
. If you use Scriptomatic
it will show you every available object available for each collection. Sorry, I don't use WMI often enough to have found a better tool... although I'm sure one or more exists.
Similarly, all this means is run a WMI query against all
collections that have
and return the result for the object named
. This way it will catch the active
network adaptor and ignore inactive or pseudo/virtual adapters.
WMI can sometimes be a little flaky, especially now that PowerShell
has gained such a foothold (which is why I've been playing with wrapping PowerShell cmdlets in AHK). Whilst PowerShell
still supports WMI cmdlets, some WMI classes have been deprecated and I guess this trend will continue. Have a read of this CIM vs. WMI CmdLets – The top reasons I changed over
). On the other hand, most WMI queries will remain for some time... and only MS can tell us how long that will be.
Hope this helps...