Windows PowerShell

From Seo Wiki - Search Engine Optimization and Programming Languages

Jump to: navigation, search
Windows PowerShell
File:Windows PowerShell icon.png
File:Windows PowerShell 1.0.png
Screenshot of a sample PowerShell session
Developer(s) Microsoft Corporation
Initial release November 14, 2006
Stable release 2.0 / July 22, 2009; 144184650 ago
Operating system Windows XP
Windows Server 2003
Windows Vista
Windows Server 2008
Windows 7
Windows Server 2008 R2
Platform x86, x86-64, Itanium
Available in Multilingual
Development status Active
Type Operating system shell
License MS-EULA
Website Windows PowerShell
Paradigm Multi-paradigm: imperative, pipeline, object-oriented, functional, reflective
Appeared in 2006
Designed by Jeffrey Snover, Bruce Payette (et al.)
Developer Microsoft Corporation
Typing discipline strong, safe, implicit, dynamic
Influenced by C#, DCL, ksh, Perl, Ruby/LISP, CL, SQL, COMMAND.COM/ cmd.exe,[1] Tcl[2]
OS Windows

Windows PowerShell is an extensible automation engine from Microsoft, consisting of a command-line shell and associated scripting language.

Windows PowerShell is built on top of, and is integrated with, the Microsoft .NET Framework. Additionally PowerShell enables easy access to COM and WMI to provide an environment in which administrators perform administrative tasks on both local and remote Windows systems.

These administrative tasks are generally performed by execution of cmdlets (pronounced commandlets), which are specialized .NET classes implementing a particular operation. These may be combined by means of scripts, which are compositions of cmdlets along with imperative logic; executables, which are standalone applications; or by instantiating regular .NET classes (or WMI /COM Objects).[3][4] These work by accessing data in different data stores, like the filesystem or registry, which are made available to the PowerShell runtime via Windows PowerShell providers.

Windows PowerShell also provides a hosting mechanism with which the Windows PowerShell runtime can be embedded inside other applications. These applications then leverage Windows PowerShell functionality to implement certain operations, including those exposed via the graphical interface. This capability has been utilized by Microsoft Exchange Server 2007[3][5] 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[6] also expose their management interface via PowerShell cmdlets. With PowerShell, graphical interface-based management applications on Windows are layered on top of Windows PowerShell. In the future all Microsoft applications running on the Windows platform are to be PowerShell aware.

Windows PowerShell includes its own extensive, console-based help, similar to man pages in Unix shells via the Get-Help cmdlet.



Codenamed "Monad", PowerShell was first shown publicly at the Professional Developers Conference in September 2003. Version 1.0 was released in 2006 for Windows XP SP2/SP3, Windows Server 2003 and Windows Vista, and included in Windows Server 2008 as an optional feature.

Windows PowerShell 2.0 was released with Windows 7 and Windows Server 2008 R2. It has also been released for older platforms, i.e. Windows XP SP3, Windows Server 2003 SP2, Windows Vista SP1 and Windows Server 2008.[7]


Every released version of Microsoft DOS and Microsoft Windows for personal computers has featured a command-line interface tool. These are COMMAND.COM (in installations relying on MS-DOS, including Windows 9x) and cmd.exe (in Windows NT-family operating systems). These are regular command line interpreters that include only a handful of basic commands. For other purposes, a separate console application needs to be provided, to be invoked from these shells. They also include a scripting language (batch files), which can be used to automate various tasks. However, they 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, preventing the creation of complex scripts by composing available functionality. In Windows Server 2003, the situation was improved,[8] 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 has its own deficiencies, as well. 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 2003, Microsoft had started to develop a new shell called Monad (aka Microsoft Shell or MSH). 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 published the first Monad public beta release on June 17, 2005, Beta 2 on September 11, 2005, and Beta 3 on January 10, 2006. They announced on April 25, 2006 that Monad was renamed to 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. Release Candidate 2 of PowerShell was released September 26, 2006 and released to web (RTW) on November 14, 2006. PowerShell for Vista was released on January 30, 2007.[10] 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 to Windows 7 and Windows Server 2008 R2. Versions of PowerShell for downlevel OSs (i.e. 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]


The commands Windows PowerShell executes may be in the form of 'cmdlets', which are specialized .NET classes designed expressly to expose a functionality via PowerShell, PowerShell scripts (*.ps1) or regular executables. If a command is an executable file, PowerShell launches it in a separate process; if it is a cmdlet, it is executed in the PowerShell process. PowerShell also 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 also enables the creation of aliases for cmdlets, which are textually translated by PowerShell into invocations of the original commands. Powershell also 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 passed via the argv (or equivalent) variable array to be parsed by the executable.

Another concept used by PowerShell is that of a pipeline. Like Unix pipelines, PowerShell pipelines are used to compose complex commands, allowing the output of one command to be passed as input to another. A pipeline is set up by piping the output of one command (or pipeline) to another command, using the | operator. But, unlike its Unix counterpart, the PowerShell pipeline is an object pipeline; that is, the data passed between cmdlets are fully typed objects, rather than character streams. When data is piped as objects, the elements they encapsulate retain their structure and types across cmdlets, without the need for any serialization or explicit parsing of the stream, as would be the need if only character streams were shared. An object can also encapsulate certain functions that work on the contained data. These also become available to the recipient command for use.[12][13] For the last cmdlet in a pipeline, PowerShell automatically pipes its output object to the Write-Host cmdlet, which creates a formatted text representation of its data, writing it to the screen.[14][15]

Because all PowerShell objects are .NET objects, they share a .ToString() method, which retrieves the text representation of the data in an object. Windows PowerShell uses this method to convert an object to text. In addition, it also allows formatting definitions to be specified, so the text representation of objects may be customized by choosing which data elements to display, and how. However, in order to maintain backwards compatibility, if an external executable is used in a pipeline, it receives a text stream representing the object, and does not integrate with the PowerShell type system.

The PowerShell Extended Type System (ETS) is based on the .NET type system, but with certain extensions. 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 an XML-based language.[16]


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

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.[17] These base classes specify certain methods - BeginProcessing()<code>, <code>ProcessRecord() and EndProcessing() - one of 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.[18] 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.

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[19] 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.[20]

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

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."


PowerShell, like Unix/Linux based shells, implements a pipeline. This pipeline enables the output of one cmdlet to be piped as input to another cmdlet. For example, the output of the Get-Process cmdlet can be piped to the Sort-Object process (e.g. to sort the objects by handle count) and then to the Where-Object to filter any process that has say less than 1 MB of paged memory, then finally to the Select-Object cmdlet to select just the first 10 (i.e. the 10 processes based on handle count).

While Unix/Linux systems have long employed the concept of pipelines, PowerShell differs in what is passed between stages in the pipeline. In Unix the output of one command is piped to the next stage of the pipeline typically as raw text. With PowerShell, the pipeline consists of .NET Objects. Using objects eliminates the need to parse arbitrary text output from one command to extract data since all objects export a consistent interface.[citation needed]


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, 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. While the language is untyped, internally the variables are stored with their types, which can be either primitive types or objects. 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. According to the variable syntax, if the path to a file is enclosed in braces preceded by a dollar sign (as in ${C:\foo.txt}), it refers 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, it will be read from the file. If an object is assigned, it is serialized before storing it.

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

Using the function keyword, PowerShell provides for the creation of functions, which can take parameters. A common problem for people new to PowerShell is that function arguments are separated by spaces, not commas:

  1. <function> <param1> <param2>: Calls the function with two arguments. (These arguments may be bound to parameters declared in the function definition or accessed by position from the $args array.)
  2. <function>(<param1>, <param2>): Calls the function with a single argument, a two element array.

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

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

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.[25] PowerShell scripts can be signed to verify their integrity, and are subject to .NET Code Access Security.

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


Another use of PowerShell is being embedded in a management application, which then 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.[3] 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.

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.[3] 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 an InputPipe, Outputpipe and ErrorOutputPipe objects, to represent the connection with the pipeline. The types are verified and parameters bound using reflection.[3] 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.

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.

PowerShell 2.0

Windows PowerShell ISE, with multiple open Powershell sessions (RunSpaces) in the Windows PowerShell 2.0

Microsoft released PowerShell 2.0 with Windows 7 and Windows 2008 R2. Windows PowerShell 2.0 is installed by default on Windows Server 2008 R2 and Windows 7.[26] For older platforms it is available via the Windows Management Framework. PowerShell V2 includes changes to the scripting language and hosting API, in addition to including more than 240 new cmdlets.[27][28]

A non-exhaustive list of the new features included in PowerShell V2 is:[29][30]

  • 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. A PSJob cannot include interactive cmdlets.
  • Transactions: Enable cmdlet and provider developers to perform transacted 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 allow 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 (formerly known as Graphical Windows PowerShell) that provides integrated debugger, syntax highlighting, tab completion and up to 8 PowerShell unicode-enabled consoles (Runspaces) in a tabbed UI, as well as 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).[31]
  • 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.[32]
  • Block Comments: PowerShell 2.0 supports block comments using <# and #> as delimiters.[33]
  • 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.

