Windows PowerShell

From Wikipedia, the free encyclopedia
  (Redirected from MSH (shell))
Jump to: navigation, search
Windows PowerShell
Windows PowerShell icon.png
Windows PowerShell 1.0 PD.png
Screenshot of a PowerShell session
Developer(s) Microsoft
Initial release November 14, 2006; 8 years ago (2006-11-14)
Stable release 4.0 / October 17, 2013; 13 months ago (2013-10-17)
Development status Active
Operating system Windows XP and later
Platform .NET Framework
Type Operating system shell, Configuration Management
License Proprietary software; a component of Microsoft Windows
Website microsoft.com/powershell
PowerShell
Paradigm(s) Multi-paradigm: Imperative, pipeline, object-oriented, functional and reflective
Designed by Jeffrey Snover, Bruce Payette, James Truher (et al.)
Developer Microsoft Corporation
Appeared in 2006
Typing discipline Strong, safe, implicit and dynamic
Influenced by Ksh, Perl, C#, CL, DCL, SQL, Tcl, Tk, Chef, Puppet[1]
Platform .NET Framework
OS Microsoft Windows

Windows PowerShell is a task automation and configuration management framework from Microsoft, consisting of a command-line shell and associated scripting language built on the .NET Framework. PowerShell provides full access to COM and WMI, enabling administrators to perform administrative tasks on both local and remote Windows systems as well as WS-Management and CIM enabling management of remote Linux systems and network devices.

In PowerShell, administrative tasks are generally performed by cmdlets (pronounced command-lets), which are specialized .NET classes implementing a particular operation. Sets of cmdlets may be combined into scripts, executables (which are standalone applications), or by instantiating regular .NET classes (or WMI/COM Objects).[2][3] These work by accessing data in different data stores, like the file system or registry, which are made available to the PowerShell runtime via Windows PowerShell providers.

Windows PowerShell also provides a hosting API with which the Windows PowerShell runtime can be embedded inside other applications. These applications can then use Windows PowerShell functionality to implement certain operations, including those exposed via the graphical interface. This capability has been used by Microsoft Exchange Server 2007[2][4] to expose its management functionality as PowerShell cmdlets and providers and implement the graphical management tools as PowerShell hosts which invoke the necessary cmdlets. Other Microsoft applications including Microsoft SQL Server 2008[5] also expose their management interface via PowerShell cmdlets. With PowerShell, graphical interface-based management applications on Windows are layered on top of Windows PowerShell. A PowerShell scripting interface for Windows products is mandated by Microsoft's Common Engineering Criteria.[6]

Windows PowerShell includes its own extensive, console-based help, similar to man pages in Unix shells, via the Get-Help cmdlet and updatable with fresh content using the Update-Help cmdlet and web based content via the -online switch to Get-Help.

Background[edit]

Every released version of Microsoft DOS and Microsoft Windows for personal computers has included a command-line interface tool (shell). These are COMMAND.COM (in installations relying on MS-DOS, including Windows 9x) and cmd.exe (in Windows NT family operating systems). The shell is a command line interpreter that supports a few basic commands. For other purposes, a separate console application must be invoked from the shell. The shell also includes a scripting language (batch files), which can be used to automate various tasks. However, the shell cannot be used to automate all facets of GUI functionality, in part because command-line equivalents of operations exposed via the graphical interface are limited, and the scripting language is elementary and does not allow the creation of complex scripts. In Windows Server 2003, the situation was improved,[7] but scripting support was still considered unsatisfactory.

Microsoft attempted to address some of these shortcomings by introducing the Windows Script Host in 1998 with Windows 98, and its command-line based host: cscript.exe. It integrates with the Active Script engine and allows scripts to be written in compatible languages, such as JScript and VBScript, leveraging the APIs exposed by applications via COM. However, it too has its own deficiencies: it is not integrated with the shell, its documentation is not very accessible, and it quickly gained a reputation as a system vulnerability vector after several high-profile computer viruses exploited weaknesses in its security provisions. Different versions of Windows provided various special-purpose command line interpreters (such as netsh and WMIC) with their own command sets. None of them were integrated with the command shell; nor were they interoperable.

