[Post-2] S/W and H/W Requirement for for Powershell

Whatever Hardware required for Installing either Server Operating system (Windows Server 2008, 2008 R2, 2012, 2012 R2 or 2016) or Client Operating System Like Windows 7, 8 and 10 that’s the only hardware dependency.

The Powershell is pre-installed on all the Server Operating system starting from Windows Server 2008, client OS Windows 7 and above. However there are stand alone downloadable are available which could be manually installed on lower versions of Operating systems (Not recommended as the support for Windows XP, Vista and Server 2003 has been stopped by Microsoft) .

The default versions of Powershell pre-Installed on respective Operating systems is as below.

PowerShell Version
Release Date
Default Windows Versions
Available Windows Versions
PowerShell 1.0
November 2006
Windows Server 2008 (*)
Windows XP SP2
Windows XP SP3
Windows Server 2003 SP1
Windows Server 2003 SP2
Windows Server 2003 R2
Windows Vista
Windows Vista SP2
PowerShell 2.0
October 2009
Windows 7
Windows Server 2008 R2 (**)
Windows XP SP3
Windows Server 2003 SP2
Windows Vista SP1
Windows Vista SP2
Windows Server 2008 SP1
Windows Server 2008 SP2
PowerShell 3.0
September 2012
Windows 8
Windows Server 2012
Windows 7 SP1
Windows Server 2008 SP2
Windows Server 2008 R2 SP1
PowerShell 4.0
October 2013
Windows 8.1
Windows Server 2012 R2
Windows 7 SP1
Windows Server 2008 R2 SP1
Windows Server 2012
PowerShell 5.0
February 2016
Windows 10
Windows 8.1
Windows Server 2012 R2
* Has to be installed through Server Manager
** Also integrated in all later Windows versions

What is Difference between various versions of Powershell?

Each Version of Powershell is backward compatible with its earlier version. Hence Cmdlets, providers, Modules, Snap-ins, Scripts, Functions and profiles that were designed in previous versions generally works with newer versions.

Windows PowerShell 3.0 includes the following new features.

  • Disconnected Sessions
  • Windows PowerShell Workflow
  • Windows PowerShell Web Access
  • Scheduled Jobs
  • Module Auto-Loading and Cmdlet Discovery Improvements
  • Get-ChildItem Attributes and Recursive Searches
  • Map Network Drives — Extend Types Without Types.ps1xml Files
  • Simplified Syntax for Where-Object and ForEach-Object
  • Updatable Help — Enhanced Online Help
  • Session Configuration Files
  • Windows PowerShell Remoting on Public Networks
  • Certificate Provider Support for Web Hosting
  • Show-Command
  •  Web Cmdlets
How to find more details about Powershell Version 3? Simply type "help about_Windows_PowerShell_3.0" on Powershell Console

Windows PowerShell 4.0 includes the following new features.

  • Windows PowerShell Desired State Configuration (DSC)
  • Save-Help now lets you save help for modules that are installed on remote computers.
  • Enhanced PowerShell debugger for Powershell Workflows
  • A RunNow parameter for Register-ScheduledJob and Set-ScheduledJob
  • Change is Default Execution Policy on 2K12 R2 (i.e. Remote Signed)
  • Method invocation by using dynamic method names is supported
  • Collection filtering by using a method syntax is now supported
  • Where() operator behavior has changed.
  • and Many More
How to find more details about Powershell Version 4? Simply type "help about_Windows_PowerShell_4.0" on Powershell Console

Windows PowerShell 5.0 includes the following new features.

  • Additional features in Desired State Configurations
  • A new module Microsoft.Powershell.Archieve
  • New Module OneGet and  PowershellGet
  • New-Item, Remove-Item, and Get-ChildItem have been enhanced to support
    creating and managing symbolic links.
  • A new detailed script tracing feature lets you enable detailed tracking and
    analysis of Windows PowerShell scripting use on a system(i.e. ETW: Event Tacing for Windows)
  • New Cryptographic Message Syntax cmdlets support encryption and decryption of content by using the IETF standard format for cryptographically protecting messages as documented by RFC5652
  • The FullyQualifiedName parameter has been added to Import-Module and
    Remove-Module cmdlets, to support storing multiple versions of a single module.
  • New Get-ItemPropertyValue cmdlet lets you get the value of a property without
    using dot notation.
  • You can now perform module version validation by running the Test-ModuleManifest cmdlet.
  • Implementation of support for multiple versions of a single Windows PowerShell module in the same folder in $PSModulePath.
How to find more details about Powershell Version 5? Simply type "help about_Windows_PowerShell_5.0" on Powershell Console
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s