Skip to main content

The Return of Out-GridView

By

Yes, our beloved cmdlet Out-GridView has been returned to us!  The original Out-Gridview was an easy and convenient way to quickly create GUI output and to accept limited input. In PowerShell Core (PSv6) we lost our beloved cmdlet.  Well, it is back!

For these demonstrations I am utilizing PowerShell 7-Preview 4.

Out-Gridview is actually being provided as a module.  Execute the code below to install it.


 Out-GridView still works the same as it did before.



Let’s take a look at a few of the features and what is new with Out-GridView.  The Quick Serach field works the same at the Filter field in the Windows PowerShell version of Out-Gridview.  Type something and if what you type appears in any of the objects property.



Here is something new.  It involves the filtering capability.



 Once you build a filter, click the Show Code button.


You can now have Out-GridView to create the filter it is using in code so you can copy it and paste it into your code.
Another Change is the when you add either the -PassThru or -OutputMode Parameters.  The PSv5 version produces an OK and a Cancel button.  The PSv7 version produces and Export and a Cancel button.  They perform the same functions as the PSv5 version.




Truth be told, I am very happy to see this simple tool back in play.  I look at my fellow “non-technical” cubical dwellers and ask myself, “what code can I write to make their lives better?”  A challenge has always been to display information to them in a way that they will except.  Translation, non-technical users do not like looking at a terminal.  The return of Out-Gridview gives us a new tool to help free our non-PowerShell savvy teammates from the rigorous life of manual repetition.

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

How to list all the AD LDS instances on a server

By
AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more