By 2002 Microsoft had started to develop a new approach to command line management, including a shell called Monad (also known as Microsoft Shell or MSH). The shell and the ideas behind it were published in August 2002 in a white paper entitled Monad Manifesto.[8] Monad was to be a new extensible command shell with a fresh design that would be capable of automating a full range of core administrative tasks. Microsoft first showed off Monad at the Professional Development Conference in Los Angeles in September 2003. A private beta program began a few months later which eventually led to a public beta program.

Microsoft published the first Monad public beta release on June 17, 2005, Beta 2 on September 11, 2005, and Beta 3 on January 10, 2006. Not much later, 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.[9] Release Candidate 1 of PowerShell was released at the same time. A significant aspect of both the name change and the RC was that this was now a component of Windows, and not an add-on product.

Release Candidate 2 of PowerShell version 1 was released on September 26, 2006 with final Release to the web (RTW) on November 14, 2006 and announced at TechEd Barcelona. PowerShell for earlier versions of Windows was released on January 30, 2007.[10]

PowerShell v2.0 development began before PowerShell v1.0 shipped. During the development, Microsoft shipped three community technology preview (CTP). Microsoft made these releases available to the public. The last CTP release of Windows PowerShell v2.0 was made available in December 2008.

PowerShell v2.0 was completed and released to manufacturing in August 2009, as an integral part of Windows 7 and Windows Server 2008 R2. Versions of PowerShell for Windows XP, Windows Server 2003, Windows Vista and Windows Server 2008 were released in October 2009 and are available for download for both 32-bit and 64-bit platforms.[11]

Design[edit]

Windows PowerShell can execute four kinds of named commands:[12]

  • cmdlets, which are .NET programs designed to interact with PowerShell
  • PowerShell scripts (files suffixed by .ps1)
  • PowerShell functions
  • standalone executable programs

If a command is a standalone executable program, PowerShell.exe launches it in a separate process; if it is a cmdlet, it is executed in the PowerShell process. PowerShell provides an interactive command line interface, wherein the commands can be entered and their output displayed. The user interface, based on the Win32 console, offers customizable tab completion but lacks syntax highlighting. PowerShell enables the creation of aliases for cmdlets, which are textually translated by PowerShell into invocations of the original commands. PowerShell supports both named and positional parameters for commands. In executing a cmdlet, the job of binding the argument value to the parameter is done by PowerShell itself, but for external executables, arguments are parsed by the external executable independently of PowerShell interpretation.[citation needed]

The PowerShell Extended Type System (ETS) is based on the .NET type system, but with extended semantics (for example, propertySets and third-party extensibility). For example, it enables the creation of different views of objects by exposing only a subset of the data fields, properties, and methods, as well as specifying custom formatting and sorting behavior. These views are mapped to the original object using XML-based configuration files.[13]

Cmdlets[edit]

Cmdlets are specialized commands in the PowerShell environment that implement specific functions. These are the native commands in the PowerShell stack. Cmdlets follow a Verb-Noun naming pattern, such as Get-ChildItem, helping to make them self-descriptive.[14] Cmdlets output their results as objects, or collections thereof (including arrays), and can optionally receive input in that form, making them suitable for use as recipients in a pipeline. But whereas PowerShell allows arrays and other collections of objects to be written to the pipeline, cmdlets always process objects individually. For collections of objects, PowerShell invokes the cmdlet on each object in the collection, in sequence.[14]

Cmdlets are specialized .NET classes, which the PowerShell runtime instantiates and invokes when they are run. Cmdlets derive either from Cmdlet or from PSCmdlet, the latter being used when the cmdlet needs to interact with the PowerShell runtime.[14] These base classes specify certain methods - BeginProcessing(), ProcessRecord() and EndProcessing() - which the cmdlet's implementation overrides to provide the functionality. Whenever a cmdlet is run, these methods are invoked by PowerShell in sequence, with ProcessRecord() being called if it receives pipeline input.[15] If a collection of objects is piped, the method is invoked for each object in the collection. The class implementing the Cmdlet must have one .NET attribute - CmdletAttribute - which specifies the verb and the noun that make up the name of the cmdlet. Common verbs are provided as an enum.[16][17]

If a cmdlet receives either pipeline input or command-line parameter input, there must be a corresponding property in the class, with a mutator implementation. PowerShell invokes the mutator with the parameter value or pipeline input, which is saved by the mutator implementation in class variables. These values are then referred to by the methods which implement the functionality. Properties that map to command-line parameters are marked by ParameterAttribute[18] and are set before the call to BeginProcessing(). Those which map to pipeline input are also flanked by ParameterAttribute, but with the ValueFromPipeline attribute parameter set.[19]

The implementation of these cmdlet classes can refer to any .NET API and may be in any .NET language. In addition, PowerShell makes certain APIs available, such as WriteObject(), which is used to access PowerShell-specific functionality, such as writing resultant objects to the pipeline. Cmdlets can use .NET data access APIs directly or use the PowerShell infrastructure of PowerShell Providers, which make data stores addressable using unique paths. Data stores are exposed using drive letters, and hierarchies within them, addressed as directories. Windows PowerShell ships with providers for the file system, registry, the certificate store, as well as the namespaces for command aliases, variables, and functions.[20] Windows PowerShell also includes various cmdlets for managing various Windows systems, including the file system, or using Windows Management Instrumentation to control Windows components. Other applications can register cmdlets with PowerShell, thus allowing it to manage them, and, if they enclose any datastore (such as databases), they can add specific providers, as well.[citation needed]

In PowerShell V2, a more portable version of Cmdlets called Modules have been added. The PowerShell V2 release notes state:

"Modules allow script developers and administrators to partition and organize their Windows PowerShell code in self-contained, reusable units. Code from a module executes in its own self-contained context and does not affect the state outside of the module. Modules also enable you to define a restricted runspace environment by using a script."[citation needed]

Pipeline[edit]

PowerShell implements the concept of a pipeline, which enables the output of one cmdlet to be piped as input to another cmdlet. For example, the output of the Get-Process cmdlet could be piped to the Sort-Object cmdlet (e.g., to sort the objects by handle count), and then to the Where-Object to filter any process that has less than 1 MB of paged memory, and then finally to the Select-Object cmdlet to select just the first 10 (i.e., the 10 processes based on handle count).[citation needed]

As with Unix pipelines, PowerShell pipelines are used to compose complex commands, using the | operator to connect stages. However, the PowerShell pipeline differs from the Unix analog in that structured .NET objects, rather than text, are passed from one stage to the next. Using objects eliminates the need to serialize data, or to extract it by explicitly parsing text output.[21] An object can also encapsulate certain functions that work on the contained data, which become available to the recipient command for use.[22][23][dead link] For the last cmdlet in a pipeline, PowerShell automatically pipes its output object to the Out-Default cmdlet, which transforms the objects into a stream of format objects and then renders those to the screen.[24][25]

Because all PowerShell objects are .NET objects, they share a .ToString() method, which retrieves the text representation of the data in an object. In addition, PowerShell allows formatting definitions to be specified, so the text representation of objects can be customized by choosing which data elements to display, and in what manner. However, in order to maintain backwards compatibility, if an external executable is used in a pipeline, it receives a text stream representing the object, instead of directly integrating with the PowerShell type system.[26][27][28]

Scripting[edit]

Windows PowerShell includes a dynamically typed scripting language which can implement complex operations using cmdlets imperatively. The scripting language supports variables, functions, branching (if-then-else), loops (while, do, for, and foreach), structured error/exception handling and closures/lambda expressions,[29] as well as integration with .NET. Variables in PowerShell scripts have names that start with $; they can be assigned any value, including the output of cmdlets. Strings can be enclosed either in single quotes or in double quotes: when using double quotes, variables will be expanded even if they are inside the quotation marks. Enclosing the path to a file in braces preceded by a dollar sign (as in ${C:\foo.txt}) creates a reference to the contents of the file. If it is used as an L-value, anything assigned to it will be written to the file. When used as an R-value, the contents of the file will be read. If an object is assigned, it is serialized before being stored.[citation needed]

Object members can be accessed using . notation, as in C# syntax. PowerShell provides special variables, such as $args, which is an array of all the command line arguments passed to a function from the command line, and $_, which refers to the current object in the pipeline.[30] PowerShell also provides arrays and associative arrays. The PowerShell scripting language also evaluates arithmetic expressions entered on the command line immediately, and it parses common abbreviations, such as GB, MB, and KB.[31][32]

Using the function keyword, PowerShell provides for the creation of functions, the following general form:[33]

