Monthly Archives: April 2013

Installing Windows PowerShell 3.0 – Part 1

Windows® 8 and Windows Server® 2012 include Windows PowerShell 3.0 and all of its prerequisites. The system also includes the Windows PowerShell 2.0 engine for backward compatibility with host programs that cannot use Windows PowerShell 3.0.

Windows PowerShell 3.0 contains:

  • Workflows
    Workflows that run long-running activities (in sequence or in parallel) to perform complex, larger management tasks, such as multi-machine application provisioning.
  • Robust Sessions
    Robust sessions that automatically recovers from network failures and interruptions and allows you to disconnect from the session, shut down the computer, and reconnect from a different computer without interrupting the task.
  • Scheduled Jobs
    Scheduled jobs that run regularly or in response to an event.
  • Delegated Administration
    Commands that can be executed with a delegated set of credentials so users with limited permissions can run critical jobs
  • Simplified Language Syntax
    Simplified language syntax that make commands and scripts look a lot less like code and a lot more like natural language.
  • Cmdlet Discovery
    Improved cmdlet discovery and automatic module loading that make it easier to find and run any of the cmdlets installed on your computer.
  • Show-Command
    Show-Command, a cmdlet and ISE Add-On that helps users find the right cmdlet, view its parameters in a dialog box, and run it.

PowerShell 3.0 is actually just one piece of the Windows Management Framework 3.0 that contains Windows Management Instrumentation (WMI), Windows Remote Management (WinRM), Management OData IIS Extension, and the Server Manager CIM Provider. This link for Windows Management Framework 3.0 has been published 2012-12-03:

It includes updated management functionality for Windows 7 Service Pack 1, Windows Server 2008 R2 SP1, and Windows Server 2008 Service Pack 2 (Windows Vista, Windows XP, and Windows Server 2003 are not supported).

Note: You must uninstall any of the pre-release packages of Windows Management Framework 3.0 prior to installing the final release.

Installing Windows PowerShell on Windows 7 and Windows Server 2008 R2

Or, install Microsoft .NET Framework 4.5 (dotNetFx45_Full_setup.exe) from the Microsoft Download Center at

Once you have finished with installation, use PowerShell console to test it.


For installation on Windows Server 2008 and on Server Core please go to this link: .

Please note that the installers for version 2 and version 3 will both overwrite version 1 if it’s already installed. Version 1 can’t exist side by side with newer versions.  When you open PowerShell console and type $PSHome, you will see that the value is still the same:

Both versions (2.0 and 3.0) are installed in the same directory named “v1.0”. They can exist and run side by side, and what is important, you can start a PowerShell 2.0 session on a machine running PowerShell 3.0.


Notice the “version switch” in the picture above: all we need to do is start a new instance and specify the version. We can do this right from the current PowerShell prompt.

Just type the following: PowerShell -ver 3.0

In the next blog I will use PowerShell scripts to download installation packages, query the computers in AD to establish which computers need an updated version of Microsoft Framework and finally, install PowerShell version 3.0 on remote computers using PowerShell one-to-many remoting technique.

Please note: Although the author has made every reasonable attempt to achieve complete accuracy of the content, he assumes no responsibility for errors or omissions. Also, you should use this information as you see fit, and at your own risk.