June 2012 - Windows PowerShell Team Blog

  1 Summary In March we introduced Windows PowerShell Workflow (PSWF), which explained why we integrated workflows with PowerShell, and what were our major investment areas for our first release. In a recent post , Jeffrey Snover summarizes this decision: “ We integrated the Windows Workflow Foundation engine into PowerShell to make it simple and easy to automate things that take a long time,...

This is the second part of our post on the high level architecture of Windows PowerShell Workflow. Part 1 of this blog post provided an overview of the architecture and its various components. This post will go into more detail on the various subcomponents and provide some insight into the internals of Windows PowerShell Workflow. The component diagram for the PowerShell Workflow Executive is repeated...

Windows PowerShell Web Access is a new feature in Windows Server 2012. It is an IIS application that provides a Windows PowerShell console in a web browser. The IIS application acts as a gateway between the web browser and the machines that you can connect to in your environment. These machines should have Windows PowerShell remoting enabled. The video below illustrates the three simple steps of setup...

Yesterday we published an RC version of the Windows Management Framework 3.0. Windows Management Framework 3.0 RC makes some updated management functionality available to earlier versions of Windows. Windows Management Framework 3.0 RC can be installed on the following Operating Systems: Windows 7 Service Pack 1 (32-bit & 64-bit) Windows Server 2008 R2 Service Pack 1 (64-bit only) – Server Core...

We’ve already discussed the biggest new PowerShell language feature – workflows – in a previous post. In this post, I’m going to describe a number of small changes we’ve made to the language. Most of the changes described here don’t introduce any new syntax, but I think you’ll agree that most of these changes make various aspects of scripting in PowerShell...