function name ($Param1, $Param2)
{
  Instructions
}

The defined function invoke in either of the following forms:[33]

name value1 value2
name -Param1 value1 -Param2 value2

PowerShell supports named parameters, positional parameters, switch parameters and dynamic parameters.[33]

PowerShell allows any .NET methods to be called by providing their namespaces enclosed in brackets ([]), and then using a pair of colons (::) to indicate the static method.[34] For example, [System.Console]::WriteLine("PowerShell"). Objects are created using the New-Object cmdlet. Calling methods of .NET objects is accomplished by using the regular . notation.[34]

PowerShell scripting language accepts strings, both raw and escaped. A string enclosed between single quotation marks is a raw string while a string enclosed between double quotation marks is an escaped string. PowerShell treats straight and curly quotes as equivalent.[35]

For error handling, PowerShell provides a .NET-based exception handling mechanism. In case of errors, objects containing information about the error (Exception object) are thrown, which are caught using the trap keyword. However, the action-or-error is configurable; in case of an error, PowerShell can be configured to silently resume execution, without trapping the exception.[36]

Scripts written using PowerShell can be made to persist across sessions in a .ps1 file. Later, either the entire script or individual functions in the script can be used. Scripts and functions are used analogously with cmdlets, in that they can be used as commands in pipelines, and parameters can be bound to them. Pipeline objects can be passed between functions, scripts, and cmdlets seamlessly. However, script execution is disabled by default and must be enabled explicitly.[37] PowerShell scripts can be signed to verify their integrity, and are subject to Code Access Security.[38]

The PowerShell scripting language supports binary prefix notation similar to the scientific notation supported by many programming languages in the C-family.[citation needed]

Hosting[edit]

Another use of PowerShell is being embedded in a management application, which uses the PowerShell runtime to implement the management functionality. For this, PowerShell provides a managed hosting API. Via the APIs, the application can instantiate a runspace (one instantiation of the PowerShell runtime), which runs in the application's process and is exposed as a Runspace object.[2] The state of the runspace is encased in a SessionState object. When the runspace is created, the Windows PowerShell runtime initializes the instantiation, including initializing the providers and enumerating the cmdlets, and updates the SessionState object accordingly. The Runspace then must be opened for either synchronous processing or asynchronous processing. After that it can be used to execute commands.[citation needed]

To execute a command, a pipeline (represented by a Pipeline object) must be created and associated with the runspace. The pipeline object is then populated with the cmdlets that make up the pipeline. For sequential operations (as in a PowerShell script), a Pipeline object is created for each statement and nested inside another Pipeline object.[2] When a pipeline is created, Windows PowerShell invokes the pipeline processor, which resolves the cmdlets into their respective assemblies (the command processor) and adds a reference to them to the pipeline, and associates them with InputPipe, Outputpipe and ErrorOutputPipe objects, to represent the connection with the pipeline. The types are verified and parameters bound using reflection.[2] Once the pipeline is set up, the host calls the Invoke() method to run the commands, or its asynchronous equivalent - InvokeAsync(). If the pipeline has the Write-Host cmdlet at the end of the pipeline, it writes the result onto the console screen. If not, the results are handed over to the host, which might either apply further processing or display it itself.[citation needed]

The hosting APIs are used by Microsoft Exchange Server 2007 to provide its management GUI. Each operation exposed in the GUI is mapped to a sequence of PowerShell commands (or pipelines). The host creates the pipeline and executes them. In fact, the interactive PowerShell console itself is a PowerShell host, which interprets the scripts entered at command line and creates the necessary Pipeline objects and invokes them.[citation needed]

Versions[edit]

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 preceding versions.

PowerShell 1.0[edit]

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.[39]

PowerShell 2.0[edit]

Windows PowerShell ISE v2.0, an integrated development environment for PowerShell scripts

PowerShell 2.0 is integrated with Windows 7 and Windows Server 2008 R2[40] and is released for Windows XP with Service Pack 3, Windows Server 2003 with Service Pack 2, and Windows Vista with Service Pack 1.[41][42]

PowerShell V2 includes changes to the scripting language and hosting API, in addition to including more than 240 new cmdlets.[43][44]

New features of PowerShell 2.0 include:[45][46][47]

  • 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 of 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).[48]
  • 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.[49]
  • Block Comments: PowerShell 2.0 supports block comments using <# and #> as delimiters.[50]
  • 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[edit]

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.[51][52]

PowerShell 3.0 is part of a larger package, Windows Management Framework 3.0 (WMF3), which also contains the WinRM service to support remoting.[52] 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.[53] Since then, updated versions have been shipped in the Windows 8 and Server 2012 beta and release candidate versions.[citation needed]

New features in PowerShell 3.0 include:[52][54]:33–34

  • 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.
  • New commands: New modules and cmdlets automate printer management previously performed via WMI.[further explanation needed]

PowerShell 4.0[edit]

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.[55]

New features in PowerShell 4.0 include:

  • Desired State Configuration[56][57][58]: 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.

PowerShell 5.0[edit]

An initial public preview of PowerShell 5.0 was made available with Windows Management Framework 5.0 (WMF5) on April 3, 2014.[59] Key features include OneGet PowerShell scriptlets to support Chocolatey's repository-based package management[60] and extending support for switch management to layer 2 network switches.[61]

Comparison of cmdlets with similar commands[edit]

The following table contains a selection of the cmdlets that ship with PowerShell, noting similar commands in other well-known command-line interpreters. Many of these similar commands come out-of-the-box defined as aliases within PowerShell, making it easy for people familiar with other common shells to start working.

PowerShell (Cmdlet) PowerShell (Alias) CMD.EXE / COMMAND.COM Unix shell Description
Get-ChildItem gci, dir, ls dir ls List all files / directories in the (current) directory
Get-Content gc, type, cat type cat Get the content of a file
Get-Command gcm help help, which List available commands
Get-Help help, man help man Help on commands
Clear-Host cls, clear cls clear Clear the screen[Note 1]
Copy-Item cpi, copy, cp copy cp Copy one or several files / a whole directory tree
Move-Item mi, move, mv move mv Move a file / a directory to a new location
Remove-Item ri, del, erase, rmdir, rd, rm del, erase, rmdir, rd rm, rmdir Delete a file / a directory
Rename-Item rni, ren, mv ren, rename mv Rename a file / a directory
Get-Location gl, pwd cd pwd Display the current directory/present working directory.
Pop-Location popd popd popd Change the current directory to the directory most recently pushed onto the stack
Push-Location pushd pushd pushd Push the current directory onto the stack
Set-Location sl, cd, chdir cd, chdir cd Change the current directory
Tee-Object tee N/A tee Pipe input to a file or variable, then pass the input along the pipeline
Write-Output echo, write echo echo Print strings, variables etc. to standard output
Get-Process gps, ps tlist,[Note 2] tasklist[Note 3] ps List all currently running processes
Stop-Process spps, kill kill,[Note 2] taskkill[Note 3] kill[Note 4] Stop a running process
Select-String sls find, findstr grep Print lines matching a pattern
Set-Variable sv, set set env, export, set, setenv Set the value of a variable / create a variable
Invoke-WebRequest iwr, curl, wget N/A wget, cURL Gets content from a web page on the Internet
Notes
  1. ^ Clear-Host is implemented as a predefined PowerShell function.
  2. ^ a b Available in Windows NT4, Windows 98 Resource Kit, Windows 2000 Support Tools
  3. ^ a b Available in Windows XP Professional Edition and later
  4. ^ Also used in UNIX to send a process any signal, the "Terminate" signal is merely the default

File extensions[edit]

  • PS1 – Windows PowerShell shell script[62]
  • PSD1 – Windows PowerShell data file (for Version 2)[63]
  • PSM1 – Windows PowerShell module file (for Version 2)[64]
  • PS1XML – Windows PowerShell format and type definitions[28][65]
  • CLIXML - Windows PowerShell serialized data[66]
  • PSC1 – Windows PowerShell console file[67]
  • PSSC - Windows PowerShell Session Configuration file[68]

Application support[edit]

Snap-ins and hosts[edit]

