Showing posts with label PowerShell. Show all posts
Showing posts with label PowerShell. Show all posts

Tuesday, April 29, 2014

PowerShell 10k - PowerShell Script Browser and Analyzer v1.1 released (easily access 10k PS Scripts, right from the ISE...)

Microsoft All-In-One Script Framework - Here Comes the Update of Script Browser & Script Analyzer 1.1

The Script Browser for Windows PowerShell ISE has received thousands of downloads since it was released a week ago. Based on your feedbacks, today we release the 1.1 update to respond to the highly needed features. The team is committed to making the Script Browser and Script Analyzer useful. Your feedback is very important to us.

Download Script Browser & Script Analyzer 1.1
(If you have already installed the 1.0 version, you will get an update notification when you launch Windows PowerShell ISE.)

1. Options to Turn on / Turn off Script Analyzer Rules

You can either select to turn on or turn off the rules in the Settings window of Script Analyzer.


You can also suggest a new Script Analyzer rule or vote for others’ suggestions. Our team monitors the forum closely. Based on your suggestions and votes, we will provide the corresponding Script Analyzer rules in future updates. We are also looking into the capability for you to write your own Script Analyzer rules and plug into the Script Analyzer.


Windows PowerShell Blog - A World of Scripts at your Fingertips – Introducing Script Browser

To reuse script samples on the Internet, the following steps seem quite familiar to IT Pros: wandering through different script galleries, forums and blogs, switching back and forth between webpages and scripting environment, and countless download, copy and paste operations. But all of these will drive one as dizzy as a goose. Need a simpler way of searching and reusing scripts? Try out the new Script Browser add-in for PowerShell ISE!


Script Browser for Windows PowerShell ISE is an app developed by Microsoft Customer Services & Support (CSS) with assistance from the PowerShell team and the Garage to save IT Pros from the painful process of searching and reusing scripts. We start from the 9,000+ script samples on TechNet Script Center. Script Browser allows users to directly search, learn, and download TechNet scripts from within PowerShell ISE – your scripting environment. Starting from this month, Script Browser for PowerShell ISE will be available for download. If you are a PowerShell scripter or are about to be one, Script Browser is a highly-recommended add-in for you.

Nearly 10,000 scripts on TechNet are available at your fingertips. You can search, download and learn scripts from this ever-growing sample repository.


Script Browser for Windows PowerShell ISE

Version: 1.1
File Name: ScriptBrowser.exe
Date Published: 4/29/2014
File Size: 1.4 MB

Script Browser for Windows PowerShell ISE enables you to search for over 9000 script samples in the TechNet Script Center from within the scripting environment. You can mark the script samples as favorites and download the script samples for later use. You will also get the chance to try out another new pilot function bundled with Script Browser - 'Script Analyzer'. We hope to learn your feedback.

One of those, you've got-to-have tool for PowerShell'ers

Monday, April 28, 2014

PowerShell 4.0 and more Quick Refs from PowerShell Magazine and Microsoft

Microsoft Downloads - Windows PowerShell 4.0 and Other Quick Reference Guides

Quickly learn tips, shortcuts, and common operations in Windows Powershell 4.0, Windows PowerShell Desired State Configuration, Windows PowerShell Workflow, Windows PowerShell ISE, Windows PowerShell Web Access, Server Manager for Windows Server 2012 R2, WinRM, WMI, and WS-Man.

Version: 1

Date Published: 4/23/2014









