View the Windows PowerShell help (including cmdlet help and the About topics) in a fully-searchable, graphical format (a standard Windows .chm file). Also included in the help file is the VBScript to Windows PowerShell Conversion Guide and a collection of PowerShell Tips of the Week.
Download the Powershell help file for: Powershell 1.0 | Powershell 2.0
1. PowerShell Remoting
Windows PowerShell 2.0 provides support for executing Cmdlets and Scripts remotely. PowerShell Remoting allows managing a collection of remote machines from a single client. Managing remote computers using PowerShell 2.0, requires that PowerShell 2.0 be installed on all the computers taking part in the operation; that is the client computer and the computer(s) being managed.
For more information:
· get-help About_Remoting
· get-help Invoke-Expression
Enable Remoting: PowerShell Remoting feature relies on Windows Remote Management (WS-Man) technology. In order for remoting to work, make sure that the WS-Man Winrm service is installed and started. To verify that Winrm service is running, do the following: PS> get-service winrmSetup places a PowerShell script (Configure-Wsman.ps1) in $pshome folder that configures WS-Man settings. To configure WS-Man for PowerShell remoting feature, please run the configure-WSMan.ps1 script from PowerShell folder (run elevated for Windows Server 2008 or Windows Vista SP1). This script does not start or stop WinRM service. & $pshome\Configure-Wsman.ps1
Known issue:
· To use Remoting Cmdlets and features, PowerShell must be started as administrator/elevated.
· PowerShell 2.0 Remoting features will not work correctly on Windows Vista RTM. Please install Windows Vista Service Pack 1 (SP1) Beta to enable PowerShell Remoting features.
2. Background Jobs
Continue At: blogs.msdn.com
The Windows PowerShell Team is pleased to release the first Community Technology Preview (CTP) of Windows PowerShell 2.0!
This release provides a “sneak peak” into the future, including key features that empower Windows administrators to: Run commands on a remote computer, or better, against N other computers. Use the new PSJob cmdlets to start remote jobs and retrieve the results, either individually or in-aggregate! Write real cmdlets in PowerShell script itself! Internationalize your scripts and their output, not to mention debugging those same scripts!
This CTP release helps developers to more easily layer their runtime or GUI on top of PowerShell, leveraging its cmdlets and remoting infrastructure. It includes APIs to create and use a pool of Runspaces (engines) to run cmdlets. This release also presents very early looks at Restricted Runspaces (the ability to declare a script, cmdlet or variable public or private) and the Graphical PowerShell (a script editor and a Unicode-enabled console). These are just a few of the new features I think are interesting in Windows PowerShell 2.0 CTP. Additionally this CTP includes some simple updates… like new parameters to select-string (Context, AllMatches, NotMatch and Encoding) and new operators like –split and -join!
Last but certainly not least, V2 builds upon Windows PowerShell 1.0 by providing backward compatibility – your 1.0 cmdlets and scripts will run on this CTP (with the exceptions noted in the Release Notes - mostly new keywords/cmdlets). If a working 1.0 script doesn’t run on V2 and is not in the known list of exceptions, please tell us about it!