Comparison of cmdlets with similar commands

The following table contains a selection of the cmdlets that ship with PowerShell noting the most similar commands in other well known command line interpreters.

Windows PowerShell
Windows PowerShell
cmd.exe / COMMAND.COM
(MS-DOS, Windows, OS/2, etc.)
(Unix, BSD, Linux, Mac OS X etc.)
Get-Location gl, pwd cd pwd Display the current directory/present working directory.
Set-Location sl, cd, chdir cd, chdir cd Change the current directory
Clear-Host cls, clear cls clear Clear the screen[34]
Copy-Item cpi, copy, cp copy cp Copy one or several files / a whole directory tree
Get-Help help, man help man Help on commands
Remove-Item ri, del, erase, rmdir, rd, rm del, erase, rmdir, rd rm, rmdir Delete a file / a directory
Rename-Item rni, ren ren, rename mv Rename a file / a directory
Move-Item mi, move, mv move mv Move a file / a directory to a new location
Get-ChildItem gci, dir, ls dir ls List all files / directories in the (current) directory
Write-Output echo, write echo echo Print strings, variables etc. to standard output
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-Variable sv, set set set Set the value of a variable / create a variable
Get-Content gc, type, cat type cat Get the content of a file
Select-String find, findstr grep Print lines matching a pattern
Get-Process gps, ps tlist,[35] tasklist[36] ps List all currently running processes
Stop-Process spps, kill kill,[35] taskkill[36] kill Stop a running process
Tee-Object tee n/a tee Pipe input to a file or variable, then pass the input along the pipeline


Examples are provided first using the long-form canonical syntax and then using more terse UNIX-like and DOS-like aliases that are set up in the default configuration.

  • Stop all processes that begin with the letter "p":
 PS> get-process p* | stop-process
 PS> ps p* | kill
  • Find the processes that use more than 1000 MB of memory and kill them:
 PS> get-process | where-object { $_.WS -gt 1000MB } | stop-process
 PS> ps | ? { $_.WS -gt 1000MB } | kill
  • Calculate the number of bytes in the files in a directory:
 PS> get-childitem | measure-object -property length -sum
 PS> ls  | measure-object -p length -s
 PS> dir | measure-object -p length -s
  • Determine whether a specific process is no longer running:
 PS> $processToWatch = get-process notepad
 PS> $processToWatch.WaitForExit()
 PS> $p = ps notepad
 PS> $p.WaitForExit()
  • Change the case of a string from lower to upper:
 PS> "hello, world!".ToUpper()
  • Insert the string "ABC" after the first character in the word "string" to have the result "sABCtring":
 PS> "string".Insert(1, "ABC")
  • Download a specific RSS feed and show the titles of the 8 most recent entries:
PS> $rssUrl = ""
PS> $blog = [xml](new-object System.Net.WebClient).DownloadString($rssUrl)
PS> $ | select title -first 8
  • Sets $UserProfile to the value of the UserProfile environment variable
 PS> $UserProfile = $env:UserProfile
  • Cast a .Net Namespace, and call a method exposed by the cast
PS> [System.Windows.Forms.MessageBox]::Show("Hello, World!")
  • Run a command line executable, with arguments.
PS> [Array]$arguments = "-h", "15", ""
PS> tracert $arguments

File extensions

  • PS1 – Windows PowerShell shell script
  • PS1XML – Windows PowerShell format and type definitions
  • PSC1 – Windows PowerShell console file
  • PSD1 – Windows PowerShell data file (for Version 2)
  • PSM1 – Windows PowerShell module file (for Version 2)

Application support

SnapIns and hosts

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
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[37] 08.02.0012 47 No No
Microsoft PowerTools for Open XML[38] 1.0 33 No No
IBM WebSphere MQ[39] 44 No No
Quest Management Shell for Active Directory[40] 1.1 40 No No
Special Operations Software Specops Command[41] 1.0 Yes No Yes
VMware Infrastructure Toolkit[42] 1.5 157 No No
Internet Information Services[43] 7.0 54 Yes No
Ensim Unify Enterprise Edition[44] 1.6 Yes No Yes
Windows 7 Troubleshooting Center[45] 6.1 Yes No Yes
Microsoft Deployment Toolkit 2010 Yes No No


Alternative implementations

The official implementation of PowerShell only runs on Windows-based operating systems and is closed source software. A project called Pash was started to create an open source implementation of PowerShell which runs on multiple operating systems via the Mono framework.[47]