Application Version Cmdlets Provider Management GUI
Exchange Server 2007 402 Yes Yes
Windows Server 2008 Yes Yes No
Microsoft SQL Server 2008 Yes Yes No
Microsoft SharePoint 2010 Yes Yes No
System Center Configuration Manager 2012 R2 400+ Yes No
System Center Operations Manager 2007 74 Yes No
System Center Virtual Machine Manager 2007 Yes Yes Yes
System Center Data Protection Manager 2007 Yes No No
Windows Compute Cluster Server 2007 Yes Yes No
Microsoft Transporter Suite for Lotus Domino[69] 08.02.0012 47 No No
Microsoft PowerTools for Open XML[70] 1.0 33 No No
IBM WebSphere MQ[71] 6.0.2.2 44 No No
Quest Management Shell for Active Directory[72] 1.1 40 No No
Special Operations Software Specops Command[73] 1.0 Yes No Yes
VMware vSphere PowerCLI[74] 5.1 R2 370 No Yes
Internet Information Services[75] 7.0 54 Yes No
Windows 7 Troubleshooting Center[76] 6.1 Yes No Yes
Microsoft Deployment Toolkit[77] 2010 Yes Yes Yes
NetApp Data ONTAP PowerShell Toolkit[78] 2.1 1158 Yes Yes
JAMS Scheduler - Job Access & Management System[79] 5.0 52 Yes Yes
UIAutomation[80] 0.8 432 No No
Dell Equallogic[81] 3.5 55 No No
LOGINventory[82] 5.8 Yes Yes Yes
SePSX[83] 0.4.1 39 No No

Alternative implementation[edit]

A project named Pash (the name is a pun on the well-known "bash" Unix shell[84]) has been an open source and cross-platform reimplementation of PowerShell via the Mono framework. Pash was created by Igor Moochnick, written in C# and was released under the GNU General Public License. Pash development stalled in 2008, but was restarted in 2012.[84][85]

See also[edit]

