Interesting find, thanks, I will give that a bash...
On 18 March 2014 15:22, Charles Sullivan <[email protected]> wrote: > The sticking point with this sort of thing always seems to be accounting > for the endless possibilities of interface names. I just found this > article for a VB script and it says that it accounts for that by querying > the adapter names first, but I haven't tried it myself. > > > > > http://blogs.technet.com/b/heyscriptingguy/archive/2007/08/20/how-can-i-tell-if-a-wireless-network-adapter-is-connected-to-the-network.aspx > > > > > > Charlie Sullivan > > Sr. Windows Systems Administrator > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *James Rankin > *Sent:* Tuesday, March 18, 2014 11:13 AM > *To:* [email protected] > *Subject:* [NTSysADM] Determining connection type > > > > Anyone know a good way I can determine whether a machine is connected to a > wireless network or not? PowerShell or VB to evaluate this would be > ideal....at the moment I am just iterating through subnet IP addresses and > identifying whether machines have one that's in a wireless range or not, > and that doesn't modularize very well. > > > > All ideas appreciated! > > > > TIA, > > > > > > > > -- > > *James Rankin* > --------------------- > RCL - Senior Technical Consultant (ACA, CCA, MCTS) | The Virtualization > Practice Analyst - Desktop Virtualization > http://appsensebigot.blogspot.co.uk > -- *James Rankin* --------------------- RCL - Senior Technical Consultant (ACA, CCA, MCTS) | The Virtualization Practice Analyst - Desktop Virtualization http://appsensebigot.blogspot.co.uk
