Script Explorer for Windows PowerShell

| by Jonathan Allen Follow 501 Followers on Mar 19, 2012. Estimated reading time: 1 minute |

A note to our readers: You asked so we have developed a set of features that allow you to reduce the noise: you can get email and web notifications for topics you are interested in. Learn more about our new features.

Microsoft has released a beta of a new tool called Script Explorer for Windows PowerShell. This tool is essentially a specialized search engine for PowerShell scripts. By default it allows administrators to browse and search for scripts in TechNet Script Center and PoshCode.

PoshCode is a community run PowerShell Code Repository designed to server the same role as Perl’s CPAN or the Python Package Index. Scripts on PoshCode are offered under the Creative Commons “No Rights Reserved” license unless otherwise specified. According to their terms of use:

Don't get us wrong: we love open source, and we aren't opposed to reciprocal open source licenses, but we strongly believe they are the wrong model for a script community. Here we must not only reuse, but more importantly, we must be able to remix, and so we require the use of licenses which are easy to remix and re-use. We strongly encourage you to use the public domain dedication for your scripts, but we request that if you choose to provide license terms, you choose a non-reciprocal open source license.

Script Explorer does not allow you to directly run the scripts that you find. Instead you are expected to either copy it to the clipboard or save it to your own repository. In addition to a local directory, the tool lets you use network file shares as repositories. These network shares must be indexed for the search functionality to work.

Since Microsoft is offering third-party scripts, Jonathan Nobel of the TechNet UK IT Professional Community Council warns,

Please, please, please always be careful about running any code that you find online, even through Script Explorer. Make sure that you understand what impact it's going to have on your environment before you run it. If you can't be quite sure, try dropping a few -whatif and -confirm parameters on any cmdlet that looks like it might alter/create/delete anything and if possible, run it on a test system before it goes anywhere near anything that's in production.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread


Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you