Out-GridView provides a better way for PowerShell to present tabulated
information. It works particularly well for displaying data returned
by get-Service or get-Process.
If you have not seen out-GridView before it could be because this is a
new cmdlet in PowerShell Version 2.0. As with any new cmdlet,
before we put out-GridView to work it's worth calling for help so that we
can check the syntax and seek out interesting parameters.
get-Help out-GridView -full
Note 1: Because I want to see examples, I
rarely use get-Help without appending the -full switch. In this case
help alerted me to sorting the columns by simply double-clicking their
heading. In addition, it was only by reading the help file that I
realized the benefit of using the 'Search' box as a filter.
Note 2: The only problem I have encountered with
out-GridView is spelling the noun. Grid View is wrong, and omitting
View is another fatal sin, Out-Grid does not work. Remember it's one
word, gridview as in Out-GridView.
Note 1: Please remember the pipe (|), especially
when you
get too ambitious, and something goes wrong with your complex experiment.
Note 2: You can also copy the data
displayed by out-GridView and paste it
into Excel. Numeric data often benefits from further manipulation by
the spreadsheets functions. I find that the old keyboard shortcuts such as Ctrl + a are handy
for selecting all the rows.
This example illustrates the benefits of adding extra PowerShell code
in order to control the headings. For example, we want the name of
each process in the first column.
Note 1: Remember that you can sort on any of
the columns simply by double-clicking.
Note 2: It surprised me to discover that you can
also drag and drop the columns to re-order the data. Resizing the columns
works intuitively, just like Excel.
Note 3: Out-GridView has a search box that you
don't normally get with get-Process. One use of this Search
capability is to filter
the data.
Example 3: Out-GridView Show in Groups
Another surprising feature of out-GridView is how we can group items. For
example, with get-Service you can aggregate the services that are stopped. Just right-click on the heading and see if it supports 'Show in
Groups'. See screenshot to the right. All in all, out-Grid
means that you can manipulate data quickly on the fly, this saves having
to revisit the code and changing the properties or adjusting the grouping
syntax.
Guy Recommends: SolarWinds LANSurveyor
LANSurveyor will produce a neat diagram of your network topology. But that's
just the start;
LANSurveyor can
create an inventory of the hardware and software
of your machines and network devices. Other neat features include dynamic
update for when you add new devices to your network. I also love the ability to export
the diagrams
to Microsoft Visio.
Finally, Guy bets that if you take a free trial of LANSurveyor then you will
find a device on your network that you had forgotten about, or someone else
installed without you realizing!
One more pleasant revelation, if you import an XML file then you can
improve the way the data displays by piping its
contents into out-GridView.
Assuming you have a suitable xml file called services.xml, try this:
Note 1: I don't want you to go away thinking
that out-GridView is only suitable for get-Service, it's just that all
Windows computers have services, and their data shows off this display
cmdlet in it's best light.
While out-GridView is easy to understand, it maybe that you already
know other members of the 'Output' family of cmdlets. My point is
that if you have already used out-File then you will know what to expect
from out-GridView. On the other hand, if this is all new territory,
then you can apply knowledge of out-GridView to out-Printer.
While out-GridView is easy to understand it maybe that you already know
other members of the 'Output' family of cmdlets. My point is that if
you have used out-File then you will know what to expect from out-GridView.
On the other hand if this is all new territory, then you can apply
knowledge of out-GridView to out-Printer.
Guy Recommends: The Orion Network Performance Monitor (NPM) 9.5
Orion's performance monitor is designed for detecting network outages.
This NPM will guide you
through troubleshooting by indicating whether the root cause is a broken link,
faulty equipment or resource overload. Because it produces
network-centric views, it is intuitive to navigate, and as result you can
see easily what's working and what's not.
Perhaps Orion's best feature is the way it suggests solutions. Moreover, if
problems arise out of the blue, then you can configure Orion NPM 9.5 to notify
members of your team what's changed and how to fix it.
PowerShell v 2.0 has a lovely new cmdlet called out-GridView, what this does
is take the output from another command and present it in a new window where
the data is displayed in an interactive table. Take the time to
research the 'Search' box and discover how to 'Show in Groups'.
Please write in if you see errors of any kind. Please report any factual mistakes, grammatical errors or broken links, I will be happy to not only to correct the fault, but also to give you credit.
The IP SLA Monitor not only helps to discover network bottlenecks, but
also teaches you about router traffic. See how effortlessly this
free monitor analyzes and then displays the IP statistics.
The key to configuring is to select the data most relevant to your
network, for example, ping echo, DNS resolution times, or HTTP
statistics.