References[edit]

  1. ^ Snover, Jeffrey (2008-05-25). "PowerShell and WPF: WTF". Retrieved 2010-10-24. 
  2. ^ a b c d e "How Windows PowerShell works". MSDN. Microsoft. Retrieved 2007-11-27. 
  3. ^ "Extend Windows PowerShell With Custom Commands". MSDN. Microsoft. Retrieved 2007-11-27. 
  4. ^ Lowe, Scott (January 5, 2007). "Exchange 2007: Get used to the command line". TechRepublic. CBS Interactive. Archived from the original on 2012-07-01. Retrieved 2007-11-28. 
  5. ^ "SQL Server Support for PowerShell!". Retrieved 2007-11-28. 
  6. ^ "Common Engineering Criteria Overview". Retrieved 2011-02-12. 
  7. ^ Dragan, Richard V. (April 23, 2003). "Windows Server 2003 Delivers Improvements All Around". PC Magazine. Ziff Davis. Retrieved 2007-11-02. "A standout feature here is that virtually all admin utilities now work from the command line (and most are available through telnet)." 
  8. ^ Snover, Jeffrey (August 2, 2002). "Monad Manifesto – the Origin of Windows PowerShell". Windows PowerShell Blog. Microsoft. Archived from the original on 1 October 2011. Retrieved 2002-08-09. 
  9. ^ Snover, Jeffrey (April 25, 2006). "Windows PowerShell (Monad) Has Arrived". Windows PowerShell Blog. Microsoft. Retrieved 2006-04-26. 
  10. ^ Snover, Jeffrey (November 15, 2006). "Windows PowerShell : Windows PowerShell & Windows Vista". Windows PowerShell Blog. Microsoft. Retrieved 2007-01-26. 
  11. ^ "Windows Management Framework (Windows PowerShell 2.0, WinRM 2.0, and BITS 4.0)". Support. Microsoft. 30 September 2013. Retrieved 24 January 2014. 
  12. ^ about_Command_Precedence http://technet.microsoft.com/en-us/library/hh848304.aspx
  13. ^ "Windows PowerShell Extended Type System". Retrieved 2007-11-28. 
  14. ^ a b c "Windows PowerShell Cmdlets". Retrieved 2007-11-28. 
  15. ^ "Creating Your First Cmdlet". Retrieved 2007-11-28. 
  16. ^ Cmdlet OverView http://msdn.microsoft.com/en-us/library/windows/desktop/ms714395(v=vs.85).aspx
  17. ^ Get-Verb http://technet.microsoft.com/en-us/library/hh852690.aspx
  18. ^ "Adding parameters That Process Command Line Input". Retrieved 2007-11-28. 
  19. ^ "Adding parameters That Process Pipeline Input". Retrieved 2007-11-28. 
  20. ^ "Windows PowerShell Providers". Retrieved 2010-10-14. 
  21. ^ "Windows PowerShell Owner's Manual: Piping and the Pipeline in Windows PowerShell". TechNet. Microsoft. Retrieved 2011-09-27. 
  22. ^ Jones, Don (2008). "Windows PowerShell - Rethinking the Pipeline". Microsoft TechNet. Microsoft. Retrieved 2007-11-28. 
  23. ^ "Windows PowerShell Object Concepts". Retrieved 2007-11-28. 
  24. ^ "How PowerShell Formatting and Outputting REALLY works". Retrieved 2007-11-28. 
  25. ^ "More - How does PowerShell formatting really work?". Retrieved 2007-11-28. 
  26. ^ about_Pipelines http://technet.microsoft.com/en-us/library/hh847902.aspx
  27. ^ about_Objects http://technet.microsoft.com/en-us/library/hh847810.aspx
  28. ^ a b about_Format.ps1xml http://technet.microsoft.com/en-us/library/hh847831.aspx
  29. ^ "Anonymous Functions and Code Blocks in PowerShell". Retrieved 2012-01-21. 
  30. ^ "Introduction to Windows PowerShell's Variables". Retrieved 2007-11-28. 
  31. ^ "Byte Conversion". Windows PowerShell Tip of the Week. Retrieved 15 November 2013. 
  32. ^ Ravikanth (20 May 2013). "Converting to size units (KB, MB,GB,TB, and PB) without using PowerShell multipliers". PowerShell Magazine. 
  33. ^ a b c "about_Functions". Microsoft TechNet. Microsoft. 17 October 2013. Retrieved 15 November 2013. 
  34. ^ a b "Lightweight Testing with Windows PowerShell". Retrieved 2007-11-28. 
  35. ^ Angelopoulos, Alex; Karen, Bemowski (4 December 2007). "PowerShell Got Smart About Smart Quotes". Windows IT Pro. Penton Media. Retrieved 15 November 2013. 
  36. ^ "Trap [Exception] { “In PowerShell” }". Retrieved 2007-11-28. 
  37. ^ "Running Windows PowerShell Scripts". Retrieved 2007-11-28. 
  38. ^ "about_Signing". Microsoft TechNet. Microsoft. 17 October 2013. Retrieved 15 November 2013. 
  39. ^ Chung, Leonard; Snover, Jeffrey; Kumaravel, Arul (14 November 2006). "It's a Wrap! Windows PowerShell 1.0 Released!". Windows PowerShell Blog. Microsoft. 
  40. ^ "PowerShell will be installed by default on Windows Server 08 R2 (WS08R2) and Windows 7 (W7)!". Windows PowerShell Blog. Microsoft. 2008-10-28. Retrieved 2011-09-27. 
  41. ^ "Windows Management Framework is here!". 2009-10-27. Retrieved 2009-10-30. 
  42. ^ "Microsoft Support Knowledge Base: Windows Management Framework (Windows PowerShell 2.0, WinRM 2.0, and BITS 4.0)". Support.microsoft.com. 2011-09-23. Retrieved 2011-09-27. 
  43. ^ "574 Reasons Why We Are So Proud and Optimistic About W7 and WS08R2". Windows PowerShell Blog. Microsoft. 2008-10-29. Retrieved 2011-09-27. 
  44. ^ [1][dead link]
  45. ^ "What's New in CTP of PowerShell 2.0". Retrieved 2007-11-28. 
  46. ^ "Windows PowerShell V2 Community Technology Preview 2 (CTP2) - releaseNotes". Retrieved 2008-05-05. [dead link]
  47. ^ "Differences between PowerShell 1.0 and PowerShell 2.0". Retrieved 2010-06-26. 
  48. ^ "GoGrid Snap-in - Managing Cloud Services with PowerShell". Windows PowerShell Blog. Microsoft. 2008-10-14. Retrieved 2011-09-27. 
  49. ^ "Emit-XML". Windows PowerShell Blog. Microsoft. 2008-10-17. Retrieved 2011-09-27. 
  50. ^ "Block Comments in V2". Windows PowerShell Blog. Microsoft. 2008-06-14. Retrieved 2011-09-27. 
  51. ^ Lee, Thomas (13 August 2012). "PowerShell Version 3 is RTM!". Under The Stairs. Retrieved 2012-08-13. 
  52. ^ a b c "Windows Management Framework 3.0". Download Center. Microsoft. 4 September 2012. Retrieved 2012-11-08. 
  53. ^ "Windows Management Framework 3.0 Community Technology Preview (CTP) #2 Available for Download". Windows PowerShell Blog. Microsoft. 2 December 2011. 
  54. ^ Honeycutt, Jerry (2012). Woolley, Valerie, ed. Introducing Windows 8: An Overview for IT Professionals. Redmond, WA: Microsoft Press. ISBN 978-0-7356-7050-1. 
  55. ^ "Windows Management Framework 4.0 is now available". Microsoft. 24 October 2013. Retrieved 4 November 2013. 
  56. ^ Levy, Shay (25 June 2013). "New Features in Windows PowerShell 4.0". PowerShell Magazine. Retrieved 26 June 2013. 
  57. ^ "Desired State Configuration in Windows Server 2012 R2 PowerShell". Channel 9. Microsoft. 3 June 2013. Retrieved 26 June 2013. 
  58. ^ Hall, Adrian (7 June 2013). "Thoughts from Microsoft TechEd North America". Blogs: Tips & Tricks. Splunk. Retrieved 26 June 2013. 
  59. ^ http://www.microsoft.com/en-us/download/details.aspx?id=42316&WT.mc_id=rss_alldownloads_all
  60. ^ https://github.com/OneGet/oneget/wiki/Q-and-A
  61. ^ http://blogs.technet.com/b/windowsserver/archive/2014/04/03/windows-management-framework-v5-preview.aspx
  62. ^ about_Script http://technet.microsoft.com/en-us/library/hh847841.aspx
  63. ^ Import-LocalizedData http://technet.microsoft.com/en-us/library/hh849919.aspx
  64. ^ about_Modules http://technet.microsoft.com/en-us/library/hh847804.aspx
  65. ^ about_types.ps1xml http://technet.microsoft.com/en-us/library/hh847881.aspx
  66. ^ Export-CliXML http://technet.microsoft.com/en-us/library/hh849916.aspx
  67. ^ Export-Console Cmdlet http://technet.microsoft.com/en-us/library/hh849706.aspx
  68. ^ about_Session_Configuration_Files http://technet.microsoft.com/en-us/library/hh847838.aspx
  69. ^ "Microsoft Transporter Suite for Lotus Domino". Retrieved 2008-03-07. 
  70. ^ "PowerTools for Open XML". Retrieved 2008-06-20. 
  71. ^ "MO74: WebSphere MQ - Windows PowerShell Library". Retrieved 2007-12-05. 
  72. ^ "PowerShell Commands for Active Directory by Quest Software". Retrieved 2008-07-02. 
  73. ^ "PowerShell Remoting through Group Policy". Retrieved 2007-12-07. 
  74. ^ "VMware vSphere PowerCLI". Retrieved 2013-03-15. 
  75. ^ "Windows PowerShell : IIS7 PowerShell Provider Tech Preview 2". Retrieved 2008-07-03. 
  76. ^ "Kudos to the Win7 Diagnostics Team". Retrieved 2009-06-15. 
  77. ^ Michael, Niehaus (10 Jul 2009). "MDT 2010 New Feature #16: PowerShell support". Retrieved 2014-10-27. 
  78. ^ "Kudos to NetApp for Data ONTAP PowerShell ToolKit". Retrieved 2010-06-15. 
  79. ^ "Heterogeneous Job Scheduling With PowerShell". Retrieved 2010-09-15. 
  80. ^ "UIAutomation PowerShell Extensions". Retrieved 2012-02-16. 
  81. ^ "EqualLogic HIT-ME with PowerShell". Retrieved 2012-03-09. 
  82. ^ "LOGINventory". 
  83. ^ "Selenium PowerShell eXtensions". Retrieved 2012-08-20. 
  84. ^ a b "Pash". SourceForge. Dice Holdings, Inc. Retrieved 2011-09-27. 
  85. ^ "Pash Project". Retrieved 2013-04-10. 

Further reading[edit]

External links[edit]