See also


  1. Jsnover @ Wikipedia: Generational list of programming languages
  2. Windows PowerShell : PowerShell and WPF: WTF
  3. 3.0 3.1 3.2 3.3 3.4 "How Windows PowerShell works". MSDN. Retrieved 2007-11-27. 
  4. "Extend Windows PowerShell With Custom Commands". MSDN. Retrieved 2007-11-27. 
  5. "Exchange 2007: Get used to the command line". Tech Republic. Retrieved 2007-11-28. 
  6. "SQL Server Support for PowerShell!". Retrieved 2007-11-28. 
  7. "Windows Management Framework is here!". Retrieved 2009-10-30. 
  8. Dragan, Richard V. (April 23, 2003). "Windows Server 2003 Delivers Improvements All Around". PC Magazine.,2704,1040410,00.asp. 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)." 
  9. Snover, Jeffrey (April 25, 2006). "Windows PowerShell (Monad) Has Arrived". Windows PowerShell team blog. MSDN. Retrieved 2006-04-26. 
  10. Snover, Jeffrey (November 15, 2006). "Windows PowerShell : Windows PowerShell & Windows Vista". Windows PowerShell team blog. MSDN. Retrieved 2007-01-26. 
  11. "Windows PowerShell v2.0 RTM download for downlevel OSs". 
  12. "Rethinking the Pipeline". Retrieved 2007-11-28. 
  13. "Windows PowerShell Object Concepts". Retrieved 2007-11-28. 
  14. "How PowerShell Formatting and Outputting REALLY works". Retrieved 2007-11-28. 
  15. "More - How does PowerShell formatting really work?". Retrieved 2007-11-28. 
  16. "Windows PowerShell Extended Type System". Retrieved 2007-11-28. 
  17. 17.0 17.1 17.2 "Windows PowerShell Cmdlets". Retrieved 2007-11-28. 
  18. "Creating Your First Cmdlet". Retrieved 2007-11-28. 
  19. "Adding parameters That Process Command Line Input". Retrieved 2007-11-28. 
  20. "Adding parameters That Process Pipeline Input". Retrieved 2007-11-28. 
  21. "Windows PowerShell Providers". Retrieved 2007-11-28. 
  22. "Introduction to Windows PowerShell's Variables". Retrieved 2007-11-28. 
  23. 23.0 23.1 "Lightweight Testing with Windows PowerShell". Retrieved 2007-11-28. 
  24. "Trap [Exception] { “In PowerShell” }". Retrieved 2007-11-28. 
  25. "Running Windows PowerShell Scripts". Retrieved 2007-11-28. 
  29. "What's New in CTP of PowerShell 2.0". Retrieved 2007-11-28. 
  30. "Windows PowerShell V2 Community Technology Preview 2 (CTP2) - releaseNotes". Retrieved 2008-05-05. 
  34. Clear-Host is implemented as a predefined PowerShell function.
  35. 35.0 35.1 Available in Windows NT4, Windows 98 Resource Kit, Windows 2000 Support Tools
  36. 36.0 36.1 Available in Windows XP Professional Edition and later
  37. "Microsoft Transporter Suite for Lotus Domino". Retrieved 2008-03-07. 
  38. "PowerTools for Open XML". Retrieved 2008-06-20. 
  39. "MO74: WebSphere MQ - Windows Powershell Library". Retrieved 2007-12-05. 
  40. "PowerShell Commands for Active Directory by Quest Software". Retrieved 2008-07-02. 
  41. "PowerShell Remoting through Group Policy". Retrieved 2007-12-07. 
  42. "VMware Infrastructure Toolkit for Windows". Retrieved 2008-10-10. 
  43. "Windows PowerShell : IIS7 PowerShell Provider Tech Preview 2". Retrieved 2008-07-03. 
  44. "Exchange Manager for 2003 and 2007". Retrieved 2008-04-23. 
  45. "Kudos to the Win7 Diagnostics Team". Retrieved 2009-06-15. 
  47. igor.moochnick - Pash

Further reading

External links

Template:Windows commands

Template:Microsoft APIsar:ويندوز باورشيل cs:Windows PowerShell de:Windows PowerShell es:Windows PowerShell fr:Windows PowerShell ko:윈도 파워셸 id:Windows PowerShell it:Windows PowerShell nl:Windows PowerShell ja:Windows PowerShell pl:Windows PowerShell pt:Windows PowerShell ru:Windows PowerShell fi:Windows PowerShell tr:Windows PowerShell uk:Windows PowerShell zh:Windows PowerShell

Personal tools

Served in 2.372 secs.