Initially using the code name “Monad”, PowerShell was first shown publicly at the Professional Developers Conference in September 2003. All major releases are still supported, and each major release has featured backwards compatibility with preceding versions.
PowerShell 1.0 was released in 2006 for Windows XP SP2, Windows Server 2003 and Windows Vista. It is an optional component of Windows Server 2008
Here we introduced Windows PowerShell ISE v2.0 , an integrated development environment for PowerShell scripts
PowerShell 2.0 is integrated with Windows 7 and Windows Server 2008 R2and is released for Windows XP with Service Pack 3, Windows Server 2003 with Service Pack 2, and Windows Vista with Service Pack 1.
PowerShell V2 includes changes to the scripting language and hosting API, in addition to including more than 240 new cmdlets.
New features of PowerShell 2.0 include:
PowerShell Remoting: Using WS-Management, PowerShell 2.0 allows scripts and cmdlets to be invoked on a remote machine or a large set of remote machines.
Background Jobs: Also called a PSJob, it allows a command sequence (script) or pipeline to be invoked asynchronously. Jobs can be run on the local machine or on multiple remote machines. An interactive cmdlet in a PSJob blocks the execution of the job until user input is provided.
Transactions: Enable cmdlet and developers can perform transactional operations. PowerShell 2.0 includes transaction cmdlets for starting, committing, and rolling back a PSTransaction as well as features to manage and direct the transaction to the participating cmdlet and provider operations. The PowerShell Registry provider supports transactions.
ScriptCmdlets: These are cmdlets written using the PowerShell scripting language. NOTE: The preferred name for script cmdlets is now Advanced Functions.
SteppablePipelines: This allows the user to control when the BeginProcessing(), ProcessRecord() and EndProcessing() functions of a cmdlet are called.
Modules: This allows script developers and administrators to organize and partition PowerShell scripts in self-contained, reusable units. Code from a module executes in its own self-contained context and does not affect the state outside the module. Modules can define a restricted runspace environment by using a script. They have a persistent state as well as public and private members.
Data Language: A domain-specific subset of the PowerShell scripting language that allows data definitions to be decoupled from the scripts and allows localized string resources to be imported into the script at runtime (Script Internationalization).
Script Debugging: It allows breakpoints to be set in a PowerShell script or function. Breakpoints can be set on lines, line & columns, commands and read or write access of variables. It includes a set of cmdlets to control the breakpoints via script.
Eventing: This feature allows listening, forwarding, and acting on management and system events. Eventing allows PowerShell hosts to be notified about state changes to their managed entities. It also enables PowerShell scripts to subscribe to ObjectEvents, PSEvents, and WmiEvents and process them synchronously and asynchronously.
Windows PowerShell Integrated Scripting Environment (ISE): PowerShell 2.0 includes a GUI-based PowerShell host that provides integrated debugger, syntax highlighting, tab completion and up to 8 PowerShell Unicode-enabled consoles (Runspaces) in a tabbed UI, as well as the ability to run only the selected parts in a script.
Network File Transfer: Native support for prioritized, throttled, and asynchronous transfer of files between machines using the Background Intelligent Transfer Service (BITS).
New Cmdlets: Including Out-GridView, which displays tabular data in the WPF GridView object.
New Operators: -Split, -Join, and Splatting (@) operators.
Exception Handling with Try-Catch-Finally: Unlike other .NET languages, this allows multiple exception types for a single catch block.
Nestable Here-Strings: PowerShell Here-Strings have been improved and can now nest.
Block Comments: PowerShell 2.0 supports block comments using <# and #> as delimiters.
New APIs: The new APIs range from handing more control over the PowerShell parser and runtime to the host, to creating and managing collection of Runspaces (RunspacePools) as well as the ability to create Restricted Runspaces which only allow a configured subset of PowerShell to be invoked. The new APIs also support participation in a Windows PowerShell managed transaction.
PowerShell 3.0 is integrated with Windows 8 and with Windows Server 2012. Microsoft has also made PowerShell 3.0 available for Windows 7 with Service Pack 1, for Windows Server 2008 with Service Pack 1, and for Windows Server 2008 R2 with Service Pack 1.
PowerShell 3.0 is part of a larger package, Windows Management Framework 3.0 (WMF3), which also contains the WinRM service to support remoting. Microsoft made several Community Technology Preview releases of WMF3. An early community technology preview 2 (CTP 2) version of Windows Management Framework 3.0 was released on 2 December 2011. Since then, updated versions have been shipped in the Windows 8 and Server 2012 beta and release candidate versions.
New features in PowerShell 3.0 include:
Scheduled jobs: Jobs can be scheduled to run on a preset time and date.
Session connectivity: Sessions can be disconnected and reconnected. Remote sessions have become more tolerant of temporary network failures.
Improved code writing: Code completion (IntelliSense) and snippets are added. PowerShell ISE allows users to use dialog boxes to fill in parameters for PowerShell cmdlets.
Delegation support: Administrative tasks can be delegated to users who do not have permissions for that type of task, without granting them perpetual additional permissions.
Help update: Help documentations can be updated via Update-Help command.
Automatic module detection: Modules are loaded implicitly whenever a command from that module is invoked. Code completion works for unloaded modules as well.
New commands: Dozens of new modules were added, including functionality to manage disks, volumes, firewalls, network connections and printer management, previously performed via WMI.
PowerShell 4.0 is integrated with Windows 8.1 and with Windows Server 2012 R2. Microsoft has also made PowerShell 4.0 available for Windows 7 SP1, Windows Server 2008 R2 SP1 and Windows Server 2012.
New features in PowerShell 4.0 include:
Desired State Configuration: Declarative language extensions and tools that enable the deployment and management of configuration data for systems using the DMTF management standards and WS-Management Protocol.
New Default Execution Policy: On Windows Servers, the default execution Policy is now RemoteSigned
Save-Help: Help can now be saved for modules that are installed on remote computers.
Enhanced debugging: The debugger now supports debugging workflows, remote script execution and preserving debugging sessions across PowerShell session reconnections.
PipelineVariable switch: A new ubiquitous parameter to expose the current pipeline object as a variable for programming purposes.
Network diagnostics to manage physical and Hyper-V’s virtualized network switches.
Where and ForEach method syntax provides an alternate method of filtering and iterating over objects.
An initial public preview of PowerShell 5.0 was made available with Windows Management Framework 5.0 (WMF5) on April 3, 2014. Key features include OneGet PowerShell cmdlets to support Chocolatey’s repository-based package management and extending support for switch management to layer 2 network switches.
On November 18, 2014, Microsoft released the November 2014 Preview of the Windows Management Framework Core 5.0 package. Improvements were made to Desired State Configuration (DSC), OneGet, PowerShellGet, PowerShell class definitions, and debugging for PowerShell background jobs and PowerShell runspaces in remote processes.
New features in PowerShell 5.0 include:
PowerShell class definitions (properties, methods)
PowerShell .NET Enumerations
Debugging for PowerShell Runspaces in remote processes
Debugging for PowerShell Background Jobs
Desired State Configuration (DSC) Local Configuration Manager (LCM) version 2.0
DSC partial configurations
DSC Local Configuration Manager meta-configurations
Authoring of DSC resources using PowerShell classes
Some Contains taken from wikipedia
I have write TCP/IP Socket programming in powershell.you will find sample of script in below link.https://www.facebook.com/groups/448517898521579/798467030193329/
If you like please share or like 😀
Every released version of Microsoft Dos and microsoft windows (for personal computer) come with command line interface tools(Shell).shell is the command line interpreter which support only few commands.For other purpose we have to invoke another console application from shell . In shell we have scripting language called (batch File)which also have limitation to automate the things as we are unable to access all the GUI Functionalities of windows through batch file.
To overcome above defects Microsoft introduces windows script host that released with windows 98 ,its command line based is cscript.exe and it interacting with Active search engines that allow to written the script into compatible language like JScript,VBScript but still its was not interacted with shell.
To overcome this Microsoft worked with new project with help to introduce new command line management with shell .this approached was newly designed and suggested by MR Monad Manifesto and first Monad was released by Microsoft. Monad public beta release on June 17, 2005.
on April 25, 2006 Microsoft formally announced that Monad had been renamed Windows PowerShell, positioning it as a significant part of their management technology offerings.
What actually Monad Manifesto purpose check here original paper
Commands which are used in Command Prompt are cmd and command which use in PowerShell is cmdlet.
Both are present in windows environmentabove windows 7 and so on .In pervious environment we have to install PowerShell but windows 7 onwards it already coming with OS.
A command which is present in command prompt gives the result in text base while cmdlet which is present in PowerShell gives result in object basic.
PowerShell cmdlet is more PowerShell scripting language then command prompt commands
PowerShell is actually very different from the Command Prompt. It uses different commands, known as cmdlets in PowerShell. Many system administration tasks — from managing the registry to WMI (Windows Management Instrumentation) — are exposed via PowerShell cmdlets, while they aren’t accessible from the Command Prompt.
In simple words we can say command Prompt is legacy environment in windows which contains old dos command and not able to access other components and features of windows, making script is very difficult but PowerShell is very PowerShell full scripting language which can able to access the features and components of windows.
Best things with PowerShell is that it support cmd commands why ?Because PowerShell have contains “aliases” that point these old commands at the appropriate new cmdlets, running the new cmdlets when you type the old commands.
This script is useful to add company information on computer and server .so that customer get support information very quickly.
Example Below : –
Download link :