The PDF files in this download are short-form Quick Reference (also called "cheat sheet") guides for IT professionals, developers, and scripting enthusiasts who want to learn tips, shortcuts, common operations, limitations, and proper syntax for using Windows PowerShell 4.0, Windows PowerShell Desired State Configuration (DSC), Windows PowerShell ISE, Windows PowerShell Web Access, Server Manager, WMI, and WS-Man in Windows Server 2012 R2 and Windows 8.1.
The following files are contained in this download.
  • PowerShell_LangRef_v4.pdf - This four-page reference describes operators, arrays, useful commands, methods, and other tips for using Windows PowerShell 4.0. Also included is a Windows PowerShell reading and tutorial resource list. This quick reference is provided by PowerShell Magazine.
  • PowerShell_ISE_v4.pdf - This two-page reference describes keyboard shortcuts and hotkeys that you can use to navigate Windows PowerShell Integrated Scripting Environment (ISE) more quickly, and describes the updated ISE object model. Also included are tips for configuring $ps.ISE options, profiles, and properties. This quick reference is provided by PowerShell Magazine.
  • PowerShell_Examples_v4.pdf - This two-page reference describes how to perform popular IT management and scripting tasks by using Windows PowerShell 4.0, including how to fetch data by using Management OData IIS Services, how to schedule jobs, how to add a #Requires statement to a script, and how to save Help for a module that is not necessarily installed on the local computer. This quick reference is provided by PowerShell Magazine.
  • PowerShell_DSC_v4.pdf - Windows PowerShell Desired State Configuration (DSC) is new for Windows PowerShell 4.0. This two-page reference provides an overview of how DSC works, and describes the DSC cmdlets, available resources, Local Configuration Manager, and advanced resource properties.
  • Quick_Reference_SM_WS12.pdf - This two-page reference describes common tasks that you can perform in the Server Manager console in Windows Server 2012 R2. Quickly learn how to manage remote servers that are running older versions of Windows Server by using Server Manager; how to run Server Manager deployment cmdlets for Windows PowerShell; how to save and export Server Manager settings, such as the servers you have added to the server pool, and custom server groups that you have created; where to find Server Manager log files; how to run popular WinRM commands such as creating a new listener; how to install roles and features on offline VHDs; and where to find documentation to help you manage multiple, remote servers by using Server Manager and Windows PowerShell.
  • Quick_Reference_WMI_ITPro_WS12R2.pdf - This two-page reference describes features that were introduced to Windows Management Instrumentation (WMI) starting in Windows PowerShell 3.0. Included are examples of how to find namespaces and classes in WMI, and detailed information about CimSession, CimInstance, CIM operations, and invoking a CIM method. The quick reference describes how to get a list of new CIM cmdlets, and defines associations, WQL, WS-Man, WinRM, and CIM indications.
  • Quick_Reference_WMI_Devs_WS12R2.pdf - This two-page reference describes features that were introduced to Windows Management Instrumentation (WMI) starting in Windows PowerShell 3.0 for developers. Included are examples of APIs and tools in WMI, and information about Convert-MofToProvider.



    If you don't PowerShell often (like me) these guides will be very nice to have...

    (via The Windows Club - Windows PowerShell 4.0 Guides from Microsoft)


    Related Past Post XRef:
    Windows Management Framework 4.0 (PowerShell 4, PowerShell ISE, Management OData, WMI, etc.) now available

    Friday, April 25, 2014

    NuGet, OneGet and MyGet is YourGet... - Using MyGet as a OneGet package source

    At the Build conference, Microsoft announced the Windows Management Framework 5.0 Preview which includes Windows PowerShell 5.0, updates to the PowerShell ISE, Network Switch Cmdlets and ... OneGet!

    What is OneGet?

    OneGet a unified package management interface component with a set of managed and native APIs, a set of PowerShell cmdlets, and a WMI provider. The component accepts both Microsoft-provided and 3rd party-provided plugins which extend the functionality for a given package type.


    As part of this Preview, OneGet is shipping with a prototype plugin compatible with Chocolatey, the so called ChocolateyProvider. This is a prototype implementation of a Chocolatey-compatible package manager that can install existing Chocolatey packages. This is a clear confirmation for the hard work done by the Chocolatey folks, and both systems will continue to evolve together, as Rob Reynolds explains in this post. If you want to follow-up on OneGet, then check out its GitHub repository and follow PSOneGet on Twitter.

    Something about a forest and trees...

    NuGet, MyGet, Chocolatey, OneGet... what?! People ask questions and occasionally can't see the forest for the trees. Here's a quick recap:

    • NuGet: a solution-level package management tool, used to manage software dependencies within the scope of a solution. It is accompanied by the NuGet Gallery, the home of many if not all .NET open source components.
    • Chocolatey: a system-level package management tool, used to manage software installations on a Windows system. It (currently) leverages PowerShell and NuGet, supports the Web Platform Installer (WebPI), MSI, RubyGems and many more, and is accompanied by the Chocolatey Gallery where you can find many popular software packages. Rob describes Chocolatey as somewhat like "apt-get", but with Windows in mind.
    • MyGet: a hosted NuGet package server where you can create and secure your own feeds. In essence, MyGet is able to host vanilla NuGet feeds, as well as Chocolatey feeds.
    • OneGet: a a unified interface to package management systems (see above)

    So what does this mean? How do these package managers play along?

    OneGet supports multiple package sources, and as stated earlier, OneGet comes with a ChocolateyProvider. As MyGet also supports Chocolatey feeds, this effectively means that you can register a MyGet feed as a Chocolatey package source in OneGet! The below diagram is an attempt to illustrate how they relate:



    How can I use a private OneGet package source?


    This flow allows you to control what packages get distributed through OneGet, avoids the need to publish your internal software to the general public, and still allows you to leverage the great new scenarios that OneGet offers!

    As usual, happy packaging! :)

    I've still not played with OneGet yet... But I'm going to. Really. Any time now... um... yeah


    Related Past Post XRef:
    PowerShell gets Chocolatey NuGet with OneGet
    Using NuGet doesn't mean you have to give it away... "Distributing .NET Licensed components using NuGet"

    Thursday, April 17, 2014

    PowerShell gets Chocolatey NuGet with OneGet

    Stefan Stranger's Weblog - Manage your IT Infrastructure - Viewing NuGet Packages with the NuGet Explorer

    You may have seen that we released the the Windows Management Framework V5 Preview and that one of the new features  is Windows PowerShell OneGet. OneGet is designed to dramatically simplify how you discover and install software packages.

    Windows PowerShell OneGet

    OneGet is a new way to discover and install software packages from around the web. With OneGet, you can:

    • · Manage a list of software repositories in which packages can be searched, acquired, and installed
    • · Search and filter your repositories to find the packages you need
    • · Seamlessly install and uninstall packages from one or more repositories with a single PowerShell command

    This first version of OneGet installs and searches software from Chocolatey repositories.  Support of additional repositories will come in subsequent versions.


    One of the things that comes getting up in discussions about using Chocolatey Packages with or without OneGet is the question how can I trust the Packages from a resource like Chocolatey? The Chocolatey Nuget Packages are build by the community so you need to be careful what you are downloading and installing like all other software from sources you don’t own yourself.

    But what if there is a easy way to view the content of NuGet Package before installing the Chocolatey NuGet packages? And that is possible using the NuGet Package Explorer.




    While I had seen the WMF v5 news, I hadn't seen, or at least registered, the OneGet news. That really does look awesome and something I'm going to have to take a much closer look at...


    Related Past Post XRef:
    Spelunking NuGet Packages with the NuGet Package Explorer (and creating, editing and publishing nupkg's with it too)
    NuGet, Open Wrap, NPanday, Chocolatey, Chewie, Ninite, top Package/Dependency Management for .Net tools
    NuGet your Enterprise?
    North by Northwest [Cadence] - Up coming casts from Northwest Cadence

    Friday, November 15, 2013

    "Community [e]Book of PowerShell Practices" September 2013 edition - Community Book of PowerShell Practices

    Released in our new Git repo: The Community Book of PowerShell Practices, an ongoing book started from this past Summer’s “Great Debates” blog post series. Grab it from and enjoy!

    PowerShellOrg / ebooks / Practices / 2013Sep_Practices /


    During the 2013 Scripting Games, it became apparent that a great many folks in the PowerShell community have vastly different ideas about what’s “right and wrong” in the world of PowerShell scripting. Some folks down-scored techniques that others praised, and vice-versa.

    After the Games, ran a series of “Great Debate” blog posts, outlining some of the more controversial issues and asking for community input. The catch is the input had to not only state what the person thought was best, but very specifically why they thought that.

    This book, which will likely be an ongoing effort, is a compilation of those Debates’ comments, formed as a “best practices” guide that is based on community input. It’s important to realize that practices are not hard-and-fast rules. Best practices are the things you usually do as a starting point, and deviate from when it’s appropriate. You should understand that these practices were formed primarily by people who are writing scripts to manage their own environment, and who are often pressed for time. They are not developing commercial software, they rarely have the luxury of extended test-and-develop cycles, and for the most part are not professional software developers. Their perspective definitely drives what they consider “best” and “worst,” but if you are working from a different perspective then you’ll have to take all of this with a grain of salt.

    Just a few pages, but from people in the field, for people in the field.

    Friday, October 25, 2013

    Windows Management Framework 4.0 (PowerShell 4, PowerShell ISE, Management OData, WMI, etc.) now available

    Keith Hill's Blog - PowerShell 4.0 Now Available

    You can get PowerShell 4.0 for down level operating systems now via the WMF 4.0 download.  NOTE: Be sure you have .NET 4.5 installed *before* you install WMF 4.0....

    Windows PowerShell Blog - Windows Management Framework 4.0 is now available

    Windows Management Framework 4.0, our package that lets you use management technologies from Windows 8.1 and Windows Server 2012 R2 on some of Microsoft’s older operating systems, is now available for you to download and install. This full-release version of Windows Management Framework 4.0 includes even more improvements than our Preview release. Be certain to read this blog post fully before installing, especially because WMF 4.0 is not compatible with certain versions of server products.


    IMPORTANT: Not all Microsoft server applications are currently compatible with WMF 4.0. Before installing WMF 4.0, be sure to read the WMF 4.0 Release Notes. Specifically, systems that are running the following server applications should not run WMF 4.0 at this time:

    • System Center 2012 Configuration Manager (not including SP1)
    • System Center Virtual Machine Manager 2008 R2 (including SP1)
    • Microsoft Exchange Server 2013, Microsoft Exchange Server 2010 and Microsoft Exchange Server 2007
    • Microsoft SharePoint 2013 and Microsoft SharePoint 2010
    • Windows Small Business Server 2011Standard

    We acknowledge that there is still a need for management of Windows Server 2008, and Windows Management Framework 3.0 remains the answer for Windows Server 2008.


    Microsoft Downloads - Windows Management Framework 4.0

    Windows Management Framework 4.0 includes updates to Windows PowerShell, Windows PowerShell ISE, Windows PowerShell Web Services (Management OData IIS Extension), Windows Remote Management (WinRM), Windows Management Instrumentation (WMI), the Server Manager WMI provider, and a new feature for 4.0, Windows PowerShell Desired State Configuration (DSC).

    Version: 1.0

    Date Published: 10/24/2013

    • Windows Management Framework 4.0 Release Notes.docx, 89 KB
    • Windows PowerShell Desired State Configuration Quick Reference for Windows Management Framework 4.0.pdf, 244 KB
    • Windows PowerShell Desired State Configuration Quick Reference for Windows Management Framework 4.0.pptx, 73 KB
    • Windows6.1-KB2819745-x64-MultiPkg.msu, 18.4 MB
    • Windows6.1-KB2819745-x86-MultiPkg.msu, 14.1 MB
    • Windows8-RT-KB2799888-x64.msu, 17.5 MB

    This release includes new features and functionality in Windows Management Framework 4.0, including the following:

    • Windows PowerShell 4.0
    • Windows PowerShell ISE
    • Windows PowerShell Web Services (Management OData IIS Extension)
    • Windows Remote Management (WinRM)
    • Windows Management Instrumentation (WMI)
    • The Server Manager WMI provider
    • A new feature for 4.0, Windows PowerShell Desired State Configuration (DSC)

    Windows Management Framework 4.0 makes updated management functionality available for installation on Windows 7 SP1, Windows Server 2008 R2 SP1, and Windows Server 2012.

    Windows PowerShell 4.0
    Some of the new features in Windows PowerShell 4.0 include:

    • Support for workflow and remote script debugging
    • Improved workflow authoring experience to make it more consistent with script authoring
    • Added PipelineVariable as a common parameter
    • Better support for downloading updatable help by using Save-Help and Update-Help in offline scenarios
    • Updated version from 3.0 to 4.0
    • Several bug fixes and performance improvements
    Windows PowerShell Integrated Scripting Environment
    Windows PowerShell ISE in Windows Management Framework 4.0 introduces:
    • Support for Windows PowerShell Workflow debugging
    • Support for remote script debugging
    • IntelliSense support for Windows PowerShell Desired State Configuration resources and configurations
    Windows PowerShell Web Services
    Windows PowerShell Web Services (Management OData IIS Extension) enables an administrator to expose a set of Windows PowerShell cmdlets as a RESTful web endpoint accessible by using OData (Open Data Protocol). This provides remote access to run cmdlets from both Windows-based and non-Windows-based client computers or devices.
    • Improved error messages in event logs
    • Endpoint versioning support
    • Autopopulation of OData dispatch schema fields
    • Support for complex types
    • Multilevel association support
    • Ability to perform large binary stream transfers
    • Support for non-Create/Read/Update/Delete (CRUD) actions
    • Key-As-Segment URL syntax support
    • Constrained resource operations

    WMI, WinRM, and Server Manager CIM Provider
    These features were included with WMF 3.0, and continue to be included in WMF 4.0. There are no significant changes to these features.

    Windows PowerShell Desired State Configuration
    Windows Management Framework 4.0 introduces Windows PowerShell Desired State Configuration (DSC), with the following highlights:

    • Local configuration manager for applying configurations on the local computer
    • Windows PowerShell language extensions for authoring DSC documents
    • PSDesiredStateConfiguration module and DSC-related cmdlets
    • A set of built-in DSC configuration resources
    • DSC service for distributed access to DSC resources

    Friday, August 02, 2013

    Azure, PowerShell, Virtual Networks, VM's, Domains and Lab building, a three part series

    chris e. avis - writing about microsoft and technology.... - Build a lab in Windows Azure for learning PowerShell – Part 3 of 3 – Configure the Virtual Machines

    I have decided to use Windows Azure as my lab environment because it is the fastest and most accessible way for me to work on this from anywhere in the world. I travel a lot so I want to be able to access the lab while on the road. This is a self-contained lab environment that for right now is just for my PowerShell learning. But it has the potential to be used for other lab scenarios and is completely expandable.

    I am using the following book to teach myself more about PowerShell -

    “Learn Windows PowerShell 3 In A Month Of Lunches” by Don Jones and Jeffery D. Hicks

    I have decided to use Windows Azure as my lab environment because it is the fastest and most accessible way for me to work on this from anywhere in the world. I travel a lot so I want to be able to access the lab while on the road. This is a self-contained lab environment that for right now is just for my PowerShell learning. But it has the potential to be used for other lab scenarios and is completely expandable.

    You can create your own Windows Azure Lab by following along. The first step is to get signed up for a Free Windows Azure Trial account here -

    To create the lab environment, we have to build out a few different pieces -

    Ongoing summary posts of what I learn as I read the book and learn more about PowerShell.


    Hopefully, if you are at the stage of wanting to learn PowerShell, you already know how to create a Windows Domain Controller. Even if you don’t have much experience with Windows Server 2012 R2 Preview, you should be able to stumble through this part easily. But there are a few configurations we need to look at to ensure all of the virtual machines can speak to each other.

    Note - If you have not already created three (3) virtual machines, go back to Part 2 to review the steps for creating the additional virtual machines. We will need a total of three (3) for our lab. Once you have the required virtual machines, come back to this post to complete the configuration

    *** Important *** – When creating the additional virtual machines, ensure they are all in the same Cloud Service, Virtual Network, and Storage Account. You can look at the configuration of the Virtual Machine we created in Part 2 to find this information


    Want to build a complete lab to play with, and learn, PowerShell? Or a series to help you learn about building such a lab on Azure? Want to see about creating your own little cloud hosted domain? Want to use your MSDN Azure allowance?

    You'll want to read this series...

    Tuesday, July 30, 2013

    "Windows 8 App Management Toolkit for Powershell" (with MS-PL Source)

    CodePlex - Windows 8 App Management Toolkit for Powershell

    Windows 8 App Management Toolkit for Powershell is the must have cmdlet for automating and managing Windows Store apps.

    The toolkit enhances the functionality of the existing Get-AppxPackage method by adding methods to

    • Launch, suspend, and terminate Windows Store apps
    • Check if the Start screen or any Windows Store apps are visible on any monitors
    • Discover the capabilities of applications such as background tasks

    One of note is that the source of all the above mentioned cmdlets is available. So you can see the C#, P/Invokes that makes the magic happen...


    (via Secret Microsoft Communications - In case you get this: We couldn't get your developer license for Windows 8.1 Preview. Our Server is unavailable right now. Please try again later.)

    Saturday, July 27, 2013

    Don't fear the shell... - "Getting Started with PowerShell 3.0" jumpstart series

    Channel 9 - Getting Started with PowerShell 3.0

    This Jump Start is designed to teach the busy IT Professionals about this powerful management tool. Learn how PowerShell works and how to make PowerShell work for you from the experts Jeffrey Snover, the inventor of PowerShell, together with Jason Helmick, Senior Technologist at Concentrated Technology. IT Professionals, Admins, and Help Desk persons learn how to improve your management capabilities, automate redundant tasks and manage your environment in scale




    You all PowerShell, right? I mean it's THE way to commandline your way to system mastery, so I'm sure you are all using it and bending it to you will?

    Well if not, here's a jumpstart just for you, presented by the invertor of PowerShell. Hard to beat that as a subject matter expert. :)

    Tuesday, April 09, 2013

    Microsoft Script Explorer - So long and thanks for all the PowerShell... (The Script Explorer is dead Jim)

    Windows PowerShell Blog - Microsoft Script Explorer: Next Steps

    For those who are familiar with Microsoft Script Explorer for Windows PowerShell, you know that we haven't released additional updates to it since we published the release candidate (RC) in August 2012. Over the past few months, we have been talking with customers and partners and taking a hard look at the adoption rate of the RC in terms of the number of downloads and the feedback we're received to date.

    One of the results of this analysis was that the adoption and usage of the pre-release versions of Script Explorer were not at the level we had hoped. Part of this stems from the fact that customers already have a number of options in the market for discovering and sharing PowerShell scripts, and most appear content to continue using these existing mechanisms. As a result, we've decided not to bring the Script Explorer project to RTM.

    In the meantime, we will start winding down the Script Explorer project. This will be a gradual process to allow time for existing users to move to other tools. We'll start by removing the RC package from the Download Center this week.

    For those who have already downloaded pre-release versions and are actively using Script Explorer in their environments, we will continue to operate the back-end script aggregation service used by Script Explorer for a few more months. We plan to turn off the service on June 14, 2013.


    Kind of sad, but better they kill it than let it linger (I guess). Of course, if there had been more of a push, maybe there would have been more adoption...

    Other suggested places where you can find PowerShell scripts and information (cribbed from the post)

    (via PowerShell Magazine - Heads up: Microsoft Script Explorer reaches the end of the road)


    Related Past Post XRef:
    "Microsoft Script Explorer for Windows PowerShell" Beta Released (Think PowerShell ISE Addon to help you search and browse for more PowerShell scripts)

    Monday, April 08, 2013

    Powering your Zipping with PowerShell and 7-Zip (and SevenZipSharp) (aka '7Zip4Powershell')

    Thomas Freudenberg - 7-Zip for Powershell

    At work we deal with different big databases, and by big I mean between 3.5 and 8 GB. Those databases are zipped with 7-Zip and stored on a server. Depending on the scenario we unzip one of these databases to a local folder and attach it to the SQL Server. To simplify these steps we have a couple of Powershell scripts, among other things invoking the command line version of 7-Zip.

    However, extracting an archive of several gigabytes over the network might take some time, and we’d like to see the progress in the Powershell console. Powershell provides a standard way to report progress by calling Cmdlet.WriteProgress, which then will be displayed by the current host (e.g. command line) appropriately.

    Therefore with some support of a co-worker I’ve written two Cmdlets for extracting and compressing archives. The syntax is simple as this:



    thoemmi / 7Zip4Powershell


    7Zip, PowerShell, SevenZipSharp .Net assembly? All used together? Cool...


    Related Past Post XRef:
    7zSharp to your .Net Archive/Unarchiving Rescue - LGPL .Net Wrapper for 7z
    .Net (C#) Interface for the 7-Zip DLL (7z.DLL)

    Friday, April 05, 2013

    WPF is to PowerShell as the PowerShell ISE is to Extensibility (Think "Extending the PowerShell ISE is as easy as 1, 2, DLL...")

    Precision Computing - Creating Add-ons, Plugins, and Tools for the PowerShell ISE

    We frequently get questions asking if the PowerShell ISE supports a feature that it doesn’t. For example, variable watch windows, function browsers, or “find all matches in the current document”.

    Or as another example, many of you are very familiar with Visual Studio and naturally wish for Visual Studio feature <x>. That <x> is usually different for each person :) The Visual Studio team is many times larger than the PowerShell team, and they’ve had a 15-year head start.

    When preparing for PowerShell V3, we realized that the appetite for new functionality in the ISE would far outstrip our ability to create it, so we designed one of the most (until now) un-heralded features in the PowerShell ISE: the ability to create custom tool windows:


    See the “Find All” pane on the right-hand side? That didn’t come with the ISE.

    Creating a PowerShell ISE Add-In / Plugin is very straight-forward. Jason gives a great overview in his blog:

    The design center of ISE plugins are that they are really just WPF UserControls. In addition, they implement the IAddOnToolHostObject interface.


    After that, the control is all yours.

    You have full access to WPF, XAML, C#, and anything else you can imagine or would expect from a WPF control. For example, here is the simplistic XAML used to create the control in the ‘Find All’ window shown above:


    All-in-all, a very easy development experience.

    Once you’ve compiled a DLL, adding it to the ISE is as easy as:


    I though this post a great example of how easy it can be to extend the PowerShell ISE. I love seeing tools being extensible like this...

    Thursday, February 28, 2013

    How Microsoft and others, empowers you with PowerShell [Think Server Services that PowerShells]

    TechNet Wiki - PowerShell-Enabled Technologies

    Many companies have provided out of the box support for managing their software with Windows PowerShell. This list only covers those companies, not any 3rd-party modules or snap-ins.


    I thought this a nice visual of all the server side tech that's PowerShell enabled/supported/etc. If you're an IT and don't know or user PowerShell, maybe this will help nudge you...

    Wednesday, February 13, 2013

    Wiki-wiki, here's some popular PowerShell add-ons...

    TechNet Wiki - Popular Add-Ons for PowerShell Users


    Just a few of the many add-ons and things you can extended PowerShell with, but good ones none-the-less...

    Friday, January 11, 2013

    The power behind PowerShell, "Windows PowerShell Language Specification Version 3.0"

    Microsoft Downloads - Windows PowerShell Language Specification Version 3.0

    Version: December 2012
    Date published: 1/10/2013

    Language: English

    Windows PowerShell Language Specification Version 3.0.docx, 539 KB

    Windows PowerShell is a command-line shell and scripting language that brings the power of the .NET Framework to command-line users and script writers. The specification in this download documents the Windows PowerShell language for Windows PowerShell 3.0. This specification is made available as part of the Microsoft Open Specifications program. For more information, see

    Here's a snap of the 334 page DocX


    And a snip of the Introduction.

    1. Introduction

    PowerShell is a command-line shell and scripting language, designed especially for system administrators.

    Most shells operate by executing a command or utility in a new process, and presenting the results to the user as text. These shells also have commands that are built into the shell and run in the shell process. Because there are few built-in commands, many utilities have been created to supplement them. PowerShell is very different. Instead of processing text, the shell processes objects. PowerShell also includes a large set of built-in commands with each having a consistent interface and these can work with user-written commands.

    An object is a data entity that has properties (i.e., characteristics) and methods (i.e., actions that can be performed on the object). All objects of the same type have the same base set of properties and methods, but each instance of an object can have different property values.

    A major advantage of using objects is that it is much easier to pipeline commands; that is, to write the output of one command to another command as input. (In a traditional command-line environment, the text output from one command needs to be manipulated to meet the input format of another.)

    PowerShell includes a very rich scripting language that supports constructs for looping, conditions, flow-control, and variable assignment. This language has syntax features and keywords similar to those used in the C# programming language (§C).

    There are four kinds of commands in PowerShell: scripts, functions and methods, cmdlets, and native commands.

    • A file of commands is called a script. [Note: By convention, a script has a filename extension of .ps1. end note] The top-most level of a PowerShell program is a script, which, in turn, can invoke other commands.
    • PowerShell supports modular programming via named procedures. A procedure written in PowerShell is called a function, while an external procedure made available by the execution environment (and typically written in some other language) is called a method.
    • A cmdlet—pronounced "command-let"—is a simple, single-task command-line tool. Although a cmdlet can be used on its own, the full power of cmdlets is realized when they are used in combination to perform complex tasks.
    • A native command is a command that is built in to the host environment.

    Each time the PowerShell runtime environment begins execution, it begins what is called a session. Commands then execute within the context of that session.

    This specification defines the PowerShell language, the built-in cmdlets, and the use of objects via the pipeline.

    Windows PowerShell: Unlike most shells, which accept and return text, Windows PowerShell is built on top of the .NET Framework common language runtime

    Not a doc I think I'll be reading in too much detail, but still something I think great to have (you know, just incase...). Plus I like that this is just available...

    Wednesday, January 02, 2013

    From Ping to Power, the IT Admin's CMD to PowerShell Cheat sheet

    Goatee PFE - Free Download: CMD to PowerShell Guide for AD

    New Years ResolutionSkip the treadmill.  Learn PowerShell.

    Hi folks. It's your friendly, neighborhood PFE again. In order to avoid the long lines to buy a treadmill the first week of January I thought I would save you some time and give you an easier New Years Resolution… Learn PowerShell.

    It's time to part with "blankie".

    For years many of us have relied on trusty command line utilities like PING, IPCONFIG, and REPADMIN. Some of us are still hanging on to those instead of embracing the brave new world of PowerShell.

    In an effort to assist with the transition and to introduce some of the cool new cmdlets in PowerShell v3 I have created a free reference guide showing how the old meets the new. For example, instead of PING try the PowerShell cmdlet Test-Connection, instead of NSLOOKUP use Resolve-DNSName, instead of GPUPDATE use Invoke-GPUpdate.

    The guide attached at the bottom of this blog post contains four packed pages of PowerShell pleasure for your perusing.


    Why would someone want to use PowerShell instead of command line utilities? There are several reasons:


    Free Download

    While studying the new 2012 cmdlets in preparation for conference talks last summer I created a quick cheat sheet for PowerShell equivalence to REPADMIN and DNSCMD. The other day I sat down and expanded this to include a raft of familiar utilities:




    This guide will get you off and running to convert any old batch files you still have lying around or hiding in scheduled tasks.

    Four pages. Really?

    Yes. I know that sounds like a lot to learn


    You can have my PING & IPCONFIG when you pry it from my cold, dead fingers... NOT! It's time to join the PowerShell age and start adjusting your typing muscle memory away from the tools that are decades old to a more modern set of tools. If you're not already a PowerShell user, think of these as your gateway drug... :)


    Monday, December 31, 2012

    PowerSwitchUserTile - Creating a Switch User Windows 8 Tile with PowerShell

    TechNet Script Gallery - Script to create a Windows 8 Switch User Tile for the Start menu (PowerShell)

    This PowerShell Script shows how to create a Windows 8 Switch User tile for the Start menu.


    Properly switching users in Windows 8 without a Start button can be a bit of a chore. Many users may want to switch users in just one click. This script enables users to click a tile to switch user on the Start menu.




    One of the killer features for Windows 8 usage in our house is our being able to have one device that we can easily switch to our own logins (and syncs with our other Win8 devices). But it is a little bit of a pain to switch users, so I wanted to capture this for future reference and use.

    Friday, November 16, 2012, powering PowerShell learning, sharing and community by the community for the community

    Hey, Scripting Guy! Blog - Introducing PowerShell.Org

    "Summary:  Guest blogger Don Jones, PowerShell MVP, talks about

    Microsoft Scripting Guy, Ed Wilson, is here. I was thinking about the PowerShell Summit and contacted PowerShell MVP Don Jones to ask him for a blog post to share information about and what exciting things are happening over there. Take it away, Don.

    Introducing PowerShell.Org

    By the Team

    If you haven’t yet visited, it’s worth your time. The site is the successor to (, and its main purpose is to serve as a Q&A site for all things Windows PowerShell and to help newcomers locate some of the other great resources that are out there. Started by Windows PowerShell MVPs Don Jones and Kirk Munro, the site is now owned by a standalone corporation,, Inc. That corporation is unique in that it’s specifically intended to be community-owned: anyone can buy shares in it, and thereby, gain a vote in the makeup of its Board of Directors (currently Jones and Munro, along with Jason Helmick and fellow MVPs Richard Siddaway and Jeffery Hicks). That makes the first community owned-and-operated online resource for Windows PowerShell!



    Welcome to the PowerShell Community is a community-owned and -operated corporation dedicated to helping IT professionals and developers master Windows PowerShell. Inside, you'll find enthusiasts and experts answering questions in our discussion forums, information on the incredibly popular (and now community-owned) Scripting Games, the latest news about our in-person PowerShell Summit event, and more. Look for regional and local events near you and connect with fellow PowerShell users, browse through our news and blog articles, and check out some of the free PowerShell books written by community members. If it's PowerShell, you'll find it on!

    ..." - About this Community

    This site is designed to be a general-purpose gathering place and portal for Windows PowerShell, providing access to Q&A forums, technical articles and blog posts, and other resources. We’re the spiritual successor to… just with a simpler look, a tighter focus on answers and education, and an easier-to-type domain name!

    The heart of this community is its discussion and Q&A forums, since most people come here looking for answers to specific PowerShell-related problems. Aside from those, we also try to provide pointers to other best-of-breed resources within the broader community. In other words, we’re not going to try and duplicate effort when someone else is already doing a great job someplace else. For example, you’ll find that many of our blog posts here are actually aggregated from elsewhere, bringing together some of the best PowerShell content we could find into one place, while letting those authors continue to do their own thing.

    This site, and the PowerShell Summit event, are owned by, Inc. This corporation is community-owned, meaning ownership shares in the company can be purchased by anyone, up to the limit of the corporation’s issued stock. Shareholder determine the makeup of the company’s Board, and the Board appoints its Officers, who execute the company’s day-to-day operation. Legal documents and other information about the corporation can be found in its dedicated forum, along with information on purchasing shares in the company.

    Our current Board (through January 31st, 2014) consists of MVPs Don Jones, Kirk Munro, Jeffery Hicks, and Richard Siddaway, along with Jason Helmick. Don Jones serves as President and CEO, Kirk Munro is our Vice-President, Jeffery Hicks is our Secretary, and Jason Helmick is our Treasurer.


    Wait, Why Another “PowerShell Community?”

    Well, we don’t really think of this as “another,” exactly. As mentioned above, this site is meant to be the successor to, which has been around since 2006 or so. This is just kind of a re-thinking of that site, with more focus on the forums (which we think are the real value-add), and more of an effort to have community experts and enthusiasts actively making sure people get answers.

    Those of us contributing to this site do so because we’ve noticed an unfortunate tendency for “communities” to spring up, get a flurry of activity, and then slowly fade away – meaning people who run across them post questions, and get no answers. So we’re trying to be very aware of that pattern, and consciously attempting to not let it happen here.

    Also, many of the “PowerShell communities” out there have been corporate-owned or -hosted. There’s nothing wrong with that, except that changing corporate priorities can sometimes leave a once-thriving community left out on its own. That’s not the case, here – this site is “owned” and monitored by members of the PowerShell community, and legally owned by an actual standalone corporation, so that the site can survive the loss of interest even by its current leadership.


    Shiny new PowerShell site.... nuff said?

    Wednesday, November 07, 2012

    Powering Tiles with PowerShell... Creating Shutdown/Restart/Logoff Windows 8 Tiles with PowerShell

    Microsoft Script Center - Create a Shutdown/Restart/Logoff Windows 8 Tile for the Start menu (PowerShell)

    Script to create a Shutdown/Restart/Logoff Windows 8 Tile for the Start menu (PowerShell)


    This PowerShell Script illustrates how to create a Shutdown or Restart or Logoff Windows 8 tile to the Start menu.


    In Windows 8, without a Start button, properly shutting down or rebooting Windows can be a bit of a chore. So many users want to shut down or reboot windows in  just one click. Now, this script enables user just clicking on a tile to shutting down, rebooting or logging off Windows from the Start menu, it really conveniently.





    And since the Surface RT has PowerShell this "should" work there too? I'm going to have to give that a try... :)

    I wonder what else we can with this? hum...

    Sunday, October 28, 2012

    Two WMI Cheat sheets (One for Dev's, one for PowerShell'ers)

    Windows Management Infrastructure Blog - WMI cheat sheet and link to MSDN documentation

    "WMI team created a useful cheat sheet summarizing what's new in WMI. This is a great reference doc for developers. We are making them available through this blog post - as is.

    The real documentation is still on MSDN (and it is being regularly updated). Cheat sheets are just a quick reference to get people started.





    Windows PowerShell Blog - WMI cheat sheet for PS users

    "We got multiple requests to publish the cheat sheet for CIM Cmdlets that was distributed in Tech Ed NA this year. Responding to popular demand, this document is attached as PDF . This is a great resource put together by WMI team for people who want to get started with CIM cmdlets.

    Standard disclaimer :-). Cheat sheet is just for a quick start to get people started - real documentation is here

    Osama Sajid..."



    Why Must I love WMI? Because it's just so damn useful! If you don't WMI, you should. These two cheatsheets (and the links in the posts) will get you started...