Microsoft's new scripting shell, formerly known as Monad or MSH
Operating System:
Contrary to most scripting languages, PowerShell 2.0 requires Windows XP SP3, Windows Server 2003 SP2, Windows Vista SP1, Windows Server 2008 SP2, Windows 7 or later.
It is installed by default on Windows 7 and Server 2008 R2.
However, it won't run on Windows Server 2008 Core, as the Windows Server 2008 Core configuration doesn't support any .NET Framework version.
For any older Windows versions, the Windows Management Framework is required.
You may also need to download and install Microsoft .NET Framework Version 2.0 if you didn't do so before.
Interpreter:
The interpreter is the "engine" that executes scripts.
It is installed by default on Windows 7 and Server 2008 R2.
For older Windows versions, download and install Windows Management Framework.
You may need to uninstall older versions of PowerShell first.
Security:
If you want to create and run your own PowerShell scripts, you need to digitally sign your scripts.
To create your own so called "self-signed" certificate you'll need makecert.exe that comes with the .NET Framework 2.0 SDK.
In PowerShell Plus creating a "self-signed" certificate takes only a couple of mouse clicks. Do read the PowerShell do
Most up-to-date, right now, are Microsoft's PowerShell pages on MSDN and TechNet.
Much of the help available on the web applies to PowerShell 1.0, but it is still valid.
Read the Windows PowerShell Owner's Manual.
"Powershell's help system is excellent! But the console window is not the best reading pane for looking through help documentation."
So download the Scripting Guys' Windows PowerShell Graphical Help File in searchable .CHM format, and Microsoft's PowerShell Quick Reference in Word format.
Other help on the web: